So you are basically using these as "defines"?
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
On Tue, Oct 13, 2009 at 2:19 PM, euromark (munich) <
dereurom...@googlemail.com> wrote:
>
> i agree with miles
>
> they should be slugged, short and precise
> and explained in both the english and foreign .po file
>
> like
>
> "regMessageSuccess"
> and
> "You have been successfully registered"
> "Sie sind nun erfolgreich angemeldet"
>
>
> or
> "valErrorRecordNameExists"
> for
> "A record with this name already exists"
>
> this way you can easily change the "original" language text (here:
> english) without having to change all the x places in the script as
> well
>
> maybe it is now supposed to be
> "You cannot have two records with the same name"
>
>
> but the short slugged term has still the same basic meaning and
> therefore remains the same
>
>
> On 13 Okt., 18:12, Miles J <mileswjohn...@gmail.com> wrote:
> > I am personal extremely against naming your ids the full sentence,
> > what purpose does that serve? Its longer in both the .po and .ctp file
> > and its a lot easier to reference slugs. To each his own I guess.
> >
> > On Oct 13, 7:42 am, "Larry E. Masters aka PhpNut" <php...@gmail.com>
> > wrote:
> >
> > > Another thing I forgot to mention. You should be using full strings you
> want
> > > translated for the msgid.Example:
> >
> > > msgid "By registering on this web site you are..."
> >
> > > This is the way the core was designed to handle translations. You will
> also
> > > find it much easier for people to translate your application if they
> have
> > > everything they need in the 1 .po file vs looking for the text related
> to a
> > > place holder.
> >
> > > --
> > > /**
> > > * @author Larry E. Masters
> > > * @var string $userName
> > > * @param string $realName
> > > * @returns string aka PhpNut
> > > * @access public
> > > */
> >
> > > On Tue, Oct 13, 2009 at 9:13 AM, Rob <rob...@catchit.pl> wrote:
> >
> > > > Any1 thought about creating little snippet which could speed up
> > > > hardcoded localization process.
> > > > Here is the simple scenerio:
> > > > 1) find strings within __('...') __('...',true) string patterns in /
> > > > app folder
> > > > 2) build arrays from default locale *.po files containing locale keys
> > > > 3) append to end of these files missing id keys in form:
> > > > msgid "_register_disclaimer"
> > > > msgstr "TOODOO"
> >
> > > > i create many multilang apps and i believe it could be major speed
> > > > boost for ppl like me.
> > > > we dont need to update these files manually every time we use __().
> we
> > > > just run script when app is ready or changed and just update TOODOO
> > > > strings or send them to translators.
> >
> > > > If some1 came up with idea how this could be easly done i would
> > > > apreciate this.
> >
> > > > regular expressions? if so, how to build fault free one?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
