On 4 mars 08, at 11:27, Jean-Daniel Dupas wrote:
Le 4 mars 08 à 11:21, Stephane Sudre a écrit :
On 4 mars 08, at 10:28, Julien Jalon wrote:
1) Might not be a good idea to use CFStringGetCStringPtr as it might
return
NULL2) kCFStringEncodingMacRoman is likely not a good choice as the
enc
Le 4 mars 08 à 11:21, Stephane Sudre a écrit :
On 4 mars 08, at 10:28, Julien Jalon wrote:
1) Might not be a good idea to use CFStringGetCStringPtr as it
might return
NULL2) kCFStringEncodingMacRoman is likely not a good choice as the
encoding, especially for localized strings
If I were y
On 4 mars 08, at 10:28, Julien Jalon wrote:
1) Might not be a good idea to use CFStringGetCStringPtr as it might
return
NULL2) kCFStringEncodingMacRoman is likely not a good choice as the
encoding, especially for localized strings
If I were you, I'd do something like (warning: Mail compiled
1) Might not be a good idea to use CFStringGetCStringPtr as it might return
NULL2) kCFStringEncodingMacRoman is likely not a good choice as the
encoding, especially for localized strings
If I were you, I'd do something like (warning: Mail compiled code):
const char* MyGetLocalizedCString(CFStringR
genstrings doesn't appear to read stdin, but you could run the C
preprocessor on your source file, send it to a temp file, and then run
genstrings on that.
cpp -DSYS_DARWIN mysource.c >/tmp/foo.c
genstrings /tmp/foo.c >outputfile
Deborah Goldsmith
Apple Inc.
[EMAIL PROTECTED]
On Mar 3, 2008
