Bug 68268 - EDITING: Sentences are inserted without spaces at the end or at the beginning
Summary: EDITING: Sentences are inserted without spaces at the end or at the beginning
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Paste
  Show dependency treegraph
 
Reported: 2013-08-19 10:13 UTC by Harald Koester
Modified: 2022-09-05 03:37 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2013-08-19 10:13:25 UTC
Problem description: 

If you copy or move words to a new position always one space is inserted in front of and after the inserted word. This does not work if you copy or move whole sentences. 

Steps to reproduce:
[1] Open new text document.
[2] Insert a paragraph with 4 short sentences. 
[3] Select second sentence with triple mouse click. 
[4] Copy to clipboard: Ctrl+C → Go on with step 5a or 5b
[5a] Move cursor directly after the full stop of the third sentence.
[6a] Insert sentence from Clipboard: Ctrl+V → The sentence is inserted without a space after the full stop. Expected: Insertion of a space.
[5b] Move cursor directly in front of the first word of the fourth sentence.
[6b] Insert sentence from Clipboard: Ctrl+V → The sentence is inserted without a space after the full stop of the inserted sentence. Expected: Insertion of a space.

The behaviour is equal if you drag and drop the sentence with the mouse. 

Bug exists already in my oldest installed version 3.5.0.
              
Operating System: Windows 7
Version: 4.1.0.4 release
Comment 1 Harald Koester 2013-08-19 12:27:47 UTC Comment hidden (obsolete)
Comment 2 Harald Koester 2013-08-19 12:29:09 UTC
Sorry, bug 68271 describes a similar problem with *paragraphs*.
Comment 3 Thomas van der Meulen [retired] 2013-08-22 15:51:15 UTC
Thank you for your bug report, I can reproduce this bug running LibreOffice.
Version: 4.1.1.2
Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903 on Mac osx 10.8.4.
Comment 4 QA Administrators 2015-04-01 14:40:59 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-04-22 14:45:12 UTC
Reproduced.

Win 7 Pro 64-bit Version: 5.0.0.0.alpha0+ (x64)
Build ID: 211c12b9c64facd1c12f637a5229bd6a6feb032a
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-18_01:51:17
Locale: fi_FI
Comment 6 QA Administrators 2017-09-01 11:16:30 UTC Comment hidden (obsolete)
Comment 7 Harald Koester 2017-09-15 10:07:43 UTC
Bug still exists in version 5.4.1 (Win7).
Bug already exists in version 3.3.0. Hence inherited from OOo.
Comment 8 QA Administrators 2019-05-27 02:45:56 UTC Comment hidden (obsolete)
Comment 9 Harald Koester 2019-06-25 12:36:17 UTC
Bug still exists in version 6.2.4. (64 bit, Win10).
Comment 10 QA Administrators 2022-09-05 03:37:45 UTC
Dear Harald Koester,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug