[Phil]

Wed Jul 10 21:51:51 2019 jidanni [...] jidanni.org - Ticket created

There is an example of how to use the text commands to place text on the page, but no example of how to use the image commands to place an image on the page.

Thu Jul 11 14:09:08 2019 PMPERRY [...] cpan.org - Correspondence added

Look at the POD for image(), under Content.pm. I updated it in PDF::Builder to be a bit clearer.

[check if overall image() examples could be improved, before closing]

[Phil]

Thu Jul 11 15:03:36 2019 jidanni@jidanni.org - Correspondence added

The main problem is on man XML::LibXML we see it mentioning all the places one is supposed to look for everything, many many pages. But on man PDF::API2 there is not even a SEE ALSO section.

Thu Jul 11 15:03:45 2019 jidanni@jidanni.org - Correspondence added

OK but the main problem is on man XML::LibXML we see it mentioning all the places one is supposed to look for everything, many many pages. But on man PDF::API2 there is not even a SEE ALSO section. For us users we only follow what is mentioned and do not use e.g., dlocate -L libpdf-api2-perl to see where things might be hidden.

Fri Jul 12 10:00:58 2019 PMPERRY@cpan.org - Correspondence added

Understood and agreed that the documentation has accreted over the years in a haphazard manner. I can't do anything about PDF::API2, but I have been upgrading PDF::Builder's docs bit by bit, and will keep your points in mind.

What is really needed is a comprehensive, task-oriented overview, but unless someone shows that a book ($$) would be in sufficient demand to make it worthwhile writing one, I'm afraid that major doc revisions and improvements will come slowly.

[Phil]

Fri Jul 12 11:26:05 2019 jidanni [...] jidanni.org - Correspondence added

Well I just want to let you know that all I know about is PDF::API2. That's what I did "use" on in my program.

As far as any "builder" package, well there isn't even the word "builder" on the PDF::API2 man page (here on Debian.) so "we might as well be talking about different packages," and "are you sure you are responding to the right bug number?"

I'm sure you are, but that's what it looks like from here.

Fri Jul 12 19:05:02 2019 PMPERRY [...] cpan.org - Correspondence added

I own it; it is a different package, forked from PDF::API2 several years ago.

[Phil]

Fri Jul 12 19:39:19 2019 jidanni [...] jidanni.org - Correspondence added

All I know is I use

Code: [Select]

$ apt-cache policy libpdf-api2-perl
libpdf-api2-perl:
  Installed: 2.033-1
  Candidate: 2.033-1
  Version table:
 *** 2.033-1 500
        500 http://opensource.nchc.org.tw/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
And to avoid filling the Debian bug tracker with upstream bugs, with my nose to the ground, I sniffed out that I should report them here (bug-PDF-API2@rt.cpan.org), so I sure hope your fork will one day make it to Debian...

[Phil]

I somewhat improved the documentation for images, showing more information sources and pointing to sample code (such as Content.pl).

Closing, in release 3.016.