Line breaks for typographic quotes don't work

[Dirk_Germany]

In German language, typographic quotes are used. Example: Er fragte: „Wie spät ist es?"

Strangely, if the closing quotation mark is the last character in a line, Affinity Publisher starts the new line before the closing quotation mark, not after.

So it looks like this:

Er fragte: „Wie spät ist es?
"

I have not found any way to solve this problem using configuration so I had to change my original text to avoid it.

[Dan C]

Hi @Dirk_Germany,

Thanks for your report!

I can confirm I've been able to replicate this here and I'm getting it logged with our development team now.

16 hours ago, Dirk_Germany said:

I have not found any way to solve this problem using configuration so I had to change my original text to avoid it.

In my testing, this doesn't seem to occur with the language set to English (UK) for the text, though of course your text will then not be spellchecked. If you set the text to use Eng (UK) in the Character Studio and re-type the quote, it should work as expected.

I hope this helps

[Dirk_Germany]

In which dialoge do I change the language? I can only find a language setting in the preferences under "Auto correction". Here is an example of the incorrect line break. Will it be fixed in the next version?

[MikeTO]

30 minutes ago, Dirk_Germany said:

In which dialoge do I change the language? I can only find a language setting in the preferences under "Auto correction".

Language is a character attribute so choose it from the Character panel in the Language section. Select the language from the Spelling list.

Cheers

[Dan C]

14 hours ago, Dirk_Germany said:

Will it be fixed in the next version?

Unfortunately I can't offer any direct guarantees or a timeline for this to be resolved at this time, but I can assure you it's been logged with our development team and will be investigated further, to be fixed asap

[StefanGold]

With 2.3.0 on macOS, the bug is the same....

Please fix this as soon as possible!

[Affinityconfusesme]

maybe in 2.4.

[MikeTO]

On 11/8/2023 at 5:19 AM, Dan C said:

Unfortunately I can't offer any direct guarantees or a timeline for this to be resolved at this time, but I can assure you it's been logged with our development team and will be investigated further, to be fixed asap

BTW, I was replying to a suggestion today to not break at a period or comma in a number (e.g., 123.456 or 123,456,) which requires manually fixing with no break. Affinity breaks at all periods and commas but that's not the way word processors and layout apps have traditionally worked. Implementing that suggestion - break at a period or comma only when the following character is whitespace or a break character - would avoid all these issues with breaking between periods and quotes without having to make a language-specific fix.

[Oufti]

4 hours ago, MikeTO said:

Implementing that suggestion - break at a period or comma only when the following character is whitespace or a break character - would avoid all these issues […]

I totally agree and support this proposition.  

I don't see any situation where it would be more problematic than the present one. 

[Dan C]

19 hours ago, MikeTO said:

BTW, I was replying to a suggestion today to not break at a period or comma in a number (e.g., 123.456 or 123,456,) which requires manually fixing with no break. Affinity breaks at all periods and commas but that's not the way word processors and layout apps have traditionally worked. Implementing that suggestion - break at a period or comma only when the following character is whitespace or a break character - would avoid all these issues with breaking between periods and quotes without having to make a language-specific fix.

Thanks for raising this here Mike, I've replied to the thread in question.

I hope this helps

[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.