We are starting work on internationalization and localization
issues for the commands and libraries.
In this context
refers to the mechanism by which messages and documentation are
displayed in a locale-specific language other than US-English
rendition of US-English), including collation order and date and monetary
refers to the mechanism by which locale-specific glyphs are input and displayed.
This work is being done in stages:
Identify message and documentation text in the source code:
this is done using the
common action and the
command to extract the text.
This mechanism has identified over 90% of the text in our code
with no source modifications
The remaining strings have been or will be manually marked using the GNU style
Messages are associated with an individual command or groups of commands and
The source contains no message numbers; messages are identified by the
for more details.
Gather messages into text catalogs for the
categories in the
machine independent message catalogs are generated by the
command for use on all architectures.
Strings in the machine-independent files are UTF-8 encoded.
The machine-independent message files are placed in the directory
commands are self-documenting (try the
option on any
command), manual pages are automatically included in the message translation
Provide translations for the
packages contain machine-independent message files for the
the initial translations were done by
we hope that interested users will humanize these translations.
If you are interested, mail
for coordination and details.
Next we will focus on
These will hinge on an implementation of
either from GNU or our own.
The problem with this work is that although the user interfaces are clearly
defined by the standards, the implementation details, such as generated file
formats and locations are unspecified, making it difficult to use efficiently.
For example, how do you implement
if you don't own