> > It seems that mysql reached stable with the version 4.1 > > So now there is full support for utf8. > > So whats now with moving the translations into database? > > We can do it for CVS HEAD only but therefore we need two things: > > 1. a database scheme (which you created already) > 2. two scripts for import/export mo/po-files.
For what you want that? The mo/po files have the english translation as key and are therefore useless for the new database scheme. Or am i wrong? Whats your opinion, how the translation work should be done? I think about that way: 1. create a webinterface at the node interface for translation updates. Create new translations entrys, add languages, ... 2. define a official translation openca version. For example: translation.openca.info 3. then people fetch a script and replace all translation calls with the new one and insert the translations keys into this master version (only english). When finished with a script, the mail it to cvs admins or insert it directly into the cvs 4. once all scripts are done, the maintainer of other langs add the translations Regards til
smime.p7s
Description: S/MIME cryptographic signature
