[- 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.
>
> C
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
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 t
[- 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
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 f
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 wrot
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
7 matches
Mail list logo
