MikeTO

Hi @Felix Gelukkig and welcome to the forums. 2.3.0 and beta 2.3.0.2165 are the same version so if one is hanging and the other isn't and you're positive there are no differences in the export settings then it's likely something to do with the setup of your retail (non-beta) version. Try starting Affinity while holding down Ctrl and clearing your user data. If that doesn't solve it, Serif may need to see the file. Good luck.

Did you want a hyphen in that split word at the end of the frame or no hyphen? If no hyphen, you'd need to do as Walt suggested. If you want a hyphen, just turn on automatic hyphenation. Go to the Paragraph panel, expand the Hyphenation section, and select "Use auto-hyphenation".

Hi and welcome to the forums. Have you tried Layer > Convert to Curves?

I can't duplicate that on macOS with the the same page/window/zoom setup but I can make it happen with different settings. But when it happens for me on macOS, the fact that it's Paste Inside is irrelevant - even Paste would paste it on the next page. Which means it's the general problem in that Publisher is trying to be helpful and paste it on the page below that is more visible even though the current page is the one above. Regardless, I think Serif could fix this because Paste Inside doesn't work the way any of us want it to work.

I'm using a 16GB M1 Pro and find it sufficient for books of several hundred pages with several hundred high res photos. I intended to buy it with 32GB but messed up. After ordering I was worried that it would be an issue because memory was a bottleneck on my Intel MBP with 16GB, but it's been fine. Even if I force Publisher to load all of my book's 14GB of linked photos into memory, macOS handles the memory swaps without me noticing. I will order 32GB next time for other reasons and I wish I'd done so this time because as @v_kyr wrote, it's good to have something in reserve. I think this is key and we've seen this with other Book export problems that were fixed in the recent 2.x updates. There were some simple books that exported as separate chapters but not as a single book. BTW, did you disable hardware acceleration (metal) as suggested by Lee? I thought I knew all of the 1980s and 90s processors but I've never heard of the Z280!

Oh you're right, I wrote that wrong. Oops. You need to press Esc Esc V because of the selected text issue. "V" will work if the cursor isn't in the frame, Esc V will work if text isn't selected, and Esc Esc V is necessary if text is selected. So we all just press Esc Esc V regardless so we don't have to think about the shortcut.

I don't think it was ever changed, 1.10 and 2.3 have the same behaviour - overflowing text in a master frame is flagged even if there's no overflowing text in the frame on any document page. I agree it should be changed.

That's the way it's supposed to work but people ask about this all the time. Press Esc once to remove the text cursor from the frame or text object and the frame or object will now be selected with the text tool. Press Esc a second time to deselect the frame or object. The issue arises because Affinity allows us to select frames and text objects with a text tool instead of just with the move tool. In most apps, you can't select objects with a text tool. But because pressing Esc once leaves the object selected so you can manipulate it, you have to press Esc a second time. Most of us have adapted by always pressing Esc twice. It requires changing some muscle memory but now I don't think about it. Esc Esc V to switch to the Move tool will always work while Esc V will work only if the cursor wasn't in the frame or text object.

Thanks. I still recommend to use a font such as Palatino Italic, rendering Arial Regular is too easy for an app because the strokes are so uniform and straight.

@wrandyr This is a known issue but it's easy to avoid. Edit the TOC 1: OHAP... paragraph styles and define all of the attributes that aren't currently defined and which are getting messed up. For example, if the TOC keeps being made italic when you update it, define the text as Regular (or something similar) instead of <No Change>. You will likely have to define the font family to do this. If the leading keeps getting messed up, define the leading in the text style. Cheers

You're talking about on-screen, right? This is probably just a Windows discussion because most Mac apps use the OS to render type so they all look identical and there would be nothing to compare. Affinity's on-screen type looks absolutely gorgeous on a retina screen. The big exception on macOS is Adobe – it still uses its own rendering code which IMO looks chunky, regardless of its selected antialiasing option. So this might just be a Windows exercise but IIRC you'll need to ensure that each sample is from an identical setup - they'll need to have the same resolution, font smoothing settings, and maybe even display orientation. It's been a couple of years but I vaguely recall that ClearType works differently if you rotate your display. If you want to do a comparison, I suggest using a font that has thin, curved, and non-uniform strokes such as Palatino Italic. Any text rendering code should be able to render Arial with some degree of competence but Palatino Italic is a real test. It was one of the original PostScript fonts and its delicate design coupled with the low-resolution monitors of the '80s and '90s wasn't always beautiful.

Hi John, there are three places you can do this. Select the text and then apply the style with: Text Styles panel - click Heading 1 Paragraph panel - select Heading 1 from the unlabeled list below the alignment icons Context Toolbar - selecting Heading 1 from the list to the right of the pilcrow icon ¶ You might also want to read the Text Styles chapter of the free Publisher manual I've shared in this forum. The link is in my signature. Cheers

Hi @Joop Vos and welcome to the forums. I've written detailed instructions for baseline grid and much more in the free Publisher manual I've shared in this forum. The link to it is in my signature below. Cheers

Are you asking for the Layer > Insertion setting which controls where copied objects are pasted to also control where duplicated objects are pasted?

Same for me, definitely a new bug.

+1 I would also like the panel to show the document's index options instead of the ones I used for another book several days ago. The panel always shows the last-used options which makes it difficult to format multiple documents' indexes at the same time. The only way to know what the options are for a document is to look at its existing index. And since spaces and dashes may be hard to discern, convert the index text to unicode so that you can retype the options in the panel. I like all the new options but I find it quite frustrating.

The problem with doing that is when you apply a text style in the future, the language will be changed. It's always better to define the language in the style. If you already created all your text styles and forgot to set Language and don't want to mess with it, you can easily update them all at once, or at least with just a few changes. Sort the Text Styles panels as hierarchical and then edit the style groups for paragraph styles. For many documents, all of the paragraph styles will be under "Base" so just edit Base and set the spelling language. All of the other styles will likely inherit this change. Cheers

Whether the pasted inside object is on the same page or not depends on a combination of the clipboard object's position, the selected object's position, and whether the clipboard and selected objects are on different sides of a facing pages document. None of this makes sense to us as users but that's the way it works. We expect the pasted object to be visible but depending on the position of clipboard object, it may be offset horizontally and vertically so that it's outside of the frame of the parent object. This isn't helpful and IMO should be changed. Also, Publisher does a facing pages adjustment when you paste an object to try to mirror the pasted object's position horizontally, and this can further offset the pasted object horizontally even though it's not relevant to pasting inside. IMO, there's no logical reason to apply a facing pages adjustment with Paste Inside. The way I think it should work is: If the copied object overlaps at all with the selected object, paste the copied object inside it without adjusting the X/Y coordinates. Trust that the user positioned the copied object as desired before copying or cutting it and paste it in the same position. If the copied object doesn't overlap with the selected object, paste the copied object inside the selected object while adjusting the X/Y coordinates so that the pasted object is visible inside the selected object. i.e., set the pasted object's offset to 0/0 from the current Transform panel anchor.

Hi @fourcade anne and welcome to the forums. First, try restarting macOS. That probably won't solve it but it's worth trying first. Second, try starting Affinity Photo while Ctrl is held down. (Press and hold Ctrl immediately after clicking the app icon.) The Clear User Data screen will appear. The screenshot below is for Publisher but it's similar to Photo - click the Effacer button in the bottom right and hopefully Photo will now start. Good luck!

Click in the "See Also" part of the index text. The character style should now be "Index Cross-reference Label". Check that Text Style panel "Current Formatting" summary at the top of the panel and see what it says. It should be "Index Entry 1 + Index Cross-reference Label + [No changes]" or something like that. If it includes "Leading override" then we'll come back to that in a bit.** If it doesn't include Leading Override, then edit the character style and see if it specifies a leading override. If so, this is easy, just delete the leading override and you should be fine. Next click in the index topic words you are cross referencing, for example, click in "dictionary" in "See also dictionary". The character style should now be "Index Cross-referenced Topic". Again, edit the character style and see if it specifies a leading override. If it does, clear it, too. **If the text styles don't include a leading override but there's a leading override applied to the "see also" text as shown in the Current Formatting summary, then this is probably similar to the TOC bug where previously-applied formatting is "picked up" when the index is generated. This happens all the time with TOC generation. You can avoid it by editing the index text styles and defining the leading override to the same value as the paragraph leading. So if your paragraph leading is 12 pt, just set character leading override to 12 pt. Good luck

It can also take longer if you choose to rasterize everything so check your PDF export settings. Good luck!

Hi @PaulB2 and welcome to the forums. I'm on an M1 Pro so it's somewhat slower than your machine but I don't find exporting to PDF to be slow, other than the preview. Note that you don't need to wait for the preview to display, just ignore it and click Export. Can you describe the types of documents you're exporting and how long they take to export?

Good idea. I recommend changing the default shortcut to a more convenient one. Instead of Option+Shift+Command+[ which I find difficult to press, I use Shift+Command+I. That one isn't assigned by default and is an easier one to press.

This one puzzles me, I can't think of any way to delete multiple endnote markers but to retain the endnote text when Positioning is set to End of Story because with that option, each note is in a separate child frame. Could you do a few tests with the broken document? Open the document and deselect all text frames by clicking on a blank part of a page. Look at the Notes panel and with Endnotes and Document-wide selected, what do you see for Note Position? Is it set to End of Story? Click in the story text and choose Select All to select all the text in the story. Scroll to the endnotes - the text in them should not be selected because they with Positioning set to End of Story, the notes will be in individual child frames. Can you confirm their text isn't selected? Click in one of the endnotes to place the text cursor in it. It should look something like this, the note's child frame should be selected with X handles at the corners to indicate it cannot be transformed. Good luck.

I don't know of any way to remove them all at once except for obviously copying the text outside of Affinity and pasting it back in. I don't think anybody else has reported a problem like this so if you can figure out what triggered it that would be useful. That fact that it's happened to you twice is concerning. I use sidenotes extensively in my Publisher manual and haven't had that problem. And I'm using footnotes in another book and not seeing any issues but it's still early days for that project. Good luck!