From: Petr Ruzicka <firstname.lastname@example.org>
Subject: Re: Question about date format
Date: Mon, 25 May 2009 09:19:07 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
so for the record, setting that fixed my issue was
"(set-w32-system-coding-system 'iso-8859-2)". Original value was
Everything works just fine now.
On Fri, Feb 27, 2009 at 6:52 PM, Petr Ruzicka <firstname.lastname@example.org> wrote:
> So I guess it's more Emacs thing than Org, could someone please kick me in a
> right direction as I'm really lost.
> Thank you
> Petr Ruzicka
> On Fri, Feb 27, 2009 at 4:41 PM, Carsten Dominik <email@example.com>
>> On Feb 27, 2009, at 3:01 PM, Giovanni Ridolfi wrote:
>>> --- Gio 26/2/09, Petr Ruzicka <firstname.lastname@example.org> ha scritto:
>>>> I'm using Org on Windows with Czech enviroment.
>>> Hi, Petr,
>>> I'm using M$Widows XP in an Italian environment.
>>> Emacs 22.3 and Emacs 23.0.9
>>> The abbreviations of weekdays are correct in Italian:
>>> DEADLINE: <2009-01-14 mer +1m> CLOSED: [2009-02-27 ven 14:08]
>>> and have nothing special in my .emacs
>>>> [2009-02-26 èt 02:36]", it should be
>>>> [2009-02-26 čt 02:36]".
>>> I think the problem is the accented letter in the time format.
>>> + Perhaps the time and date format of Emacs/Org-mode
>>> does not use UTF-8.
>>> + Carsten, could it be a bug of Emacs itself?
>> The time string comes directly from `format-time-string', an Emacs
>> - Carsten
prev parent reply other threads:[~2009-05-25 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 1:52 Question about date format Petr Ruzicka
2009-02-27 14:01 ` Giovanni Ridolfi
2009-02-27 14:58 ` Petr Ruzicka
2009-02-27 15:41 ` Carsten Dominik
2009-02-27 16:52 ` Petr Ruzicka
2009-05-25 7:19 ` Petr Ruzicka [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).