Your message dated Sun, 21 May 2023 03:00:43 +0200
with message-id <20230521010043.GB3652904@bogus>
and subject line Re: Bug#1036444: elinks: relies on file extension for files
instead of content
has caused the Debian Bug report #1036444,
regarding elinks: relies on file extension for files instead of content
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.)
--
1036444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
I tested the version in experimental using the attached file, and it
worked correctly.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761
8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
<html>
<body>
<p> para1
<p> para2
</body>
</html>
signature.asc
Description: PGP signature
--- End Message ---
