From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: gnus-icalendar international character handling
Date: Thu, 25 Feb 2016 14:18:56 +0100 [thread overview]
Message-ID: <20160225131856.GA20460@tuxteam.de> (raw)
In-Reply-To: <87bn752ao6.fsf@otenet.gr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Feb 25, 2016 at 03:15:37PM +0200, Kostas Zorbadelos wrote:
>
> Hi,
>
> this fix (removing the localized day) does not seem to fix the
> international character display of calendar events and their export to
> org files. Also, there is the timezone issue I mentioned in the other
> thread.
>
> For the record, saving the calendar MIME part (gnus-mime-save-part) and
> then importing it to a diary file with (icalendar-import-file) seems to
> work really well (handling international characters and timezone).
This is an interesting point. I haven't been following closely -- so
apologies if I'm asking something answered before, but could it be that
gnus is looking at the wrong header? Each MIME part of the multipart
message may have a different "charset" sub attribute.
Have a look at the "raw" message, perhaps there's a clue.
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlbO/0AACgkQBcgs9XrR2kZQlwCeOMJT9VrqEK3QgmWaJgCW4WAw
oDUAnjwWmPWzC6YubpqWmXDsx87T1WXh
=9qz5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-02-25 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5501.1456224411.843.help-gnu-emacs@gnu.org>
2016-02-24 1:13 ` gnus-icalendar international character handling Lars Magne Ingebrigtsen
2016-02-24 8:56 ` Jan Tatarik
2016-02-24 9:05 ` Jan Tatarik
2016-02-25 13:15 ` Kostas Zorbadelos
2016-02-25 13:18 ` tomas [this message]
2016-02-26 5:35 ` Lars Ingebrigtsen
2016-02-26 7:28 ` Kostas Zorbadelos
2016-02-26 5:35 ` Lars Ingebrigtsen
2016-02-23 10:46 Kostas Zorbadelos
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=20160225131856.GA20460@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.