It is becoming increasingly tiresome to type constructions like:
Müller to get Müller G & oacute; mez to get Gomez & # 26085; & # 26412; to get Gl & # 257; & # 382; & # 353; & # 311; & # 363; nis to get Glāžšķūnis (sweet to my heart is a village near Riga)
... and even insert ampersands and oktotorpes into your own name (oh, we managed not to encode the ellipsis)
It is clear that most of the text on the site uses only Russian Cyrillic, but for example, when translating to bring the original spelling of surnames is just a good tone, especially when there is no consensus about transcription in Russian (and there isn’t it often), and doing it through HTML-entities is an exercise for aesthetic bites, I mean not for everyone. ')
In addition, it would be a sign of respect for the foreign quarter of the habrew Audience.
I urge habraadmintsiyu to do iconv -f cp1251 -t utf8 <present_site> new_site_ on_unicode , plus a few tambourine beats on meta http-equiv in the page header and so on.
The action, although it requires accuracy and attention, is in fact uncomplicated.
Updated: As it turned out, it is not possible to insert the encoded element in the profile field at all. It is displayed anyway as & # 316; not like "ļ".