Thomas Dickey dixit: >> Here under Windows there are constant references to the character that >> begins a 16-bit-wide-character file (FF FE) or UTF-8 file (EF BB BF).
Note that this is not about Windows® though – the Byte Order Mark,
Unicode FEFF, UCS-2BE 0xFE 0xFF, UCS-2LE 0xFF 0xFE, UTF-8 0xEF 0xBB 0xBF,
is a standardised thing.
> Lynx handles _some_ cases - but a url would help, so we can see.
Attached.
Lynx handles all three poorly: the UTF-8 BOM isn’t stripped, the UCS-2
files end with an ampersand instead of the … (ellipsis).
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2<html><head> <title>Testdokument</title> </head><body> <p>Nix zu sehen…</p> </body></html>
ucs2le.htm
Description: Binary data
ucs2be.htm
Description: Binary data
_______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
