Re: genstrings
Re: genstrings
- Subject: Re: genstrings
- From: Chuck Soper <email@hidden>
- Date: Fri, 5 Mar 2004 18:40:10 -0800
At 8:18 PM -0600 3/5/04, Kevin Grant wrote:
I use genstrings to create .strings files. I just discovered that
it scans all text in source files including commented lines. Is
this known behavior? Should I file a bug report? . . . .
It almost certainly isn't aware of all possible C language syntax
and doesn't compile files, e.g. because I can't use a macro or a
constant, I must always use a real quoted string. I can't really
blame them for not putting an entire C language parser into
genstrings.
You can probably fool it pretty easily to fix the problem, e.g.
adding spaces so you have "NS LocalizedString" instead of
NSLocalizedString within your comments, etc.
Kevin G.
http://homepage.mac.com/kmg/
mail to kevin at ieee dot org
Kevin,
Thanks for the suggestion of adding a space to NSLocalizedString.
That's a good simple solution.
I really think that genstrings could (or should?) be aware of some
(certainly not all) C language syntax. The issue I found could lead
to translating unneeded strings and paying for that translation. I'll
file a problem report.
On the other hand, if it's expected behavior I suppose it could be a
feature for some users.
Chuck
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.