develooper Front page | perl.perl5.porters | Postings from June 2019

Re: [perl #134180] [PATCH] overload::OverloadedStringify docs andtests

Thread Previous | Thread Next
June 7, 2019 09:26
Re: [perl #134180] [PATCH] overload::OverloadedStringify docs andtests
Message ID:
Dave Mitchell writes:

> the bytes in patch 0002 just before the word "make" are
>     ef  bf  bd  ef  bf  bd  ef  bf  bd
> which when decoded as utf8, form these characters
>     "\x{fffd}\x{fffd}\x{fffd}"
> So I think the patches probably need resubmitting.

Ascii-only patches attached.

(That was an opening double-quote mark when I typed it, U+201C. It
should've had the UTF-8 bytes E2 80 9C.)

Dagfinn Ilmari Mannsåker writes:

> This is 2019, everything should be Unicode-capable by now,

I agree. Especially since some committers have non-Ascii characters in
their names!

And as you show, there are plenty of commit messages already
successfully using non-Ascii characters. However, what turned up on the
mailing list was clearly unusable.

The attachments in my ‘sent’ folder are unmangled if I open them with
Vim, but possibly insufficiently labelled as to how to interpret them; I
couldn't see anywhere in Zoho's webmail client to specify attachment
headers. It may have been that if I'd sent them some other way they
would have made it through fine.

Or maybe only folk with commit bits are free to use any characters in
their messages, and those of us submitting via RT need to use a
restricted subset. I shall try to remember to watch my typing in future.

Hugo van der Sanden via RT writes:

> All three of your commit messages have some utf8 in there,

Thanks for spotting the issue, Hugo (and the other typo).

Apologies for the distraction, all. 

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About