Hi Guillermo, I’m not yet at the point of thinking about css or even UI changes. If you want to you and you aren’t already familiar with Antora UI bundles you could take a look.
I think the I18n Asciidoc proposal would be too inconvenient for Tomee…. my experience with related systems was pretty horrible. As I understand, Tomee has the (normally english) original adoc file in the same directory as any contributed translations. I think this is going to continue to work well, as it’s really easy to understand what to do…. just take the adoc file and translate it, keeping the structure if appropriate. I suppose it might be possible to, for each untranslated page and each language, generate a page saying “translate me” and perhaps with a google-translate rendition. That seems a bit in the future though. I was just thinking about the problems of how to organize and present the translations in Antora. Thanks! David Jencks > On Feb 7, 2020, at 11:16 AM, Guillermo García <[email protected]> wrote: > > On Thu, Feb 6, 2020 at 11:14 PM David Jencks <[email protected]> > wrote: >> >> After building myself a couple of tiny websites using Antora ( > https://antora.org) I’ve become somewhat interested in site generation from > asciidoc.... >> Does this seem like a direction worth pursuing? I’m willing to spend a > few days organizing stuff better, fixing the warnings and errors, and > sprucing up the UI (I can change colors and remove the irrelevant stuff > from the header, but advanced css is beyond me at this point). > > Hi David, > > It's a great approach. Count with me in CSS related changes. Just create > the corresponding JIRA ticket and assign it to my JIRA user: bitcoder. > >> There are also a couple of directions of experimentation I might like to > pursue: >> >> — Antora doesn’t have a good strategy for multi-language sites. Since > there’s at least some translation going on here, this seems like a good > place to try out solutions. I haven’t found the translations yet :-) > Provisionally my first idea would be to represent languages as versions: > 8.0 is english, 8.0-sp, 8.0-pt, 8.0-ru etc are the other languages. You > could pick your language in the lower left component-version selector (on > the preview only tomee/8.0 is present) > > > Not sure how i18n is being provided for TomEE documentation. We could find > a way to track which parts of a translation need to be updated when the > source document changes by using a localization management tool, like the > po4a [1] perl module. > > Besides, there's some interesting proposal [2] to use localization in the > AsciiDoc project coming in next releases. > >> >> ... >> >> thanks >> David Jencks >> >> ps. My google search for the docs brought up this: >> >> https://tomee.apache.org/latest/docs/documentation.html >> >> which doesn’t look good. >> > > It was my first impression too when I was reached the TomEE documentation. > I already fixed some weird characters for the documentation.adoc in > TOMEE-2767 [3], I am just waiting for changes to be deployed. > > -- > Guillermo Garcia > > > [1] https://github.com/mquinson/po4a > [2] https://github.com/asciidoctor/asciidoctor/wiki/Design-Doc:-i18n > [3] https://issues.apache.org/jira/browse/TOMEE-2767
