Noone would expect that so you'd need to explain it and get people to spell correctly. Not convinced it is a good UX.
"Just localization" isn't "just". Many people have the wrong localization on their computers. Partly because they don't always communicate in their native language. But also because google et. al. are doing such a piss poor job of it.
It is also always weird if your are on an international site. Enter everything in English and then suddenly is expected to enter some fields in your native language.
> "Just localization" isn't "just". Many people have the wrong localization on their computers.
Think about this for a minute longer. Do you have an example or scenario for the use of a Web site where the author can fall into a pit of success (despite having the user's wrong localization) on all things except for dates and that would be broken by allowing* this date input method?
Even ignoring that:
What I said was that "any permutation of full year, full month name, and day of the month is unambiguous". There are a finite number of months and a finite number of localized tokens for representing those months. Do you have an example of two different locales that use the same token (or token sequence) to denote different months on the calendar?
"Just localization" isn't "just". Many people have the wrong localization on their computers. Partly because they don't always communicate in their native language. But also because google et. al. are doing such a piss poor job of it.
It is also always weird if your are on an international site. Enter everything in English and then suddenly is expected to enter some fields in your native language.