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

[Kenichi Handa]

In article <address@hidden>, Andreas Schwab <address@hidden> writes:

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

If that is the original intention of that function, that
should be mentioned in the docstring clearly.  In addition,
just a vector of 128 (instead of the current 256) should be
enough.  Using char-table here is much less efficient.

But, is it surely called with English dates only?

---
Kenichi Handa
address@hidden