Thanks Fabian:)
it works with the name of the framework...I wasn't thinking about it as I was (wrongly) assuming it would know "where" it was.

One last thing, if I want to pass the languages NSArray from the the application (displayDestinationKey) to the localizedName method in the framework, how would I do that?

I'll have a look at wonder anyway, but I always like to know the "built-in" way:)

Thanks again,

Xavier



Hi Xavier,

If you refer to a "Localizable.strings" file in a framework named "Backend", it should read:

String result = WOApplication.application().resourceManager ().stringForKey(anAttributeOfTheEntity, "Localizable", anAttributeOfTheEntity, "Backend", null);

Yes, and if aLanguagesList is null, it will pick up the available key anyway. So this is correct and work as expected in my application, but when I try to use it in a framework, it seems like it doesn't get any value:(

Are you passing in the framework name, i.e. "Backend" in the example above?
in fact I'm trying to have this line directly in the framework.
In this case I got null value (not an exception, just null string.

IMHO you'll still have to pass in the framework's name, whether the method is in a class in your framework or not. This is just so WOResourceManager knows where to look for the .strings file. Then of course you'll have to make sure the .strings file is well-formed and correctly included in your framework.

HTH

Fabian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects% 40anazys.com

This email sent to [EMAIL PROTECTED]


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to