fab2008 wrote: > > There is no reason to create a class, a simple php file with message codes > is enough in order to make gettext work, something like this: > > <?php > $a = 'isEmpty'; > $a = 'notString'; > ... > ?> > > and parse it with 'xgettext -a strings.php'. Option -a stands for all > string so every PHP string in this file will be included in the output > catalog file. >
Sure, thanks for that. The problem I had was getting PoEdit to do that for me. Currently, I just point it to application root directory and set it parsing. It doesn't do the -a option as far as I can see. Now, when I have my custom gettext phing task up and running, this is certainly the method I'll use... :) Cheers, Jamie. -- View this message in context: http://www.nabble.com/Using-a-gettext-Zend_Translate-object-with-Zend_Form-tp16092578s16154p16210665.html Sent from the Zend Framework mailing list archive at Nabble.com.
