Localizing plug-in displayName

[Clarence Locke]

I understand how to localize a key that hangs off the "root" of an info.plist file (e.g., CFBundleGetInfoString) by placing the localization in the appropriate InfoPlist.strings file.

How do I localize the string associated with the displayName key:

<plist version="1.0">
<dict>
<key>ProPlugPlugInList</key>
<array>
<dict>
<key>className</key>
<string>...</string>
<key>displayName</key>
<string>I WANT TO LOCALIZE THIS</string>
</dict>
</array>
</dict>
</plist>

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Aperture-dev mailing list (Apertu...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/aperture-dev/aperture-dev%2Bgarchive-9674%40googlegroups.com

This email sent to aperture-dev+...@googlegroups.com

[Blake Seely]

I think you can put displayName in your InfoPlist.strings file just like you would any longer localizable key. Have you tried that already and had it not work?

-Blake

On Aug 30, 2010, at 12:19 PM, Clarence Locke wrote:

> I understand how to localize a key that hangs off the "root" of an info.plist file (e.g., CFBundleGetInfoString) by placing the localization in the appropriate InfoPlist.strings file.
>
> How do I localize the string associated with the displayName key:
>
> <plist version="1.0">
> <dict>
> <key>ProPlugPlugInList</key>
> <array>
> <dict>
> <key>className</key>
> <string>...</string>
> <key>displayName</key>
> <string>I WANT TO LOCALIZE THIS</string>
> </dict>
> </array>
> </dict>
> </plist>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Aperture-dev mailing list (Apertu...@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:

> http://lists.apple.com/mailman/options/aperture-dev/bseely%40apple.com
>
> This email sent to bse...@apple.com

[Clarence Locke]

Admittedly, I had not tried it.  Mainly because I actually have two (2) entries in the ProPlugPlugInList array, so there is already some ambiguity as to _which_ displayName is to be found:

 <plist version="1.0">
 <dict>
 	<key>ProPlugPlugInList</key>
 	<array>
 		<dict>
 			<key>className</key>
 			<string>...</string>
 			<key>displayName</key>
 			<string>I WANT TO LOCALIZE THIS</string>
 		</dict>

 		<dict>
 			<key>className</key>
 			<string>...</string>
 			<key>displayName</key>
 			<string>AND I ALSO WANT TO LOCALIZE THIS OTHER THING</string>
 		</dict>
 	</array>
 </dict>
 </plist>

And also because the placement of the key is not at the root of the hierarchy — it's really at :ProPlugPlugInList:0:displayName (to use the PlistBuddy parlance).

While authoring this email, I tried all of the following permutations in the InfoPlist.strings file (all of which failed to generate a localized representation in the Aperture export menu):

1)

displayName = "foo";

2)

displayName = "foo";
displayName = "bar";

3)
:ProPlugPlugInList:0:displayName = "foo";
:ProPlugPlugInList:1:displayName = "bar";

4)
ProPlugPlugInList:0:displayName = "foo";
ProPlugPlugInList:1:displayName = "bar";

[Blake Seely]

Off the top of my head, I don't know the answer about multiple separate plug-ins, but it looks like Aperture 2's Dodge & Burn plug-in put the displayName key in its Localizable.strings file - try doing the same and see if that works for you.

Beyond that, somebody from the Aperture team may be able to answer more specifically. If putting a displayName key in Localizable.strings doesn't work, please file a bug. I also filed a bug asking for this to be included in the docs.

-Blake

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Aperture-dev mailing list      (Apertu...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:

[Clarence Locke]

If I create a single displayName key in the Localizable.strings file, then both export menu items use the localized string.  If I create two (or more) displayName keys, then both export menu items use the localized string of the last key.

I am going to create a bug for being able to non-ambiguously associate a localized string for multiple ProPlug PlugIn entry displayName _and_ infoString keys.

http://lists.apple.com/mailman/options/aperture-dev/clarence%40blueroomsoftware.com

This email sent to clar...@blueroomsoftware.com