From: Mario Peter <empee0@gmail.com>
To: ding@gnus.org
Subject: Re: gnus-icalendar utf-8 charset issue
Date: Thu, 28 Nov 2013 23:39:48 +0100 [thread overview]
Message-ID: <87fvqgdubv.fsf@gmail.com> (raw)
In-Reply-To: <87siug2qv3.fsf@nb-jtatarik2.xing.hh> (Jan Tatarik's message of "Thu, 28 Nov 2013 21:50:08 +0100")
On Nov 28 2013, 21:50, Jan Tatarik <jan.tatarik@gmail.com> wrote:
> On Thu, Nov 28 2013, Mario Peter wrote:
>>> Can you share the actual ical attachment?
>> sure ( i removed the whole bunch of attendies)
>
> Hm, that did not help :( I have the same utf-8-unix encoding setup and
> have no trouble with umlauts.
>
> Can you perhaps create and send new appointment, with my email as an
> attendee? So I get to play with the original ical, not a copy-pasted
> one.
I've just sent an invitation via outlook, and this one works
perfectly. Everything looks nice (even the time, my other issu) ...
I'm a little bit confused now.
Mario
--
Mario Peter
de,pl,en
http://www.mpeter.de
next prev parent reply other threads:[~2013-11-28 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:43 Mario Peter
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 [this message]
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=87fvqgdubv.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).