Russian font is ugly

This is what I see on desktop app:

There might be something different about our systemsā€¦

Iā€™ve looked that happen in HTML code when I change font in the Settings.
When I set Roboto elements, I get this style.
style=ā€œfont-family: Roboto, ā€œMicrosoft YaHeiā€, å¾®č½Æ雅黑, ā€œHiragino Sans GBā€, 冬青黑体;ā€
When I set Whitney
style=ā€œfont-family: Whitney, ā€œMicrosoft YaHeiā€, å¾®č½Æ雅黑, ā€œHiragino Sans GBā€, 冬青黑体;ā€

The different is not mach, only first element is changed. This list tells web browser where to search character. Now it knows what to do if it canā€™t find character in the font. It must search in the second font, in the third, and so on.

On my system I donā€™t have Microsoft YaHei and å¾®č½Æ雅黑 font. I have ā€œHiragino Sans GBā€ font. And this font on my system has a lack.

Maybe Erica has ā€œMicrosoft YaHeiā€ font in her system.

1 Like

Ah, I see!

If you just want to use the system font, maybe try out the ā€œSystemā€ option under ā€œFontā€?

On that note, I think this is related.

If I set system or any other, I still has a problem with search results, bookmark alerts, and item dragging.

1 Like

Re: search results, thatā€™s the same bug raised by @dvasyukova above.

The other places are system text. To distinguish them from user-input text, they donā€™t use the custom set font.

Pavel, thatā€™s not what I meant. I meant all this is because these Russian symbols are missing in Roboto, which leads to the weird spacing as ā€œHiragino Sans GBā€ is used. If Whitney were complete in the first place, all this would be solved.

Makes sense?

1 Like

The search results font bug has already been reported here.

1 Like

Thanks for digging this up!

How will you fix this?
Can you add missed characters to Whitney?
I think you also could add default font to the list
Whitney, ā€œMicrosoft YaHeiā€, {NEW}, å¾®č½Æ雅黑, ā€œHiragino Sans GBā€, 冬青黑体;
Where {NEW} - is some russian compatible font, which is look alike on Whitney.

It might break other fonts because of the exactly same reason we talked about here, so I still prefer figuring out how to add the missing fonts in Whitney.

we can change font in settings, but when we share a list it opens with default options. I suggest two ways for this:

  1. open shared lists with options setted by author
  2. change default font to Roboto (or almost any other from existing list) for Cyrillic

Soā€¦ the latest update says the bug should be closed, but even after clearing the cache in Chrome, I still see something like this:

Sorry we had a late release. Should be fixed on the web version now.

Thanks for release, guys! Search looks good for cyrillic font users.

But thereā€™re some places that disrespects font config:

  1. ā€œMove itemā€ dialog:
  2. Dragging files in sidebar
  3. ā€œUnbookmarkā€ dialog (mentioned by @Pavel above in this thread)
    UPD: for all similar dialogs, like ā€œDeleting documentā€

Instead of Whitney I use Calibri Light font and my notes look nice, but not search results. So I confirm this bus and up vote for this too.

In addition to that, when I exporting my note to html or sharing it - it gets with ugly spaces with Whitney font.

it would be great, if exported or shared notes were with the user selected font

Are you using the desktop version? Is it on the latest version? Could you check the version of your desktop app for me? You can do that by choosing the ā€œAboutā€ option in the main menu (menu icon at the top right corner).

The sharing issue is because the anonymous visitor cannot use your setting. You can vote in the poll here about this issue: Should anonymous visitors use your view settings?

ver. 1.0.43 it says it up to date:

this is how my note looks like:

and this is how it looks like when im exporting it:

more to report. this is how search results look like:

I see, thatā€™s what you meant by ā€œsearch resultā€. This is more often referred to as ā€œfile finder resultsā€.

I thought you meant global search results (see screenshot below):

I see the issue, thanks for clarifying. The screenshot is really useful to avoid miscommunication. Weā€™ll fix this as soon as we can.

1 Like

@Pavel @Andrii_Vyshniak weā€™re cleaning up the bugs and would like to know if the bug is still happening to you? If not weā€™ll close this bug.