Your message dated Mon, 27 Apr 2015 13:33:28 +0200
with message-id <[email protected]>
and subject line was apparently fixed a long time ago
has caused the Debian Bug report #561744,
regarding lynx-cur: lynx doesn't handle URIs with non-ASCII characters correctly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
561744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561744
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lynx-cur
Version: 2.8.8dev.1-1
Severity: normal

With the first attached file, the first two URIs are not handled
correctly: the "è" character is replaced by %E8 instead of %C3%A8
as required by the XML spec (so that the document isn't found):

  http://www.w3.org/TR/xmlschema-2/#anyURI
  http://www.w3.org/TR/xlink/#link-locators

Note: It is not clear whether non-ASCII characters are allowed in
XHTML 1.0: they are allowed in XML and the document validates, but
they are forbidden in HTML 4. Anyway the HTML 4 spec says how they
should be handled (i.e. in the same way as in XLink):

  http://www.w3.org/TR/html4/appendix/notes.html#non-ascii-chars

Everything works fine with the second file. This shows that lynx
uses the encoding of the document to decide what to do (which is
bad).

Also note that in both files, NFD doesn't work, but I assume that's
a problem with the XLink spec and/or the web server (really, when
typing a URL, the user shouldn't care whether an accented character
is represented using NFC or NFD).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages lynx-cur depends on:
ii  debconf [debconf-2.0]  1.5.28            Debian configuration management sy
ii  libbsd0                0.1.6-1           utility functions from BSD systems
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libgcrypt11            1.4.5-1           LGPL Crypto library - runtime libr
ii  libgnutls26            2.8.5-2           the GNU TLS library - runtime libr
ii  libncursesw5           5.7+20090803-2    shared libraries for terminal hand
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages lynx-cur recommends:
ii  mime-support                  3.48-1     MIME files 'mime.types' & 'mailcap

Versions of packages lynx-cur suggests:
pn  lynx-cur-wrapper              <none>     (no description available)

-- debconf information excluded
Title: Test of Accented Characters in URLs

With NFC:

With NFD:

Title: Test of Accented Characters in URLs

With NFC:

With NFD:


--- End Message ---
--- Begin Message ---
Version: 2.8.8dev.5-1

A new test can be found on:

  https://www.vinc17.net/test/url-accented-latin1.html

I could check with lynx-cur 2.8.8dev.5-1, 2.8.8dev.12-2 and 2.8.9dev5-2
that the resolved URL's are correct, e.g.

  https://www.google.com/search?q=%C3%A8

for the first three.

  https://www.google.com/search?q=è
  https://www.google.com/search?q=&#xe8;
  https://www.google.com/search?q=%C3%A8

(which makes all search engines happy). Thus closing.

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---

Reply via email to