| Summary: | FILEOPEN ODT: Layout ODT of file written with 7.1 broken with 6.1 | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Telesto <telesto> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INSUFFICIENTDATA | ||
| Severity: | normal | CC: | ilmari.lauhakangas, vsfoote |
| Priority: | medium | ||
| Version: | 7.1.0.0.alpha0+ | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Example file
Example file ODT for export to DOCX DOCX Example PDFs of sample ODT opened and exported 6.1.6, 6.2.5, 7.1.0 PDF exported with 6.1 master |
||
|
Description
Telesto
2020-07-26 12:48:36 UTC
Created attachment 163554 [details]
Example file
Created attachment 163556 [details]
Example file ODT for export to DOCX
Created attachment 163558 [details]
DOCX Example
1. open the file attached file (DOCX)
2. CTRL+A
3. CTRL+C
4. CTRL+N
5. CTRL+SHIFT+V RTF
Hmm, can't confirm *any* difference is quality between /a admin installs of arecent 7.1.0alpha0+ and a 6.2.5.2 release build. Version: 6.2.5.2 (x64) Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Rendering of the document canvas match, and Export to PDF produce comparable results. We'll need better STR... (In reply to V Stuart Foote from comment #4) > Hmm, can't confirm *any* difference is quality between /a admin installs of > arecent 7.1.0alpha0+ and a 6.2.5.2 release build. > > Version: 6.2.5.2 (x64) > Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 > CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; > Locale: en-US (en_US); UI-Language: en-US > Calc: threaded > > Rendering of the document canvas match, and Export to PDF produce comparable > results. > > We'll need better STR... My bad, used 6.2 bibisect branch somewhere in the middle: Try 6.1 Created attachment 163581 [details]
PDFs of sample ODT opened and exported 6.1.6, 6.2.5, 7.1.0
Still can't confirm. Opening/rendering of ODT at 6.1.6.3 matches that at 7.1.0.0
Attachment is zip of PDF export from each--matching display in LO GUI
Created attachment 163584 [details]
PDF exported with 6.1 master
No problem here, please re-test Version: 7.2.0.0.alpha0+ (x64) Build ID: 796c7f612603490dda9277ced0f6ab3cce3bc116 CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded (In reply to Telesto from comment #7) > Created attachment 163584 [details] > PDF exported with 6.1 master Typo: should be 7.1 Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp |