Copying selected word usually copies following unselected space

[MikeTO]

There's a confusing bug in selecting words which makes it hard to text without copying the space after it. This one has been driving me nuts for a long time because it seemed unpredictable but I worked out the pattern today.

1. Start Publisher and draw a text frame and type "One Two Three Four"
2. Click before or after "Two". Using keyboard shortcuts, Shift select the word one character at a time. Choose Copy. This works, the space is not copied to the clipboard. The same is true if you forward or backward select the entire word instead of doing it character by character.
3. Double click "Two" and choose Copy - now the clipboard will contain the following space which was not selected. This isn't correct but it's predictable so it's not too bothersome.
4. Here's where it gets confusing. Repeat step 2. Now it will copy the following space no matter how you try to Shift select "Two".
5. You can clear the problem by Shift selecting something else and copying it. You can also clear the problem by typing a character before or after the word.

I don't know if this is specific to Mac.

[laurent32]

14 hours ago, MikeTO said:

Double click "Two" and choose Copy - now the clipboard will contain the following space which was not selected. This isn't correct but it's predictable so it's not too bothersome

That's a real bug !

14 hours ago, MikeTO said:

Here's where it gets confusing. Repeat step 2. Now it will copy the following space no matter how you try to Shift select "Two"

I don't seem to have that problem if I hit alt-shift select the whole word or shift select the word letter by letter…

[Callum]

Hi Mike,

Good catch I've logged this with our developers to be investigated further

Thanks
C

[Affinity Info Bot]

The issue "Space incorrectly gets added to text on clipboard if you double click a word to highlight" (REF: AFB-4947) has been fixed by the developers in internal build "2.2.0.1951".
This fix should soon be available as a customer beta and 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 @Serif Info Bot to notify us.