From: Adrian Bunk <bunk@stusta.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
mgarski@post.pl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Convert files to UTF-8 and some cleanups
Date: Mon, 14 May 2007 18:46:08 +0200 [thread overview]
Message-ID: <20070514164608.GS7984@stusta.de> (raw)
In-Reply-To: <46488D6A.3030608@s5r6.in-berlin.de>
On Mon, May 14, 2007 at 06:25:14PM +0200, Stefan Richter wrote:
> John Anthony Kazos Jr. wrote:
> > You can't post a patch to UTF-8 in plain text, because it isn't plain
> > text.
>
> Of course it is, you said so...
>
> > MTAs and MUAs mangle the hell out of them. Look back in the archives
> > for my postings. Once you've got something in UTF-8, -*THEN*- you can post
> > in plain inline text.
>
> ...yourself. Just send as
>
> Content-type: text/plain; charset="utf-8"
>
> Of course a patch like that will usually contain several character sets,
> but that's no problem as long as the byte codes are preserved and we can
> easily see how the end result looks like. The important thing is that
> the submitter's and committer's MUAs do it right and reviewers' MUAs do
> it sort of right. Also, nobody cares if there is still some pre-WWI
> 7bit-only MTA operated in some lone desert town. And if some web
> archive of LKML isn't compatible to internet mail, then that's tough luck.
The problem is that the unconverted characters are always invalid UTF-8 [1],
and it's 100% correct for a MUA to convert these invalid UTF-8
characters to replacement characters - if a MUA claims to send valid
charset="utf-8", it is simply not allowed to preserve the byte codes.
> Stefan Richter
cu
Adrian
[1] except for some cases with two or more non 7bit ASCII
characters in a row
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-05-14 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 23:54 [PATCH] Convert files to UTF-8 and some cleanups Marcin Garski
2007-05-14 0:08 ` Marcin Garski
2007-05-14 14:14 ` Stefan Richter
2007-05-14 15:28 ` John Anthony Kazos Jr.
2007-05-14 16:25 ` Stefan Richter
2007-05-14 16:41 ` Stefan Richter
2007-05-14 16:46 ` Adrian Bunk [this message]
2007-05-14 17:17 ` Stefan Richter
2007-05-14 17:48 ` Jan Engelhardt
2007-05-14 18:06 ` Stefan Richter
2007-05-14 20:10 ` Jan Engelhardt
2007-05-14 20:25 ` Adrian Bunk
2007-05-14 20:36 ` Jan Engelhardt
2007-05-14 20:41 ` Adrian Bunk
2007-05-14 21:14 ` Jan Engelhardt
2007-05-14 22:20 ` Stefan Richter
2007-05-15 8:05 ` Jan Engelhardt
2007-05-15 16:23 ` [PATCH] Pekka Pietikainen goes UTF-8 Pekka Pietikainen
2007-05-16 6:05 ` H. Peter Anvin
2007-05-16 6:55 ` Jan Engelhardt
2007-05-16 15:11 ` H. Peter Anvin
2007-05-16 16:38 ` [PATCH] Pekka Pietikainen goes UTF-8 (try #2) Pekka Pietikainen
2007-05-16 17:16 ` Pekka Pietikainen
2007-05-16 17:53 ` Björn Steinbrink
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=20070514164608.GS7984@stusta.de \
--to=bunk@stusta.de \
--cc=jakj@j-a-k-j.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarski@post.pl \
--cc=stefanr@s5r6.in-berlin.de \
/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