mick0005 Posted January 10 Posted January 10 Hi, i noticed that I'm not able to set the curser correctly or mark a word correctly in certain lines. As you can see in my sample screenshot, it happens in (some, not all) lines with an automatic hyphenation and the cursor/mark position acts like the whole word which is hyphenated would be in the next line. In my example i marked the word "Workshops" with a double click on it, it can be clearly seen that the blue mark is wrong (as are the curser positions in that line). It only seems to appear with the font "Source Sans Pro" as far as I noticed yet. Quote
Hangman Posted January 10 Posted January 10 Hi @mick0005 and welcome to the forums, I've not been able to replicate the issue on Windows or Mac with the German Language and Hyphenation dictionaries set. Could you upload the document or a document containing the text frame(s) so we can take a look... Text Selection.mp4 Quote Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Komatös Posted January 10 Posted January 10 1 hour ago, mick0005 said: It only seems to appear with the font "Source Sans Pro" as far as I noticed yet. Source Sans Pro was replaced by Source Sans 3. Which version do you have installed? Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
mick0005 Posted January 12 Author Posted January 12 On 1/10/2025 at 7:55 PM, Komatös said: Source Sans Pro was replaced by Source Sans 3. Which version do you have installed? Version 2.010, but I tried Source Sans 3 now, no difference. Quote
Komatös Posted January 12 Posted January 12 1 hour ago, mick0005 said: now, no difference. I have tested your test file with two Windows versions (one of them in a virtual machine) and a Mac, unfortunately I could not reproduce the behaviour either. The only thing I can think of now that might help you is to deactivate hardware acceleration in the Publisher (can be found in the settings under Performance). Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
Hangman Posted January 12 Posted January 12 On 1/10/2025 at 5:06 PM, mick0005 said: i noticed that I'm not able to set the curser correctly or mark a word correctly in certain lines. It's actually the Column End Zone value which is set to 10 mm for the Standardabsatz 1 text style in the sample file... Setting the value to 6 mm or less removes the problem though interestingly the problem only appears on Windows... HCl 1 Quote Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
MikeTO Posted January 12 Posted January 12 @Hangman is right, it's actually the combination of using Column End Zone with Justified text. These two features don't work together. We've seen this before and a variation of it is logged as AF-2478 although I don't think it encompasses the whole issue. HCl 1 Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted February 28 Author Posted February 28 On 1/12/2025 at 2:53 PM, Circulus said: It's the minimal word length and the minimum prefix in the hyphenation in the Standardabsatz1 text style. If I set this to 0 for both options the strange offset disappears. Thanks, that works, it's a useful solution depite not a logical one. HCl 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.