Tree
- Tree:
a6dfaa9747977a7c9bb574cedb3b8e39c6335a2a
- Date:
- Message:
- devdraw: set displaydpi on devdraw x11 attach (#178) See https://plan9port-review.googlesource.com/c/plan9/+/1470 for discussion of the approach, especially Michael Stapleberg's comment: Note that chromium, firefox and others have tried this and then switched to using the Xft.dpi X resource, see e.g. https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/ui/libgtk2ui/gtk2_ui.cc and especially http://sources.debian.net/src/gnome-settings-daemon/3.18.2-1/plugins/xsettings/gsd-xsettings-manager.c/?hl=824#L80 for some anecdata about why this approach doesn’t work out. The Xft.dpi resource is being set accurately by desktop environments (GNOME, KDE, …) and can easily be changed by users of niche window managers by editing ~/.Xresources. I suggest we check only Xft.dpi, without considering the DPI environment variable or the monitor width/height.
README | commits | blame |
mkfile | commits | blame |
mnihongo.c | commits | blame |
tmac.nihongo | commits | blame |
README
mnihongo is a fairly clumsy troff post-processor that catches unicode characters that might be japanese, looks them up in a font file (currently /lib/font/bit/pelm/unicode.9x24.font) to get the bits, converts that to postscript, and dumps that in the output. Widths are taken from troff font Jp, which has at best a simple approximation to the truth. The program itself is normally called implicitly by loading the troff macro package -mnihongo, which does a .pi command.