On Aug 20, 9:15 pm, ava <[email protected]> wrote:
> Hi Marc,
>
> as for multilingual I suggest the following procedure:
>
> 1. create po file by bake (cake.php i18n extract)
> 2. load po file into translation table:
> - flag new records as new (status: n)
> - set current date for existing records if msgid matches.
>
> 3. translation can now take place in the web application: user
> (translator) flags translated records as "translated" (status: t)
>
> 4. create a new po file for each language, source is the translation
> table.
> - take "not translated" text if the item is not translated.
>
> Translation Table:
>
> CREATE TABLE `translations` (
> `id` int(7) NOT NULL auto_increment,
> `msgid` varchar(100) ,
> `locale` char(2) default 'en',
> created timestamp,
> last_used timestamp,
> status char(1), -- (t:translated, n: new, needs translation, r:
> to be reviewed, u: updated, needs translation
> `msgstr` text ,
> );
Why don't you just write a model/datasource to edit the po files
directly? Challenging thought it might be, you could even pull the
extract task appart and use the same file writing logic.
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
