Karl Williamson <public@khwilliamson.com> wrote on Wed, 13 Apr 2011 09:44:39 MDT: > I've now pushed to blead, at Jesses's suggestion, all the pod changes. > These include things in perlre that address this confusion. I started out noticing that perlunicode was talking about warnings categories in all caps when it shouldn't. 1296 Perl will warn (using the warning category SURROGATE which is a 1297 sub-category of UTF8) if an attempt is made 1345 (using the warning category NONCHAR which is a sub-category of UTF8) if 1354 NON_UNICODE which is a sub-category of UTF8) if an attempt is made to I had just planned to generate a patch for those, but then when I got in there, I ended up doing a light proofread. The patch below looks bigger than it is. Specific things I changed include: * Specified CWCM instead of making people sift through perluniprops; hope that's right. * Updated the tr18 ref to the current v13, and made sure that we were indeed still current with that. v13 includd the \N{} recommendation. * Added a footnote to Unicode::LineBreak in the tr18 table. * Tried to fixed the brain-buster about all not unbearded denizens not shaving themselves except for the barber's wife. Sorry. I mean this one: In C<quotemeta> or its inline equivalent C<\Q>, all characters whose code points are above 127 are not quoted in UTF-8 encoded strings, but all are quoted in UTF-8 strings. That (still) makes no sense to me. Here's the wording I came up with that reflects what I *thought* it was trying to say: In C<quotemeta> or its inline equivalent C<\Q>, no characters code points above 127 are quoted in UTF-8 encoded strings, but in byte encoded strings, code points between 128-255 are always quoted. See previous mail. Karl and others should probably make sure I am not misstating anything in the proffered patch below. --tomThread Previous | Thread Next