Em Sun, 12 Dec 2021 16:59:53 +0900 Akira Yokosawa <akiyks@xxxxxxxxx> escreveu: > This patch set improves conversions of DOT -> PDF and SVG -> PDF > for PDF docs. > > * DOT -> PDF conversion First of all, package requirement for docs generation should be auto discovered by: scripts/sphinx-pre-install and should not break the ones detected by check_distros() and that supports PDF generation. > > Current scheme uses "dot -Tpdf" (of graphviz). > > Cons: > - openSUSE's dot(1) does not support -Tpdf. I'm sure I tested pdf generation in the past with openSUSE by the time I wrote sphinx-pre-install script. Perhaps some change at either openSUSE or at the docs makefile broke support for it. > - Other distro's dot(1) generates PDFs with unnecessarily wide > margins for inclusion into LaTeX docs. > > Patch 1/3 changes the route to two steps: > > 1. DOT -> SVG by "dot -Tsvg" > 2. SVG -> PDF by "rsvg-convert -f pdf" with fallback to convert(1). rsvg-convert is not present on Fedora (nor on RHEL and CentOS), as far as I'm aware. > Pros: > - Improved portability across distros > - Less space for graphs in final PDF documents > > Con: > - On systems without rsvg-convert, generated PDF will be of raster > image. Raster images are a very bad idea. Why don't keep use "dot -Tpdf" when supported by the system? instead of falling back to raster images? > * SVG -> PDF conversion > > Current scheme uses convert(1) (of ImageMagick) > > Cons: > - Generated PDFs are of raster image. Some of them look blurry. > - Raster image tends to be large in size. > - convert(1) delegates SVG decoding to rsvg-convert(1). > It doesn't cover full range of Inkscape specific SVG features > and fails to convert some of SVG figures properly. > > Failed conversions are observed with: > - Documentation/userspace-api/media/v4l/selection.svg > - Documentation/userspace-api/media/v4l/vbi_525.svg > - Documentation/userspace-api/media/v4l/vbi_625.svg What do you mean by failed? With the current way, the VBI ones seem OK to me: https://linuxtv.org/downloads/v4l-dvb-apis-new/pdf/media.pdf (This is daily updated. On today's build the raw VBI ones are in page 1031/1032) Do you mean that your changes caused a regression there? > If you have Inkscape installed as well, convert(1) delegates SVG > decoding to inkscape(1) and the above SVGs are rendered correctly. > > So if Inkscape is required for converting those SVGs, why not use it > directly in the first place? I remember that the main focus were to be able to generate PDF at the major distros. It should be OK to use whatever tool, provided that it won't cause regressions with such distros. Not that is should matter much for the others, but my particular interest is that it shouldn't cause regressions neither on Debian nor on Fedora, as those are the ones I use for PDF generation. Debian is used at linuxtv.org, where we do automate builds for PDF, ePUB and HTML. Fedora is what I used locally, in order to test and fix issues on media PDF document output. > Patch 2/3 adds a route of SVG -> PDF conversion by inkscape(1). > Patch 3/3 hides warning messages from inkscape(1) which are harmless > in command-line uses. > > Pros: > - Generated PDFs are of vector graphics. > - Vector graphics tends to be smaller in size and keeps looking nice > while zoomed in. > - SVGs drawn by Inkscape are fully supported. > > On systems without Inkscape, there won't be any change in behavior. > > Thanks, Akira > -- > Akira Yokosawa (3): > docs: sphinx/kfigure.py: Use rsvg-convert(1) for DOT -> PDF conversion > docs: sphinx/kfigure.py: Use inkscape(1) for SVG -> PDF conversion > docs: sphinx/kfigure.py: Redirect warnings from inkscape to /dev/null > > Documentation/sphinx/kfigure.py | 109 ++++++++++++++++++++++++++++---- > 1 file changed, 97 insertions(+), 12 deletions(-) > > > base-commit: a32fa6b2e8b4e0b8c03f5218afa0649e188239c5 Thanks, Mauro
