The default in pod2man was changed to warn on formatting errors instead of 
silently sticking the errors into the generated POD documentation. An 
"=encoding" declaration is not optional any more if there are non-ASCII 
characters in the POD.

How to reproduce:

# perl -v
This is perl 5, version 18, subversion 2 (v5.18.2) built for 
i386-freebsd-thread-multi-64int

# pod2man --section=1 --release="3.3.0" --name=BackupPC --center="BackupPC user 
guide" ./doc/BackupPC.pod ./backuppc.1
./doc/BackupPC.pod around line 4800: Non-ASCII character seen before =encoding 
in 'Paъgang.'. Assuming ISO8859-1
POD document had syntax errors at /usr/local/bin/pod2man line 71.

Adding of an "=encoding" declaration will fix the issue:

--- doc/BackupPC.pod.orig       2014-05-13 17:40:09.000000000 +0400
+++ doc/BackupPC.pod    2014-05-13 17:40:27.000000000 +0400
@@ -1,3 +1,5 @@
+=encoding ISO8859-1
+
  =head1 BackupPC Introduction
.
  This documentation describes BackupPC version 3.3.0,

P.S. The pod2man warning stops installation of sysutils/backuppc port on 
FreeBSD with perl 5.18.

--
Alexander

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to