From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/3] doc-rst: generic way to build PDF of sub-folder
Date: Fri, 26 Aug 2016 08:34:27 -0300 [thread overview]
Message-ID: <20160826083427.10a58f25@vento.lan> (raw)
In-Reply-To: <1472052976-22541-1-git-send-email-markus.heiser@darmarit.de>
Hi Markus,
Em Wed, 24 Aug 2016 17:36:13 +0200
Markus Heiser <markus.heiser@darmarit.de> escreveu:
> From: Markus Heiser <markus.heiser@darmarIT.de>
>
> Hi Mauro,
>
> here is a small patch series which extends the method to build only sub-folders
> to the targets "latexdocs" and "pdfdocs".
>
> If you think, that the two first patches works for you, path them with your next
> merge to Jon's doc-next.
>
> The last patch in this series is just for you. It is a small example to
> illustrate how we can build small books and link them with intersphinx.
Didn't actually review the patches (I'm about to take a short trip).
Just tested the results of those 3 patches.
It worked. However, I saw two issues there:
1) Now, the documentation, when using SPHINXDIRS=media is not output
at the Documentation/output/latex anymore, but, instead it created a
Documentation/output/media/latex and wrote the books there.
2) If built without SPHINXDIRS, it is producing just one document and
storing it at Documentation/output. I would expect it to do the same
on both cases.
Btw, I'm planning to split the media documentation on 4 books even when
building without SPHINXDIRS. There are two reasons for that:
1) the uAPI book has a different licence than the other books;
2) the uAPI book should be split into 5 parts, and each part should
reset the chapter numberation to 1, in order to produce the same
chapter numbering as the HTML book.
>From what I saw, the control if LaTeX will use parts/chapter/section
or just chapter section is controlled per conf.py file. It means that
we'll need to have a separate conf.py for the uAPI book - or to have
an Sphinx extension that would allow adjusting the LaTeX layout via
some meta-tags at the book's index.rst.
Regards,
Mauro
next prev parent reply other threads:[~2016-08-26 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 15:36 [PATCH 0/3] doc-rst: generic way to build PDF of sub-folder Markus Heiser
2016-08-24 15:36 ` [PATCH 1/3] doc-rst: generic way to build PDF of sub-folders Markus Heiser
2016-11-02 11:43 ` Jani Nikula
2016-11-02 14:07 ` Markus Heiser
2016-11-02 14:48 ` Jani Nikula
2016-08-24 15:36 ` [PATCH 2/3] doc-rst: define PDF's of the media folder Markus Heiser
2016-08-24 15:36 ` [PATCH 3/3] doc-rst:media: build separated PDF books (experimental) Markus Heiser
2016-08-26 11:34 ` Mauro Carvalho Chehab [this message]
2016-08-26 11:55 ` [PATCH 0/3] doc-rst: generic way to build PDF of sub-folder Markus Heiser
2016-09-01 14:53 ` Jonathan Corbet
2016-09-01 14:56 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160826083427.10a58f25@vento.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).