Umlaut encoding has been smashed in the client recently - please fix

[cvoelker]

Hi, I assume that Umlauts are stored properly in UTF-8 or a similar convertible format and have been displayed that way until now. But a week or two ago (current version 5.16.2 (23409) on Mac), you presumably decided to switch that to the broken Windows 1252 encoding which makes me have to change my display name with each different meeting. It is no big deal, but annoying, as it has to be done constantly and is a very stupid fault from ages ago which I hoped would never come back. Also, I have no idea, whether this appears on other participants screens as well or not.