Quote
Please check with "yiic message" and see if it fits your need.
You may refer to /framework/messages which contains messages extracted using this tool.
Ok, I found [tt]yiic message[/tt] extracts the strings to separate PHP files, one per category (or context). This doesn’t fit quite well for my needs, since I need the strings (in fact, I already have thousands of them) in gettext format, all of the messages in one file per locale, with or without context, for instance:
msgctxt "print operation status"
msgid "Printing"
msgstr "Imprimindo"
msgid "Editing"
msgstr "Editando"
So the extractor and merger for this needs to be created (it could be done, let me try in PHP, but we already have [tt]xgettext[/tt], which could fit
). BTW, I'm sorry, but I must insist that the autosave feature from Prado ruled. Do you plan to integrate it in Yii? I mean, keep [tt]yiic message[/tt] but also have autosave 
Another thing I'm finding different from Prado is that:
localize('Hello {w}', array('w'=>'World'));
is now:
Yii:t('demo#Hello {w}', array('{w}'=>'World'));
, notice the [tt]{}[/tt] sorrounding the substitution variable. Is there any reason for this change? I'll try to modify the extractor to work the old way and to work with context as a parameter and not as a prepended string. If this were successful, may you consider commiting my changes? I really think that the way KDE and GNOME work with context is cleaner and more elegant.
Also, if I do this:
Yii:t('demo#Hello {w}', array('w'=>'World'));
I get [tt]Hello {World}[/tt] , so I think there’s a bug somewhere in the regex… 
Now, my newbie mistakes: I’m modifying the hello world demo from the svn, I have created protected/config/main.php: (mistake found
)