Re: gcc and unicode support
Re: gcc and unicode support
- Subject: Re: gcc and unicode support
- From: Ken Thomases <email@hidden>
- Date: Wed, 9 Jul 2008 16:45:53 -0500
On Jul 9, 2008, at 4:34 PM, Jean-Daniel Dupas wrote:
It appears that it does not works with plain c files, but only with
obj-c file whatever that code is.
CFString("hé hé hé") will compile correctly if the file has the .m
extension but not if the file has the .c extension.
warning: main.c:5: warning: input conversion stopped due to an input
byte that does not belong to the input codeset UTF-8
The file is really an utf-8 file (check with Text Edit and
HexFiend). The input codeset is right (gcc tell it expects utf-8 in
the output message).
Is this a bug in the C parser, or is this an expected limitation.
I don't know if it's supposed to work with C files. The thing I would
recommend that you check, though, is what encoding Xcode thinks the
file has. In Xcode, select the file and do Get Info. The encoding is
listed on the General tab.
Cheers,
Ken
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden