2 ms·
Not at all, it's a valid bug that's indicitaive of a deeper problem, presenting uncertain and locale-specific conclusions as being certain. Even if you do lang
by richmarr 11y ago
Not at all, it's a valid bug that's indicitaive of a deeper problem, presenting uncertain and locale-specific conclusions as being certain.
Even if you do language and locale-sniffing using n-grams you still have a certainty problem.
In the UK we traditionally use DD/MM/YY format, although since "9/11" the papers have started slipping into MM/DD format, and younger people have followed suit somewhat.
In the UK it's therefore completely crazy to rely on NLP to interpret "6/7/12" which might mean 7th June or 6th July. If you're going to capture it you need to ask the user, so you need both.
- wodenokoto 11y agoWith that being said, it still needs to do sanity check. Is it a valid date? if not, will it be if we change the format? Nobody really knows what you mean when you write a data as xx/xx/xx. It has to be assumed from context. I've even have border control ask me about the expiration date of my passport since they couldn't figure out if it was day-month or month-day. I couldn't tell them either, because it wasn't written explicitly. Later I realised I could deduce it from my birthdate.
- richmarr 11y agoNot to be overly inflamattory, but whoever designed that passport (an inherently international object) without taking into account international date format deserves to be fired. Then re-hired. Then fired again.