Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: Re[2]: 8-bit headers not encoded
Date: 09 Jan 2000 00:04:41 +0300	[thread overview]
Message-ID: <m3k8lkff6e.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Florian Weimer's message of "08 Jan 2000 21:38:24 +0100"

"FW" == Florian Weimer writes:

 >> Then, 8-bit cyrillic text in subject was sent as 8-bit, but NOT in
 >> koi8-r; it was in iso-8859-5 encoding. what should i do to make
 >> gnus use koi8-r for 8-bit text in headers?

 FW> Okay, I'll try to fix it as soon as I find some time
 FW> (unfortunately, that's a big problem at the moment...).  In the
 FW> meantime, could you resist to set this variable at all?

well, when posting to some newsgroups, i need to use 8-bit koi8-r
encoded text in headers (e.g. subject) because otherwise cyrillic text
will be messed up when gatewaying them e.g. to FidoNet.

so, i do need this feature :-) (meanwhile, i could use gnus 5.8.2)

 FW> The default value seems to work correctly (it uses
 FW> quoted-printable in the header).

to be pedantic, gnus uses for iso-8859-5 not quoted-printable, but `b'
type encoded-word (which is closer to base64 than to quoted-printable).

 FW> BTW, do you specify `iso-8859-5' somewhere as default?

Not much, but i wish i had a possibility to specify preferable
cyrillic charsets for message body on a per-group basis. currently,
gnus insists on using a charset which is defined in a line like

(put-charset-property 'cyrillic-iso8859-5 'preferred-coding-system 'koi8-r)

for all cyrillic postings. I'd like to be able to specify a preferred
cyrillic charset on a per-group basis (e.g. like
gnus-group-posting-charset-alist). this would be useful not only for
cyrillic, but also for other languages which have several popular
charsets in use. for russian, we have at least five charsets: koi8-r,
windows-1251, cp866, mac-cyrillic, iso-8859-5 (there are even more of
them: e.g. cp855; the total number of variants is more than 20
different 8-bit cyrillic charsets!).

then one may wish to use by default, say, a windows-1251 charset for
some newsgroups, and koi8-r otherwise, etc...

for european latin-based languages, there are also several charsets in
use (e.g., ISO latin-N charsets and windows codepages)...

 FW> I wonder where that charset is coming from.

it is coming from ISO. :-) It was once a russian state standard
GOST19768-74, but later, koi8-r (and in some areas, cp866, and then
cp1251) was adopted as a de-facto standard.

	Best regards, -- Vladimir.



      reply	other threads:[~2000-01-08 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-05 18:45 Roman Belenov
2000-01-05 20:02 ` Florian Weimer
2000-01-06 11:13   ` Re[2]: " Roman Belenov
2000-01-06 13:32     ` Florian Weimer
2000-01-06 14:25       ` Re[4]: " Roman Belenov
2000-01-06 22:07       ` Re[2]: " Vladimir Volovich
2000-01-06 23:01         ` Kai Großjohann
2000-01-08 20:38         ` Florian Weimer
2000-01-08 21:04           ` Vladimir Volovich [this message]

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=m3k8lkff6e.fsf@vvv.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    /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).