Package: elinks Version: 0.13.2-1+b1 Severity: important I have all my personal web pages ending in the their ISO language code as extension, so the Apache server chooses the appropriate one according to the Accepted-Language HTTP header from the browser. This means all my files are named like
foo.xhtml.en foo.xhtml.es This is necessary in my case, and common practice. ELinks chokes at this, though, because it relies on extension rather than content for identifying HTML and the extension isn't .xhtml nor .html. The consequence is they aren't recognized as HTML, but as application/something, forcing you to open the file as binary and parse it afterwards as HTML with ^\. As soon as I link any of these files to .xhtml extension and open them from that name they are recognized immediately. It's the same with .html. I think there are two possible solutions to this: 1. Adapting to Apache's naming convention and so recognizing all ISO language codes as extension. 2. Relying on content instead of extension, which means just making Elusive try to parse the file, and is, IMHO, the correct solution.
