Re: MacRoman -> UTF8 [solved]

On 3/22/09 4:29 PM, Peter Duniho said: >Of particular note is Apple's own mail archive for the mailing list. >Maybe they've fixed it recently... Apple's archives are not a nice as cocoabuilder's (which I highly recommend), which seems to thread correctly even if the subject changes, see:

Re: MacRoman -> UTF8 [solved]

On Sun, Mar 22, 2009 at 5:22 AM, Uli Kusterer wrote: > On 22.03.2009, at 12:22, Michael Ash wrote: >> >> On Sun, Mar 22, 2009 at 3:48 AM, Ben Lachman wrote: >>> >>> Just for the record, this was an issue with my HTTP content type settings >>> and the charset that the input was encoded in, not any

Re: MacRoman -> UTF8 [solved]

On Sun, Mar 22, 2009 at 8:22 AM, Uli Kusterer wrote: > On 22.03.2009, at 12:22, Michael Ash wrote: >> >> On Sun, Mar 22, 2009 at 3:48 AM, Ben Lachman wrote: >>> >>> Just for the record, this was an issue with my HTTP content type settings >>> and the charset that the input was encoded in, not any

Re: MacRoman -> UTF8 [solved]

On Mar 22, 2009, at 5:22 AM, Uli Kusterer wrote: On 22.03.2009, at 12:22, Michael Ash wrote: Just a general request for the list here: could we not add "[solved]" to the topic when the problem is solved? It breaks threading and causes confusion. Just stick it into the original thread. The act o

Re: MacRoman -> UTF8 [solved]

On 22.03.2009, at 12:22, Michael Ash wrote: On Sun, Mar 22, 2009 at 3:48 AM, Ben Lachman wrote: Just for the record, this was an issue with my HTTP content type settings and the charset that the input was encoded in, not any issue with NSString. Just a general request for the list here: co

Re: MacRoman -> UTF8 [solved]

On Sun, Mar 22, 2009 at 3:48 AM, Ben Lachman wrote: > Just for the record, this was an issue with my HTTP content type settings > and the charset that the input was encoded in, not any issue with NSString. Just a general request for the list here: could we not add "[solved]" to the topic when the

Re: MacRoman -> UTF8 [solved]

Just for the record, this was an issue with my HTTP content type settings and the charset that the input was encoded in, not any issue with NSString. ->Ben -- Ben Lachman Acacia Tree Software http://acaciatreesoftware.com email: blach...@mac.com twitter: @benlachman mobile: 740.590.0009

Re: MacRoman -> UTF8

On Sat, Mar 21, 2009 at 3:50 PM, Ben Lachman wrote: > On Mar 21, 2009, at 5:38 PM, Clark Cox wrote: > >> On Sat, Mar 21, 2009 at 2:31 PM, Ben Lachman wrote: >>> >>> My software uses UTF8 almost exclusively.  However, for some odd reason, >>> arguments passed from a perl cgi script to one of my co

Re: MacRoman -> UTF8

On Sat, Mar 21, 2009 at 6:50 PM, Ben Lachman wrote: >>>  That's not a problem since I can just use >>> [NSString stringWithCString:argv[i] encoding:NSMacOSRomanStringEncoding]. >>>  However it seems that one can't convert MacRoman -> UTF8 after you get >>> it >>> into a NSString. >> >> I don't kno

Re: MacRoman -> UTF8

On Sat, Mar 21, 2009 at 5:50 PM, Ben Lachman wrote: > Thats what I thought. However, say I start by reading "bén" as I noted > above, then I call printf("%s", [myStringReadFromMacRoman UTF8String]) and > it prints "bÈn". However if I call printf("%s", [myStringReadFromMacRoman > cStringUsingEnc

Re: MacRoman -> UTF8

On Mar 21, 2009, at 5:38 PM, Clark Cox wrote: On Sat, Mar 21, 2009 at 2:31 PM, Ben Lachman wrote: My software uses UTF8 almost exclusively. However, for some odd reason, arguments passed from a perl cgi script to one of my command line helper apps are encoded as MacRoman. Where is the C

Re: MacRoman -> UTF8

On Sat, Mar 21, 2009 at 2:31 PM, Ben Lachman wrote: > My software uses UTF8 almost exclusively.  However, for some odd reason, > arguments passed from a perl cgi script to one of my command line helper > apps are encoded as MacRoman. Where is the CGI script getting the text, and what encoding doe