Skip Menu |
 

This queue is for tickets about the JSON-Any CPAN distribution.

Report information
The Basics
Id: 90130
Status: resolved
Priority: 0/
Queue: JSON-Any

People
Owner: ether [...] cpan.org
Requestors: dmn [...] debian.org
Cc:
AdminCc:

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



Subject: [PATCH] missing =encoding in JSON::Any POD
Date: Thu, 7 Nov 2013 21:36:12 +0200
To: bug-json-any [...] rt.cpan.org
From: Damyan Ivanov <dmn [...] debian.org>
Download (untitled) / with headers
text/plain 486b
Hi, While updating the Debian package of JSON-Any to version 1.32, I noticed that the generated manual page contains the following section: POD ERRORS Hey! The above document had some coding errors, which are explained below: Around line 701: Non-ASCII character seen before =encoding in 'Mannsaaker'. Assuming ISO8859-1 adding '=encoding ISO8859-1' fixes this. Trivial patch attached. Thanks for considering, dam, Debian Perl Group
Download pod-encoding.patch
text/x-diff 348b

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

This should be fixed in 1.33.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.