On Mar 30, 2008, at 2:55 PM, Mark O'Neill wrote:
>> According to what? Some tool that doesn't realize this is a UTF-8
>> file, I would say. Most Mac apps these days have some way you can
>> tell them what encoding the file is; check that, correct it (to
>> UTF-8), and you'll see that the data is correct.
>
> But... Surely if the resulting file is a plain text file, it should
> write out plain text?
Of course it does. You do realize that there are hundreds of
different forms of "plain text," right?
> The copyright symbol isn't some bizarre never-
> used character after all, and has been used in ascii for a loooong
> time.
No, it is not and has never been part of the ASCII character set.
> What I mean is, if I write out:
>
> CopyrightText=©
>
> with a TextOutputStream it should appear like that in TextEdit,
> shouldn't it?
If TextEdit happens to correctly guess the encoding of the file,
yes. If not, then no. Such is life in a world where Unicode was
only invented a few years back and is still not universally used.
> I don't see how that's an encoding issue when I'm *writing* to the
> file. Or am I missing something?
Apparently so. Perhaps the text encoding FAQ will help -- please
search the archives for it.
Best,
- Joe
--
Joe Strout
Inspiring Applications, Inc.
http://www.InspiringApps.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|