Bug 132372 - EDITING DOCX: Consecutive spaces in table cell not ignored if they start at the beginning
Summary: EDITING DOCX: Consecutive spaces in table cell not ignored if they start at t...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables
  Show dependency treegraph
 
Reported: 2020-04-24 07:09 UTC by NISZ LibreOffice Team
Modified: 2024-02-02 16:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Word (11.59 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-04-24 07:09 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer (95.74 KB, image/png)
2020-04-24 07:09 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-04-24 07:09:36 UTC
Created attachment 159884 [details]
Example file from Word

If a table cells text is long, spanning multiple rows and centered, the line breaking behaves differently when it contains consecutive spaces: If they are between visible letters, they are hidden and have no effect on alignment.
But if they start the cell text, they are not hidden and are considered for alignment.

The hiding results in consistent behavior with Word, which ignores the consecutive spaces when calculating alignment. 
Probably Writer should do the hiding of spaces even if they start the cell content.


Steps to reproduce:
    1. Open attached document

Actual results:
First tables text looks different than in Word, 

Expected results:
Similar behavior to Word, so that Word-made files layout can match.

LibreOffice details:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 94a7ceae287a7967e8f013d012673e26637c6bb5
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL

Also happens in older versions way back to 3.5.0
Comment 1 NISZ LibreOffice Team 2020-04-24 07:09:53 UTC
Created attachment 159885 [details]
Screenshot of the original document side by side in Word and Writer
Comment 2 Dieter 2020-04-29 11:38:51 UTC
I confirm it with

Version: 7.0.0.0.alpha0+ (x64)Build ID: 8c8b3a4f83f67882b284ddc3b3fe10d3fe6dedf4CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GBCalc: CL
Comment 3 BogdanB 2022-01-27 20:55:31 UTC
REPRO in 7.4

Retested with
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 2f4f4cbeb8e50081d607b86b0475b93971c40ab8
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 4 QA Administrators 2024-01-28 03:13:59 UTC
Dear NISZ LibreOffice Team,

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