From: Mario Peter <empee0@gmail.com>
To: ding <ding@gnus.org>
Subject: gnus-icalendar utf-8 charset issue
Date: Wed, 27 Nov 2013 18:43:14 +0100 [thread overview]
Message-ID: <8761rdhhal.fsf@gmail.com> (raw)
Hi again,
I wonder if anybody has a working gnus-icalendar setup with german
umlauts. I see the following if the vcal attachment consists utf-8 coded
umlauts:
,----
| Summary: Kl\303\244rung der Fragen
| Location: +4969 2222 16176 #266 4422 313
| Time: <2013-11-29 Fri 10:30-11:30>
| Attendance: Optional
| Method: REQUEST
| Status: Not replied yet
|
| Hallo,
|
| nach Abgleich der Kalender ist es doch vor Freitag nicht m\303\266glich
| gewesen einen passenden Termin zu finden.
`----
The rest of the buffer (headers etc) shows umlauts as usual, only the
vcalendar entries plus description are affected.
The buffer coding system is utf-8-unix
Can you help?
regards, Mario
--
Mario Peter
de,pl,en
http://www.mpeter.de
next reply other threads:[~2013-11-27 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:43 Mario Peter [this message]
2013-11-27 23:56 ` Jan Tatarik
2013-11-28 14:49 ` Mario Peter
2013-11-28 20:50 ` Jan Tatarik
2013-11-28 22:39 ` Mario Peter
2013-11-29 8:07 ` Jan Tatarik
2013-11-29 21:04 ` Jan Tatarik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761rdhhal.fsf@gmail.com \
--to=empee0@gmail.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).