If cells have customized thinner and thicker border lines - for example like a
Sudoku table - the thickness of the lines around the selected cell is not in-
creased. If the bottom right tag of the selected cell lies on a thicker border
line, it will be invisible.
Check against OpenOffice 3.3.0 where the line thickness of the borders of the
selected cell is increased.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Created attachment 54784 [details]
Created attachment 54785 [details]
Created attachment 54786 [details]
I am able to confirm the earlier reported bug 36825 with LibO 3.5.0 beta1.
In fact things turned worth:
- the borderlines are much thicker then specified in the ods-file, the orders
of the selected cell are not enhanced
- there are minor deviations in the metrics, @198% scale the table occupies
the whole screen width under LibO, it don´t under OOO or MS-Office
- WHOW! Importing the same table from an xls-file leads to a nearly perfect
(neglecting the minor deviations of the metrics) result!!!!
System environment: Win XP de SP3
The file Sudo32.ods had been created with OpenOffice 3.3.0.
The file Sudo32.xls was exported with OpenOffice 3.3.0
Sudo32.ods, from OpenOffice 3.3.0,
Sudo32.xls, from Openoffice 3.3.0,
Sudo32LibO.png, Screenshot from LibOdev3.5.0 beta1
Sudo32LibOdevXLSimport.png, Screenshot from LibOdev3.5.0 beta1
Sudo32OOO.png, Screenshot from OpenOffice 3.3.0 (looks like
Volker J. Hellborg
This bug hasn't seen any action. Switching ASSIGNED to NEW
Volker if you are still working on this, please re-assign yourself.
** 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 (4.4.2 or later)
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)
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: 2015-05-02
Hi Volker, I think this bug report is the same as Bug 56846. Can you confirm?
I closed this as a duplicate of the newer bug 56846 because that one is more clear. Volker; feel free to reopen if you don't agree.
*** This bug has been marked as a duplicate of bug 56846 ***