[publican-list] looking forward; was: Publican 4.3.0 released

[Jeff Fearn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

G'day,

On 05/08/2015 04:12 AM, R P Herrold wrote:
> On Thu, 7 May 2015, Jeff Fearn wrote:
> 
> congratulations
> 
> In looking through the release notice, it seems development 
> matters are largely driven off of bugzilla entries.  I don't 
> know that these 'nits' have been expressly filed, nor indeed 
> if the RHEL documentation is produced via Publican, but here 
> goes:
> 
> Problem 1:
> Kerning causes 'scrapes' off of a PDF to have embedded white 
> space -- an example is as follows:
> 
> http://gallery.herrold.com/stuff/source-kerning.png 
> 	and
> http://gallery.herrold.com/stuff/result-kerning.png
> 

This seems to be dependant on the combination of PDF generator and font
being used. See https://bugzilla.redhat.com/show_bug.cgi?id=1141312 for
how it occurs in wkhtmltopdf. There are some upstream bugs related to
kerning issues that have been addressed by banging on the font
configuration.

e.g. see
https://github.com/wkhtmltopdf/wkhtmltopdf/issues/45#issuecomment-34543222
for an example of how tweaking the font config helped on Debian.

> Problem 2: 
> 
> Page numbers are not 'hot links' in the PDF 'table of 
> contents' rendering (compare contra PDF's generated in a some 
> LaTeX markup / DVi / PS / PDF chains) -- the 'circled' page 
> number in an index, when clicked, does nothing

I've not looked at these tools chains in quite some time and Publican
has no direct support for them.

If you can provide your full work flow I can take a poke a round and see
if it's an easy fix. I'm assuming there is an upstream template
somewhere that needs tweaking.

> http://gallery.herrold.com/stuff/dead-page-numbers.png
> 
> I built a quick example of a large set of documentation (in 
> part machine generated) -- see pg 4 ff of the PDF
> 
> http://gallery.herrold.com/stuff/commands.pdf
> 
> 
> Question:
> 
> Are these 'interesting' bugs that I should file,

Yeah, while I wont say we are "happy" to get bugs we do encourage people
to open them if they are getting annoyed by something :)

> and would a 
> fix in Publican flow into later versions of RHT documentation?

It depends on the change, Red Hat have a brand that customises a lot of
stuff so it's quite possible some changes will never get to their
output, but of course a lot do.

Cheers, Jeff.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iQEcBAEBAgAGBQJVS+IyAAoJELs3R4zxGZvKQ+4H/jU7sKygGdP8wuDWMF7YmQA1
cX2S2h2cTUI9RXz1ajyWLzhsXVF3F0ctlgxJHuJKbfUy+Av5O4qqn+c6nIKkvxc3
MkBdVCKYkfgTAu8MOnSrLUbThDbZxjhxhbC1+FjG0fNo1FJO7H4FyUZbv1gl2JTs
27VnT5qJiu2nDoxrh4Vz9QZkvCqhGxaZqbeGOhUhMFvWNXOVtAPYpsoJYbaGq0lX
b1lnBqyDZHJQIOqUrFMMZzhawK/VUb5m5bFnsAE5P+LnCIsc1Veakqui5TRPeqXd
2Jpz6uPbQM9dLESG4/cSTOyCoLaMitDBO7KMNYH6vAf+rM4J4y16V+Oi/ih58/4=
=oEIr
-----END PGP SIGNATURE-----