Menu
▾
▴
#186 Add tag for easier i18n process
Hi,
I am working on the Jmol project, the documentation is
written using DocBook XML and we would like to use
the xml2po package to help to translate (and maintain)
the documentation in other languages (german,
french, ...)
Some parts of the documentation shouldn't be translated
(for example, commands to type, command line options,
scripts examples, ...). It would be useful to be able to
specify in the source DocBook XML that those parts
shouldn't be translated, so that xml2po can ignore them
when creating/updating the .pot/.po files.
I was thinking that a simple tag like <noi18n> could be
used: it would be ignored by DocBook, but it would tell
xml2po that there is no need to translate this string.
If there's an other way of doing this kind of things, I am
really interested in knowing :)
Thanks,
Nico
Logged In: YES
user_id=118135
> I was thinking that a simple tag like <noi18n> could
> be used: it would be ignored by DocBook, but it would
> tell xml2po that there is no need to translate this
> string.
What you can do that won't require adding anything new
to DocBook is to use one of the existing DocBook
"common attributes" -
http://docbook.org/tdg/en/html/ref-elements.html#common.attributes
For example:
<userinput condition="noi18n">tail messages</userinput>
Logged In: YES
user_id=1096197
Thanks for the tip, I will see how I can use it with xml2po.
That would be great to have standard ways to deal with i18n
in DocBook.
Logged In: YES
user_id=118135
Perhaps a new "i18n" common attribute could be added
<userinput i18n="no">tail messages</userinput>
Logged In: YES
user_id=1096197
Seems a good way to handle this kind of need
Logged In: YES
user_id=193218
The Committee suggested that this request could be
handled without adding a new element. A list of
elements that should not be translated should
be given to the translators, for example. Otherwise
do an XSLT transform to add such an attribute
to the copy given to the translators. Or use
xml:lang="" to indicate no language for an element,
which would indicate that it is not to be translated.
Logged In: YES
user_id=189932
W3C is working on generally usable way to markup content
that should/should not be translated. See
http://www.w3.org/TR/its/
This can be easily integrated into DocBook as it uses its
own namespace.
Logged In: YES
user_id=1096197
That's great that something standard is being done for the
translations !
Too bad that it won't probably be available (specified +
tools using it) before a long time
Thanks for the answers :)
Logged In: YES
user_id=189932
Actually, ITS can be added into DocBook quite easily:
http://xmlguru.cz/2006/03/docbook-and-its
Logged In: YES
user_id=1096197
Well, adding it is one thing, but what I am looking for is
tools that really uses it: a tool that can extract the
strings that need to be translated and then put back the
translated strings in the xml file.
Do you know such tool ?
Logged In: YES
user_id=189932
If you are looking for tools, try asking at docbook-apps
mailing list or at some list devoted to automated
translation.
This tracker is used solely for DocBook schema.