On 6/9/05, Jesse Grosjean <email@hidden> wrote:
> Buy default most of the NSLocalizedString macros only search for
> strings in the main bundle. This means that if you are writing a
> plugin you have to use the long form
> NSLocalizedStringFromTableInBundle, and that tends to be a pain in
> the neck, lots of extra typing. Ideally I would like to redefine the
> NSLocalizedString macros to look like this:
>
> #define NSLocalizedString(key, comment) [[NSBundle bundleForClass:
> [self class]] localizedStringForKey:(key) value:@"" table:nil]
> #define NSLocalizedStringFromTable(key, tbl, comment) [[NSBundle
> bundleForClass:[self class]] localizedStringForKey:(key) value:@""
> table:(tbl)]
>
> But when I do that I get lots of "redefined" warnings. Is there a way
> to get rid of these warnings for this particular case, or a better
> approach to this problem that I'm not thinking about? I would like to
> use NSLocalizedString instead of defining my own macro so that
> genstrings will work.
You can still use your own macro and genstrings will work. Look at the
"-s" parameter in the man page.
--
Clark S. Cox III
email@hidden
http://www.livejournal.com/users/clarkcox3/http://homepage.mac.com/clarkcox3/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
