Re: genstrings and the build system (was Re: Unicode - Converting memory to match NSCell -stringvalue?_
Re: genstrings and the build system (was Re: Unicode - Converting memory to match NSCell -stringvalue?_
- Subject: Re: genstrings and the build system (was Re: Unicode - Converting memory to match NSCell -stringvalue?_
- From: Jim Correia <email@hidden>
- Date: Sat, 31 May 2003 18:14:42 -0400
On Saturday, May 31, 2003, at 05:27 PM, Bill Cheeseman wrote:
on 03-05-31 1:47 PM, Jim Correia at email@hidden wrote:
Something else entirely?
I create mine manually while I'm writing code, because I like to
organize my
.strings files to match the organization of my code files.
That brings up another question I forgot to ask.
Do people generally just inline NSLocalizedString(@"blah", @"blah
comment) as necessary, or define them someplace
#define BLAH_STRING NSLocalizedString(@"blah", @"blah comment)
(I'm used to defines/constants for STR# stuff in carbon, but this is a
sort of different beast. Still it is sometimes easier to have a string
local to where you use it, and sometimes convenient for them to be all
in one place.)
Since genstrings only collates duplicate strings in one file it seems
the define/constant route will minimize effort during localization for
strings that tend to be reused.
So what do people with large cocoa apps tend to do? (As a point of
reference it looks like the Omni frameworks just use the macros inline
as necessary.)
Jim
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.