Position of vertical lines are lost when saving in XML format, whatever the anchor and the reference for mesurements.
It works well with Word 97-2003 (.doc) format, but not with Word 2007-2013 XML (docx).
Steps to Reproduce:
1.Create a document with vertical (or oblique) line(s)
2.Save as Word 2007-2013 XML (docx) and close
3.Reopen the document
Positions of lines are altered, and lines may be lost depending of whcih combination of anchor - reference of mesurement.
Keep correct positions
User Profile Reset: No
Apparently, positons of horizontal lines work correctly.
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
I can confirm with Version: 18.104.22.168.alpha0+
Build ID: 834cebd153573eea3cc321eca5bcb572b4776dec
CPU threads: 4; OS: Windows 6.1; UI render: default;
and Version: 22.214.171.124.alpha0+
Created attachment 139024 [details]
Created attachment 139025 [details]
Hi Silvain, Raal,
LO 126.96.36.199 Build ID: 4044db1653798618515c987464157abee9229c11
but not with:
LO 188.8.131.52.beta1 Build ID: b7cfa1eab1cb1e94f71d6df6612b73f231d0bf92
and upper versions under windows 7
Vertical Lines Positions were also reserved in XML format with
LO 184.108.40.206 Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd
I bibisected with Linux 44max, but got this obviously wrong result (about menus):
Author: Matthew Francis <email@example.com>
Date: Sun Mar 15 02:52:51 2015 +0800
Author: Matthew J. Francis <firstname.lastname@example.org>
AuthorDate: Thu Sep 18 18:33:00 2014 +0800
Commit: Tor Lillqvist <email@example.com>
CommitDate: Thu Sep 18 12:59:32 2014 +0000
fdo#69090 Avoid using a string after free
The trouble is that the commits are not in chronological order! The preceding commit is newer than the blamed one, but it does not show the problem.
(In reply to Buovjaga from comment #6)
> The trouble is that the commits are not in chronological order! The
> preceding commit is newer than the blamed one, but it does not show the
This was apparently my failure to understand timezones.
Bibisecting using repo bibisect-43max points to two incorrect states, first the slanted lines is only positioned slightly lower than the vertical one in the DOCX, and later they become positioned below one another (as in raal's comparison screenshot).
Bibisecting the first change yields the following range (LO crashed in between):
Bibisecting the second change yields the following commit:
author Jacobo Aragunde Pérez <firstname.lastname@example.org> 2014-04-14 18:53:34 +0200
committer Jacobo Aragunde Pérez <email@example.com> 2014-04-15 11:35:49 +0200
"fdo#70838: fix rotation transformation in DML exporter
This patch fixes an error in commit
The referred commit is in the range above, so I'm assuming that's what caused the first change:
author Jacobo Aragunde Pérez <firstname.lastname@example.org> 2014-03-22 13:16:52 +0100
committer Jacobo Aragunde Pérez <email@example.com> 2014-03-22 23:58:15 +0100
fdo#70838: apply rotation transformations to DML anchor position
Dear Silvain Dupertuis,
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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!