Bug 66776 - Importing .xls: Change in Cell Border Width Conversion
Summary: Importing .xls: Change in Cell Border Width Conversion
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-10 14:27 UTC by Jeff Evans
Modified: 2016-01-24 02:05 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
MS Excel originated spreadsheet with 3 border widths (18.50 KB, application/vnd.ms-excel)
2013-07-10 14:27 UTC, Jeff Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Evans 2013-07-10 14:27:28 UTC
Created attachment 82276 [details]
MS Excel originated spreadsheet with 3 border widths

In 3.6.5, Border widths of the 3 thicknesses are converted to 0.30pt, 0.90pt and 1.20pt. This appears in print roughly in accordance with MS Excel XP. In 4.0.4 the conversions are 0.20pt 0.60pt and 0.80pt. Can we please revert to 3.6.5 interpretation?

Having just printed samples, MS Excel XP actually prints the lines even thicker than LO 3.6.5, but I can live with that; maybe something with my printer driver?

Sorry if this has been raised before, I couldn't spot it on a cursory scan.

I raised an analogous bug in the Filesave area back in 3.5 or so. Interpretation of line thickness needs to be consistent.
Comment 1 Yousuf Philips (jay) (retired) 2014-06-08 09:24:12 UTC
When examining the border thickness of the example file, here are the results from various LibO versions for the first cell.

3.3.0  - 1.00pt, 2.50pt, 4.00pt
3.6.7  - 0.30pt, 0.90pt, 1.20pt
4.0.6  - 0.20pt, 0.60pt, 0.80pt
4.1.6  - 0.05pt, 1.00pt, 1.50pt
4.2.4+ - 0.75pt, 1.75pt, 2.50pt

Not sure what to make of this, as its all over the map and i couldnt find any particular setting in the options which defined the thickness.
Comment 2 QA Administrators 2016-01-17 20:03:04 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (5.0.4 or later)  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Comment 3 Jeff Evans 2016-01-24 02:05:16 UTC
Bug was resolved some time ago, as noted by Yousouf above.
Just checked previously suppled sample and get satisfactory results in LO 5.0.3 vs MS Office 2010.

Thanks.