this update fixed https://bugzilla.redhat.com/show_bug.cgi?id=1494563#c1 for me

works for me in a VM

Works great! LGTM! =)

Didn’t break the world this time. :)

Thank you for the info guys! I'm glad this works better now. :) There's one more problem caused by this update (ImageMagick not building with these fonts), so I have to wait until that is fixed (in ImageMagick) before I decide to push it into stable.

Seems to be OK, except that Cyrillic fonts look signally larger.

And it looks somewhere like this:

In contradistinction to Cinnamon, dissimilarity not show itself in KDE environment, but typeface weight of window titles are affected.

Roboto Medium 11 window title looks as tiny like this:

works

this works fine now

I haven't noticed any change, at least it's not overriding default fonts

@anonymous Hmm, I guess in your case this update caused overwrite of some low priority LGC (Latin Greek Cyrillic) font that you were using before for displaying the Cyrillic characters.

IMHO it has 2 solutions: 1) I lower the priority of Standard Symbols PS font (used to display LGC characters AFAICT) in the package, but it can keep overriding other LGC fonts with even lower priority. 2) I change the "hinting" of the font for the fontconfig, telling it to make it smaller by default. However, it would require another rounds of guess-build-try-evaluate, because I can't read anything in LGC, and I would need your help in evaluatiing the changes to the size of the font.

I still prefer 2) as a solution, but the question is, if you are OK with helping me in this matter? :) Another question is - do you think that should block the release of urw-base35-fonts, or can I push it to stable this week?

@dkaspar

I would have thought, there are no especial needs to block the release at the moment, but it needs some ajustments in future. In particular regarding KDE's window titles custom font overriding by default one.

In relation to Firefox' menu fonts dissimilarity, this does not manifest itself in any way under KDE environment in contradistinction to Cinnamon.

And as for guess-build-try-evaluate method I would recommend to open whatsoever pages containing diverse characters in its titles and watch the results in Firefox menus and history under Cinnamon, for example.

e.g. https://habrahabr.ru/post/308032/

http://itc.ua/news/nissan-podtverdil-debyut-goryachey-versii-elektromobilya-new-leaf-nismo-concept-na-tokiyskom-avtosalone-i-rasskazal-o-spetsialnoy-versii-leaf-2-zero-dlya-evropyi/

or e.g. http://www.opennet.ru/

1. The problem was absent with urw-fonts-2.4, so maybe, if it is possible, there are some reasons to use the same settings 'schema'.

2. One more thing: xterm recently reports that it

   cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1"
   

   and I don't know if it has anything to do with this update.

@anonymous:

"I would have thought, there are no especial needs to block the release at the moment, but it needs some ajustments in future."

We have discovered one more bug, that LibreOffice is not able to use these fonts anymore, that I will be soon fixing. But since the Beta is coming, I'm pushing this into stable.

Dissimilarity with Cyrillic and Latin fonts size is also present in Amarok under KDE environment:

As far as I remember, resemblant issue had already happened a few months ago after freetype update. Perhaps this will somehow help: FEDORA-2017-43db8d2e92

Dissimilarity with Cyrillic and Latin fonts size is also present in Amarok under KDE environment:

As far as I remember, resemblant issue had already happened a few months ago after freetype update. Perhaps the way it was solved will somehow help: FEDORA-2017-43db8d2e92

Hello @anonymous, we were discussing some issues at urw-base35-fonts upstream (https://github.com/ArtifexSoftware/urw-base35-fonts/issues/13), and I'm starting to get a feeling that one problem described there is causing this issue for you.

To clarify, the selected priority/ordering value of 60 for urw-base35-fonts is actually still too high, thus overriding some of the fontconfig defaults (which are less common though). I will be thinking about switching to value 61 or even lower, at least for Standard Symbols PS font which is most likely causing this (?).

I will have a discussion with fontconfig upstream about this as well, but probably no sooner than next week, because I'm engaged in my primary job responsibilites at the moment. :-/ Sorry for the inconvenience.

All right, it's nothing at all such a serious and nothing presses for me. I just wanted let know that such issues exist :)