Re: approxidate parsing for bad time units

From: Jeff King <peff@peff.net>
Date: Sep 7, 2012, 13:54 UTC
Message-ID: <20120907135452.GA1290@sigill.intra.peff.net>
In-Reply-To: <CAFE6XREG5-gwjzvyP9r_hfyY3bWSV2=Bjv9ZbXkejXQRoqYERA@mail.gmail.com>

On Thu, Sep 06, 2012 at 02:01:30PM -0700, Jeffrey Middleton wrote:

Show 5 quoted lines

> I'm generally very happy with the fuzzy parsing. It's a great feature
> that is designed to and in general does save users a lot of time and
> thought. In this case I don't think it does. The problems are:
> (1) It's not ignoring things it can't understand, it's silently
> interpreting them in a useless way.

Right, but we would then need to come up with a list of things it _does_ understand. So right now I can say "6 June" or "6th of June" or even "6 de June", and it works because we just ignore the cruft in the middle.

So I think you'd need to either whitelist what everybody is typing, or blacklist some common typos (or convince people to be stricter in what they type).

> So I do think it's worth improving. (Yes, I know, send patches; I'll
> think about it.)

You read my mind. :)

-Peff