benwiggy

Ah: they were hidden by another panel. Thanks.

In Publisher, I used to be able to make a new paragraph style from a selection, but I can no longer find the option. It's not in the Panel menu for TStyles, and Paragraph doesn't have one. The drop-down list in Paragraph panel has nothing apposite either.

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.

??? Surely if it's due to the last few OS versions, then startup times for earlier OSes than those would be faster. (And indeed, I remember they were.) Bu I don't have this problem with any other apps, and if it's not a universal experience, then that should suggest it can be fixed.

I've just been tearing my hair out trying to work out my leading wasn't working -- and all because of "Leading Override" in Character style. What on earth is the point of that? And any reason why it sets it own arbitrary value when you've expressly set the leading in the Paragraph panel?

Is anyone NOT seeing this bug on Mac? That would be useful data. Affinity staff and apps are always showcased in Apple's 'announcements'. You'd think that Affinity would have some clout to get Apple to have a look at this problem which only affects their apps.

Ah! There it is! Thanks so much.

I have a document that is in Italian and English, and I want to use the same Paragraph Styles in each. How can I set the language outside of the Paragraph Style dialog? Or do I have to duplicate the Styles? Thanks

Thanks. So there's no way of "100%-ing" a text frame, if you've accidentally sized it using the blue anchor that's very slightly near the other blue anchor.....? 🙄

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.

Any new of this? The inability to import PDFs for vector editing is still a massive obstacle to the use of Designer.

A fair point, @walt.farrell. But there remain problems -- and yet again, they're all about imported PDFs.

Sigh. There are just so many needless quirks to Affinity's PDF handling, that make it unreliable for this kind of work.

Check the page range in the Export dialog?

I see it's been mentioned before, here: The Preflight Profile should automatically match the requirements of the Export Preset. Having a default that throws out false warnings is 'not ideal'.

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.

Given that Affinity can't rasterize a PDF accurately, it's not wise to do this anyway.

After updating the OS, the problem has returned to the duplicated apps.

We know! The question is ... how long before Affinity catches up?

Yes, this does seem to improve things. Thanks. I can't imagine what duping the files changes.

Thanks,

Then you need more options: Embedded Passthrough, Embedded "interpreted"; linked passthrough, linked "interpreted".

This is all very interesting, but why do other apps not have the problems that Affinity does with importing PDFs?

Does 'embedding' differ from 'interpret' and 'passthrough' only in terms of adding the document to the Affinity file? Presumably it's also 'interpreted'?