Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

european headers

0 views
Skip to first unread message

Ian Zimmerman

unread,
Jan 2, 2003, 3:02:32 PM1/2/03
to

What do I need to do to see 8859-[12] encoded headers correctly? I am
quite sure it just worked out of the box with Gnus 5.8.8 + Emacs20,
but it is not working now in Gnus 5.9.0 + Emacs21.

--
Ian Zimmerman, Oakland, California, U.S.A.
if (sizeof(signed) > sizeof(unsigned) + 4) { delete this; }
GPG: 433BA087 9C0F 194F 203A 63F7 B1B8 6E5A 8CA3 27DB 433B A087

Lars Magne Ingebrigtsen

unread,
Jan 2, 2003, 3:40:16 PM1/2/03
to
Ian Zimmerman <i...@speakeasy.org> writes:

> What do I need to do to see 8859-[12] encoded headers correctly? I am
> quite sure it just worked out of the box with Gnus 5.8.8 + Emacs20,
> but it is not working now in Gnus 5.9.0 + Emacs21.

It's supposed to work even better now. What are you seeing?

--
(domestic pets only, the antidote for overdose, milk.)
la...@gnus.org * Lars Magne Ingebrigtsen

Ian Zimmerman

unread,
Jan 2, 2003, 6:36:57 PM1/2/03
to

itz> What do I need to do to see 8859-[12] encoded headers correctly?
itz> I am quite sure it just worked out of the box with Gnus 5.8.8 +
itz> Emacs20, but it is not working now in Gnus 5.9.0 + Emacs21.

Lars> It's supposed to work even better now. What are you seeing?

Empty square boxes :-(

Actually latin-1 is okay (I see Kai's name right), it's the other
charsets that aren't (latin-2, latin-[12]+euro).

I have just read the part of Emacs manual on fontsets, and I put this
in my .Xresources:

Emacs.Fontset-0: -B&H-LucidaTypewriter-Medium-R-Normal-Sans-12-120-75-75-M-70-fontset-EmacsLucida, iso8859-2: -B&H-Lucida Console-Medium-R-Semi Condensed--12-120-75-75-M-80-iso8559-2
Emacs.font: fontset-EmacsLucida

it didn't help.

Lars Magne Ingebrigtsen

unread,
Jan 2, 2003, 7:13:22 PM1/2/03
to
Ian Zimmerman <i...@speakeasy.org> writes:

> Empty square boxes :-(

This probably means that you don't have the right fonts installed.

I think it was Simon that gave this recipe for how to install the
required fonts on Debian.

$ apt-get install `apt-cache search font|grep ^xfonts|awk '{print $1}'|sort|uniq|grep -v xfonts-bochs`

Ok, you probably don't need all those fonts, but it worked for me.
:-)

Ian Zimmerman

unread,
Jan 2, 2003, 8:22:30 PM1/2/03
to

Lars> Ian Zimmerman <i...@speakeasy.org> writes:
>> Empty square boxes :-(

Lars> This probably means that you don't have the right fonts
Lars> installed.

Sorry, but what are the "right" fonts? I told emacs to use Lucida
Console, which _does_ come in 8859-2 encoding. I can verify this with
xfontsel or xfd or any of those.

Lars> I think it was Simon that gave this recipe for how to install
Lars> the required fonts on Debian.

Lars> $ apt-get install `apt-cache search font|grep ^xfonts|awk
Lars> '{print $1}'|sort|uniq|grep -v xfonts-bochs`

I need my disk space for other things.

Does anybody understand how this fontset stuff is supposed to work?

Ian Zimmerman

unread,
Jan 2, 2003, 9:28:11 PM1/2/03
to

Lars> Ian Zimmerman <i...@speakeasy.org> writes:
>> Empty square boxes :-(

Lars> This probably means that you don't have the right fonts
Lars> installed.

After some experiments it seems that Gnus won't display the right
glyphs unless it can find a variant of the _primary_ font in the
required encoding. By primary I mean the one that gives its name to
the fontset. In other words, the whole fontset section looks like
nonsense, null and void, it might just as well not be there.

Comments? _is_ it supposed to work? Or does Gnus bypass it and look
for the glyphs by itself? If so why?

Lars Magne Ingebrigtsen

unread,
Jan 2, 2003, 11:29:00 PM1/2/03
to
Ian Zimmerman <i...@speakeasy.org> writes:

> After some experiments it seems that Gnus won't display the right
> glyphs unless it can find a variant of the _primary_ font in the
> required encoding. By primary I mean the one that gives its name to
> the fontset. In other words, the whole fontset section looks like
> nonsense, null and void, it might just as well not be there.

As far as I know, Gnus just decodes the specified charset, and then
it's up to Emacs to display the resulting characters.

What fontset selection code are you thinking of?

Ian Zimmerman

unread,
Jan 3, 2003, 1:27:31 AM1/3/03
to

itz> After some experiments it seems that Gnus won't display the right
itz> glyphs unless it can find a variant of the _primary_ font in the
itz> required encoding. By primary I mean the one that gives its name
itz> to the fontset. In other words, the whole fontset section looks
itz> like nonsense, null and void, it might just as well not be there.

Lars> As far as I know, Gnus just decodes the specified charset, and
Lars> then it's up to Emacs to display the resulting characters.

Lars> What fontset selection code are you thinking of?

C-h i m emacs <ret> i fontsets <ret> n

What I am saying is that my specifying the ",[CHARSET: FONT-NAME]"
clause has no effect.

Lars Magne Ingebrigtsen

unread,
Jan 3, 2003, 2:14:42 AM1/3/03
to
Ian Zimmerman <i...@speakeasy.org> writes:

> itz> After some experiments it seems that Gnus won't display the right
> itz> glyphs unless it can find a variant of the _primary_ font in the
> itz> required encoding. By primary I mean the one that gives its name
> itz> to the fontset. In other words, the whole fontset section looks
> itz> like nonsense, null and void, it might just as well not be there.
>
> Lars> As far as I know, Gnus just decodes the specified charset, and
> Lars> then it's up to Emacs to display the resulting characters.
>
> Lars> What fontset selection code are you thinking of?
>
> C-h i m emacs <ret> i fontsets <ret> n

Ah. I thought you were talking about font selection code in Gnus.

> What I am saying is that my specifying the ",[CHARSET: FONT-NAME]"
> clause has no effect.

That certainly sounds like a bug. I'm guessing that the Emacs
development list would be a likely place to report this.

Kai Großjohann

unread,
Jan 3, 2003, 4:26:49 PM1/3/03
to
Ian Zimmerman <i...@speakeasy.org> writes:

>iso8859-2: -B&H...

I think that Emacs uses iso-8859-2, not iso8859-2.

--
Ambibibentists unite!

Ian Zimmerman

unread,
Jan 4, 2003, 1:02:00 AM1/4/03
to

>> iso8859-2: -B&H...

Kai> I think that Emacs uses iso-8859-2, not iso8859-2.

Hmm. The manual section says

>> The construct `CHARSET:FONT' specifies which font to use (in this
>> fontset) for one particular character set. Here, CHARSET is the
>> name of a character set, and FONT is the font to use for that
>> character set. You can use this construct any number of times in
>> defining one fontset.

It never does define "name of a character set", and that concept is
not in the index. The only full example given is

Emacs.Fontset-0: -*-fixed-medium-r-normal-*-24-*-*-*-*-*-fontset-24,\
chinese-gb2312:-*-*-medium-r-normal-*-24-*-gb2312*-*

"chinese-gb2312" is indeed one of the things that list-character-sets
displays. Hmmm, i see a "character sets" section in the elisp
manual. Maybe we're missing a crucial hyperlink here.

0 new messages