Thierry Carrez wrote on 11/23/2017 5:38 PM:
Doug Hellmann wrote:
On Nov 22, 2017, at 11:22 AM, Ian Y. Choi <ianyrc...@gmail.com> wrote:
Maybe there would be some chance to be also considered with PDF builds?
I created an WIP patch on openstack/horizon repository  to highlight
which changes to be needed for PDF build support on docs and releasenotes.
Although there is currently one warning using "python setup.py build_sphinx"
I think the warning would be quite fine now since using sphinx-build command
"-b latex" option works well and such command execution is how PTI is going
from my understanding .
It does make sense to build PDFs. Do you think we want to always build them?
From now, I have several perspectives:
- Since PDF builds do not require additional modification to existing
RST documents, always building would be a good idea
(although few RSTs might have problems - from previous experiences,
for example, some deprecated usage or
unsupported unicode characters in font files).
- Some PDF output might be awkward because of image position and table
those can be easily modified .
- Since PDF builds require additional packages in bindep.txt , build
jobs might be slow.
(I am also copying this to openstack-docs mailing list for .)
We really really need to stop using that separate mailing list. Now that the
project teams are managing their own documentation, we should just have the
docs discussions on the -dev list so everyone can participate.
How about closing that list?
Petr, how do you think about closing that list and encourage current
to use openstack-dev with [docs] tag?
With many thanks,
OpenStack Development Mailing List (not for usage questions)