Bob P

Do Serif actually look at these posts? This has been an active thread for over 3 years and nothing has happened.

MikeTo; Thanks for your reply but after 35 years in prepress, I think I know how to find issues in files. It is not up to me or you to debug Affinity software. Should have been tested thoroughly before release. Too many bells and whistles and not enough attention paid to the basics methinks.

Mine doesn't. Don't see any posts from Affinity...

Would appear to work OL with some V1 docs but that is not very reassuring

V2 Windows Pub crashes when saving V1 doc as V2

Stiil no option to select page/current article/ for S&R.

Totally agree with all of the above. In Publisher 1.10.5 is so confused it changes the style definition. Yesterday para style Body left the font/trait as was so you could import text in several fonts and they would be retained but para spacing, colour etc would change to that required. Today para style Body changes all the fonts to one defined in a style it created from pasted word text. If i try to correct or delete, all my previous use of Body changes to Bold. Doubt if Serif will do anything about it though, still waiting on response to a Search&Replace issue posted in October 2020

So far so good. just done a quick test and it worked. Time will tell......

No matter how I try to copy tabbed text from a AFP story into a table. AP crashes. Is it just me? WI7 W10

Sorted a while ago. All to do with an exposure adjustment layer on text

There is other text on the same page which is 100%K and defined using the same Global colour which is correct. Here are 2 s creenshots showing the issue

*I have defined a global colour as 100%K. I apply it to text. Visually it is not black. the Colour picker tool says it is 78% black. PDF exports as 78% black. Useless!!!! What is the excuse SERIF? BTW I joined a post a while ago about defining a S&R scope but so far SERIF have failed to respond. Is there any point in suggesting improvements or complaining if nobody listens?

Not being able to specify the scope for Find and Replace is a major omission.

I agree, would be a big help when producing documents for various platforms