From: Eli Zaretskii <eliz@gnu.org>
To: "Wong, Philip" <Philip.Wong@warwick.ac.uk>
Cc: rpluim@gmail.com, 34684@debbugs.gnu.org
Subject: bug#34684: 26.1; Strange characters when inserting date
Date: Mon, 11 Mar 2019 19:29:47 +0200 [thread overview]
Message-ID: <83va0p48vo.fsf@gnu.org> (raw)
In-Reply-To: <DB7PR01MB4171D0050B0563F8E667F92CAF480@DB7PR01MB4171.eurprd01.prod.exchangelabs.com> (Philip.Wong@warwick.ac.uk)
> From: "Wong, Philip" <Philip.Wong@warwick.ac.uk>
> CC: "rpluim@gmail.com" <rpluim@gmail.com>, "34684@debbugs.gnu.org"
> <34684@debbugs.gnu.org>
> Date: Mon, 11 Mar 2019 16:55:42 +0000
>
> Thanks Eli, you're right.
>
> I still get '<2019-03-11 ¶g¤@>'
OK, as expected. This means Org is indeed off the hook, the problem
is with format-time-string and/or the Windows implementation of the
strftime function.
Does the below produce correct results, or does it also produce
garbled strings:
M-: (insert (format-time-string "<%Y-%m-%d %A>" (current-time))) RET
This is the same as what you tried, but with capital %A instead of
lower-case %a. %A should produce the full name of the weekday.
Also, please evaluate each of the following expressions with
M-: ... RET (replace the "..." with each expression below), and
please tell what each of them produced:
(w32-get-current-locale-id)
(w32-get-locale-info (w32-get-current-locale-id) t)
(w32-get-default-locale-id)
(w32-get-default-locale-id t)
(locale-info 'days)
next prev parent reply other threads:[~2019-03-11 17:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB7PR01MB41710340234EF2B900832154AF750@DB7PR01MB4171.eurprd01.prod.exchangelabs.com>
2019-02-28 17:55 ` bug#34684: 26.1; Strange characters when inserting date 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
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 [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83va0p48vo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).