On Nov 17, 2006, at 23:25 UTC, Youri wrote: > > This just means that TextEdit hasn't properly guessed the text > > encoding. You could make it guess a little better by writing out a > > byte-order mark at the beginning of the file, or you can just tell > > TextEdit to open this as UTF-8. > > How do you do this?
I had to look this one up myself, as it's been a while... see question 10 in: <http://support.realsoftware.com/listarchives/realbasic-nug/2004-02/msg00615.html> > > You can't. It's up to the individual reader app; some are smarter than > > others, but there is generally NO fool-proof way to know what encoding > > a particular text file might be. > > Ok, but how is it that when we receive text files every day we just > double-clic on them and they open fine in Word, NeoOffice, Appleworks > etc...? Sounds like you've been very lucky in the past. I've had all of those apps (well, not NeoOffice, which I've never heard of before) improperly open text files from time to time. Such is life, alas. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
