Strange encoding differences between *Summary* & *Article*

Strange encoding differences between *Summary* & *Article*

[Stephen Zander]

In <19990127114144A.nakaji@zeisei.dpri.kyoto-u.ac.jp>, recently seen
on this list the following encoding
(=?iso-2022-jp?B?GyRCJEokKyQ4GyhC?=) resulted in '~~~' appearing in
the *Summary* buffer while the correct hirigana was displayed in the
*Article* buffer.

Is that supposed to happen?

-- 
Stephen
---
It should be illegal to yell "Y2K" in a crowded economy.  :-) -- Larry Wall

Re: Strange encoding differences between *Summary* & *Article* (なかじ)

[Lars Magne Ingebrigtsen]

Stephen Zander <gibreel@pobox.com> writes:

> In <19990127114144A.nakaji@zeisei.dpri.kyoto-u.ac.jp>, recently seen
> on this list the following encoding
> (=?iso-2022-jp?B?GyRCJEokKyQ4GyhC?=) resulted in '~~~' appearing in
> the *Summary* buffer while the correct hirigana was displayed in the
> *Article* buffer.

I'm unable to reproduce this with XEmacs 21 or Emacs 20.  When I view
this article, for instance, I get, er, hirgana (what does that mean)?, 
displayed in the summary buffer.  

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

Re: Strange encoding differences between *Summary* & *Article* (Ê«¸)

[Jason L Tibbitts III]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> When I view this article, for instance, I get, er, hirgana (what does
LMI> that mean)?, displayed in the summary buffer.

Japanese has two alphabets containing 46 characters apiece, in addition to
the thousands of pictographs called kanji.

Katakana, the angular alphabet, is used to write exclamations, words
borrowed from other languages, and for emphasis.

Hiragana, the cursive alphabet, is used pretty much everywhere else.

One day I must learn how to get Emacs/Gnus to do Japanese; I feel years of
classes and study circling the bowl due to lack of practice...

 - J<

Re: Strange encoding differences between *Summary* & *Article* (なかじ)

[なかじ]

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

Lars> I get, er, hirgana (what does that mean)?, 

Right it's hiragana. My family name, NAKAJI.

Re: Strange encoding differences between *Summary* & *Article* ( =?iso-2022-jp-2?b?GyRCJEokKyQ4GyhC?=)

[Stephen Zander]

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
    Lars> I'm unable to reproduce this with XEmacs 21 or Emacs 20.
    Lars> When I view this article, for instance, I get, er, hirgana
    Lars> (what does that mean)?, displayed in the summary buffer.

Hmm.  Maybe it's an Xemacs 20.4 problem then.  BTW, should *Summary*
have any particular coding-system (or whatever it is)?  Or do you get
the font changes with text properties?

-- 
Stephen
---
It should be illegal to yell "Y2K" in a crowded economy.  :-) -- Larry Wall

Re: Strange encoding differences between *Summary* & *Article* ( =?iso-2022-jp-2?b?GyRCJEokKyQ4GyhC?=)

[Lars Magne Ingebrigtsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 879 bytes --]

^[$B$J$+$8^[(B <nakaji@zeisei.dpri.kyoto-u.ac.jp> writes:

[...]

This Subject header displayed a bit oddly for me in the article buffer 
-- the "(^[$B$J$+$8^[(B)" appeared on a line by itself, in the continuation of 
the first line.  So I `C-u g', and see that the Subject header is
really:

Subject: Re: Strange encoding differences between *Summary* & *Article*
 =?iso-2022-jp?B?KBskQiRKJCskOBsoQik=?=

Now, this is a perfectly valid header generated by Mew.  In fact, it's
probably the only way to create this header that is compliant with
RFC2047.  But RFC2047 says nothing about removing linear white space
before encoded words when displaying; only about removing linear white 
space *between* encoded words.

As far as I can see.

So how should Gnus display this header?

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

Re: Strange encoding differences between *Summary* & *Article* ( =?iso-2022-jp-2?b?GyRCJEokKyQ4GyhC?=)

[Lars Magne Ingebrigtsen]

Stephen Zander <gibreel@pobox.com> writes:

> Hmm.  Maybe it's an Xemacs 20.4 problem then.  BTW, should *Summary*
> have any particular coding-system (or whatever it is)?  Or do you get
> the font changes with text properties?

No; Mule takes care of all the font thingies.

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