[hibernate-dev] documentation translations
steve at hibernate.org
Thu Feb 11 15:00:17 EST 2016
Ok, then I will drop the 'en-US' part from the path.
A related discussion about the 'html' versus 'html_single' paths.
Currently the asciidoctor outputs are put into the 'html' path, but what
goes there is what is normally considered html-single. At the moment
Asciidoctor does not offer chunked html rendering, hence why we only render
the one "html single" output.
But to be consistent, I think we should rename the "html" in these asciidoc
paths to "html_single". I have changed the build for 5.1 to only generate
one docbook doc (integrationGuide) until we get that one migrated. That
way we have consistency between docbook and asciidoc outputs but also in
what is normal usage.
On Thu, Feb 11, 2016 at 11:46 AM Vlad Mihalcea <mihalcea.vlad at gmail.com>
> I think it's nearly impossible to keep documentation to date across
> several languages.
> If the users haven't complained that we didn't maintain the non-English
> I'd suppose we could simply focus on the English version only.
> Google Chome does a decent job when translating articles from English to
> other languages anyway.
> On Thu, Feb 11, 2016 at 6:57 PM, Steve Ebersole <steve at hibernate.org>
>> The translations of the ORM documentation (at least) is completely out of
>> date. Has been for many years. To the point where we stopped even
>> publishing translations.
>> So at this point, as we migrate to Asciidoc(tor) and make changes to doc
>> hosting do we plan for eventual translations? Or do we move forward
>> assuming no translations?
>> At the end of the day this is a simple point in that I need to know
>> to preserve the en-US directory in the publishing or not. But if we do
>> plan on having translations, it seems odd to even deal with these language
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
More information about the hibernate-dev