Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Sep 2012 16:33:15 +0200
From:      Michael Gmelin <freebsd@grem.de>
To:        "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
Subject:   Re: Problems submitting patch containing UTF-8 characters
Message-ID:  <25078838-7464-440D-8977-DC2671AE03F3@grem.de>
In-Reply-To: <20120930141935.GA88537@charon.picobyte.net>
References:  <20120930050803.7914caf6@bsd64.grem.de> <20120930141935.GA88537@charon.picobyte.net>

next in thread | previous in thread | raw e-mail | index | archive | help


On 30 Sep 2012, at 16:19, Shaun Amott <shaun@FreeBSD.org> wrote:

> On Sun, Sep 30, 2012 at 05:08:03AM +0200, Michael Gmelin wrote:
>> I recently ran into a problem submitting a PR containing UTF-8
>> characters, they ended up garbled, so the maintainer couldn't apply the
>> patch cleanly.
>=20
> GNATS, unfortunately, records no information about character encoding.
> To make matters worse, it actually removes many headers from e-mail
> replies, meaning query-pr.cgi can usually only work on guesses and
> assumptions.
>=20
> Headers are however preserved inside MIME parts, and if there are any of
> these headers, they are used; but in this case your MUA hasn't included
> encoding information here.
>=20
> Shaun
>=20
> --=20
> Shaun Amott // PGP: 0x6B387A9A
> "A foolish consistency is the hobgoblin
> of little minds." - Ralph Waldo Emerson

The question remains though, why is it trying to re-encode characters as UTF8=
 when it just received what should be 8bit ASCII to it (passing it through t=
ransparently should work)? Especially in case of a binary attachment (which i=
t shows correctly in base64 encoded form but tries to UTF-8 encode on downlo=
ad). To me this looks like a (web server?) configuration issue.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25078838-7464-440D-8977-DC2671AE03F3>