• 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: file encoding
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: file encoding


  • Subject: Re: file encoding
  • From: Alexey Proskuryakov <email@hidden>
  • Date: Tue, 07 Feb 2006 11:48:41 +0300
  • Thread-topic: file encoding

On 07.02.2006 00:04, "Howard Shere" <email@hidden> wrote:

> If I change the encoding of the file in Xcode 2.x to utf16 and tell it
> to reinterpret then I can see the text correctly except for those same
> characters which were changed in Xcode 1.5.
>
> Clearly the files are messed up. I am looking for the right process to
> fix them. I think they should all be utf16

  I think TextWrangler is the best tool for fixing problems like this - it
should remove the extra zero bytes either automatically on open, or with
Text->Zap Gremlins, if the file encoding is set to UTF-8 or MacRoman. Then,
it's straightforward to convert the files to UTF-16.

  If TextWrangler guesses a wrong encoding for the file, File->Open has a
way to override this, and there's also File->Reopen Using Encoding.

- WBR, Alexey Proskuryakov


 _______________________________________________
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

References: 
 >file encoding (From: Howard Shere <email@hidden>)

  • Prev by Date: Re: Upgrade Error: Xcode 2.2 & GCC 4.0.1
  • Next by Date: Re: STL vector debugging
  • Previous by thread: file encoding
  • Next by thread: STL vector debugging
  • Index(es):
    • Date
    • Thread