Kelly Bellis

Good point, and I also don't know what is actually meant by 'invalid' so I tried deliberately messing up the link, both its displayed text and its embedded hyperlink, but the error was never kicked up in Preflight.

Thanks Mike! If I understand correctly, it should look like this ? :

Thank you Gary for your suggestion, but isn't a link's validity determined by it being able to successfully reach the URL?

RE: Publisher v2.5.5 Is it possible for Preflight to be set to ignore spelling errors in all URLs? For example, ignore any uninterrupted string that begins http ... and then finally coming to a space?

Thank you Mike!

Thanks Walt. I own Photo (& Designer too) but fail to see how their tools can be brought into Publisher. Currently, my work around has been to use a third-party PDF creator/ editor to insert additional information in the Description: area revealed by the PDF reader; e.g., using Ctrl+D.

Thank you, thank you, thank you! Many thanks to Mike Loader for his exceptional Expert Guide to Affinity Publisher - https://forum.affinity.serif.com/applications/core/interface/file/attachment.php?id=311069&key=d8af9155774b126b552bc1057bcf63bc I've been playing around with adding metadata content intended to be revealed in the PDF reader; e.g., Ctrl+D, but can only see some of what was entered in AfPub2 from the main menu, Window, References, Fields, Fields panel. For example, none of the Comments section under the AfPub Fields panel Document Information section is revealed in the PDF reader. Neither is the value for the Revision field. The Tags field's value appears to be equivalent to Keywords in the PDF reader. First - Is this the correct AfPub tool to be using to embed metadata for a PDF? Second - If I create a custom field using the AfPub Fields panel; e.g., Description, how is it embedded into the document?

I very much appreciate your digging into this Ken, and hopefully too, the developers likewise appreciate it. The depth of your understanding of the issue and your sharing it with them is in part what convinces me to stick with Affinity Publisher. Props to you!

Hi Ken, I was using this font: https://www.fontsquirrel.com/fonts/im-fell-english-pro?q[term]=english&q[search_check]=Y Also, I was only playing with these 2 options Sorry, that this may not be of much help. After playing around further with all of this in existing and new documents, the previously reported behavior isn't always predictable. Also, the font apparently plays a huge component, which I'm guessing you already know. For example, I tried playing around with Minion Pro and checking both boxes saw things change, but the ancient rule about the regular lowercase s at the ends of words was ignored and instead showed the long s. Unchecking the boxes, all reverted back to the lowercase s

Hi Walt, No, I had not, but opened up the document again and tried it and that made no difference in regards to any reversions.

This is some pretty exciting news Mike - thank you! I've been playing around with this whole new part (for me) of the AfPub universe and want to leave a breadcrumb for anybody coming along later, that the Show Typography Panel tool tip was revealed after hovering the mouse cursor over the ellipsis: The next bit of fun was after changing all instances of the 's' to the typical lowercase as per your suggestion, then selecting the entire bits of text in the text box and seeing the 18th century arcane rules* being correctly applied by simply checking/ ticking the Historical Forms box under Alternate - super nerd cool!! However, and possibly worth mentioning for the developers, and while all of the text was selected, that after unchecking the Historical Forms box under Alternate, the long S didn't revert back to the more contemporary version of the lowercase s. * https://prologue.blogs.archives.gov/2021/12/14/the-long-s/

Cool. Thank you Mike for sharing this good news - much appreciated!

In the example above, we see the rendered Unicode U+017F as the long S, but it gives the Spell Checker in AfPub2 v.2.5.2 (Windows) a bit of indigestion: Is it possible to teach the Spell Checker that there is mapping equivalency; i.e., U+017F = s ?

This certainly isn't a dire need, I'm just curious if macros can be recorded in Affinity Publisher v2.5.2 (Windows) and then add a custom shortcut to play the macro? For example, Ctrl+L to run: U+017F, then select string, then Alt+U this would then result in a medial, or long S being returned; e.g.,

Thank you for pushing the RC. After installing v2.5.2 and after only a first blush* seems to have addressed the issue. I will test further, but wanted to thank you for your help. *Installed, opened app, opened AfPub document, edited without issue, saved, closed, exited. Repeated, again without issue. YAY!