https://bugs.documentfoundation.org/show_bug.cgi?id=168535

            Bug ID: 168535
           Summary: Handling ellipsis, quotation mark and space as one
                    character
           Product: LibreOffice
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
I often use an italic font for quoted text. The problem is marking the text
(for italics) without quotation marks at the beginning and end. If there is an
ellipsis (…), followed by a quotation mark, sWriter recognises this sequence of
characters (including the subsequent space after the Q-mark) as one character,
rather than three (ellipsis, quotation mark, space). This only happens if
sWriter replaces the three dots written manually with a default ellipsis mark.

Steps to Reproduce:
1. Write some text using quotation marks and three dots, whereby the three dots
are automatically changed to an ellipsis.
2. Select text by repeatedly pressing the right arrow key (while holding
CTRL+SHIFT) from the beginning (after the first quotation mark) to the second
quotation mark.

Actual Results:
The text will be selected up to the beginning of the next word. Ellipses,
quotation mark and the subsequent space will be handled as one character.

Expected Results:
The selection should stop after the ellipses and before quotation mark.


Reproducible: Always


User Profile Reset: No

Additional Info:
See attached example file.
It should be noted that this behaviour also occurs when using the CTRL+arrow
key combination to move the cursor by words (in both directions). 

Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 16; OS: Windows 10 X86_64 (10.0 build 19045); UI render:
Skia/Raster; VCL: win

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to