1 2 3 Previous Next 30 Replies Latest reply on Aug 19, 2012 8:39 AM by aslak Go to original post
      • 15. Re: Call for translators
        dan.j.allen

        Yes hantsy, translations received! Thank you very much for your contribution. I'm thrilled that you've introduced Ike to Chinese!

         

        I have one question. You've translated "Getting Started" and "Getting Started Faster with Forge". Would you be willing to translate "Getting Started: Rinse and Repeat". That third tutorial completes the "First Steps" section*.

         

        Thanks again!

         

        *ignore the shrinkwrap guide since it's not complete

        • 16. Re: Call for translators
          dan.j.allen

          Takayuki, thank you for contributing two Japanese translations, and introducing Ike to Japan!

           

          I noticed that you translated "Getting Started: Rinse and Repeat" and "Get Started Faster with Forge". Would you be willing to translate "Getting Started", which is the very first tutorial in the set?

           

          Thanks again!

          • 17. Re: Call for translators
            dan.j.allen

            Takayuki, could you translate the titles of these two guides?

             

            • Getting Started: Rinse and Repeat == ?
            • Get Started Faster with Forge == ?

             

            Thanks!

            • 18. Re: Call for translators
              hantsy

              I will continue it in my spare time, and commit the work as soon as possible.

               

              BTW: I found the file language symbol was renamed to "zh" from "zh_cn" in the file name, is it  possible to use "zh_cn" to differentiate "zh_cn"  from "zh_tw"(which is stand for the Tranditional Chinese) ?

              • 19. Re: Call for translators
                dan.j.allen

                Ah, I meant to post about that change. I am planning to support the zh_cn code. The original language support that Aslak added has a hard-coded reference to the two character syntax. I switched the file suffix to zh temporarily so the translation would generate correctly. I've added a task to fix the hard-coded reference, then I'll switch it back to zh_cn.

                 

                Thanks again for contributing the translations. We really appreciate the time you've spent on them.

                • 20. Re: Call for translators
                  dan.j.allen

                  You motivated me to fix it Done.

                  • 21. Re: Call for translators
                    bmajsak

                    Hey guys,

                     

                    I'm half way through PL translation of getting started and I came across quite a weird problem. Awestruct is not rendering the page correctly. It simply truncates everything after first non-ASCII char (version on openshift have the same problem).

                    My env: Ubuntu 11.10 x64, JRuby 1.6.6 ((ruby-1.8.7-p357) (2012-01-30 5673572) (OpenJDK 64-Bit Server VM 1.6.0_23) [linux-amd64-java]), Awestruct 0.2.12

                     

                    I switched to JRuby cause I couldn't make Awestruct running on Ruby

                     

                    Any ideas?

                     

                    Cheers!

                    • 22. Re: Call for translators
                      dan.j.allen

                      Great to hear about your progress! You guys are really crankin' out the translations

                       

                      At the moment, you have to use awestruct with native ruby to process translated files (any file that contains a diacritic character). The RedCloth Java scanner (used by JRuby) doesn't handle them properly.

                       

                      Here's my env:

                       

                      My env: Ubuntu 11.10 x64, ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux], Awestruct 0.2.12

                       

                      Hopefully you can get Awestruct working with native Ruby. Hit me up on e-mail, we'll iron it out and update the README accordingly.

                      • 23. Re: Call for translators
                        iapazmino

                        Hi,

                        The Spanish translation is ready here.

                        Sorry for the delay.

                        • 24. Re: Call for translators
                          dan.j.allen

                          Fantastic news Ivan. If you can send a pull request, that will make it easier for us to ensure you get credit for the commit. If you are having trouble with the pull request, drop into #jbosstesting on Freenode IRC and we can help you out.

                           

                          Gracias!

                          • 25. Re: Call for translators
                            gvespucci

                            Hi Dan

                            Since I'll start Italian translation I would ask you if there is a WYSIWYG editor for Textile I can use.

                            Thank you

                            • 26. Re: Call for translators
                              gvespucci

                              Forgive me, but what is the

                              reference_rev: 52f8fbd2ff5f00fbbd70729a40f1d6ab124e600e

                              in the Getting Started I have to use in the it version?

                              • 27. Re: Call for translators
                                edewit

                                Hi all,

                                 

                                I'll do the dutch version... this easter I don't have a whole lot planned so I'll get right on it

                                 

                                Erik Jan

                                • 28. Re: Call for translators
                                  dan.j.allen

                                  I don't know of a WYSIWYG editor for Textile (though there's a chance that one exists). We actually prefer it that way because it allows us to have pixel perfect accuracy of the lines, spacings and marks.

                                   

                                  Just do your best to preserve the marks, such as "h3. " at the beginning of a line or "%" around the callout boxes as you can and everything will layout nicely The best way to preview your work is to run awestruct locally. Either way, I'll make sure to correct any glitches when I review it....so I've got you covered.

                                   

                                  You can ignore the reference_rev property. That's something our script uses to keep track of whether a translation is in sync. It gets filled in automatically, so you can just ignore it.

                                   

                                  Let us know if you run into any problems and need help. Good luck!

                                  • 29. Re: Call for translators
                                    dan.j.allen

                                    Jan, awesome! That will push us past 10 translations! Have a good Easter!