Daniel Woste

Thanks for reporting this :+1: Unfortunately, I can not reproduce it, but I get many other errors from RST-plugins directly. I'm unsure what the reason is, maybe some API changes...

Thanks for the detailed report. It's really helpful. :+1: This one needs a deeper analysis, but I hope to find some time soon.

Sorry to say, but ``needextract`` will not work with ``external_needs``, because external needs have no docutils/html based representation, so no content got already rendered by sphinx, which we can reuse/copy...

Ohh, tough one. I'm afraid that this is not doable. `needextract` itself gets executed after the rst-rendering phase of Sphinx. So this is too late to add any rst-based (pre/post-)content....

Other examples: ``[HW-4 and AR19.11]:419, [HW-5 and AR20.11]:520,unknown``

I think we already have this information available in the `needs.json` file. So it should be easily possible...

Nice idea. For ``needextract`` this is possbile, but not for `needextend`, becauseito does not write any output to the HTML. So it can't be a link target. For `needextract` I...

I think this feature can only be based on data from needs.json files and the version data that may be stored inside these. As a rough idea, you could configure...

I would take a look at the final data only. So after all other "manipulation" methods have been applied (templates, needextend, dynamic functions). And I agree that not every change...

As I don't have control over the SVG content (generated via Sphinx and its extension), I changed the lines as follows to get at least the build done: https://github.com/Kozea/WeasyPrint/blob/e9c45c7060036a65b62dd05a944199be1f441ffd/weasyprint/svg/__init__.py#L619 to...