Add support for PDF/UA-1 - #114
Andrew15-5 wants to merge 1 commit into
Conversation
Does not affect docs.
|
As was mentioned in the Documentation thread, it appears that text-based figures (and apparently also Lines 497 to 508 in 9e8e243 highlight option: Lines 694 to 703 in 9e8e243 and a general thing: Lines 1601 to 1613 in 9e8e243 The first two can be caught with the provided test. If you add highlight for a code block, the second snippet is used, if no So...it actually propagates to the inner snippet for no highlights. Wrapping that in This tells me that #figure([text], caption: [])
#figure([a --- b], caption: [])
#figure(text(red)[a --- b], caption: [])
#figure(`raw`, caption: [])
#figure(caption: [], ```
raw
block
```)Since I don't see any relevant documentation to all this (in |
|
Thank you, please note I will be adding it in dev-v1.4.0 directly, I'll try to add you as a commit author on it. |
|
I see a few related commits now. Did you intent to add |
|
I will indeed, but I'll probably do one big "co-authors" commit at the end of the PR with everybody involved :) |
|
I will close this in the meantime. The commit with all co-authors will come before I go and work on the new docs (likely a gh.io website now). Thank you for taking the time! I did use your solution. It'll be in #141. |
Closes #113.
My first approach was to provide all the missing alt text, which was really not something someone would wanna read anyway. And so I discovered
pdf.artifactthrough @xkevio. And it definitely falls under the decorative images for the two bottom images, but for the rest... There is no mention offigurehacks, but since they are invisible and all, I guess it makes more sense to convert all figures into artifacts as well.Tested with
Not sure if text of a language should be omitted. Of course, it's not 100% certain the code with this package is a one single thing or not, compared to the default, but either way, reading the language name might be very useful, though would be strange if there are no references to it in the text.
The docs use figures/images, IIRC, so this does not make them PDF/UA-1 compatible, since it's not part of the package.