30 Jun
2008
30 Jun
'08
11:04 a.m.
On Mon, Jun 30, 2008 at 12:49, Hans-Joerg Bibiko bibiko@eva.mpg.de wrote:
The only definite way to get the encoding is to parse the ENTIRE file or parse to the first byte sequence which determine the used encoding one-to-one. Or one uses the obsolete UTF-8 BOM (byte order marker at the beginning of a file).
Ok... So I guess the real bug is that Quicklook and other utilities decide to fall back on MacRoman instead of utf8.
Thanks for the clarification :-)
Cheers, V