Created attachment 121928 [details]
DOC with headers in portrat and landcape
While looking at Bug 37146, I noticed that header with frame from landcape is not properly shown in DOC, even if it's portrait only document.
Sorry, wrong click.
Created attachment 121932 [details]
printscreen from Word 2010
I can confirm with LO 22.214.171.124.alpha0+
repro in 6.1+
** 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 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!
still repro in
Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: ru-RU (ru_RU); UI-Language: en-US
LO can rotate textboxes, but frames cannot be rotated?
> Frames cannot be rotated
> For text at 180 degrees rotation in Word before Word 2010, you need to use Frames in landscape mode.
We should not be able to rotate frames. This would introduce export issues. Rather frames need to be extended to correctly render landscape pages like word does.
Created attachment 148612 [details]
DOC with frame not in header
Example showing that the issue is not related to the header/footer
Created attachment 148613 [details]
DOCX landscape frames also incorrectly rendered
Created attachment 161024 [details]
Example document with 0 90 and 270 degree text rotation
An improved version of attachment 160866 [details] from bug #69175
There a VML shape is rotated, which is converted by Writer to a frame. The text direction setting is imported correctly this way, only the shape dimensions are incorrect.
Word can convert those VML shapes to frames, which opens up this bug.
The text direction setting is not imported in frames, but the frame dimensions are correct at least.
Created attachment 161025 [details]
Screenshot of the example document in Word and Writer 7.0
Version: 126.96.36.199.alpha1+ (x64)
Build ID: 442c7b95e2ee94b66a9854d0cb22f8ecb76532c6
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win;
Locale: hu-HU (hu_HU); UI: en-US
Sorry for the noise this is indeed a frame import bug.
@Tibor I thought you might be interested in this
Daniel Arato (NISZ) committed a patch related to this issue.
It has been pushed to "master":
tdf#97128 DOCX import: fix frame direction
It will be available in 7.1.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Created attachment 166172 [details]
DOCX with headers in portrait and landcape
Timur added DOC attachment 121928 [details] as original sample with headers in portrait and landcape, DOCX variant added now
Luke added DOC attachment 148612 [details] and DOCX attachment 148613 [details] with frame in body
NISZ added DOCX attachment 161024 [details] example document with 0 90 and 270 degree text rotation and Screenshot attachment 161025 [details]
Created attachment 166173 [details]
Example document with 0 90 and 270 - compared MSO LO
This is a nasty bug. Obviously DOCX example attachment 166172 [details] and attachment 148613 [details] had more issues, not all resolved.
What I see improved or fixed is DOCX attachment 161024 [details]. Here is a screenshot MSO and LO 7.1+ before and after the fix.
I guess DOC will remain, not a problem to open a new bug for that.
FYI: attachment 168130 [details] (from bug 138503) is dying on assert(!m_aFrameDirectionQueue.empty());
Hi Daniel, NISZ Team,
I believe https://cgit.freedesktop.org/libreoffice/core/commit/?id=af4e5ee0f93c1ff442d08caed5c875f2b2c1fd43 introduced https://crashreport.libreoffice.org/stats/signature/writerfilter::dmapper::DomainMapper_Impl::SetFrameDirection(short), one of the most reported crashes in 188.8.131.52 ( https://crashreport.libreoffice.org/stats/version/184.108.40.206 ), any idea on how to reproduce it ?
(In reply to Xisco Faulí from comment #18)
I believe Justin L's report of the failing assert above is the best lead we have at the moment.
(In reply to Dániel Arató (NISZ) from comment #19)
> (In reply to Xisco Faulí from comment #18)
> I believe Justin L's report of the failing assert above is the best lead we
> have at the moment.
oh, I missed that, and of course, it crashes in a release build. I'll report it in another issue...