• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: newbie unicode problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: newbie unicode problem


  • Subject: Re: newbie unicode problem
  • From: j o a r <email@hidden>
  • Date: Mon, 31 Jan 2005 10:29:49 +0100


On 2005-01-31, at 10.09, Daniel Child wrote:

I have tried UTF-8 as the encoding for source files, but that didn't work. (Naturally I set appropriate fonts for the textfields in the IB window.) Actually, UTF16 seems like a more logical choice, but for some reason, if I set source files to UTF16, I get a string of warnings and errors about invalid characters when I build and run.

If I were you I would not assume that I could enter these strings in your source files. At the very least read about all the problems people usually have when attempting to do so in the list archives.


That said, if you only get strings from the user interface at runtime, you shouldn't have to think about encodings at all (as long as you're not converting your NSStrings into something else, in which case you do).

j o a r

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >newbie unicode problem (From: Daniel Child <email@hidden>)

  • Prev by Date: CFPasteboardResolveAllPromisedData crash
  • Next by Date: Re: NSMenuItem setKeyEquivalentModifierMask not working as expected
  • Previous by thread: Re: newbie unicode problem
  • Next by thread: Re: newbie unicode problem
  • Index(es):
    • Date
    • Thread