MikeTO

Hi, what language do you want to set as the default? You can set Affinity's default language by first selecting it from the Character panel's Language > Spelling list and then choosing Edit > Defaults > Save. I've included a lot of information about spelling dictionaries in the free Publisher manual I've shared in this forum - the link is in my signature. Cheers

Hi. First, you can find more information about special characters and stories in the free Publisher manual I've shared in the forum. The link is in my signature below. This is an odd issue, it almost looks like the end of story symbol is appearing for each paragraph or line of text. How was the document created? From scratch or from opening a PDF? Is View > Show Text Flow on? I'm wondering if each of those is a separate text frame rather than a single frame. Could you share a test document here? Good luck.

FYI this is a known bug and affects any text field with values between 0 and -1p.

@undercovergypsy I replied in the other thread you posted about this to.

It's a US vs. UK English string difference. Oddly, the UK string is "Normalize" with a Z instead of an S. It's "Preserve" in the US version.

Which versions of Windows and Affinity are you using? Did this just start happening or has it been happening for a while? If it just started happening, did you try restarting your PC? Do you have any third-party mouse drivers or utilities installed, such as the Logitech software? What type of mouse do you have? Is it a high DPI mouse? If it's wireless, is it fully recharged? If you have a trackpad, too, try disconnecting your mouse and seeing if the issue also happens with your trackpad. Or if. you're using the trackpad already, try using a mouse instead. Good luck

Keep in mind that there's no way to keep multiple documents in sync in terms of design. If a year from now you want to change the layout or text formatting, you'll have to make changes to all of the documents. There aren't features to use an external style sheet or a way to refresh a master page in multiple documents at once. I've provided some workaround tips on importing text styles and master pages in the free manual I've shared in this forum. Cheers

Hi @Giannis and welcome to the forums. The Hyperlinks feature is limited to Publisher so that's why you can't find it. Here's a reply from Serif from three years ago on the subject.

Thanks, it works great now.

it would today, but see the final paragraph in my suggestion. It should check for frames on the master layer, not just the document page layers.

I added this to my first post: Support multiple stories per page use case: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. This makes it impossible to use AutoFlow for both stories in a side-by-side layout (e.g., a Bible translation). AutoFlow could instead check if the new frame would overlap with an existing frame on the page. If it would overlap, create a new page, but if not, then create the frame on the existing page.

I'm glad you pointed this out. There's a really simple solution for the side-by-side use case which I didn't provide a suggestion for. I'll edit my post above to add that. I'd prefer to avoid having autoflow as a frame property, I think that might confuse users.

For this type of document, I recommend: Create a new document - turn off facing pages if it is on Go to the master page Using the Frame Text tool, draw a text frame on the master page Type a placeholder quotation and format it the way you want it, including centering the text Go to page 1 and replace the placeholder quotation with the actual one for that page Add additional pages and type quotations Into them, too Good luck

Hi @Rogalsky and welcome to the forums. Are you using Running Headers? If so, this is a known bug in 2.3.0 which has already been fixed for the upcoming 2.4 release. I don't think this fix is included in the upcoming 2.3.1. release. If this isn't what your issue is, could you provide more details?

If all the text is in a series of linked text frames, you could use Select All and then centre the text. If the text is in separate frames but uses consistent text styles, you could edit the text style and choose Centre which would change all text formatted with that styles. If the text is in separate frames and doesn't use text styles, then there are a few options: Using the Move tool, select all the frames on one page, and choose Centre - that will change all the text in all of the selected frames at once. You will need to repeat this for each page. Use Find and Replace. Click the Gear icon beside Find, select Format, select Paragraph, and set Alignment to Left. Click the gear icon beside Replace, select Format, select Paragraph, and set Alignment to Centre. Click the Find button and it will find all left-aligned text. Click the Replace All button to change all text in the document to centred, or click Replace for each search result you want to change. There are other options such as using the Style Picker tool but I think this will get you started. Cheers

There is a learning curve to AutoFlow because the Text Flow Out control is small and must be Shift clicked so it's not discoverable - you have to read/watch instructions or ask in this forum or you will never find the feature. People keep asking about this so I entered a suggestion today to improve discoverability.

Users keep asking about why Publisher doesn't flow text automatically like other apps. This is because the AutoFlow feature isn't discoverable - the Text Flow Out control must be Shift clicked so new users have to read/watch instructions or seek help. I never use AutoFlow because it breaks my documents but the suggestions below would address all of these issues. Add setting for automatic AutoFlow: Most apps have an on/off setting for auto flow and when selected will auto flow text without needing to click a control like Publisher. Those apps can also delete blank pages automatically. Publisher doesn't delete unneeded pages so to keep this simple, I suggest adding an "Automatic AutoFlow" checkbox to settings, selected by default, that would prompt the user to automatically auto flow when text is overset. In a perfect world, the alert would include a "Don't show this again" checkbox that would disable the setting without having to visit settings, to avoid annoying experienced users. Add setting to limit AutoFlow to master page frames: The current feature is manual so pages are never created accidentally, but if the automatic option was enabled, it could get annoying when you temporarily overset a small text frame while editing an image caption. This is why ID limits the feature by default to primary text frames. Publisher doesn't have a primary frame feature but a similar option to limit it to master page frames would be nice. It should limit it to true master page frames, not to text frames pinned inline in master frames. Add setting to always add pages at end of story: AutoFlow correctly creates pages at the end of a section instead of at the end of a document which is great for those who use sections. For those who don't and who use separate stories for each "chapter", Publisher really needs an End of Story option because otherwise the new frame will be created at the end of the document, potentially hundreds of pages later. ID offers three options: End of Story, End of Section, and End of Document but Publisher does a great job of automatically choosing End of Section versus Document so I think it only needs a checkbox named "Always add pages at end of story". Add setting to preserve spreads: You might not want a single page to be added because it will mess up your perfect spreads which is why ID offers its "Preserve Facing-Pages Spreads" option. This option adds full spreads and not single pages and would be a good enhancement for Publisher. Support multiple stories per page use case: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. This makes it impossible to use AutoFlow for both stories in a side-by-side layout (e.g., a Bible translation). AutoFlow could instead check if the new frame would overlap with an existing frame on the page. If it would overlap, create a new page, but if not, then create the frame on the existing page. Fix issue with non-master frames created on top of master frames: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. But it will create a frame on an existing page with a large master frame full of text - the end result will never be usable. It would be better if autoflow also checked for text names in master page layers. Thanks

If this isn't specific to the beta then please post in the regular v2 bugs forum. I believe this helps the Serif team keep things straight. Thanks

Hi, in Settings > Performance, do you have Hardware Acceleration > Enable Metal Compute Acceleration selected? If so, deselect it and change Display (a few rows above it) to OpenGL. This will help with random crashes. If you already have these settings, then perhaps somebody else will have a better idea. Good luck.

This was a really fun example to add to the manual - it's cool that we can include images in a TOC so easily. For the manual I also reversed the images and page numbers in the example using the option to do so in the TOC panel which provided a real-world example of when you might want to reverse the page numbers. I wouldn't use this pictorial index approach myself, unless Serif adds the ability to alpha sort TOCs, a feature that is occasionally requested. ID has this feature and I think it would be useful for pictorial TOCs because there's no way to include a pinned image in an index. But if we could alpha sort a TOC, I could use this for something like a sculpture index. I'd have to include some text with the images to use alpha sorting but I'd need that for an index anyway. So + 1 for alpha sorting of TOCs - I could easily add sculpture and symbol "indexes" to my history book using the TOC feature.

Hi @Katejsej and welcome to the forums. The exported SVG is measured in pixels and your document is likely set to 300 dpi. Change the document DPI to 72 in Document Setup or when creating the document and you'll get the results you're probably expecting. Cheers

I'm seeing the same thing but this isn't new in the beta, it was this way in 2.3.0, too.

I'm not seeing this on macOS so it might be Windows specific.

This isn't new in the beta or even in v2. It happens with any character attribute and at any position in the text other than at the start of a new paragraph - it's not specific to character styles. If you backspace to the start of a change in character formatting, then Affinity will change to the character formatting before that character. Backspacing deletes the hidden control codes for the formatting at the same time it deletes the character. This isn't necessarily a bug, some apps (Apple Pages) work this way and other apps (MS Word, Apple TextEdit) work the other way. Like you, I prefer the other way but I'm used to it now.

I made a catalogue-y example for my manual to demonstrate this.