GNU bug report logs -
#14908
Problem opening attachments that contain umlauts
Previous Next
Reported by: Stefan Reichör <stefan <at> xsteve.at>
Date: Fri, 19 Jul 2013 13:04:02 UTC
Severity: normal
Found in version 5.13
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 14908 in the body.
You can then email your comments to 14908 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bugs <at> gnus.org
:
bug#14908
; Package
gnus
.
(Fri, 19 Jul 2013 13:04:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Stefan Reichör <stefan <at> xsteve.at>
:
New bug report received and forwarded. Copy sent to
bugs <at> gnus.org
.
(Fri, 19 Jul 2013 13:04:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hallo There,
I am not sure if it is an emacs misconfiguration or a gnus problem.
When I get an attachment that contains umlauts in the filename I am not
able to open it (I have to save it first and then I can open it)
I have attached a small pdf file without an umlaut and one containig an umlaut.
Stefan.
Gnus v5.13
GNU Emacs 24.3.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4)
of 2013-07-11 on ubu64
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
100 Legal commands
ARTICLE [message-ID|number]
AUTHINFO USER name|PASS password|GENERIC program [argument ...]
BODY [message-ID|number]
CAPABILITIES [keyword]
DATE
GROUP newsgroup
HDR header [message-ID|range]
HEAD [message-ID|number]
HELP
IHAVE message-ID
LAST
LIST [ACTIVE [wildmat]|ACTIVE.TIMES [wildmat]|DISTRIB.PATS|DISTRIBUTIONS|HEADERS [MSGID|RANGE]|MODERATORS|MOTD|NEWSGROUPS [wildmat]|OVERVIEW.FMT|SUBSCRIPTIONS]
LISTGROUP [newsgroup [range]]
MODE READER
NEWGROUPS [yy]yymmdd hhmmss [GMT]
NEWNEWS wildmat [yy]yymmdd hhmmss [GMT]
NEXT
OVER [range]
POST
QUIT
STARTTLS
STAT [message-ID|number]
XGTITLE [wildmat]
XHDR header [message-ID|range]
XOVER [range]
XPAT header message-ID|range pattern [pattern ...]
Report problems to <usenet <at> ger.gmane.org>.
.
382 Begin TLS negotiation now
100 Legal commands
ARTICLE [message-ID|number]
AUTHINFO USER name|PASS password|GENERIC program [argument ...]
BODY [message-ID|number]
CAPABILITIES [keyword]
DATE
GROUP newsgroup
HDR header [message-ID|range]
HEAD [message-ID|number]
HELP
IHAVE message-ID
LAST
LIST [ACTIVE [wildmat]|ACTIVE.TIMES [wildmat]|DISTRIB.PATS|DISTRIBUTIONS|HEADERS [MSGID|RANGE]|MODERATORS|MOTD|NEWSGROUPS [wildmat]|OVERVIEW.FMT|SUBSCRIPTIONS]
LISTGROUP [newsgroup [range]]
MODE READER
NEWGROUPS [yy]yymmdd hhmmss [GMT]
NEWNEWS wildmat [yy]yymmdd hhmmss [GMT]
NEXT
OVER [range]
POST
QUIT
STARTTLS
STAT [message-ID|number]
XGTITLE [wildmat]
XHDR header [message-ID|range]
XOVER [range]
XPAT header message-ID|range pattern [pattern ...]
Report problems to <usenet <at> ger.gmane.org>.
.
[ö.pdf (application/pdf, attachment)]
[a.pdf (application/pdf, attachment)]
Information forwarded
to
bugs <at> gnus.org
:
bug#14908
; Package
gnus
.
(Fri, 31 Jan 2014 00:46:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 14908 <at> debbugs.gnu.org (full text, mbox):
Stefan Reichör <stefan <at> xsteve.at> writes:
> I am not sure if it is an emacs misconfiguration or a gnus problem.
>
> When I get an attachment that contains umlauts in the filename I am not
> able to open it (I have to save it first and then I can open it)
>
> I have attached a small pdf file without an umlaut and one containig an umlaut.
I'm unable to reproduce this bug.
These are the messages I get when I hit `RET' on the two attachments:
Viewing with /usr/bin/xdg-open %s
Displaying /usr/bin/xdg-open /tmp/emm.2023yDH/\ö.pdf...done
Viewing with /usr/bin/xdg-open %s
Displaying /usr/bin/xdg-open /tmp/emm.2023_NN/a.pdf...done
What messages do you get?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Information forwarded
to
bugs <at> gnus.org
:
bug#14908
; Package
gnus
.
(Fri, 31 Jan 2014 08:22:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 14908 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Lars!
Thanks for looking into this.
> Stefan Reichör <stefan <at> xsteve.at> writes:
>
>> I am not sure if it is an emacs misconfiguration or a gnus problem.
>>
>> When I get an attachment that contains umlauts in the filename I am not
>> able to open it (I have to save it first and then I can open it)
>>
>> I have attached a small pdf file without an umlaut and one containig an umlaut.
>
> I'm unable to reproduce this bug.
>
> These are the messages I get when I hit `RET' on the two attachments:
>
> Viewing with /usr/bin/xdg-open %s
> Displaying /usr/bin/xdg-open /tmp/emm.2023yDH/\ö.pdf...done
> Viewing with /usr/bin/xdg-open %s
> Displaying /usr/bin/xdg-open /tmp/emm.2023_NN/a.pdf...done
>
> What messages do you get?
First I used evince to open pdf files. However switching to xdg-open
does not fix the problem for me:
Viewing with /usr/bin/xdg-open %s
Displaying /usr/bin/xdg-open /tmp/emm.8325I4U/a.pdf...done
Viewing with /usr/bin/xdg-open %s
Displaying /usr/bin/xdg-open /tmp/emm.8325VCb/\ö.pdf...done
xdg-open: file '/tmp/emm.8325VCb/ö.pdf' does not exist
Now I tried the following: I use the log-arg.py script to find out about
the file name that is sent to the external process (put the following
line in ~/.mailcap):
application/pdf; /home/srei/log-arg.py %s; test=test "$DISPLAY" != ""; description=Portable Document Format; nametemplate=%s.pdf
Now I see that ö is encoded as latin-1:
Char: ö (246, #o366, #xf6, file #xF6) point=18 of 23 (74%) column=17
I guess my system expects unicode.
I invoked the log-arg.py script from the shell and get cmd-arg1-shell.
I use the following setup in my .emacs:
(prefer-coding-system 'utf-8)
(set-default-coding-systems 'utf-8)
(setq file-name-coding-system 'utf-8)
(setq-default buffer-file-coding-system 'iso-latin-1)
(set-language-environment 'Latin-1)
Thanks,
Stefan.
[log-arg.py (text/x-python, attachment)]
[cmd-arg1 (application/octet-stream, attachment)]
[cmd-arg1-shell (application/octet-stream, attachment)]
Information forwarded
to
bugs <at> gnus.org
:
bug#14908
; Package
gnus
.
(Fri, 31 Jan 2014 08:28:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 14908 <at> debbugs.gnu.org (full text, mbox):
Hi Lars!
> Hi Lars!
>
> Thanks for looking into this.
>
>> Stefan Reichör <stefan <at> xsteve.at> writes:
>>
>>> I am not sure if it is an emacs misconfiguration or a gnus problem.
>>>
>>> When I get an attachment that contains umlauts in the filename I am not
>>> able to open it (I have to save it first and then I can open it)
>>>
>>> I have attached a small pdf file without an umlaut and one containig an umlaut.
>>
>> I'm unable to reproduce this bug.
>>
>> These are the messages I get when I hit `RET' on the two attachments:
>>
>> Viewing with /usr/bin/xdg-open %s
>> Displaying /usr/bin/xdg-open /tmp/emm.2023yDH/\ö.pdf...done
>> Viewing with /usr/bin/xdg-open %s
>> Displaying /usr/bin/xdg-open /tmp/emm.2023_NN/a.pdf...done
>>
>> What messages do you get?
>
> First I used evince to open pdf files. However switching to xdg-open
> does not fix the problem for me:
>
> Viewing with /usr/bin/xdg-open %s
> Displaying /usr/bin/xdg-open /tmp/emm.8325I4U/a.pdf...done
> Viewing with /usr/bin/xdg-open %s
> Displaying /usr/bin/xdg-open /tmp/emm.8325VCb/\ö.pdf...done
>
> xdg-open: file '/tmp/emm.8325VCb/ö.pdf' does not exist
>
> Now I tried the following: I use the log-arg.py script to find out about
> the file name that is sent to the external process (put the following
> line in ~/.mailcap):
> application/pdf; /home/srei/log-arg.py %s; test=test "$DISPLAY" != ""; description=Portable Document Format; nametemplate=%s.pdf
>
> Now I see that ö is encoded as latin-1:
> Char: ö (246, #o366, #xf6, file #xF6) point=18 of 23 (74%) column=17
>
> I guess my system expects unicode.
> I invoked the log-arg.py script from the shell and get cmd-arg1-shell.
>
> I use the following setup in my .emacs:
>
> (prefer-coding-system 'utf-8)
> (set-default-coding-systems 'utf-8)
> (setq file-name-coding-system 'utf-8)
> (setq-default buffer-file-coding-system 'iso-latin-1)
> (set-language-environment 'Latin-1)
I found the problem:
I removed "(set-language-environment 'Latin-1)" from my .emacs and now it works :-)
Without your feedback that this works for you I wouldn't have been able to track this down.
Thanks again!
Stefan.
bug closed, send any further explanations to
14908 <at> debbugs.gnu.org and Stefan Reichör <stefan <at> xsteve.at>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 31 Jan 2014 08:29:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 28 Feb 2014 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 11 years and 111 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.