On Fri, Apr 22, 2016 at 05:48:37PM +1000, Lex Trotman wrote: > From my (limited) perspective, the most important thing is to support > i18n of generated text, since it is a blocker for making documents in > other languages if humans translate content and the generated text > still comes out in English. That should be the first target of any > resources that make themselves available. > > Once that block is removed everything else is just an improvement :)
I TOTALLY agree here. Tools to handle translation strings are already in place: po4a support asciidoc nicely. I always look with suspect at "big project" because although the due big efforts, they sometimes miss the point and in a "big" way. The step-by-step approach have many advantages: 1) gives user very quickly an improvement that is usable _now_ and every one is happy 2) you have faster feedback for the direction to choose 3) the smaller the step the little the probability to take a wrong direction 4) the smaller the step the less effort you have to change direction if you find yourself in a cul-de-sac. For an example I could have used asciidoctor instead of asciidoc more than a year ago with the i18n in place. And I am sorry for this. -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------ -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
