Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

benwiggy
Members-
Posts
151 -
Joined
-
Last visited
Everything posted by benwiggy
-
It seems to be setting that value in .indl imports. I'm pretty sure I wouldn't have set such a thing in InDesign, even if it existed. Even so, anything that negates the behaviour of another attribute should have some kind of 'flag' showing that the overridden value is currently not taking effect. Workflows often involve multiple people, who may not realise what someone else has done.
-
Yes, I'd definitely like to see this. Otherwise, I have to cut and paste to BBEdit just to Smarten the Quotes, and back.
-
I have a fairly basic document, but the text is behaving very strangely. I have a text frame with overmatter. When I make new text frame to flow the text, the text is tiny! (2.4pt, compared to 10pt). IfI select all, and try to 'correct' the size to 10pt, then the text in the first frame goes massive to 42pt. In the end I had to paste the text into a new frame to stop it. But I have no idea what's causing it. (And in the new text frame, the leading is fixed, even though align to Baseline is off, and I can't see any way of changing that either!) Anyone know what's going on? Thanks.
-
If I load a PDF that is not PDF/X compliant (but otherwise a perfectly 'normal' and valid PDF for printing) as a "Pass-through" onto a page, and then Export the page as a PDF, I get a Preflight warning that the PDF version is "not compatible with the export version" and "the PDF will be rasterized". Firstly, this seems to depend on the Preflight profile, whose default is for PDF/X-3 PDFs -- regardless of the PDF Export Profile's "Compatibility" setting for PDF versions. Secondly, the PDF does not, in fact, get rasterized. Thirdly, it claims the PDF is version 1.7, when in fact, it's actually 1.4. Or does it mean the intended version of the exported PDF? It's not clear. Fourthly, l can't remember InDesign ever complaining about PDF versions in this way: it would just create a PDF/X-3 PDF, regardless of the 'image' PDFs' versioning. Transparency might get rasterized, but that's slightly different from "This PDF will be rasterized". Is this another quirk of Affinity's bizarre approach to handling PDFs, or just a bad UI, or something else? The warning seems to be incorrect, inappropriate, and lacking in detail.
-
Accurately import PDFs?
benwiggy replied to benwiggy's topic in Feedback for Affinity Designer V1 on Desktop
We know! The question is ... how long before Affinity catches up? -
Accurately import PDFs?
benwiggy replied to benwiggy's topic in Feedback for Affinity Designer V1 on Desktop
This is all very interesting, but why do other apps not have the problems that Affinity does with importing PDFs? -
Accurately import PDFs?
benwiggy replied to benwiggy's topic in Feedback for Affinity Designer V1 on Desktop
Is a placed PDF not opened, read, displayed, and printed? What many people want to do with PDFs is open them in a vector package for editing. Other apps manage to do this, outlining glyphs where necessary. Lots of Photo editors can raster a PDF page, without altering the text because it's tried to 'interpret' the contents in some bizarre way. -
Now that we have Passthrough PDF in Publisher, will we see a similar feature in Designer to open PDFs accurately, outlining any glyphs you're not sure about? (Or even an "Outline fonts" checkbox in the import options?) And similarly being able to raster a PDF in Photo without text being "interpreted"? Thanks
-
downgrade
benwiggy replied to affinityuser13's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Another reason to maintain a backup. There are plenty of software developers that don't let you download earlier versions, either. -
Definitely not as good as the original. Bitmapping to 300 dpi will lose significant quality for vector line-art (which is what text is), and would need to be at 1200dpi. JPEGging can also create artefacts in areas of high contrast, particularly with type. Better workarounds are: outline the font data in the PDF (so that the text just becomes vector images); or convert to EPS, of which, for some reason, Affinity can read the embedded fonts correctly.
- 125 replies