Bug #113570 for CSS-Inliner: Install fails

Mon Apr 04 13:34:52 2016 rlauer6 [...] comcast.net - Ticket created

Subject:	Install fails
Date:	Mon, 4 Apr 2016 13:34:43 -0400
To:	bug-CSS-Inliner [...] rt.cpan.org
From:	Rob Lauer <rlauer6 [...] comcast.net>

Constant(\N{INTERROBANG}‽ </body> </html> ) unknown: (possibly a missing "use charnames ...") at t/entities_utf8.t line 13, within string Constant(\N{INTERROBANG}) unknown: (possibly a missing "use charnames ...") in regex; marked by <-- HERE in m/Got any games\N{INTERROBANG} <-- HERE ‽/ at t/entities_utf8.t line 34. t/entities_utf8.t ......... Dubious, test returned 255 (wstat 65280, 0xff00) Any suggestions? Thanks Rob

Wed Apr 06 15:55:54 2016 KAMELKEV [...] cpan.org - Correspondence added

Hi Rob, What version of perl are you using? Named characters have been part of the standard Perl distribution since 5.16, you can read about them here: http://perldoc.perl.org/charnames.html My guess is that you are not using 5.16 yet? -Kevin On Mon Apr 04 13:34:52 2016, rlauer6@comcast.net wrote: Show quoted text

> Constant(\N{INTERROBANG}‽ > </body> > </html> > ) unknown: (possibly a missing "use charnames ...") at > t/entities_utf8.t line 13, within string > Constant(\N{INTERROBANG}) unknown: (possibly a missing "use charnames > ...") in regex; marked by <-- HERE in m/Got any > games\N{INTERROBANG} <-- HERE ‽/ at t/entities_utf8.t line > 34. > t/entities_utf8.t ......... > Dubious, test returned 255 (wstat 65280, 0xff00) > > > Any suggestions? > > Thanks > > Rob

Wed Apr 06 15:55:55 2016 The RT System itself - Status changed from 'new' to 'open'

Wed Apr 06 16:19:41 2016 rlauer6 [...] comcast.net - Correspondence added

Subject:	Re: [rt.cpan.org #113570] Install fails
Date:	Wed, 6 Apr 2016 16:19:29 -0400
To:	bug-CSS-Inliner [...] rt.cpan.org
From:	Rob Lauer <rlauer6 [...] comcast.net>

perl 5.10 Rob On Wed, Apr 6, 2016 at 3:55 PM, Kevin Hatim Kamel via RT < bug-CSS-Inliner@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=113570 > > > Hi Rob, > > What version of perl are you using? > > Named characters have been part of the standard Perl distribution since > 5.16, you can read about them here: > http://perldoc.perl.org/charnames.html > > My guess is that you are not using 5.16 yet? > > -Kevin > > > On Mon Apr 04 13:34:52 2016, rlauer6@comcast.net wrote:

> > Constant(\N{INTERROBANG}‽ > > </body> > > </html> > > ) unknown: (possibly a missing "use charnames ...") at > > t/entities_utf8.t line 13, within string > > Constant(\N{INTERROBANG}) unknown: (possibly a missing "use charnames > > ...") in regex; marked by <-- HERE in m/Got any > > games\N{INTERROBANG} <-- HERE ‽/ at t/entities_utf8.t line > > 34. > > t/entities_utf8.t ......... > > Dubious, test returned 255 (wstat 65280, 0xff00) > > > > > > Any suggestions? > > > > Thanks > > > > Rob

> > > >

Thu Apr 07 02:56:32 2016 SREZIC [...] cpan.org - Correspondence added

See also http://matrix.cpantesters.org/?dist=CSS-Inliner+4003 --- tests fail on all systems with perl < 5.16. On 2016-04-06 15:55:54, KAMELKEV wrote: Show quoted text

> Hi Rob, > > What version of perl are you using? > > Named characters have been part of the standard Perl distribution > since 5.16, you can read about them here: > http://perldoc.perl.org/charnames.html > > My guess is that you are not using 5.16 yet? > > -Kevin > > > On Mon Apr 04 13:34:52 2016, rlauer6@comcast.net wrote:

> > Constant(\N{INTERROBANG}‽ > > </body> > > </html> > > ) unknown: (possibly a missing "use charnames ...") at > > t/entities_utf8.t line 13, within string > > Constant(\N{INTERROBANG}) unknown: (possibly a missing "use charnames > > ...") in regex; marked by <-- HERE in m/Got any > > games\N{INTERROBANG} <-- HERE ‽/ at t/entities_utf8.t line > > 34. > > t/entities_utf8.t ......... > > Dubious, test returned 255 (wstat 65280, 0xff00) > > > > > > Any suggestions? > > > > Thanks > > > > Rob

Wed Jul 27 00:41:09 2016 KAMELKEV [...] cpan.org - Correspondence added

Hi Rob, The library now makes an attempt (not a very good one...) to support UTF-8 characters. Several people requested UTF-8 support, and given that it's now 2016 it seemed appropriate to add. Perl 5.10 does not support UTF-8, which is evidenced by the error you are seeing. I would suggest using one of the older versions that predates the UTF-8 changes, at which point you should not run into this problem. Besides the UTF-8 support there isn't too much else that changed, so you should be pretty good with the older version. thanks, Kevin On Wed Apr 06 16:19:41 2016, rlauer6@comcast.net wrote: Show quoted text

> perl 5.10 > > Rob > > On Wed, Apr 6, 2016 at 3:55 PM, Kevin Hatim Kamel via RT < > bug-CSS-Inliner@rt.cpan.org> wrote: >

> > <URL: https://rt.cpan.org/Ticket/Display.html?id=113570 > > > > > Hi Rob, > > > > What version of perl are you using? > > > > Named characters have been part of the standard Perl distribution since > > 5.16, you can read about them here: > > http://perldoc.perl.org/charnames.html > > > > My guess is that you are not using 5.16 yet? > > > > -Kevin > > > > > > On Mon Apr 04 13:34:52 2016, rlauer6@comcast.net wrote:

> > > Constant(\N{INTERROBANG}‽ > > > </body> > > > </html> > > > ) unknown: (possibly a missing "use charnames ...") at > > > t/entities_utf8.t line 13, within string > > > Constant(\N{INTERROBANG}) unknown: (possibly a missing "use charnames > > > ...") in regex; marked by <-- HERE in m/Got any > > > games\N{INTERROBANG} <-- HERE ‽/ at t/entities_utf8.t line > > > 34. > > > t/entities_utf8.t ......... > > > Dubious, test returned 255 (wstat 65280, 0xff00) > > > > > > > > > Any suggestions? > > > > > > Thanks > > > > > > Rob

> > > > > > > >

Wed Jul 27 01:19:18 2016 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

On Wed Jul 27 00:41:09 2016, KAMELKEV wrote: Show quoted text

> Hi Rob, > > The library now makes an attempt (not a very good one...) to support > UTF-8 characters. > > Several people requested UTF-8 support, and given that it's now 2016 > it seemed appropriate to add. > > Perl 5.10 does not support UTF-8, which is evidenced by the error you > are seeing.

Perl 5.10 most certainly does support UTF-8, but the \N{...} construct requires the charnames module to be loaded. Perl 5.16 was the first version that would load it automatically for you behind the scenes when you write \N{...}. Two of the tests that use \N already have this line: use charnames ':full'; If you add it to the other one (entities_utf8.t), it works on 5.10 as well. See the attachment.

Subject:

open_zWeLAKHz.txt

diff -rup CSS-Inliner-4003-EnCYfn/t/entities_utf8.t CSS-Inliner-4003-VZHaAg/t/entities_utf8.t --- CSS-Inliner-4003-EnCYfn/t/entities_utf8.t 2015-11-23 16:33:10.000000000 -0800 +++ CSS-Inliner-4003-VZHaAg/t/entities_utf8.t 2016-07-26 22:18:04.000000000 -0700 @@ -5,6 +5,7 @@ use lib qw( ./lib ../lib ); use Test::More; use Cwd; use CSS::Inliner; +use charnames ':full'; plan(tests => 3);

Mon Sep 19 16:46:48 2016 KAMELKEV [...] cpan.org - Correspondence added

That appears to be the necessary detail I needed to fix this SPROUT. Thanks. In the middle of a sprint, but can apply the suggested change and deploy afterwards. On Wed Jul 27 01:19:18 2016, SPROUT wrote: Show quoted text

> On Wed Jul 27 00:41:09 2016, KAMELKEV wrote:

> > Hi Rob, > > > > The library now makes an attempt (not a very good one...) to support > > UTF-8 characters. > > > > Several people requested UTF-8 support, and given that it's now 2016 > > it seemed appropriate to add. > > > > Perl 5.10 does not support UTF-8, which is evidenced by the error you > > are seeing.

> > Perl 5.10 most certainly does support UTF-8, but the \N{...} construct > requires the charnames module to be loaded. Perl 5.16 was the first > version that would load it automatically for you behind the scenes > when you write \N{...}. > > Two of the tests that use \N already have this line: > > use charnames ':full'; > > If you add it to the other one (entities_utf8.t), it works on 5.10 as > well. See the attachment.

Sun Jul 16 19:46:59 2017 KAMELKEV [...] cpan.org - Correspondence added

Fixed in 4008

Sun Jul 16 19:47:05 2017 KAMELKEV [...] cpan.org - Status changed from 'open' to 'resolved'