It looks like Discourse forums don’t load if the character encoding is set to Windows-1251 for Russian. To reproduce, set the character encoding to “Cyrillic (Windows-1251)” and visit the homepage of a forum. It will just be a blank page. There are error messages in the console that look something …

I wouldn’t do it myself. :slight_smile: A user in Russia was getting a blank page. It took several hours to track down the cause and I couldn’t reproduce it until I set my browser’s encoding to Windows-1251. I’m wondering if other Russian language users are experiencing blank pages. It’s apparentl…

We have several forums working in Russia. There is no problem if, as written above, UTF-8 is used. We did not experiment or set the encoding Windows-1251. What for? UTF-8 works for everything. There was no blank page on any of the forums. The browser does not switch to windows-1251. I tried in 3 …

cp1251 isn’t dead yet, so I’m not stunned to hear that some users still have a browser which defaults to it. As of this month(16/12/19) a little over 11% of .ru sites use windows-1251 .

I’m not sure why you aren’t seeing it there. I used this browser plugin in Chromium to test it. (Firefox seems to disable the character encoding menu on some sites.) I just tried with a third Discourse forum, and that one doesn’t load either. I don’t know why that user has the OS set to Windows-12…

Interesting, please look, with this plugin there is a white page on the forum: https://toxu.ru I watched the encoding windows-1251 on this site.

When I visit your site and set it to Windows-1251, I get a blank page and these errors (same as the other sites). [error] I’ve just heard an update from the user though — they are using Windows XP with Chrome 49, so that is probably the source of the problem. I did a quick search through the ana…

Chrome dropped XP in April 2016. Firefox dropped in June 2018 so it’s a better alternative than Chrome. But in the end the user should upgrade ASAP.

I’m going to warn them about the security risks and offer to assist with Linux if they want to do that. During the debugging I made a long list of everything to check for when those requests come in. I need to add “Windows NT 5.1” and browser versions to the list for next time.

Forum breaks when using Windows-1251 Cyrillic/Russian encoding

Support

gerhard (Gerhard Schlager) December 14, 2019, 10:46pm 2

Why would you do that? Discourse uses UTF-8 and that works for Russian too.

Topic		Replies	Views
Problem with umlauts when embedding Discourse on another website Support embedding	2	406	December 13, 2023
URLs with encoding are altered when using Discourse link function Support	7	164	April 15, 2026
Unicode (Russian) username validation fails randomly Translations	5	1436	December 16, 2019
Weird encoding issue on categories page Support unsupported-install	15	506	February 5, 2025
Using alternative browsers like Konqueror and Falcon? Support	19	2106	February 8, 2020

Forum breaks when using Windows-1251 Cyrillic/Russian encoding

Related topics