Re: Fwd: parse-time-string error with non ASCII timestamp

[Andreas Schwab]

Kenichi Handa <address@hidden> writes:

> In article <address@hidden>, Andreas Schwab <address@hidden> 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.

Right, but is the more clean change, IMHO.

> 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.

parse-time-string only handles English dates anyway.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."