orschaef

Really wondering what is taking so long here. I think it is a matter of priority. But I always thought that PDF export is something like a core feature of such software. I also wrote on Twitter to the official Affinity account and got the reply: "This is something that is still being looked into by our developers I'm afraid."

And why does other software get it right, then? And why can I see for correct PDFs with format 410x310mm that pdfcpu outputs 1162.20, 878.74 pt? This looks like floating point to me. But even if I use this points in Affinity Publisher (switching to points from mm) and then export again I still get 1162.32, 878.88 which is wrong again. This is a rounding bug. Or do I miss something here?

Hey everyone, any news on that issue? For me this is somehow blocking, since I need to provide correct data for the press. In my case I can reproduce the issue when creating a fresh new document: 400x300mm and 5mm bleed (300dpi) which should result in 410x310mm. What preview shows me is 41,01x31,01cm. Would really like to know until when we can expect a fix here.

Hi all, I really like the data merge feature but I wonder if it is planned to provide more automation for it. Currently we have the use case of creating CVs for our colleagues. Everyone can provide the content by writing a json file. We have a CI pipeline which merges all json CVs into a single json file, which then contains one dataset per colleague. This json file we use to generate the CVs and export them as PDF afterwards. But it would be super awesome if nobody would need to open APub to do that manually - instead I can imagine some sort of CLI / API or whatever which just takes a json file, does the data merge and gives some export options. I know this may not be in any focus right now - but are there plans?