9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] conversion of charsets in upas/fs
Date: Tue,  1 Feb 2005 18:11:07 +0100	[thread overview]
Message-ID: <5d1294dbc2ec360ffbcdcc8fd86e829f@voidness.de> (raw)
In-Reply-To: <58218e63961d40d19c91d9e10f0be666@voidness.de>

> 0xfc represents 'ü' in iso-8859-15 but sed replaces it by 0xc2 and
> 0xc8.  Why?  It should only hide bogus 'From ' lines in the mail body.
> Is sed allowed to replace 0xfc by something different here?

I don't feel good answering to my own mails so often.  But someone
mailed to me off-list and made clear that sed doesn't have to be able
to read non-utf input. I understand that point now.

Is it then desireable for pipeto.lib to deal with the situation?  I am
trying to modify it to fit my needs.  If pipeto.lib should deal with
incoming 8bit ISO-* mails I will put it as patch on sources when I
finished.

Heiko



  reply	other threads:[~2005-02-01 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29 13:57 Heiko Dudzus
2005-01-31  1:21 ` Kenji Okamoto
2005-01-31 14:05   ` Heiko Dudzus
2005-01-31 18:40     ` Russ Cox
2005-01-31 19:19       ` boyd, rounin
2005-02-01  8:24       ` Heiko Dudzus
2005-02-01 10:29         ` Heiko Dudzus
2005-02-01 17:11           ` Heiko Dudzus [this message]
2005-02-01 20:41             ` Sape Mullender
2005-02-01 20:45               ` boyd, rounin
2005-02-01 18:26           ` Russ Cox
2005-02-01 18:37             ` rog
2005-02-01 19:50               ` boyd, rounin
2005-02-02 10:59               ` Heiko Dudzus
2005-02-02 13:48                 ` Russ Cox
2005-02-02 23:41                   ` Heiko Dudzus
2005-02-01  1:42     ` Kenji Okamoto
2005-02-01  3:42       ` Russ Cox

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=5d1294dbc2ec360ffbcdcc8fd86e829f@voidness.de \
    --to=heiko.dudzus@gmx.de \
    --cc=9fans@cse.psu.edu \
    /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).