File tree Expand file tree Collapse file tree 1 file changed +24
-1
lines changed Expand file tree Collapse file tree 1 file changed +24
-1
lines changed Original file line number Diff line number Diff line change @@ -249,7 +249,30 @@ XXX Changes (i.e. rewording) of diagnostic messages go here
249249
250250=item *
251251
252- XXX Describe change here
252+ Certain diagnostics about byte sequences that are supposed to comprise a
253+ UTF-8 encoded character, but that are invalid in some way, now don't
254+ include bytes irrelevant to that determination. An example is
255+
256+ =over
257+
258+ =item old message
259+
260+ Malformed UTF-8 character: C<\xc1\x27> (any UTF-8 sequence that starts with
261+ C<\xc1> is overlong which can and should be represented with a different,
262+ shorter sequence)
263+
264+ =item new message
265+
266+ Malformed UTF-8 character: C<\xc1> (any UTF-8 sequence that starts with
267+ C<\xc1> is overlong which can and should be represented with a different,
268+ shorter sequence)
269+
270+ =back
271+
272+ In this case the C<\xc1> is all that is needed to make the sequence
273+ invalid. Whatever comes after it is irrelevant (in this case, C<\x27>),
274+ and including it in the message might lead the reader to think that it
275+ somehow does matter.
253276
254277=back
255278
You can’t perform that action at this time.
0 commit comments