Hi Christophe,
I've been researching reST/Sphinx lately (email coming Sometime Soon --
hopefully later today) and wanted to chime in with some observations,
based on the translation workflow for that.
On 6/16/20 12:52 PM, Christophe JAILLET wrote:
I've been looking for a tool that could do some xml --> po files
updates. The files to translate would then be only some small pieces of
text that could be handled by poedit or equivalent software.
This is also Sphinx's approach to translation, based on gettext.
The main advantages I see are:
- ease to spot changes
- same sentences in different files (or even branch) are translated
only once
FWIW, Sphinx splits translatable chunks by paragraph when constructing
its .pot templates, and it puts them into separate files based on the
source location. So though you might have to duplicate some work, you
also get a little more context.
(Though from looking at your .pot template, it looks like your tool also
set up some, but not all, of the translations this way.)
- ease to merge work of different contributors
- some translation web sites have a translation process that ease
access to contributor, with the possibility for the translation
community to validate others translation (Some years ago, I've been
using https://translatewiki.net for that)
As another example, the sphinx-intl tool integrates directly with the
Transifex service, which appears to be used by the Sphinx project
itself. It looks like it may have a "free" tier for OSS projects. I know
nothing more about it.
Using something like po files for the translation would also lead to
only partly localized files. Little by little, the not-updated part of
the doc would get replaced by the more up-to-date English version. I
don't think it is an issue. I prefer a mixed language document than
having something that I can not trust because I don't know what is
up-to-date or not.
This was also one of the big questions I had about the Sphinx approach.
My own opinion isn't particularly useful here, since I consume the docs
in English.
Do you think that such an approach is viable ?
Given that other large projects seem to use a similar approach, it seems
like it should be viable from a technical perspective. I can't speak to
the usability of the .po translation tools themselves.
--Jacob
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
