Skip Menu |

This queue is for tickets about the CSS-DOM CPAN distribution.

Report information
The Basics
Id: 85955
Status: resolved
Priority: 0/
Queue: CSS-DOM

People
Owner: Nobody in particular
Requestors: gregoa [...] debian.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: [PATCH] POD fixes
Date: Fri, 7 Jun 2013 22:17:52 +0200
To: bug-css-dom [...] rt.cpan.org
From: gregor herrmann <gregoa [...] debian.org>
In Debian we are currently applying the attached patch to CSS-DOM. We thought you might be interested in it, too. Description: add encoding to non-ascii pod Pod::Simple got more picky Origin: vendor Author: gregor herrmann <gregoa@debian.org> Last-Update: 2013-06-07 Thanks in advance, gregor herrmann, Debian Perl Group

Message body is not shown because sender requested not to inline it.

From: dsteinbrunner [...] pobox.com
On Fri Jun 07 16:18:15 2013, gregoa@debian.org wrote: Show quoted text
> In Debian we are currently applying the attached patch to CSS-DOM. > We thought you might be interested in it, too. > > Description: add encoding to non-ascii pod > Pod::Simple got more picky > Origin: vendor > Author: gregor herrmann <gregoa@debian.org> > Last-Update: 2013-06-07 > > > Thanks in advance, > gregor herrmann, Debian Perl Group
Alternately, you could replace the non ascii quote chars with ascii ones and skip the encoding which I think is a better fix. metacpan.org currently shows these errors on the corisponing module pages: CSS::DOM Around line 746: Non-ASCII character seen before =encoding in 'Perl’s'. Assuming UTF-8 CSS::DOM::PropertyParser Around line 873: Non-ASCII character seen before =encoding in 'I’ve'. Assuming UTF-8
Ping? What's the current plan, making the encoding explicit, or dropping the non-ascii char? intrigeri, Debian Perl Group
On Fri Jan 24 14:37:53 2014, intrigeri@boum.org wrote: Show quoted text
> Ping? What's the current plan, making the encoding explicit, or > dropping the non-ascii char? > > intrigeri, Debian Perl Group
The patch has just been applied in version 0.16. (Thank you, Gregor Herrmann.) Sorry for the long silence.