Re: new nonempty files have wrong encoding information
Re: new nonempty files have wrong encoding information
- Subject: Re: new nonempty files have wrong encoding information
- From: David Ewing <email@hidden>
- Date: Fri, 12 Mar 2004 10:57:22 -0700
On Mar 11, 2004, at 7:10 PM, John Karp wrote:
When I create a new cocoa bjective c file in a project, it is always
in UTF-16 encoding regardless which encoding I have choosen in
Preference for Text Editing. So I have to "Reinterpret" the skeleton
file as UTF-16. Since gcc only understands 8 bit code, I then have to
convert it to UTF-8 or other encoding compatiable with 8-bit code. I
haven't tried other cases, but I am guessing that that this is due to
the template files themselves being in UTF-16 encoding and somehow my
preference setting is not being respected by the new file menu
command. What is the fix for this annonyance? Please point me to
earlier post if it has been addressed (I searced but did not find
anything.)
This is a known issue. But I don't think the files start out as UTF-16.
They should start out with an 8-bit encoding. I don't recall which one,
but it should be compatible with gcc. Reinterpreting the encoding as
UTF-8 should be safe. What is your default encoding set to in your
preferences?
Dave
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.