CI Jobs for Doc Build PDF

[kreuzberger]

The CI Jobs for the doc builds SEEMS to work, but on windows pdf builds weasyprint returns with an error code an the pdf is not generated.
Seems to be an windows issue only.

Regarding the doc build itself there are several warnings, also missing files (demo) are not generated.

it should be clarified what is the intention of this build steps and also to build dependencies.

I personally tried to get the build fixed on windows, but was not successfull. Weasyprint tries to find dependent msys libraries, but still seems to fail.

[kreuzberger]

After playing around it seems that the sphinx generated document itself is causing the problem cause other html pages seems to be converted properly on windows with the setup used by the CI (reproduced in local VM)

[kreuzberger]

Testing with my "test framework" from the pull request for me it worked after commenting out the monospace font families from main.css

/*
@font-face {
  font-family: monospace;
  src: url(fonts/FiraMono-Regular.ttf); }

@font-face {
  font-family: monospace;
  font-weight: 400;
  src: url(fonts/FiraMono-Medium.ttf); }

@font-face {
  font-family: monospace;
  font-weight: bold;
  src: url(fonts/FiraMono-Bold.ttf); }
*/

With these fonts enabled the msys2 build get a segfault on windows.
May this help. May the force be with you :-)

[kreuzberger]

It seems that font-family: monospace; causes the problems.
After changing to another font-family like font-family: 'FiraMono'; like for the other fonts the issue is gone.

See the linked pull request #121 and the now working windows tests and docs directory generation

This is just a workaround, you may find a better solution for it.

[kreuzberger]

Seems to be related to Kozea/WeasyPrint#441, errors on font-faces could lead to weasyprint crashes.
As far as i now understood, the unquoted monospace leads to the error cause generic font names should not be used as only font-family definition.
See https://www.w3.org/TR/CSS2/fonts.html#value-def-generic-family.

Changed it in the PR and now should be CSS conform