>Translations are currently a problem because we need first to 
>update 'po' 
>files. I intend that this will be one of the tasks for maintanance 
>release R14.0.2.

I don't speak or read additional languages, but I would like to see 
i18n files receive attention too.

I try to remember to update the i18n files when I make changes in 
the main files, but I don't always remember (I'm working on updates 
now to match some recent patches). Considering all of the renaming 
and rebranding changes made in git, I suspect the i18n files are in 
horrible shape.

We have made changes to the top level help handbooks. I am certain 
no related updates have been made in the i18n files.

There is the challenge of when we update screen captures to update 
the i18n versions too. That probably does not require a native 
language speaker, but does require toggling to the other language 
to create the screen capture.

Part of our focus when we address the i18n files should be to 
develop a guideline so as a group we can update i18n files as much 
as possible when we modify the main files.

Darrell