[--------- 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
