Gnus development mailing list
 help / color / mirror / Atom feed
From: Nuutti Kotivuori <nuutti.kotivuori@smarttrust.com>
Cc: ding@gnus.org
Subject: Re: '.' at the beginning of summary buffer lines
Date: Thu, 30 Aug 2001 14:40:29 +0300	[thread overview]
Message-ID: <87y9o16al5.fsf@smarttrust.com> (raw)
In-Reply-To: <iluzo8ir8th.fsf@barbar.josefsson.org>

Simon Josefsson wrote:
> Nuutti Kotivuori <nuutti.kotivuori@smarttrust.com> writes:
> 
>>> Anyone know how to insert the U+2018 and U+2019 characters in
>>> emacs?
>>
>> Assuming MULE-UCS - insert-ucs-character. #x2018 works in XEmacs,
>> ?\x2018 in Emacs, I believe - the function takes a simple number
>> from the minibuffer as input. However, the documentation is in
>> MULE-UCS package, you can refer to it there.
> 
> So ****this**** should look nice to everyone that manages UTF-8?

It didn't :) I replaced a whole load of crap with stars so the message
does not get split into 5 charset parts when sending ;)

> It looks nice to me, with a vanilla Emacs 21 and vanilla RedHat
> fonts.

After sending?

> Err, Gnus won't let me post this mail.  QP encoding fails.  It seems
> to think the (emacs) character set for this buffer should be
> `eight-bit-control' instead of `mule-unicode-0100-24ff'.

Hmm. Maybe mm-mime-mule-charset-alist might be in error. I think that
one uses unicode-a, unicode-b, ... for charsets, not
mule-unicode-something.

And another thing is in mm-find-mime-charset-region - it uses a rather
dumb logic in picking utf-8 as the encoding.

> Doesn't Gnus handle the Unicode stuff in Emacs 21?

No idea - I have gotten it to work in XEmacs with MULE-UCS and a small
hack to Gnus code.

[...]

> (I'm manually forcing this mail to be sent anyway, if you edit the
> charset=eight-bit-control into charset=utf-8 maybe it works.)

I got an error in QP decoding :)

>> Character set       ‘   ’
>> --------------------------
>> Macintosh Roman    212 213
>> Macintosh Cyrillic 212 213
>> ISO 8859-7:1987    161 162
>>
>> If you want to get the ISO 8859-7 character, you can say:
>>
>> (make-char 'greek-iso8859-7 161)
>> (make-char 'greek-iso8859-7 162)
> 
> Doesn't seem to work for me, the characters look like a upside down
> !  and a cents character with a vertical line.

Well, those two characters in the ISO 8859-7:1987 are defined to be:

Hex | Dec | Chr | Code | ISO/IEC 10646-1:2000 Character Name
----+-----+-----+------+----------------------------
 A1 | 161 |  ‘  | 8216 | LEFT SINGLE QUOTATION MARK  
 A2 | 162 |  ’  | 8217 | RIGHT SINGLE QUOTATION MARK

How did you see the characters I put in the message? (after Character
set, up there). I put them in the buffer with insert-ucs-character. If
I am not entirely wrong, something bugs if you don't see them as
quotation marks - or can't insert them as such. The sending charset
for the message appears to be ISO-8859-7.

-- Naked


  reply	other threads:[~2001-08-30 11:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 17:33 Florian Weimer
2001-08-26 17:36 ` Henrik Enberg
2001-08-26 17:47   ` Karl Kleinpaste
2001-08-26 18:57     ` Florian Weimer
2001-08-26 18:54       ` Amos Gouaux
2001-08-26 20:08         ` Florian Weimer
2001-08-26 20:59         ` Russ Allbery
2001-08-26 21:26           ` Simon Josefsson
2001-08-29 15:31             ` Harry Putnam
2001-08-29 17:00               ` Simon Josefsson
2001-08-29 18:30                 ` Kai Großjohann
2001-08-29 16:46             ` Nuutti Kotivuori
2001-08-29 18:59               ` Simon Josefsson
2001-08-30 11:40                 ` Nuutti Kotivuori [this message]
2001-08-30 13:55                   ` Josh Huber
2001-08-31 14:08                     ` Nuutti Kotivuori
2001-09-01  0:37                       ` Daniel Pittman
2001-08-31 14:11                     ` Nuutti Kotivuori
2001-08-31 23:29                   ` Simon Josefsson
2001-08-26 21:39           ` Lars Magne Ingebrigtsen
2001-08-26 21:22       ` Kai Großjohann
2001-08-26 23:09       ` Karl Kleinpaste
2001-08-26 18:58   ` Florian Weimer
2001-08-26 19:54     ` Lars Magne Ingebrigtsen
2001-08-27 13:47   ` Emerick Rogul

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=87y9o16al5.fsf@smarttrust.com \
    --to=nuutti.kotivuori@smarttrust.com \
    --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).