This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc git commit hooks update.


* Joseph Myers:

> On Wed, 17 Apr 2019, Carlos O'Donell wrote:
>
>> > One problem with the old hooks was that they did not generate a
>> > Content-Type header, which was unhelpful when the mails also weren't pure
>> > ASCII.  I see the new ones are generating 'Content-Type: text/plain;
>> > charset="us-ascii"'.  Will they also be smart about specifying an
>> > appropriate character set (so UTF-8 if the commit message / author name /
>> > diff contents are valid UTF-8 but not ASCII, for example)?
>> 
>> All of this is handled by python's email package and some handling
>> on the hooks part. If everything is ASCII then we don't do any special
>> encoding and just send ASCII. Otherwise we choose UTF-8 first and if
>> that fails a decode test then we fallback to ISO-8859-1.
>
> This does not seem to be working as intended.  See e.g. 
> https://sourceware.org/ml/glibc-cvs/2019-q2/msg00147.html (UTF-8 bytes 
> marked as us-ascii, so ’ appears as â??, for example).

I expect that this is unrelated to the change and was this way before.
I haven't modified those parts.

Defaulting to charset=utf-8 is probably the best option here, even
though the message text might not be UTF-8 always.  I think this
requires modifications to the Python scripts.

Thanks,
Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]