Le jeudi 13 juin 2024 à 00:29 +0200, Guillem Jover a écrit : > On Thu, 2024-06-13 at 00:02:43 +0200, Martin Quinson wrote: > > Le mercredi 12 juin 2024 à 17:14 +0200, Guillem Jover a écrit : > > > > > > Unfortunately neither Encode::find_encoding()->name nor > > > Encode::resolve_alias() seem helpful here because they return > > > "utf-8-strict" for "UTF-8" which will not match against "utf-8" for > > > the canonical "utf8". > > > > The problem is that Perl has a rather unexpected behavior wrt utf8, UTF-8 > > and UTF8. These names are not aliases of others in Perl. See > > https://perldoc.perl.org/Encode#UTF-8-vs.-utf8-vs.-UTF8 > > Sure, but here I think this does not matter (in theory), because it > depends on how the pod parser interprets the encoding name, and from > checking the perl code it seems it maps /utf-?8/i to ":encoding(UTF-8)". > So they are really treated the same, at least when it comes to POD, that > does not mean perl has that distinction for the encoding in other > contexts.
Ok, ok. You are perfectly right. This distinction between utf8 and UTF-8 is perfectly useless in the context of POD files. I just pushed yet another commit to not do that in POD. > Please tell me whether it looks good to you now. Thanks, Mt
signature.asc
Description: This is a digitally signed message part
