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 appreciate your point, but I am at a loss to fully understand: what problems do you exactly see with embedding the unicode string? I thought this would be more legible...people touching the code would immediately see hat they are doing, which wouldnt be the case with unicode escape sequences. by the way, this is for a fun project. and thanks for those links Commented Jan 17, 2010 at 17:27
  • For a range of (mostly) English alphabet characters, the byte values of encoded characters are the same for a file encoded as UTF-8, MacRoman or Windows-1252. But, a character like À (\u00C0) will be stored as the bytes C3 80, CB and C0 respectively. Copying the file to another PC will require you to document the encoding so that other people can edit and compile the code correctly. That isn't a huge problem - and may be the best approach if you're writing a non-English application. Commented Jan 17, 2010 at 18:19