From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: patch: \201 when cache (was: bug: \201 in summary buffer)
Date: 02 May 1999 16:54:25 +0200 [thread overview]
Message-ID: <87g15fcyji.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "02 May 1999 10:27:01 -0400"
François Pinard <pinard@iro.umontreal.ca> writes:
> Allowed or not, such characters often occur in practice. I've been told
> that some countries consider normal and very practical, despite standards
> may say, to just let 8-bit clean transport of email, and then assume their
> national charset. I quite understand such reasons, and for email which
> is not internationally aimed, encoding headers is just unneeded complexity.
>
> In my personal case, I much prefer international-aware headers. But we
> should not be utterly dogmatic for others, and be prepared to cope with
> 8-bit characters in headers, whatever standards may say.
Being from such a country, I (for once) fully agree with everything
Francois said.
Speaking of "national charsets", we are still waging a battle to make
iso-8859-2 the standardly used charset, instead of the Windows "code
page 1250".
next prev parent reply other threads:[~1999-05-02 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-31 8:39 bug: \201 in summary buffer Vladimir Volovich
1999-03-31 13:24 ` Kai.Grossjohann
1999-04-17 5:37 ` Lars Magne Ingebrigtsen
1999-04-17 13:36 ` Kai.Grossjohann
1999-05-02 5:34 ` patch: \201 when cache (was: bug: \201 in summary buffer) Shenghuo ZHU
1999-05-02 13:17 ` Stainless Steel Rat
1999-05-02 14:27 ` François Pinard
1999-05-02 14:43 ` Stainless Steel Rat
1999-05-02 17:21 ` François Pinard
1999-05-03 16:04 ` Stainless Steel Rat
1999-05-02 14:54 ` Hrvoje Niksic [this message]
1999-05-02 16:46 ` Per Abrahamsen
1999-05-02 16:44 ` Shenghuo ZHU
1999-05-03 16:05 ` Stainless Steel Rat
1999-05-02 19:43 ` Kai.Grossjohann
1999-05-03 16:13 ` Stainless Steel Rat
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=87g15fcyji.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).