That was a long time ago.

Traditionally, character's under Unix were encoded in a locale-specific manner: ISO 8859-1 in Western Europe, ISO 8859-2 in Eastern Europe, EUC-JP in Japan, etc. In the 1990s, there was a major push to get XFree86 (the ancestor of X.Org) to switch to locale-independent UTF-8, lead mainly by Markus Kuhn and Bruno Haible.

The link is to Markus Kuhn's web page, which appears to describe the UTF_8 software available around 1998 or so.

▲

sheept 7 hours ago | parent [-]

UTF-8 is not locale independent. You cannot correctly render multilingual UTF-8 text without also specifying its locale, and some transformations like uppercase/lowercase also depend on the locale.

	▲	Joker_vD 6 hours ago \| parent \| next [-]
		> You cannot correctly render multilingual UTF-8 text without also specifying its locale You can render it pretty well, not perfect, but good enough to actually read it, as opposed to not being able to render it at all or rendering mojibake à la РљСЂР°РєРѕР·СЏР±СЂС‹ instead.
	▲	numpad0 5 hours ago \| parent \| prev \| next [-]
		At least touching Unicode strings in wrong locales only mildly corrupts the strings. Plenty of Win32 apps would crash if the system locale is in UTF-8.
	▲	sourcegrift 6 hours ago \| parent \| prev [-]
		Eg: some cjk characters render differently based on whether mainland China, Taiwan, or Japan. One example 骨 (from my old notes so tiny chance this example is incorrect)