From: Kenichi Handa <handa@m17n.org>
To: Andreas Schwab <schwab@suse.de>
Cc: zslevin@gmail.com, emacs-devel@gnu.org
Subject: Re: Fwd: parse-time-string error with non ASCII timestamp
Date: Tue, 17 Apr 2007 20:50:00 +0900 [thread overview]
Message-ID: <E1HdmC8-000240-AJ@etlken.m17n.org> (raw)
In-Reply-To: <jek5wbxmkc.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 17 Apr 2007 13:33:23 +0200)
In article <jek5wbxmkc.fsf@sykes.suse.de>, Andreas Schwab <schwab@suse.de> writes:
[...]
>>> (defsubst parse-time-string-chars (char)
>>> ! (and (< char (length parse-time-syntax))
>>> ! (aref parse-time-syntax char)))
> >
> > It seems that this is the right fix at the moment because
> > parse-time.el doesn't pay attention to non-ASCII characters
> > at all. In the future, we may have to improve it for
> > non-ASCII characters if necesary.
> I'd guess all that needs to be done is to make parse-time-digits and
> parse-time-syntax char tables.
Just making them char-tables has the same effect as above.
If we want to handle a multibyte time-string well, we must
set proper values to those char-tables which, I think, is
beyond what we should do at the moment.
> > Shall I install that change?
> digit-char-p has the same problem.
But, it seems that it is never called with a multibyte
character.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-04-17 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1175499420.269736.200740@b75g2000hsg.googlegroups.com>
2007-04-17 10:10 ` Fwd: parse-time-string error with non ASCII timestamp Levin Du
2007-04-17 11:20 ` Kenichi Handa
2007-04-17 11:33 ` Andreas Schwab
2007-04-17 11:50 ` Kenichi Handa [this message]
2007-04-17 14:32 ` Andreas Schwab
2007-04-17 23:07 ` Kenichi Handa
2007-04-18 2:02 ` Richard Stallman
2007-04-18 2:46 ` Kenichi Handa
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1HdmC8-000240-AJ@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
--cc=zslevin@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.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).