On May 03, 2006, at 12:04 UTC, Arnaud Nicolet wrote: > That explain the fact that an encoding is not specified in a text > file (obvious, but was somehow a > mystery).
In a less insane world, this wouldn't be a problem on the Mac, since we could have text files that are pure text in the data fork, and contain an encoding indicator in the resource fork. Any good Mac app would know how to read and write that extra data so that encodings would almost always be known. But, resource forks weren't used at NeXT, so Apple has thrown them out and in this way (and many others), now has the same problem as any other OS. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Available for custom REALbasic programming or instruction. _______________________________________________ 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>
