Skip Menu |

This queue is for tickets about the Test-LeakTrace CPAN distribution.

Report information
The Basics
Id: 47493
Status: rejected
Priority: 0/
Queue: Test-LeakTrace

People
Owner: Nobody in particular
Requestors: frequency [...] cpan.org
Cc:
AdminCc:

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



Subject: POD/Manpage Issues in Test::LeakTrace::JA
Hi: While upgrading the Debian package for Test::LeakTrace we discovered the following issue with JA.pod: <standard input>:187: warning [p 1, 9.5i]: can't break line <standard input>:189: warning [p 1, 9.8i]: can't break line <standard input>:200: warning [p 2, 0.2i]: can't break line <standard input>:300: warning [p 3, 3.0i]: can't break line <standard input>:323: warning [p 3, 6.8i]: can't break line <standard input>:325: warning [p 3, 7.2i]: can't break line I'm not sure if this is because the text is encoded in Japanese (UTF-8?) rather than standard ASCII. Hopefully you can figure out how to resolve those warnings :-) Cheers, Jonathan
Hi, Show quoted text
> While upgrading the Debian package for Test::LeakTrace we discovered the > following issue with JA.pod:
Hmm, I updated Pod::Parser and Pod::Man, but I cannot repro these warnings. Can you please explain more details? versions of Pod::Parser, Pod::Man, and perl itself? Regards, -- Goro Fuji (gfx) GFUJI at CPAN.org
Hi: After looking into it some more, I suspect that it's probably because the system lacks things like a Japanese font, causing pod2man to convert all the Unicode characters to "XXXX" etc. I suspect that the multi-byte wide characters might wrap properly, but the same is not true when all the bytes have simply been substituted for X. Here are the lines in question: 187 \&\f(CW\*(C`Test::LeakTrce\*(C'\fR\s-1XXXXXXXXXXXXXXXXXXXXXXXXXXXX\s0\f(CW\*(C`Test::Builder\*(C'\fRXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXSXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXX 189 \&\s-1XXX\s0\fB\s-1XXX\s0\fRXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 200 XXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXX\f(CW\*(C`Data::Dumper\*(C'\fR\s-1XXXXXXXXXXXXXXXX\s0 300 \&\s-1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\s0 323 \&\s-1XXXX\s0\f(CW\*(C`Test::LeakTrace\*(C'\fR\s-1XXXXXXX\s0\f(CW\*(C`PL_runops\*(C'\fRXXXXXXPerl VMXOPXXXXXXXX1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXPerlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 325 \&\s-1XXX\s0\f(CW\*(C`no_leaks_ok()\*(C'\fR\s-1XXXXXXXXXXXX\s0\f(CW\*(C`leaked_count()\*(C'\fR\s-1XXXXXXSVXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\s0\f(CW\*(C`leaktrace()\*(C'\fR\s-1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\s0 The easiest way to resolve it from our end is just patching the distribution to remove that POD file. However, I'm not sure how useful it might be for users of your module -- if they install Test::LeakTrace and expect a Test::LeakTrace::JA pod, it won't be available on Debian. On the other hand, if we could figure out the dependencies that it needs to render the Japanese writing -- the fonts, etc -- then we could simply get our build systems to install them so as to avoid these warnings. Cheers, Jonathan On Wed Jul 01 20:52:52 2009, GFUJI wrote: Show quoted text
> Hi, >
> > While upgrading the Debian package for Test::LeakTrace we discovered the > > following issue with JA.pod:
> > Hmm, I updated Pod::Parser and Pod::Man, but I cannot repro these
warnings. Show quoted text
> > Can you please explain more details? versions of Pod::Parser, Pod::Man, > and perl itself?
perl -V output: Summary of my perl5 (revision 5 version 10 subversion 0) configuration: Platform: osname=linux, osvers=2.6.26-1-vserver-amd64, archname=x86_64-linux-gnu-thread-multi uname='linux excelsior 2.6.26-1-vserver-amd64 #1 smp sat jan 10 19:46:42 utc 2009 x86_64 gnulinux ' config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN -Dcccdlflags=-fPIC -Darchname=x86_64-linux-gnu -Dprefix=/usr -Dprivlib=/usr/share/perl/5.10 -Darchlib=/usr/lib/perl/5.10 -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5 -Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl/5.10.0 -Dsitearch=/usr/local/lib/perl/5.10.0 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Dsiteman3dir=/usr/local/man/man3 -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio -Uusenm -DDEBUGGING=-g -Doptimize=-O2 -Duseshrplib -Dlibperl=libperl.so.5.10.0 -Dd_dosuid -des' hint=recommended, useposix=true, d_sigaction=define useithreads=define, usemultiplicity=define useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef use64bitint=define, use64bitall=define, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2 -g', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='4.3.3', gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='cc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib /lib64 /usr/lib64 libs=-lgdbm -lgdbm_compat -ldb -ldl -lm -lpthread -lc -lcrypt perllibs=-ldl -lm -lpthread -lc -lcrypt libc=/lib/libc-2.9.so, so=so, useshrplib=true, libperl=libperl.so.5.10.0 gnulibc_version='2.9' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E' cccdlflags='-fPIC', lddlflags='-shared -O2 -g -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP USE_64_BIT_ALL USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API Built under linux Compiled at Jun 12 2009 21:45:11 @INC: /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl . Pod::Parser: 1.35 Pod::Man: 2.1801 Show quoted text
> > Regards,
Closing, doesn't look like an issue with the dist itself if the system doesn't have the necessary fonts to display the POD.