• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: The Good Path to D2W localization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The Good Path to D2W localization


  • Subject: Re: The Good Path to D2W localization
  • From: Pascal Robert <email@hidden>
  • Date: Thu, 10 Jul 2014 10:25:55 -0500 (CDT)
  • Thread-topic: The Good Path to D2W localization

Works great for property keys, thanks!

But it doesn't work for navigation. I added this:

  "Nav.Computers" = "Ordinateurs";
  "Nav.CreateComputer" = "Ajouter un ordinateur";
  "Nav.SearchComputers" = "Rechercher des ordinateurs";

and my NavigationMeny.plist:

(
    {
        name = Root;
        directActionClass = DirectAction;
        directActionName = default;
        children = ("Computers", "Mobile", "Software", "Networks", "Manufacturers", "Locations");
    },
    {
        name = "Computers";
        action = "session.navController.listComputersAction";
        children = ("CreateComputer","SearchComputers");
    },
    {
        name = "CreateComputer";
        action = "session.navController.createComputerAction";
    },
    {
        name = "SearchComputers";
        action = "session.navController.searchComputersAction";
    }
)

But I still get "Computers", "CreateComputer" and "SearchComputers" in the navigation.

----- Mail original -----
De: "Fabian Peters" <email@hidden>
À: email@hidden
Cc: "Pascal Robert" <email@hidden>
Envoyé: Jeudi 10 Juillet 2014 09:58:12
Objet: Re: The Good Path to D2W localization

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


  • Follow-Ups:
    • Re: The Good Path to D2W localization
      • From: Fabian Peters <email@hidden>
References: 
 >The Good Path to D2W localization (From: Pascal Robert <email@hidden>)
 >Re: The Good Path to D2W localization (From: Fabian Peters <email@hidden>)

  • Prev by Date: Re: The Good Path to D2W localization
  • Next by Date: build directory path is not working
  • Previous by thread: Re: The Good Path to D2W localization
  • Next by thread: Re: The Good Path to D2W localization
  • Index(es):
    • Date
    • Thread