Re: [elinks-users] Support for unicode characters in URL
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. Is there something I can do to get elinks work also with these URLs? 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. % elinks --version ELinks 0.12pre5 I mention the latter because I remember that maybe 2-3 years ago I did have some trouble getting the version of Elinks that came with debian to work with my en_UTF8 locale. I had to build my own from a more recent tarball AFAICR.. With the current version that comes with debian stable, I don't remember doing any kind of customization, so my guess is that whatever problem I had with UTF-8 in the past was fixed and that this should work out of the box with any recent version of Elinks.. CJ -- HOW ARE YOU GENTLEMEN? ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Support for unicode characters in URL
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
