In one respect, I might agree with you.
But in a prior life, I managed a software engineering team for a very American company. By that I mean, all the software was written for use by Americans, i.e., English-only.
Then the company acquired a company in Europe, and the two software teams had to work together, both teams reporting to me. Which they did quite excellently. No personality clashes, the EU team willing to work late to talk with the US team. And the US team willing to come in early to talk with the EU team. So far so good.
But when we had to merge the software, there was one little detail that everyone (everyone!, including me as the manager) overlooked.
The EU team routinely develops software that works with many languages ("internationalized" - there are software conventions, guidelines and maybe even standards for internationalizing software). While the US team routinely wrote software for one language, English.
Fortunately, the relationship between the acquiring company and the acquired company was most excellent. It was chalked up to experience.
Some members of the EU development team were invited to the NYC area for a week of business meetings to explain the development of software for an international audience. The company handled it well. It was a most fun week for the developers (NYC!!!). New friendships were made (this was 30 years ago, and I know some of those "across-the-pond" friendships are still quite active.)
So... sorry for the diversion, but the US fixation upon basic ASCII irks me at times.
So, where was I...
... Might not have been the smartest choice for a name change if they expect it to be used. ...
Only in the United States will you find archaic websites that cannot handle things like u-umlaut.
RCade, you know that I have the highest respect for what you create here, but really. u-umlaut?