After update Discourse, custom font does not apply to cyrillic characters

Support
1

Hello! I haven’t updated my self-hosted discourse for a while (since about November 2024), and today I updated it.
I found one problem. I use Montseratte font as the base font on the forum. And after the update, all cyrillic characters (in the message body, in the names of topics, categories, in the list of tags) are not displayed in this font, but instead are displayed in the usual font used by the browser by default. At the same time, latin characters and numbers are displayed correctly using the font selected in settings.

На скриншоте представлен фрагмент веб-страницы форума, посвященного обсуждению Blu-ray, UHD и программного обеспечения Scenarist, а также плагинов для редактирования видео. (Подпись к изображению от AI)
На скриншоте представлен фрагмент веб-страницы форума, посвященного обсуждению Blu-ray, UHD и программного обеспечения Scenarist, а также плагинов для редактирования видео. (Подпись к изображению от AI)660×443 28.9 KB

I tried rebuild app, clearing the browser cache, trying to browse in incognito mode, nothing helps.
I also tried using several other fonts, and the result was the same. Only when I set as base font Inter(or reset base font setting to default), both cyrillic and latin characters begin to be displayed as the same font.

Изображение представляет собой скриншот веб-страницы с информацией о программном обеспечении для работы с Blu-ray дисками, включая Scenarist и инструменты Red Giant, а также обсуждение вопросов, связанных с Full HD и 4K UltraHD. (Подпись к изображению от AI)
Изображение представляет собой скриншот веб-страницы с информацией о программном обеспечении для работы с Blu-ray дисками, включая Scenarist и инструменты Red Giant, а также обсуждение вопросов, связанных с Full HD и 4K UltraHD. (Подпись к изображению от AI)627×344 24.6 KB

Any thoughts on how to fix this?

2 Likes
2

Hi!

I’ve looked at these screenshots for a while now and I have to admit: I can not see the difference between them… Can you point it out please?

3

Well… I’ll try to explain as much as I can.

My screenshots will show what we will call three stages of font display.

  1. How it was before the update [and in the font settings the Montseratte font was selected].
  2. This is how it became after the update [and in the font settings the Montseratte font was selected].
  3. This is how it became after the update [and in the font settings, the default font was selected]

This screenshot shows stages 2 and 3.
Here, to illustrate the difference in display, you should pay attention to a couple of inscriptions. First is: FullHD and 4K

image
image408×344 29.6 KB

Obviously, this inscription look different.
And then, you need to look at inscription Работаем и

image
image408×344 30.6 KB

And this inscription are look the same.

But, let me remind you… at the second stage, [after the update], the Montseratte font was selected in the font settings, and at the third, the default font.

Thus, at the second stage, when the Montseratte font was selected after the update, the english text is displayed with the Montseratte font, and the russian text is displayed with the default font (just like at the third stage, when the default font was selected in the settings).

And here is how the fonts in both languages looked at the first stage [before the update]:

image
image639×344 77.1 KB

As you can see, at first stage [before update], all text display with Montseratte font.

This problem is not related to the browser or device, as it happens the same everywhere.
Also, it has nothing to do with any one font. I tried changing the font to another, and at stages 2 and 3, I still have the default font with russian text, and selected font with english text on second stage.

1 Like
4

Hi again,

Thanks for that thorough explanation. I can’t repro it on my site, but I’m not giving up (yet).

Is your forum public? Would be easier to have a look at where the problem is manifesting.

5

Yes. Its wedframe.ru
I`ll enable Montseratte font for more clarity.

1 Like
6

Thanks, I’ve found the issue. Discussing internally and will let you know when I know more :slight_smile:

1 Like