• 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: Illegal byte sequence
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Illegal byte sequence


  • Subject: Re: Illegal byte sequence
  • From: Greg Guerin <email@hidden>
  • Date: Fri, 8 Dec 2006 09:54:40 -0700

Mark Wagner wrote:

>(in case it doesn't come through correctly, that's a whole series of
>characters with values greater than 127).  The file's encoding is set
>to Mac OS Roman.

The way it's arranged looks like it's part of some kind of charset
translation algorithm, but it's not a mapping I recognize.

You should probably change it to use only wide-char escapes, \xNNNN, for
each char.

Personally, I'd probably write a tool for it, copy and paste the text into
a data-file, then run the tool on the data.  The tool should be pretty
easy: read a byte, emit an escape-sequence.  Even if the tool isn't
perfect, it should save a lot of error-prone drudgery.  If the sequence
were shorter, it might be a tossup: tool or manual conversion.

The process would also benefit from a unit test for whatever code uses the
array, to confirm that your changes don't break whatever it's doing.

  -- GG


 _______________________________________________
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

  • Prev by Date: Re: Illegal byte sequence
  • Next by Date: Re: Build slowdown with 4 processors vs. 2 or 1?
  • Previous by thread: Re: Illegal byte sequence
  • Next by thread: Per-processor type framework linking?
  • Index(es):
    • Date
    • Thread