Re: The Good Path to D2W localization
Re: The Good Path to D2W localization
- Subject: Re: The Good Path to D2W localization
- From: Fabian Peters <email@hidden>
- Date: Thu, 10 Jul 2014 13:58:12 +0000
Hi Pascal,
You shouldn't need to specify additional rules. By default ERDDefaultDisplayNameAssignment handles localization and ERModern is quite good at logging unknown or deprecated localization keys. My localization files consist mostly of these types of keys:
"Entity.name.Location" = "Ort";
"PropertyKey.amount" = "Betrag";
"Pages.CreatePerson" = "Person anlegen";
"Nav.Settings" = "Einstellungen";
"TabKey.Owner" = "Eigentümer";
This covers entity names, property names, page configurations and navigation elements. I only subclassed the default assignment to handle entity-specific property names.
Fabian
Am 10.07.2014 um 13:35 schrieb Pascal Robert <email@hidden>:
> Hi,
>
> What is the proper way to do D2W localization? In the wiki, it says that you should add rules like this:
>
> 100 : (pageConfiguration like '*Computer*' and propertyKey = 'model') => displayNameForProperty = "Computer.PropertyKey.model" [ERDLocalizedAssignment]
>
> And having the correspondant
>
> "Computer.PropertyKey.model" = "Modèle";
>
> in the Localizable.strings. It works, but that means I will have to add a lot of rules. Is there a better way to do localization without the rules? This is with ERModernLook.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden