On Thursday, 5 September 2013 at 04:31, William Blunn wrote:
> But the documentation says that they are equivalent.
>
> So the documentation would appear to be at odds with the behaviour.
Yeah, this is a bug. This one:
https://rt.cpan.org/Public/Bug/Display.html?id=87267
This was actually fixed
Remember, this is tonight!
On 2 Sep 2013, at 18:45, Peter Corlett wrote:
[...]
> (The) Kings Arms
> 65 Newcomen Street
> SE1 1YT
>
> http://london.randomness.org.uk/wiki.cgi?King%27s_Arms,_SE1_1YT
> http://www.beerintheevening.com/pubs/s/22/2291/Kings_Arms/Borough
On 2013-09-05 09:31, William Blunn wrote:
It seems that decode_utf8(...) is a no-op if the input string has the
UTF8 flag on, but decode("utf8", ...) will always try to decode
regardless of the state of the UTF8 flag.
But the documentation says that they are equivalent.
So the documentation wou
The documentation for Encode::decode_utf8 begins:
$string = decode_utf8($octets [, CHECK]);
Equivalent to $string = decode("utf8", $octets [, CHECK]).
So what should the following one-liner emit?
perl -E 'use charnames ":full"; use Encode; my $x = "\N{LATIN CAPITAL
LETTER A WI
