From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Philip.Wong@warwick.ac.uk, 34684@debbugs.gnu.org
Subject: bug#34684: 26.1; Strange characters when inserting date
Date: Fri, 01 Mar 2019 16:09:24 +0200 [thread overview]
Message-ID: <837ediit4b.fsf@gnu.org> (raw)
In-Reply-To: <m2lg1yzoye.fsf@gmail.com> (message from Robert Pluim on Fri, 01 Mar 2019 14:47:21 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Philip.Wong@warwick.ac.uk, 34684@debbugs.gnu.org
> Date: Fri, 01 Mar 2019 14:47:21 +0100
>
> > That's only so if the above produces the same garbled result as in the
> > original report. Does it?
>
> Didnʼt I send this yesterday?
>
> $ LANG=zh_HK src/emacs -Q -l ss.el
> (require 'org)
> (org-time-stamp)
> <2019-03-01 五>
>
> I think '五' is 'Five', but donʼt quote me on that.
This is not garbage by any measure. Please compare with what the OP
reported.
In any case, the original report was for Thursday, not Friday. the
former should AFAIU display 四. But neither is nowhere close to the
sequence the OP reported, not even if I break the correct character
into individual bytes, so some other factor is at work here.
> So at least for me itʼs working correctly (in both *scratch* and an
> Org-mode buffer), which means thereʼs something wrong in the
> reporter's configuration somewhere.
What, if anything, is wrong with the OP's configuration is exactly the
issue here. There's no question that current-time and
format-time-string work in general.
next prev parent reply other threads:[~2019-03-01 14:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:16 bug#34684: 26.1; Strange characters when inserting date Wong, Philip
2019-02-28 17:55 ` Eli Zaretskii
2019-02-28 19:11 ` Robert Pluim
2019-02-28 19:15 ` Eric Abrahamsen
2019-02-28 19:56 ` Eli Zaretskii
2019-03-01 10:00 ` Robert Pluim
2019-03-01 10:35 ` Eli Zaretskii
2019-03-01 13:47 ` Robert Pluim
2019-03-01 13:49 ` Robert Pluim
2019-03-01 14:09 ` Eli Zaretskii [this message]
2019-03-01 14:25 ` Robert Pluim
2019-03-01 14:42 ` Eli Zaretskii
2019-03-11 9:41 ` Wong, Philip
2019-03-11 10:43 ` Robert Pluim
2019-03-11 10:47 ` Wong, Philip
2019-03-11 14:58 ` Eli Zaretskii
[not found] ` <DB7PR01MB4171B6AF4751C4D196E19DECAF480@DB7PR01MB4171.eurprd01.prod.exchangelabs.com>
2019-03-11 16:41 ` Robert Pluim
2019-03-11 16:43 ` Wong, Philip
2019-03-11 16:54 ` Eli Zaretskii
2019-03-11 16:55 ` Wong, Philip
2019-03-11 17:29 ` Eli Zaretskii
2019-03-11 17:35 ` Wong, Philip
2019-03-11 17:55 ` Eli Zaretskii
2019-03-12 9:58 ` Wong, Philip
2019-03-12 16:01 ` Eli Zaretskii
2019-03-12 16:04 ` Wong, Philip
2020-05-22 12:10 ` Bastien
2020-05-22 12:18 ` Eli Zaretskii
2019-03-12 3:42 ` bug#34684: " Takaaki Ishikawa
2019-03-12 15:53 ` Eli Zaretskii
2019-03-11 14:45 ` Eli Zaretskii
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=837ediit4b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34684@debbugs.gnu.org \
--cc=Philip.Wong@warwick.ac.uk \
--cc=rpluim@gmail.com \
/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.