[mythtv] [mythtv-commits] Ticket #8674: Use older version of FreeMono.ttf
Michael T. Dean
mtdean at thirdcontact.com
Tue Jul 20 21:30:54 UTC 2010
On 07/20/2010 05:20 PM, Jim Stichnoth wrote:
> On Tue, Jul 20, 2010 at 8:03 AM, Michael T. Dean wrote:
>> I guess I just haven't seen the lowercase
>> "st"combination (or figured it was an error in captions).
> Probably not interesting to most people, but... Apart from silly
> captioner mistakes, most NTSC closed caption errors are seen as a
> dropped pair of adjacent characters. A cc packet has two characters,
> and when the packet gets corrupted, both characters are dropped. This
> is why it was clear to me that "st"->"t" wasn't a dropped packet
> problem. Plus the fact that it started showing up only after the
> mythui-osd merge. I would love to understand why there are so many
> 2-character packet corruptions in the VBI information in digital OTA
> recordings that I receive with virtually perfect signal strength and
> quality, and the same being true with DISH/HDPVR recordings where the
> captions are drawn by the STB.
Heh. Good to know.
I figured out when testing before committing why I hadn't seen the
issue--for EIA-708 captions, we're only using FreeMono for mono serif
since the change to MythUI and , and it seems my
broadcasters/show-captioning-companies aren't using mono serif fonts.
So, it's only trunk post-mythui-osd and, generally, will only affect
EIA-608 users or users whose EIA-708 captions specify mono serif. After
swapping all of the EIA-708 fonts to FreeMono, it was /very/ obvious
what you were seeing. :)
More information about the mythtv-dev