Interior Book Design

For #2 it was not possible to create a proof document. It DOES REALLY happen now and again but I don't see how and even copying the very same headlines to a different document does not lead to the same effect. I could provide a document for the staff if they were interested.

Wonderful, thanks. The rectangle trick, I'm using all the time for the table of contents. 😀

I have proof of concept for #1. See attachment. Running footers are fine in APub 2.4.2 (and were in 2.5.0?), but are truncated in APub 2.5.2 Win. MyBook.afpub

#1: Apply limits is not selected and it works fine for one of the headlines that does not run through 2 frames and it works completely fine in 2.4.2. #2: Source Sans Pro, but even if I change the font to whatever font, it does not matter. Here are the settings:

I was happy when running headers were introduced, I'm not so happy, now. I've done two projects, recently with two different problems. See my screenshots. In my first project, I was pleased that Publisher interpreted a heading 1 running through 2 frames quite nicely and created a running footer without any problems. It still does in 2.4.2. Unfortunately, this behaviour had gone in the latest release 2.5.2 (Windows). Here, it swallows the 2nd part of it. In my second project, Publisher just removes letters from the beginning of my running headers now and again. In this book, I use two different master pages with different running headers, maybe this is too much for Publisher. Sorry, I am not allowed to attach the files.

Strange, do you have an explanation for this? There is nothing wrong with facing pages in Word?! And in my RTF file, I also have those two styles. Anyway, thanks for helping to find a workaround, I very much appreciate your help! Heidi-BB.rtf

Right you are, Walt. However, you'd expect minor problems, not fundamental things such as placing problems. And, secondly, Publisher practically lures users to immediately switch to the new version. The proof of the pudding: most of my participants came with version 2.5 installed, already! In the light of this, shall I as the teacher base the seminar on an older version?

Today, I've tried to place this simple Word file and Affinity Publisher 2.5.0 on Windows crashed. 2.4.2 did not crash, importing the same file. APub 1 does not crash, either. However, if I convert this file into an RTF file, it imports fine, even in Publisher 2.5.0 What goes wrong? (It was extremely embarrassing because it happened in front of my course participants. I'm currently teaching a typesetting class in Publisher. My participants couldn't import their Word files, either.) Heidi_BB.docx Note: Publisher 1 seems to have been much more robust as far as importing Word files are concerned. I have pretty complex and complicated Word files that nicely import into Publisher 1 but always cause Publisher 2 to crash.

Hi, just to remind you, the "closing quote bug" still remains. (2.4.2 for Windows 11) It is quite annoying in a novel with a lot of conversation ... Okay, I know the workaround, but ... Thank you. :-) ClosingQuoteBug.afpub ClosingQuoteBug.afpub

Funnily enough, on my zen book with AMD Ryzen 9, there is no "redraw jump". Maybe it has to do with the graphics processor?

Yes, I mean the "momentary redraw jump". Okay, I see, this seems to be a known issue. Thanks and sorry for mentioning it, again. BTW: Your manual is second to none, absolutely phenomenal!

I don't know if this is a bug or a feature: The text flow jumps when scrolling through documents, and this happens across all documents, not just one. 2.4.2 on Windows 11. I wish it were stable. FlowJumpsWhenScrolling.mp4

See my image. It has always been happening when importing bullet lists from Word, for years now. In Pub 1 and 2. Today I ask: Why is that so? These ghost styles are not easy to remove, the command to remove unused styles does not work, I have to do it manually. Greetings and thanks in advance! Johann

Okay, I'm using Windows. I haven't tested it on MacOS, though. Update: Okay, it works on macOS. So, this is a Windows-related bug.

And here comes my file. The language does not seem to matter. small_caps_DE.afpub

No, it does not. It just breaks without hyphen. I'm preparing another document.

Hi everyone, I've encountered a problem in both Affinity Publisher 1 and 2 that affects text formatting, particularly hyphenation in Small Caps. Here's a brief breakdown, see my image: Normal Hyphenation: Works fine with standard text formatting. All Caps Hyphenation: Hyphenation also functions correctly with text in All Caps. Small Caps Hyphenation: When applying Small Caps, the automatic hyphenation is ignored, leading to awkward spacing and visually unappealing text alignment in the document. This issue persists regardless of whether direct formatting or a character style is applied. Given that Small Caps is a common format used in novels and professional books, the lack of proper hyphenation significantly impacts the readability and aesthetic of the text. I have attached a graphic illustrating these points, showing the normal text (1), All Caps with working hyphenation (2), and Small Caps where the hyphenation fails (2), resulting in large gaps. Could anyone provide insights or a workaround for this issue? Thanks for your help!

Thanks, great proposal. Meanwhile, I've discovered the No Break option, already, and use it as a workaround.

I've spotted the following problem, see image: (Sorry, I cannot upload the image. I try to type it:) Behaviour in Publisher 2.4: Er blickte mich mit seinen treuen Augen an und sagte: „Hallo! “ How it should be and how it is in Publisher 1.10: Er blickte mich mit seinen treuen Augen an und sagte: „Hallo!“ Bottom line: The closing (German) quotation mark incorrectly breaks after a full stop or exclamation mark ... which makes it extremly difficult to typeset special kinds of books such as novels.

I opened a novel, typeset in v1. In v2, many closing quotation marks, that once were at the end of the line, now break to the next line, see image attached. And no, there is no blank between the full stop and the quotation mark, of course not.

That, in fact, is a very good workaround, thank you!

I know, but after editing the Default profile the name of the Profile switches to <Custom> and next time Default shows the same, unwanted behavior, again. I want it once and for all, Walt!

To my mind, the preflight function is overzealous. Spelling mistakes shouldn't even create warnings. Spelling check is done by my colleagues who do the copy editing/proof reading. It should be done in a word processor, not in a DTP app. Therefore, I would like to get rid of those annoying warnings for good! How can I do that? I know that I can create my own profile and that I can create even categories. But that means I have to choose this profile/category first. For me, this is one click to many. I want it out of the box, by default. Is this possible? Maybe by somehow (but how?) changing the settings of the Default category? Can I break the habit of always creating warnings in regard to (alleged) spelling mistakes? Thanks!

Nicholas, not sure if this is a good idea. You get automated responses only and might wait for weeks for an answer.

I'm growing more and more frustrated. On 30th of November, I ordered the Publisher WorkBook, together with some t-shirts. The t-shirts arrived a few days later, the book did not. On 5th of January I wrote a kind e-mail to support. Almost instantly, I've received an automated reply: "Thanks for getting in touch. Due to high amounts of e-mails there will be a delay in replying and we expect to get back to you within 72 hours during the working week." Yes, they did. On 9th of January, I've received another automated mail: " We are sorry that your email to Affinity Orders has been in the queuing system for more than 72 Hours. Due to the high number ..." That's it. Automated responses, no book. WHAT'S UP, GUYS? PLEASE BE SO KIND AS TO SEND MY BOOK. AFTER ALL, YOU HAVE RECEIVED PAYMENT, ALREADY. THANKS!