I'm happy to help!

On Wed, Apr 2, 2008 at 11:38 PM, neeocis <[EMAIL PROTECTED]> wrote:
>
>  Dear b logica,
>  I don't know how can i give you my greetings to you.
>  Thank you very much....
>  You saved my life.. :)
>
>  On Apr 2, 11:00 pm, "b logica" <[EMAIL PROTECTED]> wrote:
>  > Yes, but you shoulduse__d() instead of __() to translate. Look at
>  > the method in cake/basics.php. In a nutshell, you woulduseit like:
>
> >
>  > __d('common', 'some string to translate')
>  > __d('common', 'some string to translate', true)
>  > __d('msgid_will_use_in_ctp_file1', 'some string to translate', true)
>  >
>
> > On Wed, Apr 2, 2008 at 6:33 AM, neeocis <[EMAIL PROTECTED]> wrote:
>  >
>  > >  Dear all,
>  > >  I am trying to figure out that is it possible and orfeasibletouse
>  > >  multiple.pofilesfor each language like...
>
> > >  /app/locale/eng/LC_MESSAGES/common.po
>  > >  /app/locale/eng/LC_MESSAGES/msgid_will_use_in_ctp_file1.po
>  > >  /app/locale/eng/LC_MESSAGES/msgid_will_use_in_ctp_file2.po
>  > >  ---------
>  > >  /app/locale/fin/LC_MESSAGES/common.po
>  > >  /app/locale/fin/LC_MESSAGES/msgid_will_use_in_ctp_file1.po
>  > >  /app/locale/fin/LC_MESSAGES/msgid_will_use_in_ctp_file2.po
>  >
>  > >  Because, the system we are developing will must support more than 3
>  > >  languages and the static contents are huge. So if i canusemultiple
>  > >  filesrather than /app/locale/eng/LC_MESSAGES/default.po
>
> > >  than it will be more easier for me to maintain, update and develop.
>  >
>  > >  Pleasehelpme on this regards..  any resource/links will be
>
>
> > >  appritiate.
>  >
>  > >  Thanks in advance,
>  > >  Neeocis
>
>  >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to