From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: bbdb acting up with Kai's name
Date: Wed, 05 Jun 2002 17:42:04 +0200 [thread overview]
Message-ID: <vafvg8xu3zn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <871yblep8c.fsf@eu.citrix.com> (John Cooper's message of "Wed, 05 Jun 2002 16:09:55 +0100")
John Cooper <john.cooper@eu.citrix.com> writes:
> I suppose so - if I use the following font, the character is displayed
> correctly:
> -b&h-lucida console-medium-r-semi condensed--17-120-100-100-m-100-iso8859-15
>
> However, there doesn't seem to be an iso-8859-15 variant of the font I like for
> my Gnus frame, namely:
> -etl-fixed-medium-r-normal-*-*-160-*-*-c-*-iso8859-1
Indeed. I wonder if the GNU intlfonts package will be augmented?
> > You could also store .bbdb in an encoding which differentiates between
> > Latin-1 and Latin-9 (emacs-mule and the iso-2022 encodings come to
> > mind) and then store two versions of my name. Newer bbdb versions
> > have a variable bbdb-file-coding-system. You must make sure that the
> > file on disk agrees with this coding system, though:
> >
> > C-x C-f ~/.bbdb RET
> > C-x RET f foo RET
> > C-x C-s
> >
> > Then set bbdb-file-coding-system to foo.
>
> Hmm, my bbdb doesn't have this variable - I'm using 2.34 which
> bbdb.sourceforge.org claims to be the latest released version.
Oh. Why do I have 2.35, then? Hm.
> Perhaps it's easiest for me to just put up with the outline
> character and figure out how to tell BBDB to just quietly accept
> duplicate names.
If you store that one variation of my name, then you will be fine.
(Until I move to Poland :-)
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-06-05 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 18:57 Josh Huber
2002-05-31 20:37 ` Josh Huber
2002-06-02 8:26 ` Kai Großjohann
2002-06-03 23:20 ` Josh Huber
[not found] ` <87660xc06h.fsf@eu.citrix.com>
2002-06-05 14:30 ` Kai Großjohann
2002-06-05 15:09 ` John S Cooper
2002-06-05 15:42 ` Kai Großjohann [this message]
2002-06-05 18:10 ` Josh Huber
2002-06-06 9:19 ` Kai Großjohann
2002-06-06 9:19 ` Kai Großjohann
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=vafvg8xu3zn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).