Re: The Good Path to D2W localization
Re: The Good Path to D2W localization
- Subject: Re: The Good Path to D2W localization
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 10 Jul 2014 13:36:47 -0700
The easiest way I know is to load the page with non-localized content, then dump the created keys to the console (/wa/dumpCreatedKeys). That gives you your missing keys. I haven’t used it, but there’s a ERD2WPageRunner to help you do this for all your pages. Hand it an array of page names, createPages(), then /wa/dumpCreatedKeys. Probably useful if you want to dump keys for each language supported.
On Jul 10, 2014, at 6:35 AM, Pascal Robert <email@hidden> wrote:
> 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