Re: Client-side font rendering system - from FAQ
[- Sun 17.Mar'13 at 11:19:31 -0500 Chris Bennett :-] I also use mutt and I want to see UTF8 properly. I put: export LC_CTYPE=en_US.UTF-8 in my .profile and I get OK results. I don't need to change my actual font with that. Won't swear it will work for you. Chris Yes I did all of that - I always read OS docs and FAQ's. The xterm issue is weird, with some fonts I can see chinese/korean/japanese but not Arabic - with other fonts it's the reverse. The best way i've found is not to use a font for any terminal emulators and let it use its default. I see more unicode charaters that way that by using any other fonts. It's not a major issue for me, just a little niggle. Using urxvt seems to cover most of the charset issues; but I like to use as much of the default installation as possible. If I could get [u]xterm to do this then i'd have no need to install urxvt. I know that 99.9% of the time it's user config screw-ups, not the software. I've clearly missed something or done something wrong. Like I said, i'll just use urxvt. Cheers for replies and advice anyway. Jamie. -- James Griffin: jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Client-side font rendering system - from FAQ
I also use mutt and I want to see UTF8 properly. I put: export LC_CTYPE=en_US.UTF-8 in my .profile and I get OK results. I don't need to change my actual font with that. Won't swear it will work for you. Chris
Client-side font rendering system - from FAQ
I've added some fonts using pkg_add(1). Having looked at and read http://www.openbsd.org/faq/truetype.html, in the section Client Side Font Rendering, it says that fints added as a package from the ports collection are registered automatically. Does this include when fonts are added using pkg_add(1) or only when compiled from the ports tree? Because i've added fonts using pkg_add(1), i'm unsure if I need to register them or not. Could someone confirm this? Thanks for your time, Jamie -- James Griffin: jmz at kontrol.kode5.net [A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38]
Re: Client-side font rendering system - from FAQ
as of msttcorefonts-2.0p0 the package does not override /etc/fonts/conf.d/31-nonmst.conf that's the one glaring exception i can think of (there are also old bmp fonts that install outside default paths, but i've no idea if such packages exist) On Sat, Mar 16, 2013 at 3:40 AM, James Griffin j...@kontrol.kode5.net wrote: I've added some fonts using pkg_add(1). Having looked at and read http://www.openbsd.org/faq/truetype.html, in the section Client Side Font Rendering, it says that fints added as a package from the ports collection are registered automatically. Does this include when fonts are added using pkg_add(1) or only when compiled from the ports tree? Because i've added fonts using pkg_add(1), i'm unsure if I need to register them or not. Could someone confirm this? Thanks for your time, Jamie -- James Griffin: jmz at kontrol.kode5.net [A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38]
Re: Client-side font rendering system - from FAQ
On Sat, Mar 16, 2013 at 04:07, Andres Perera wrote: as of msttcorefonts-2.0p0 the package does not override /etc/fonts/conf.d/31-nonmst.conf that's the one glaring exception i can think of The part about server-side rendering is kind of an exception. A new font will show up in chrome or firefox right away, but xterm won't be able to find it until you run xset +fp. At least that was my experience. Because i've added fonts using pkg_add(1), i'm unsure if I need to register them or not. Could someone confirm this? Internally, the ports tree builds a package and installs that. The final result of pkg_add will never be different than building the port, except you'll have more disk space free. :)
Re: Client-side font rendering system - from FAQ
[- Sat 16.Mar'13 at 9:35:46 -0400 Ted Unangst :-] The part about server-side rendering is kind of an exception. A new font will show up in chrome or firefox right away, but xterm won't be able to find it until you run xset +fp. At least that was my experience. Yes, I did run xset + fp so that should have sorted it out. Having said that, the only way I can get all Unicode characters to display, namely in my MUA which is mutt, is by leaving the xterm font to the default. Even if I set to a larger size, like 7x14 for example, the characters don't display properly. I have got urxvt installed which works fine but I don't see why I can't get xterm to do the same thing. I've tried lots of options in my .Xdefaults file. It doesn't matter now as I can read the small font fine. Internally, the ports tree builds a package and installs that. The final result of pkg_add will never be different than building the port, except you'll have more disk space free. :) It was just the explanation on the FAQ page I referred to that I found a bit ambiguous; it suggested, to me at least, that building the font from a port would set up the fonts automatically but pkg_add(1) would not. Just my dumb interpretation of that description I guess. Thanks for taking the time to reply -- to both of you. Jamie -- James Griffin: jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Client-side font rendering system - from FAQ
On Sat, Mar 16, 2013 at 02:06:57PM +, James Griffin wrote: Yes, I did run xset + fp so that should have sorted it out. Having said that, the only way I can get all Unicode characters to display, namely in my MUA which is mutt, is by leaving the xterm font to the default. Even if I set to a larger size, like 7x14 for example, the characters don't display properly. Here is what I did for unicode chars in .Xdefaults: UXTerm*font: -adobe-courier-medium-r-*-*-18-*-*-*-*-*-iso10646-* I found this using xfontsel, and running uxterm instead of xterm. Now, i can see all chars for various languages in mutt. -- James Griffin:jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
