> On Tue, Jun 25, 2013 at 03:48:37AM EDT, Lars Bjørndal wrote: >> On intranet at work, there sometimes happens to be unicode (UTF-8) >> characters such as a Norwegian ø in the filename. With lynx I can >> retrieve these files, but not with elinks. [...]
* Chris Jones <cjns1...@gmail.com> [13-06/25=Tu 18:37 -0400]: > I did the following to create a test file: > % echo 'øøøøøø' > /tmp/file-ø > Pointed elinks to /tmp/file-ø > and was able to display the file's content successfully. > Vim tells me that the characters in the file are U+00F8. [...] Lars's email, including the From header, was encoded in ISO-8859-1 (aka Latin-1), not UTF-8, and \370 is the Latin-1 encoding of small letter o with stroke; the UTF-8 encoding for that would be \303\270. Lars also says "unicode (UTF-8)", suggesting a confusion; they are not synonymous. Chris reports that Vim reports that the file was encoded in Latin-1. Perhaps Lars is using multiple encodings without realizing it. It's particularly easy for an X-based desktop to have encodings different from those selected by environment variables in terminal sessions, and those encodings might differ from that of the filesystem. _______________________________________________ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
