This was originally posted in the documentation mailinglist: Translating the OGo Website.

Hi,

the website translation is hit a bit by similiar problems like the OGo application translation since it is generated by the OGo CMS (OGo Publisher).

I think we can workaround the problems by using ISO-Latin-1 HTML files and by encoding any Non-Latin-1 chars using entities (eg ≻ or ä). We'll see. If we have the Western languages translated, German, Spanish, French, Italien etc, we are a whole lot further in any case.

For Japanese, Chinese etc you should probably use UTF-8 and we'll see whether we can get it processed using OGo Publisher templates. I think we should be able to work that out.

Anyway, now instructions to get started translating the website. All the pages are currently in CVS, you can checkout the webserver using:

$ export CVSROOT=":pserver:anonymous@cvs.opengroupware.org:/cvs"
$ cvs login # (just press enter for the password)
$ cvs -z3 -q checkout www

The CMS uses templates to assemble web pages using individual parts.

We already prepared the www tree to contain different languages in different subdirectories, more exactly in "en" (English), "de" (German), "fr" (French), "es" (Spain).
We'll need to add additional codes for additional languages.

So how should you translate ? Well, for the initial translation you should just copy everything from the "en" tree to your language, eg:

$ cd en
$ cp -ra * ../es/
$ cd ../es/
$ rm -rf `find . -name CVS`

then start translation ;-) If you have some initial version ready, you should send me a tar of the language directory and I'll check it into CVS.

Since the website is still in flux, it's actually some work to keep track of changes. We should probably write some script which can be run from the language subdirectory and which shows files that changed in the en tree based on the file modification date. Probably not too difficult (any contributor ? ;-).

Let me know in the list if you need further help and I'll step in.

Thanks a LOT for your help,
   Helge