GNU bug report logs -
#20231
25.0.50; package.el mangles non-ascii content in downloaded archive-contents data
Previous Next
Reported by: Steve Purcell <steve <at> sanityinc.com>
Date: Mon, 30 Mar 2015 16:23:02 UTC
Severity: normal
Merged with 20010
Found in versions 24.4, 25.0.50
Done: Artur Malabarba <bruce.connor.am <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Ivan Shmakov <ivan <at> siamics.net>
> Date: Sat, 11 Apr 2015 19:30:21 +0000
>
> >>>>> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> […]
>
> >> As insert-file-contents may imply a whole lot of additional
> >> processing beyond decoding UTF-8, I’d rather use an explicit
> >> decode-coding-region here
>
> > Can you explain why? What additional processing can get in the way?
>
> One of the examples I can readily think of is enriched-decode,
> which will automatically be called should there be a
> ‘Content-Type: text/enriched’ line near the top of the file
> being read (per format-alist.)
Yes, but is that kind of processing harmful for the case at point?
Also, are we sure we will never get a compressed file, for example, or
some other binary file? In those cases, decoding is not TRT.
> I have no example at hand of how such processing may be
> triggered in practice, but avoiding it altogether seems to me
> like a saner approach.
It is also slower. Again, I have no idea if speed matters in this
case.
This bug report was last modified 10 years and 31 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.