Je 2012-Jan-02 je 20:01, Klaus-Peter Wegge skribis: > Dear Lynx Team, > > URLs with non-ascii characers are getting more popular in Europe. > For example: http://www.hörkomm.de (German site). > > lynx releases (2.8.6 and 2.8.7) cannot deal with such URLs on my suse or > debian mashines, while various grafic browsers and even LINKS on the > same systems can handel such URLs. More precisely: > lynx cannot connect the remote host for this URLs.
I don't know what the other people are doing wrong. That URL works for me in Firefox. It only works in Lynx when I get the ASCII representation via the idn command-line program (that is, http://www.xn--hrkomm-wxa.de) . One wonders why Lynx is built with libidn [1] if it can't accept that from either the command line (where it escapes the domain name as if it were a file name) or in the program itself (where no decoding is done). [1] It's definitely linked with libidn: $ ldd `which lynx` linux-gate.so.1 => (0xffffe000) libz.so.1 => /usr/lib/libz.so.1 (0xb77e0000) libbz2.so.1 => /usr/lib/libbz2.so.1 (0xb77cf000) libidn.so.11 => /usr/lib/libidn.so.11 (0xb779c000) libslang.so.2 => /usr/lib/libslang.so.2 (0xb7678000) libm.so.6 => /lib/i686/libm.so.6 (0xb762f000) libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0xb75d6000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0xb7409000) libdl.so.2 => /lib/libdl.so.2 (0xb7404000) libpthread.so.0 => /lib/i686/libpthread.so.0 (0xb73ea000) libc.so.6 => /lib/i686/libc.so.6 (0xb726c000) /lib/ld-linux.so.2 (0xb77f9000) _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
