In my application, there is a field that represents the end of the accounting year for an entity. This "date" is the same every year, so what we currently present to the user is field with a month and day. (Think about a short date with the year omitted)
Does anyone have experience or know of research/recommendations for localizing this kind of field? I got some stakeholder input suggesting that people who think in day-month-year order will think in the same order when thinking about dates without a year. For example, "the last day of June" is mentally "thirty" (pause) "six" to someone with this mental model, but "six" (pause) "thirty) to someone who operates in month-day-year culture.
Is it as simple as dropping the year from the localized format so you have the day and month in the right order?