From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: bug#34684: 26.1; Strange characters when inserting date Date: Fri, 01 Mar 2019 16:09:24 +0200 Message-ID: <837ediit4b.fsf@gnu.org> References: <83h8cnkdc5.fsf@gnu.org> <83zhqfit5u.fsf@gnu.org> <83d0naj30v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:36101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gzirT-0002ua-Ks for emacs-orgmode@gnu.org; Fri, 01 Mar 2019 09:10:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gzirS-0007Or-Rc for emacs-orgmode@gnu.org; Fri, 01 Mar 2019 09:10:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:42402) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gzirS-0007Og-NK for emacs-orgmode@gnu.org; Fri, 01 Mar 2019 09:10:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gzirS-0004Et-B4 for emacs-orgmode@gnu.org; Fri, 01 Mar 2019 09:10:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: (message from Robert Pluim on Fri, 01 Mar 2019 14:47:21 +0100) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Robert Pluim Cc: Philip.Wong@warwick.ac.uk, 34684@debbugs.gnu.org > From: Robert Pluim > 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.