Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: problem with utf-8 encoding in Gnus
Date: Tue, 26 Nov 2002 09:37:44 -0500	[thread overview]
Message-ID: <m33cpo2y87.fsf@heechee.beld.net> (raw)
In-Reply-To: <ilufztpodwa.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 25 Nov 2002 16:41:25 +0100")

On Mon, 25 Nov 2002, jas@extundo.com wrote:
> Yes.  Your fontset doesn't have the characters.  The following
> fontset works here:
> 
> -Misc-Fixed-Medium-R-Normal--18-120-100-100-C-90-ISO10646-1

I supposed (wrongly) that the bold variant would have the same
characters as the medium one.  I'm using the ucs-fonts package, and
the bold variant (7x14B.bdf) is TARGET1, which is the minimal UCS
range in the ucs-fonts package.  I guess I'll switch to a TARGET3 font
like the one you mention or 7x14.bdf when I need to view more of the
UCS range.  It seems like all the bold fonts in the ucs-fonts package
are TARGET1.

Unfortunately, I don't like the look of the normal variants at all
(they are too thin) so I'll have to keep switching back and forth.
I'll ask the maintainer of ucs-fonts about the plans to bring bold
variants up to TARGET3.

I wonder if Gnus could intelligently switch between a regular and a
Unicode font as needed.  I know I can do a manual switch with
shift-Mouse1 as an Emacs function and that's fine, but perhaps Gnus
could be smart about showing messages with characters unavailable in
the current fontset.

Thanks
Ted




  reply	other threads:[~2002-11-26 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 12:27 Ted Zlatanov
2002-11-25 12:38 ` Roman Belenov
2002-11-25 15:41 ` Simon Josefsson
2002-11-26 14:37   ` Ted Zlatanov [this message]
2002-11-28 22:21     ` Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m33cpo2y87.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).