Yeah, my statement my have been a bit ambiguous.
What I meant is the "tools" shipped with Xcode 3.0 and later supports
UTF-8 in constant strings 8-).
The tools include genstrings.
And, please file a bug for updating the doc.
Thanks,
Aki
On 2008/08/15, at 13:32, Sean McBride wrote:
On 8/15/08 1:13 PM, Aki Inoue said:
Yes, the compiler shipped with Xcode 3.0 and later supports UTF-8 in
constant strings.
Aki,
Thanks for your reply.
I'm not sure you understood however. I know that the compiler accepts
UTF8 in constant NSStrings, but what I'm not sure about is the
'genstrings' command line tool (see 'man genstrings'). I've tested,
and
genstrings works with non-ASCII strings, but the docs say it
doesn't. I
want to be sure the docs are just old and that I'm not getting lucky.
Still it's recommended to keep your constant strings ASCII-only for
performance.
Well, performance is secondary to correctness.
Thanks,
Sean
Aki
On 2008/08/15, at 12:09, Sean McBride wrote:
Hi all,
The docs for NSLocalizedString() say "In order to be parsed
correctly by
genstrings, 'key' should not contain any high-ASCII characters."
On 10.5.4 / Xcode 3.1, this does not seem to be true. Anyone know
if
the docs are simply out of date? I suspect that since 10.5 now
allows
UTF8 in @"" strings that NSLocalizedString/genstrings were updated
as well.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
