[mythtv-users] OSD fonts badly rendered on a 16:9 TV

[Nicolas Will]

On Wed, 2007-10-03 at 11:06 -0600, Joe Ripley wrote:
> On 10/3/07, Nicolas Will <nico at youplala.net> wrote:
> > No Xinerama at all.
> >
> > None configured in xorg.conf, none reported in Xorg.0.log.
> >
> > For completeness, I have posted both files there:
> >
> > http://www.youplala.net/~will/htpc/bad_fonts/
> >
> > Thanks for looking at my issue.
> 
> As Daniel mentioned in your trac ticket, check out:
> 
> http://www.mythtv.org/wiki/index.php/Display_Size
> 

Hehehe.

Friendly place, here.

OK, I decided not to be too offended by the abuse.

On top of the NVIDIA way of hard-coding the DPI (yes, I did read the FAQ
on the wiki) I have added the display size stuff.

Section "Monitor"
        Identifier      "MonitorTMDS"
        Option          "DPMS"
        Option          "UseEdidDpi"            "FALSE"
        Option          "DPI"                   "100 x 100"
        # For 1920x1080 at 100dpi  (16:9)
        DisplaySize  487 274
EndSection

I kick gdm in order to restart X.

I check, same bad rendering for the OSD. No mention of DisplaySize in
the X logs. I still get the normal NVIDIA stuff:

(**) NVIDIA(0): DPI set to (100, 100); computed from "DPI" X config
option

So why not remove the NVIDIA-specific stuff, and only leave the
displaysize statement?

Section "Monitor"
        Identifier      "MonitorTMDS"
        Option          "DPMS"
        # For 1920x1080 at 100dpi  (16:9)
        DisplaySize     487 274
#       Option          "UseEdidDpi"            "FALSE"
#       Option          "DPI"                   "100 x 100"
EndSection

I swiftly do that and restart X.

The menus have very small fonts now. But the OSD is still badly
rendered.

I check the X logs and still get no mention of DisplaySize.

But instead I get this:

(--) NVIDIA(0): DPI set to (46, 46); computed from "UseEdidDpi" X config
option

DisplaySize is apparently not a valid entry for the NVIDIA driver...

But rest assured that DisplaySize was a valid entry when I was using the
on-board Intel GPU. I had tried it a few months ago, and still it did
not fix my OSD text rendering issues. I do read wikis and mailing list
archives. I do use Google too.


So it sounds like I'm not such a complete moron after all and that
closing the ticket may have been done slightly too early.

So, what's your take on what I still think is a bug?

Nico