-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with urw-d050000l.conf #27
Comments
If you install the |
thanks @fabiangreffrath! Are you saying this issue has been introduced by maintainers? Because i installed the package from CentOS repo. |
No, the CentOS package seems to provide the file with the right priority. Try running |
Yes, it appeared before
this is what i have in
I do not have Impact installed, but still documents which use Impact shouldn't be rendered with D050000l |
Looks like it is not a new issue: https://www.reddit.com/r/SteamPlay/comments/9a7mon/making_a_open_source_equavilent_to_corefonts/e4vy3dm/ |
That's a completely different issue then. However, I agree that a symbols font shouldn't be registered as an alternative for "fantasy" fonts. |
thanks @fabiangreffrath. I updated the description to avoid further confusion. |
Any other comments, guys, expectations probably? |
I still see D050000L as an alias for fantasy. D050000L is clearly not a font that should be categorized as such. |
Hi guys, first 2 definitions in fontconfig/urw-d050000l.conf are making D050000L preferred font for fantasy family. $ fc-match Dingbats |
@chris-liddell These two aliases should probably get removed. |
Hi guys,
D050000l by some reason is preferred font for fantasy family. According to https://www.w3.org/Style/Examples/007/fonts.en.html this family used for decorative fonts, and we have this:
somewhere in fontconfig and this:
in
60-latin.conf
,so installing urw-base35-fonts results in incorrect subtitution Impact -> D050000l.
UPD: I do not have Impact installed, but still the following behavior is very confusing:
Am i missing something?
The text was updated successfully, but these errors were encountered: