On Fri, Apr 22, 2016 at 12:42 AM, 'Marco Ciampa' via asciidoc < [email protected]> wrote:
> > That's on the roadmap. I'm fairly certain it will happen (in some > capacity) > > in 2015. > > Ok now we are well inside 2015 :-) > What can I say, a lot changed since then :) How is going the i18n effort? May I contribute / test / see the efforts? We're in the design phase. There are several issues: * https://github.com/asciidoctor/asciidoctor/issues/788 * https://github.com/asciidoctor/asciidoctor/issues/1129 (as well as others, if you search for internationalize, i18n or translation). There are also many facets to 18n. There's i18n labels (which Asciidoctor supports in a basic way), there's translation of the text and then there's layout stuff like RTL. I think that this is very important for the whole asciidoc(tor) project. Agreed. It's really a matter of resources. It's going to take a lot of time to implement a good solution and that opportunity (time & funding) just hasn't presented itself yet. I want to be clear that my goal is to move the bar forward. I don't just want to do what everyone else is doing blindly. I want to have a solution that is well-suited for translators and/or integrates well with translation systems. Feel free to jump in on any of those issues. As I always say, "activity drives progress" Cheers, -Dan -- Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen -- 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.
