Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I now get "invalid byte sequence in UTF-8". Are 160.chr and 194.chr not valid UTF-8 characters? Commented Sep 8, 2010 at 14:45
  • Dunno, apparently not. Why not place the actual characters in there instead of the bytes. Or cast the string itself to ASCII-8BIT? Commented Sep 10, 2010 at 8:04