phpWebSite Content Management System

Hi,

Toughts on:
Translations/Localizations/Workflow

Would it be a good idea to integrate in the localized Cvs the right French naming for the links like?:
In English you have:
/topics.php (would be: "sujets.php")
/links.php (would be: "repertoire.php" or "signets.php" or "liens.php")
/user.php (would be: "utilisateur.php")
/submit.php (would be: "soumettre.php")
/calendar.php (would be: "calendrier.php")
Would it be an exhaustive task? I did it for my needs but... what do you think of that?

I would also verymuch like to contribute to the French translation where I would like to see it revisited. Where can I get the tools needed to contribute?

Would be great also if the modules would be quickly translated based on an ever growing online glossary to which I would like to contribute, and that the modules developer could get their language files from. In fact it would be nice if every module would work the same way as the Calendar (with a language.php) file.

Any input on that is welcome. It is just that I don't know where to ring the bell;-)

Just toughts!
Long live phpWebsite!

Best regards,
Yves

I think the translation system in phpws is a BAD THING (tm).

It should use translation-on-the-fly. Having the SAME files for every language simply is waste of space - and you would have to change each and every file for all installed languages if you fix a bug in one language.

I hope the "admins" will do something about the wrong style of translation.

The way translations are done in the future will change but not like requested here.

Translating the file names would be as problematic as translating variable names. We have a hard enough time with the content. An error in file names would bring the system to its knees.

As for 'language-on-the-fly'. No. Never. Nyet. There is no reason to eat up cycles comparing/parsing one set of text to another. Why have it anyway? Most of your web site's content in entered in one language. This language is going to be the same as the language tarball. I don't see why people want language on the fly. The content can never be on the fly, why should anything else? If you speak multiple languages, set up mirrors.

What we DO plan on doing to make this easier is have a translation module. Changes in the core code will be at the top of a list. The translators will be notified there are new things to update. When we run a distribution, it will come from this database. This should aleviate the problems with the .pp files.

Matt