<div dir="ltr">On Thu, Aug 22, 2013 at 12:41 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 08/22/2013 03:11 PM, Yeechang Lee wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That said, I am not sure if the cause is necessarily OSD/theme-related<br>
per se, or even with MythTV at all. I use two 0.26 frontends, one<br>
Linux and one OS X. With the stock/fallback osd_subtitle.xml, both the<br>
FreeMono and Droid Sans Mono fonts behave badly on the OS X frontend<br>
(whether Jean-Yves' standalone or the MacPorts one). With FreeMono,<br>
some punctuation marks are either partially obscured (question mark)<br>
or don't appear at all (apostrophe, period). With Droid Sans Mono,<br>
they appear but parts are cut off, as are other letters, notably the<br>
capital W and capital O.<br>
<br>
Similar behavior occurs with other free mono fonts I've tested,<br>
Liberation, DejaVu, and Ubuntu. Only the proprietary Bitstream Vera<br>
Sans Mono--that Liberation and DejaVu are clones of--seems to appear<br>
correctly on OS X, but of course we can't distribute it. Since, as I<br>
mentioned, this only seems to occur on OS X, it's quite possibly an<br>
Apple-specific font-rendering issue.<br>
</blockquote>
<br>
Oops. This reminds me that k-man on irc noticed that (sometimes? for some fonts? always?) the font face name is exposed differently on his Mac OS X system than on his GNU/Linux systems:<br>
<br>
<a href="http://irc.mythtv.org/ircLog/channel/3/2011-08-15" target="_blank">http://irc.mythtv.org/ircLog/<u></u>channel/3/2011-08-15</a><br>
<br>
Try putting the .otf, .ttf, or .ttc file(s) for the fonts into your theme directory (at least temporarily) and running the frontend on both platforms with -v gui,file --loglevel debug and you should see information like:<br>
<br>
In file '<filename>', found font(s) <face name>'<br>
or<br>
Unable to register font(s) in file '<filename>'<br>
<br>
Do you get different face names or errors or anything? The log messages will show exactly what Qt gets from the underlying platform font managers. If they're different, we'd have to fix this with code (and it wouldn't be that much code--like I have no excuse for not having finished it in 2 years :( ). I still think the approach he asked for (and I described) in the IRC conversation is the best approach--basically a fallback face name approach, similar to that used by CSS.<br>
<br>
I'd also like Stuart Morgan's opinion on the approach before we put it in.<br><br></blockquote><div>It definitely sounds like a font substitution problem. Monospaced font characters should obviously have the same width, and when they don't, it can be a problem with the font definition (the font designer wasn't careful about keeping monospacing), or there are missing characters that get substituted from a similar font, or the entire font is substituted. I expect it is the latter, because I am cursed with the ability to notice miniscule deviations in alignment/spacing and it's been a long time since I've seen any issues with FreeMono or Droid Sans Mono captions. Hopefully Mike's suggestions can root out the root cause.</div>
<div><br></div><div>Jim</div></div></div></div>