Package: lynx-cur Version: 2.8.8dev.16-1 Severity: important XHTML is standard, and it's a real bug if a web browser, like lynx, doesn't support it (without relying on displaying the document in some other web browser), as this prevents lynx from displaying some pages. XHTML has no additional features compared to HTML, so that this is just a matter of parsing.
There are two steps: 1. First add full XHTML support. I don't know what is the status of this step. 2. Once (1) has been done, XHTML (application/xhtml+xml) should obviously be accepted by default, i.e. when "Preferred media type" is set to "Accept lynx's internal types". This is currently not the case. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lynx-cur depends on: ii libbsd0 0.6.0-1 ii libbz2-1.0 1.0.6-5 ii libc6 2.17-93 ii libgcrypt11 1.5.3-2 ii libgnutls26 2.12.23-7 ii libidn11 1.28-1 ii libncursesw5 5.9+20130608-1 ii libtinfo5 5.9+20130608-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages lynx-cur recommends: ii mime-support 3.54 lynx-cur suggests no packages. -- debconf information: lynx-cur/etc_lynx.cfg: lynx-cur/defaulturl: http://www.vinc17.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
