Improvement of source code line markers and HTML2PDF layout fixes
This release contains a change in how the source code line markers work, as well as several small HTML2PDF layout fixes.
The source code line markers were changed to include the next source line that follows immediately after the marker. As discussed with a user in #2434, this behavior of line markers makes more sense compared to the previous approach, which assumed that the source line had to be followed by a line marker, forcing both the source line and the marker to be on the same line. Thanks to @Mooan for initiating this discussion and contributing a pull request.
The HTML2PDF fixes include an important correction for an issue where running titles were not displayed on some pages in certain cases. For now, we have implemented a workaround, and the complete fix is being tracked in the upstream html2pdf4doc repository.
What's Changed
- Bump version to 0.11.2 by @stanislaw in #2452
- fix(backend/sdoc): do not generate auto-generated content with auto-uid and export/sdoc commands by @stanislaw in #2453
- fix(RST): do not exit(1) but raise RuntimeError by @stanislaw in #2454
- fix(html2pdf_generator): support printing RST as well as other markups by @stanislaw in #2455
- feat(HTML2PDF): integrate --strict mode, split normal tests and HTML2PDF tests by @stanislaw in #2456
- fix(sdoc_source_code): correct LineMarker range and add validations by @Mooan in #2458
- refactor(backend/sdoc_source_code): de-duplicate line_marker_processor by @stanislaw in #2460
- Disable backgrounds of problematic split sections (workaround for html2pdf4doc bug) by @mettta in #2462
- Preserve meta in narrative nodes and prevent split admonition. by @mettta in #2463
- fix(source_file_view_object.py): fix SourceMarkerTuple is_range_marker decision by @stanislaw in #2464
New Contributors
Full Changelog: 0.11.2...0.12.0
