Bug 87341 - FORMATTING: Wrong cells formating
Summary: FORMATTING: Wrong cells formating
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.4.1 release
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Calc-Cells
  Show dependency treegraph
 
Reported: 2014-12-15 20:39 UTC by Yan Pas
Modified: 2023-04-24 04:17 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
file and screen (231.03 KB, application/x-rar)
2014-12-15 20:39 UTC, Yan Pas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Pas 2014-12-15 20:39:53 UTC
Created attachment 110880 [details]
file and screen

On the screenshot difference between Excel and Calc. For example problematic cells are F2, B1, C9
              
Operating System: All
Version: 4.3.4.1 release
Comment 1 Buovjaga 2014-12-16 12:09:05 UTC
Confirmed -> NEW.

I see in the cells with № ауд, there are simply a lot of empty spaces between them. What is the situation in Excel? A line break? If I replace the spaces in LibreOffice with a line break (ctrl-enter), it looks the same.

Lowered severity per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg

Win 7 64-bit Version: 4.5.0.0.alpha0+
Build ID: 170616e9f2d30c1302bbb5a7a4b588bc05cd5cc9
TinderBox: Win-x86@39, Branch:master, Time: 2014-12-12_01:58:46
Comment 2 Yan Pas 2014-12-16 14:12:21 UTC
Looks like simple spaces. I do not have a clue how to find out what symbols are there (excel can't show hidden symbols). Copy-pasting to notepad shows that there are spaces. 
hex view:
e2 84 96 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 d0 b0 d1 83 d0 b4
Comment 3 Yan Pas 2014-12-16 14:16:45 UTC
Also in Calc first line is not displayed entirely, while in excel all letters are visible
Comment 4 QA Administrators 2015-12-20 16:06:00 UTC Comment hidden (obsolete)
Comment 5 Yan Pas 2015-12-20 22:04:35 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-01-03 19:54:55 UTC Comment hidden (obsolete)
Comment 7 Yan Pas 2017-01-06 20:02:34 UTC
5.2.3 still reproducible (Linux Mint 18)
Comment 8 QA Administrators 2018-01-07 03:31:18 UTC Comment hidden (obsolete)
Comment 9 Xavier Van Wijmeersch 2018-01-07 15:20:32 UTC
still reproducible with versions from 5.3.1.2 to 6.1.0.0 alpha0+
Comment 10 QA Administrators 2019-01-08 03:43:23 UTC Comment hidden (obsolete)
Comment 11 Xavier Van Wijmeersch 2019-01-08 20:51:04 UTC
repro with

Version: 6.3.0.0.alpha0+
Build ID: 32b85ec64e5c901369ce3ce5dbda0e96f2ec7fc0
CPU threads: 2; OS: Linux 4.19; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-07_16:08:14
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 12 QA Administrators 2021-01-08 04:20:11 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2023-01-09 03:21:01 UTC
Dear Yan Pas,

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