[rmetzler]

I'm German and I hate half assed i18n.

Often the translation is done poorly, E.G. the word "open" has two different meanings when translated to German, depending on if it's used as a verb or adverb.

I especially used to hate the translation for git, because I couldn't understand it, since they even translated all the core concepts like "branch" into "Ast". It seems like it's better now, but there are still errors which are not translated, so the screentext is mixed German and English.

In the software I maintain I hate translations, because all the time project managers forget that I need the texts in two languages. Also there's never the perfect time to do the texts, since you almost always have to change the UI and all translations.

One tip: if you use dates, please use YYYY-MM-DD and not MM/DD/YYYY. The first format is universally understood, the second one almost always trips me up since we use DD.MM.YYYY in Germany.

[derefr]

> One tip: if you use dates, please use YYYY-MM-DD and not MM/DD/YYYY. The first format is universally understood, the second one almost always trips me up since we use DD.MM.YYYY in Germany.

Usually, datetime stringification takes a locale, and uses the formatter for that locale. Doing i18n by picking one "universally-understood" format, rather than just giving each user the format colloquially familiar to them, is rather uncommon.

[rmetzler]

You're right. This tip was meant to be used in non-localized UIs.

[anotherevan]

I often use "D MMM YYYY" (e.g., "5 Nov 2017") in my UIs when it is practical as I think it is the easiest to read, unambiguous date representation, at least amongst English speaking humans.

I'll use YYYY-MM-DD internally, or in places where sorting is important (e.g., as part of file names).