• 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: Accessing Localized File Menu String
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Accessing Localized File Menu String


  • Subject: Re: Accessing Localized File Menu String
  • From: Yvan KOENIG <email@hidden>
  • Date: Mon, 20 Jul 2009 17:49:44 +0200


Le 10 juil. 2009 à 08:37, Chris Page a écrit :

On Jul 9, 2009, at 10:30 PM, Philip Aker wrote:

Any solution in sight for scriptors? In a recent discussion it was found out that some often used Apple applications are setting both the 'name' and the 'title' of menu items to the localized string. This makes it impossible to ask for a menu by an unchanging term and consequently one is forced to use an index (which may be unreliable between releases). I'm not sure if nib tools usable for this situation are available on a user setup which doesn't have the Developer tools installed.

The solution is to report bugs against those applications. <http:// bugreport.apple.com/>


A workaround might be to use the available command-line tools to harvest localized strings from the nibs and place them in *.strings files in your script bundle. This ties the script to a particular version of the target application, but could be updated automatically if you wrote a script to do it.

If I understand well, we are supposed to be able to do the trick with nibtool.
Alas, Nib files embedded in Apple's applications like iWork or even TextEdit are 'compiled' so nibtool returns an error message when we try to use it.


Is there a trick to get rid of that ?
It's quite pitiful to read that the correct path is to grab datas from the nib files when these ones can't be treated.
At this time, I'm just able to get a raw list of every menu items titles but they are not ordered the same so, it's a huge task to find which local string is the translation of a given English one.


For Numbers, I did the trick for French, Da and Dutch but it's really boring.

Maybe I missed the trick allowing us to deal with compiled nibs.

Yvan KOENIG (from FRANCE lundi 20 juillet 2009 17:49:38)



_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden
  • Follow-Ups:
    • Re: Accessing Localized File Menu String
      • From: Chris Page <email@hidden>
    • Re: Accessing Localized File Menu String
      • From: Yvan KOENIG <email@hidden>
References: 
 >Accessing Localized File Menu String (From: Ian was here <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Chris Page <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Philip Aker <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Chris Page <email@hidden>)

  • Prev by Date: Re: QuicKeys and script activation
  • Next by Date: Adium
  • Previous by thread: Re: Accessing Localized File Menu String
  • Next by thread: Re: Accessing Localized File Menu String
  • Index(es):
    • Date
    • Thread