From: "Роман Донченко" <dpb@corrigendum.ru>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jay Soffian" <jaysoffian@gmail.com>, "Jeff King" <peff@peff.net>,
"Thomas Rast" <tr@thomasrast.ch>
Subject: Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly
Date: Mon, 24 Nov 2014 21:09:48 +0300 [thread overview]
Message-ID: <op.xpucqml8nngjn5@freezie> (raw)
In-Reply-To: <CAPc5daVjNDg5CcWsMwfn=DZhwpCBdU2LYXOpFWZwhx2p8hLRww@mail.gmail.com>
Junio C Hamano <gitster@pobox.com> писал в своём письме Mon, 24 Nov 2014
10:27:51 +0300:
> On Sun, Nov 23, 2014 at 3:50 PM, Роман Донченко <dpb@corrigendum.ru>
> wrote:
>> The RFC says that they are to be concatenated after decoding (i.e. the
>> intervening whitespace is ignored).
>>
>> I change the sender's name to an all-Cyrillic string in the tests so
>> that
>> its encoded form goes over the 76 characters in a line limit, forcing
>> format-patch to split it into multiple encoded words.
>>
>> Since I have to modify the regular expression for an encoded word
>> anyway,
>> I take the opportunity to bring it closer to the spec, most notably
>> disallowing embedded spaces and making it case-insensitive (thus
>> allowing
>> the encoding to be specified as both "q" and "Q").
>>
>> Signed-off-by: Роман Донченко <dpb@corrigendum.ru>
>
> This sounds like a worthy thing to do in general.
>
> I wonder if the C implementation we have for mailinfo needs similar
> update, though. I vaguely recall that we have case-insensitive start for
> q/b segments, but do not remember the details offhand.
That's what git am uses, right? I think that already works correctly (or
at least doesn't have the bug this patch fixes). I didn't do extensive
testing or look at the code, though.
>
> Was the change to the test to use Cyrillic really necessary, or did it
> suffice if you simply extended the existsing "Funny Name" spelled with
> strange accents, but you substituted the whole string anyway?
>
> Until I found out what the new string says by running web-based
> translation on it, I felt somewhat uneasy. As I do not read
> Cyrillic/Russian, we may have been adding some profanity without
> knowing. It turns out that the string just says "Cyrillic Name", so I am
> not against using the new string, but it simply looked odd to replace the
> string whole-sale when you merely need a longer string. It made it look
> as if a bug was specific to Cyrillic when it wasn't.
Ah, if only I had thought of including profanity beforehand. ;-)
Seriously though, I just needed to hit the 76 character limit, and
switching the keyboard layout is a lot easier than copypasting Latin
letters with diacritics (plus I had trouble coming up with a long enough
extension of "Funny Name"...). I can see how that's problematic, though;
I'll change it.
> As you may notice by reading "git log --no-merges" from recent history,
> we tend not to say "I did X, I did Y". If the tone of the above message
> were more similar to them, it may have been easier to read.
Technically, I said "I do", not "I did"... but sure, point taken.
Roman.
next prev parent reply other threads:[~2014-11-24 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 23:50 [PATCH] send-email: handle adjacent RFC 2047-encoded words properly Роман Донченко
2014-11-24 7:27 ` Junio C Hamano
2014-11-24 15:44 ` Jeff King
2014-11-24 18:09 ` Роман Донченко [this message]
2014-11-24 15:36 ` Jeff King
2014-11-24 18:26 ` Роман Донченко
2014-11-24 23:03 ` Jeff King
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=op.xpucqml8nngjn5@freezie \
--to=dpb@corrigendum.ru \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=peff@peff.net \
--cc=tr@thomasrast.ch \
/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).