Trouble with unicode, I think
Trouble with unicode, I think
- Subject: Trouble with unicode, I think
- From: Mark Patterson <email@hidden>
- Date: Wed, 1 Sep 2004 13:52:00 +1000
Hi,
I had been experimenting with the russian keyboard to get to learn
about unicode, and then fired up xcode, and accidentally entered and
deleted some russian characters. When I tried to build, that file was
giving me errors that didn't seem to make sense, about character /378
(from memory, probably wrong) in the first line.
I looked at the offending .m file in HexEditor (from ex-cinder.com),
and noticed that the file was encoded in utf-16. D'Oh. I guess GCC
doesn't handle that yet. But it was a difficult thing to restore it.
Why does the editor allow it if the rest of the system is going to give
up on it?
I used SubEthaEdit, which confirmed that it was in utf-16, did some
copy-and-pasting to a new window, saved it as utf-8 and tried to open
it in x-code. This time it looked like Chinese, and was all on one
line. It looked like objective-C in SubEthaEdit, and chinese pictograms
in xcocde.
In the end I deleted the files and reconstructed them in XCode. A lot
of time wasted.
Is this a known issue?
=== Mark
_______________________________________________
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.