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
Subtitle and OSD fonts broken with fontconfig 2.10.92 #63
Comments
Yep, this is a known fontconfig problem and mpv can't do anything about it. (Even if not, mpv doesn't use fontconfig directly, libass does.) I guess we should leave this open until fontconfig is fixed, as many will hit this issue. |
Bug report about a similar problem with Firefox: https://bugzilla.redhat.com/show_bug.cgi?id=946859 Contains links to the offending commit and the upstream Firefox bug report as well. mplayer2 bug report, exactly the same issue: http://devel.mplayer2.org/ticket/230 (edit: it's the same issue, but unlike mplayer2, mpv's progress bar is not broken because it does not use characters for drawing the bar) One user reported that he tried with fontconfig 2.10.92.7-g03216cc (which contains the fix), and that it doesn't fix the OSD issue. However, Firefox web fonts supposedly work again. |
This is a bummer. |
fontconfig bug report: https://bugs.freedesktop.org/show_bug.cgi?id=63922 Looks like it's definitely a fontconfig bug. The latest fontconfig release(s) don't work, and fontconfig git is broken too. |
Pushed a commit that works around this issue with fontconfig git, but not with fontconfig 2.10.92 (AFAIK memory fonts are broken completely in that commit). |
Should be fixed with fontconfig 2.10.93, which was released 2 days ago. Summary: 2.10.92 is broken with anything that uses memory fonts, use 2.10.93 instead or any other version. |
Embedded fonts in MKVs are replaced with Arial Unicode MS with fontconfig 2.10.92 (included in the latest Homebrew).
The culprit is fontconfig 2.10.92, as mplayer2 has the same problem: https://bbs.archlinux.org/viewtopic.php?pid=1260215
Switching back to fontconfig 2.10.91 fixes the problem.
The text was updated successfully, but these errors were encountered: