On Feb 16, 1:56 pm, Gonzalo Servat <[email protected]> wrote:
> On Mon, Feb 16, 2009 at 9:26 AM, AD7six <[email protected]> wrote:
>
> > IMO you'd be better off using __d('stuff', $xyz) - that way your
> > 'manual' entries are in a seperate po(t?) file to the file cake
> > extract writes to. Seehttp://api.cakephp.org/file/basics.php#function-__d
>
> Actually, AD, what you suggested is good for places where I used to call
> __(), but there are some methods in CakePHP's source that call __() (like
> the FormHelper::inputs() method .. not sure what function does the call, but
> at some point it calls __() on the column names). Since I have no way of
> controlling those, I'm not sure how I could maintain a set of translations
> for the column names and have CakePHP respect them when doing an extract.
There are very few uses of __() in the core/form helper. The one
you're referring to is:
http://api.cakephp.org/view_source/form-helper/#line-460
I would recommend extending the core where it doesn't fit your needs
e.g.
http://trac.assembla.com/mi/browser/branches/base/views/helpers/mi_form.php#L59
The mi_i18n and mi_extract tasks generate the po file that helper
method looks for - but it's just an example, generate and use po files
however suits you best.
hth,
AD
>
> - Gonzalo
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
