Quotation mark at the end moves to new line

[StefanGold]

Wie kann ich verhindern, dass ein Anführungszeichen am Ende ALLEINE in eine neue Zeile umgebrochen wird, obwohl da kein Leerzeichen dazwischen ist. In einem Buch mit sehr viel wörtlicher Rede macht das enorm viel Arbeit, das alles von Hand zu korrigieren.

How can I prevent a quotation mark at the end from being wrapped into a new line ALONE, even though there is no space in between? In a book with a lot of literal speech, it's a lot of work to correct everything by hand.

[MikeTO]

I recall this bug happening in the last year. I thought it was fixed but I am able to duplicate it with German text in 2.3.0 and the quotation mark inserted by the autocorrect feature, 201C.

test.afpub

 

[StefanGold]

7 minutes ago, MikeTO said:

I recall this bug happening in the last year. I thought it was fixed but I am able to duplicate it with German text in 2.3.0 and the quotation mark inserted by the autocorrect feature, 201C.

test.afpub

 

Thanks, I'm afraid that by the time the bug fix comes, it will be too late for me 😪

[thomaso]

4 minutes ago, StefanGold said:

I'm afraid that by the time the bug fix comes, it will be too late for me 😪

Could it work as workaround to add an invisible "soft-hyphen" before the quote mark or the word that is followed by the quote mark? Or a "narrow non-breaking space" before the quote mark? (I can't test/experience the issue in my V1)

If this works you could use Find & Replace with Regex to get the special character added for all instances in the document with "Replace All".

[walt.farrell]

42 minutes ago, MikeTO said:

I recall this bug happening in the last year. I thought it was fixed

Not shown as fixed, if it's this one: https://forum.affinity.serif.com/index.php?/search/&tags=AF-1036

[walt.farrell]

19 minutes ago, thomaso said:

Could it work as workaround to add an invisible "soft-hyphen" before the quote mark or the word that is followed by the quote mark? Or a "narrow non-breaking space" before the quote mark? (I can't test/experience the issue in my V1)

If this works you could use Find & Replace with Regex to get the special character added for all instances in the document with "Replace All".

It works with a Zero-Width Non-Joiner from the Text > Insert > Spaces and Tabs menu, at least in Mike's test file.

As a reg-ex, for the Find and Replace panel: Make sure the Find options are set to Regular Expression. Set the Find string to “ and set the Replace string to \x{200c}“

[thomaso]

1 minute ago, walt.farrell said:

It works with a Zero-Width Non-Joiner

Is that expected … or an issue? – From its name I would expect a non-joiner to support separation rather than keeping two characters together.

In your linked thread DanC mentions another workaround: to change the language. Apart from the possible language change for quotation marks via F&R for existing text, I wonder why F&R doesn't replace the appearance of existing typographic quotation marks when their language gets switched e.g. from German („ “) to English (“ ”)? If these characters are language related (same keyboard keys) I'd expect they could/would get changed with a style parameter (i.e. language). – Am I missing something or is Affinity lacking this option?

[walt.farrell]

1 hour ago, thomaso said:

Is that expected … or an issue? – From its name I would expect a non-joiner to support separation rather than keeping two characters together.

It seems that it's a character that is intended to be used between two letters that might otherwise become a ligature, to keep them from joining. I haven't investigated all the defined characteristics, but in that usage I could see it being treated as non-breaking, too.

[Dan C]

Thanks for your report @StefanGold!

As above, this is a known issue which is already logged with our development team - I've 'bumped' the development report with this thread for you now to bring it to their attention once again 

[Affinity Info Bot]

The issue "Typographic quotes can be orphaned to a new line, depends on language set and leading character" (REF: AF-1036) has been fixed by the developers in the latest beta build (2.6.0.3027). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.