Posted Sep 18, 2006 17:43 UTC (Mon) by JLCdjinn
In reply to: So far, so missing i18n
Parent article: A survey of the DocBook landscape
There are issues here at a variety of levels that usually include DocBook (the language) as well as tools that process DocBook. First, you (in the generic sense) may want to write the same text in several different languages in the same document. This is called profiling, and DocBook has facilities for profiling such as the
os attributes. DocBook XSL: The Complete Guide has a chapter called "Profiling (conditional text)" that talks about these issues both in DocBook as well as support for these features in the DocBook XSL stylesheets.
It sounds like you may also be interested in i18n (internationalization) support with respect to automatically generated portions of an output document. Clearly, such support is the responsibility of tools that process DocBook. Again, DocBook XSL: The Complete Guide provides a thorough treatment of the way in which the DocBook XSL stylesheets allow for language-specific generated content in its section titled "Language support".
One criticism that you might level against DocBook (and many XML dialects) is the choice of language (usually English) for their tag names. Clearly element names like
section only have meaning to those who understand English. A problem like this must be solved at the XML level; one possible solution is the DSRL (Document Schema Renaming Language) approach. See the DSRL documents on the DSDL (Document Schema Definition Languages) web site for details.
It would be interesting to learn what tools you are using in order to try to fix the problem with those tools.
to post comments)