You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to know if there are any plans to support the LaTeX tagging project. Using tagging, it will be one day possible to create fully tagged pdf files from LaTeX code, in order to create accessible documents (see also https://latex3.github.io/tagging-project/).
In my project I can already use this in part, but with a kludge:
In my make.bat file I prepend the tex file created from Sphinx's make with something like this:
and after that modification I build this tex file. The result is then a pdf file that passes validation for the PDF/A-4F validation profile in verapdf. It would be nice to see latex_ configuration values for conf.py that can be used to prepend this to the tex file automatically. Are there already conf.py entries for that?
The text was updated successfully, but these errors were encountered:
the "testphase" value is AFAIK going to vanish one day, but even without this value, setting the pdfstandard and version values would be nice. Or is there another way in Sphinx to control that?
Hello everyone,
I would like to know if there are any plans to support the LaTeX tagging project. Using tagging, it will be one day possible to create fully tagged pdf files from LaTeX code, in order to create accessible documents (see also https://latex3.github.io/tagging-project/).
In my project I can already use this in part, but with a kludge:
In my make.bat file I prepend the tex file created from Sphinx's make with something like this:
and after that modification I build this tex file. The result is then a pdf file that passes validation for the PDF/A-4F validation profile in verapdf. It would be nice to see latex_ configuration values for conf.py that can be used to prepend this to the tex file automatically. Are there already conf.py entries for that?
The text was updated successfully, but these errors were encountered: