@julientaq @spaceninja Do you happen to know how well those might support PDF/UA or WCAG 2 standards for accessible PDFs? Anything that doesn't is a non-starter for me.
iText and PrinceXML both claim to support PDF/UA.
On the WeasyPrint site, they also claim to be able to produce PDF/UA compliant files. I wonder if anyone knows of examples I might look at?
I don't see any mention of accessibility in vivliostyle or paged.js.
Pour créer les #PDF sur Paheko.cloud, nous utilisons le logiciel #PrinceXML, édité par le créateur de #CSS. C'est un outil très efficace et agréable à utiliser, mais non libre.
En conséquence, pour améliorer les outils libres de création de PDF dans l'avenir, cet été nous avons contribué 100 € à #DomPDF et 100 € à #WeasyPrint (développé par @courtbouillon).
On cherche aussi un⋅e développeur⋅se (payé) pour passer 1-2 jours sur DomPDF pour améliorer sa gestion de la mémoire :)
"Fun" problem at work. Perhaps someone saw something like that.
So.. we have html document with injected style=css content. And we generate a pdf from it with #PrinceXML 7.1 . Based solely on the #css content, we either get or not encode issues with some of the \@Include'd template's text (#Norsk chars: øæå).
I already checked if it might be a non-standard for, but it is mot the case. Also, it only happens for the template using tabs for indent, but that would be a weird reason for it all...
