Open DirkBodenschatz opened 1 year ago
The .. needtable:: directive works in my case (windows) for various builders (latex, latexpdf, html and confluence). Is it working fine when you build for latex?
@daniel3097 Just an information to the project setup. I have many different files and needs (used for the html build) but, there is only one file out of all files which is additionally build as PDF (via latexpdf). So, what I figured out after your comment is the following:
1.) There is no issue with e.g.: needtable
and needextractc
for latex as well as latexpdf build, if I have everting in the file which is build via latexpdf. No use of needs defined in other files.
2.) The exception occurs only, if I move the .. tcd:: TCD 1 ....
and .. tcd:: TCD 2....
to another file.
Working example located in one rst file:
.. tcd:: TCD 1
:id: TCD_001
:tags: requirement
This is an example ....
.. tcd:: TCD 2
:id: TCD_002
:tags: requirement
This is another example ...
.. needtable::
:types: tcd
:style: table
:columns: id, title, status
.. needextract::
:filter: id in ['TCD_001', 'TCD_002']
@DirkBodenschatz :
I tried your example and i also faced issues (but it looked different that yours). Made clean improved a bit - but still errors.
hi What helped in my case was when i removed :sytle: table in ...needtable::
.. needtable:: :types: req :columns: id, title, status
.. needextract:: :filter: id in ['R_MIIO-01', 'R_MIIO-02']
i hope this helps in your case as well.
the pdflatex path looked attractive to me as well to generate a pdf. but its "tough" - so i started exploring the ebook path (wasn't much better) and the confluence path (works well).
On linux https://github.com/useblocks/sphinx-simplepdf might be worth to try (i have no experience, but it looks impressive)
latexpdf build leads to an exception if I use
.. needextract::
is used. The same happens also if.. needtable::
is used The html build works fine .....