Re: gcc and unicode support
Re: gcc and unicode support
- Subject: Re: gcc and unicode support
- From: Jean-Daniel Dupas <email@hidden>
- Date: Thu, 10 Jul 2008 00:16:18 +0200
Le 9 juil. 08 à 23:48, Jean-Daniel Dupas a écrit :
Le 9 juil. 08 à 23:45, Ken Thomases a écrit :
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
Xcode see it as utf-8 file too, and I tried using gcc directly and
got the same result.
Don't bother, I had a look at gcc sources, and this is considered as
an objc features, and it's not implemented in cc1 but only in cc1obj.
The warning is completly irrelevant and whatever the charset is, it
will always returns the same output.
But I don't see any good reason :-|
_______________________________________________
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