At the moment, your best option for doing prosumer or lower DTP … is a time machine. Microsoft Publisher — which was pretty bad — is going end of life. Affinity’s products, including Designer, cannot currently be purchased and it’s unclear whether version 3 will be a perpetual license. (Assuming what replaces version 2 will be something reasonably describable as version 3. Strange rumors abound.)

If you’re fairly good at HTML / CSS, don’t mind being unable to realistically collaborate with others, and have $500 (before tax), Prince XML might be for you. But at that point, I suspect you’re a pro who has outsized reasons for hating Quark or Adobe InDesign.

Scribus is one of those things where you only recommend it if you’ve either a) never used Scribus, or b) never used so much as a Word Processor newer than Word Perfect 5.1. (I have produced several things with Scribus. The most recent was less than a year ago. It’s still cringe-inducingly painful.)

So that’s fun.

ETA: apologies for the frequent edits. I shouldn't have drafted this from a phone.

#DTP #AffinityDesigner #PrinceXML #Microsoft #DesktopPublishing

Prince Output · Prince Documentation

<link rel="preconnect" href="https://fonts.googleapis.com">

@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.

#PDF #PDFUA #TaggedPDF #iText #PrinceXML #WeasyPrint

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 :)

@copiepublique

"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...