Joe,
Thanks for your explanation, but
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?
The preview in the finder shows the text properly, and so does
NeoOffice...
OK, so the Finder and NeoOffice are guessing correctly.
I tried UTF16, MacRoman without any luck with Textedit.
Who knows what TextEdit is guessing? I'm sure it will tell you
somewhere if you poke around enough.
So, the question is : What shall I use to be sure that any
Wordprocessor/Text Editor will display my file correctly on Mac, on
Windows and in a multiplatform way?
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...?
Best regards,
Youri
Is there somewhere in a text file that we can specify the encoding
used
at the creation, so the Wordprocessor will know?
Nope -- apart from, perhaps, a byte-order mark, which some text editors
will recognize and others will not.
_______________________________________________
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>
