It's not weird. You would imagine that only a few languages would have a title
like "VERB NOUN". The rest could use god knows what.
And using rules for localization will produce hundreds of them for no gain.
Also, it's a difference between page titles and button titles so it makes sense
to have two distinct values but allow for the same one.
Cheers, Anjo
Am 21.10.2010 um 15:46 schrieb David Avendasora:
> Hey Johan,
>
> I had the same problem to start with. They are handled by the
> Localizable.strings instead of rules (yeah, weird, I know)
>
> For Example in Resources/English.lproj/Localizable.strings I have:
>
> "Pages.QueryAccount" = "Search for Accounts";
>
> In Resources/Spanish.lproj/Localizable.strings I have:
>
> "Pages.QueryAccount" = "Buscar para Los Cuentas";
>
> Dave
>
> On Oct 21, 2010, at 9:28 AM, Johan Henselmans wrote:
>
>> I might say I really like the way ERModernLook…looks.
>>
>> One question that remains for me how localization is taken care of:
>>
>> I added
>>
>> # Localization
>> ERXLanguages = (en,nl)
>> er.extensions.ERXLocalizer.defaultLanguage=English
>> er.extensions.ERXLocalizer.useLocalizedFormatters=true
>> er.extensions.ERXLocalizer.fileNamesToWatch=("Localizable.strings","ValidationTemplate.strings")
>> er.extensions.ERXLocalizer.availableLanguages=(English,Dutch)
>> #er.extensions.ERXLocalizer.frameworkSearchPath=(app,ERModernDirectToWeb,ERDirectToWeb,ERExtensions)
>>
>> er.extensions.ERXLocalizer.English.locale = en
>> er.extensions.ERXLocalizer.Dutch.locale = nl
>>
>> to the Properties, and Localizable.strings in Dutch.lproj and English.lproj
>> tend to work for the navigation menu items, but I noticed that some of the
>> stuff does not localize by default:
>>
>> For instance, there if I have a queryPageForEntityNamed it still tells
>> "Query [Entity Name]", and editPageForNewObjectWithEntityNamed it tell
>> "Create [Entity Name]".
>>
>> I'd like to be able to replace
>> Query with 'Zoek'
>> and
>> Create with "Maak"
>>
>> for instance.
>>
>> I could not find a way to localize these terms nor the entityNames, like
>> Ramsay Gurley does in his R2D2W framework and templates, where one can add
>> in Localizable.strings
>>
>> (eg)
>> "Entity.name.Performance" = "Voorstelling";
>>
>> Have I overlooked something? Plans in that direction?
>>
>> (that was the dutch lesson for today).
>>
>>
>> Johan Henselmans
>> jo...@netsense.nl
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
>>
>> This email sent to webobje...@avendasora.com
>>
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/anjo%40krank.net
>
> This email sent to a...@krank.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
