Wit/datetime does not understand European date notation

[RetardVeverca]

Wit/datetime recognizes only US all-numeric date format (MM/DD/YYYY). All other formats which are usually used in Europe (DD/MM/, DD.MM, DD/MM/YYYY, DD.MM.YYYY ...) are converted to wit/number (e.g. "from 25.6 to 30.6" -> wit/number, wit/number) or to wit/datetime (e.g. "from 12.11 to 16.11" -> wit/datetime: from 8/17/2016, 12:11:00 AM to 8/17/2016, 4:12:00 PM) with dates recognized as hours. Even if you write the whole date with year and days which can't be interpreted as hours, you get back wit/number (e.g. "from 25.6.2016 to 30.6.2016" -> 4 x wit/number).

My wit/datetime is not trained with anything weird:

Examples:

[danqing]

There needs to be a locale field. Otherwise there's no way to tell whether 8/9 is aug 9 or sep 8.

[nirmalrayan]

Do we have any solutions to this issue. Even my bot goes mad if date is passed in dd/mm/yyyy or other European formats.. But since all our users are from India, getting them to enter date in mm/dd/yyyy format is weird.. Please provide fix asap

[patapizza]

@nirmalrayan wit/datetime is powered by Duckling. However locales are not supported yet: facebook/duckling#33

[botlee]

If this issue is closed, should it recognize European format? And if so, where should I config it in the app? Thanks

[patapizza]

@botlee You can set the locale parameter in the context.