Jean-Christophe Helary wrote:
On 13 juil. 07, at 00:07, Uwe Fischer wrote:
Jean-Christophe Helary wrote:
...
To make things even clearer, I am saying that using _any_
intermediary format for documentation is a waste of resources.
...
let me add some words to your message:
Uwe,
Thank you so much for your mail !
The application help files are XML files. See http://
documentation.openoffice.org/online_help/techdetails.html for details.
The Help Viewer converts the XML files to HTML when they are displayed.
Using XML, it should be even more easy to use a straight forward
translation process without intermediate files.
That is very good to know. There are already free generic XML filters
that produce valid XLIFF: Okapi framework for ex, developed by Yves
Savourel, also editor of the XLIFF 1.0 spec. Okapi is developed in
.NET 2.0 but I keep asking Yves to make it compatible with Mono so
that it can be used in other environments. As a side note, OmegaT's
XLIFF filter has been made to specifically support Okapi's output.
Today we have a 1:1 correspondence of paragraphs as the smallest
units to be translated. Each paragraph has an ID number to ensure
the correct mapping of translated text. This means that no
localization with additional or removed parts of text is possible.
Not 21st. century technology in my opinion.
No, but that means that correct TMX files are a possibility (even
now). By the way I wonder why Rafaella told me creating TMXs of the
state of the strings before the current updates was impossible ?
to clarify: the only possibility I have is to provide you TMX files in
which translation exactly matches the English text now. If the English
source has been changed I have following situation:
New English text - Old translation (matching previous text).
In the database I have no possibility to provide you with files
containing Old English text and Updated English text.
Rafaella
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
