Summary: | FILEOPEN DOCX Paragraph direct formatting settings not prioritized over style settings in VML shape | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | NISZ LibreOffice Team <libreoffice> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | jluth, nemeth, xiscofauli |
Priority: | medium | Keywords: | bibisected, bisected, filter:docx, regression |
Version: | 7.0.0.3 release | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=128153 https://bugs.documentfoundation.org/show_bug.cgi?id=129700 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 108230, 136406 | ||
Attachments: | Screenshot of the original document side by side in Word and Writer |
Description
NISZ LibreOffice Team
2020-09-02 20:23:37 UTC
(In reply to NISZ LibreOffice Team from comment #0) > Before the font name was correct, but the rest of the settings wasn’t. Calibri is the system default - so that is an easy one to get right by accident. When unzipping the document, there are only two references to Calibri - in fonttable and theme1. I don't see it as a direct formatting attribute at all. So is it coming from <w:rFonts w:asciiTheme="minorHAnsi" w:hAnsiTheme="minorHAnsi" w:cstheme="minorHAnsi"/> ? I don't think LO has any support for themes, except for GRAB_BAG round-tripping. Even doing anything in MS Word like selecting a style changes it to Gothic. So I am going to say this exposed an existing problem or implementation lack. Reproduced in Version: 7.2.0.0.alpha0+ Build ID: 84af20ef3ea72190784e9e7be820684c2558ba8c CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Font is calibre in this version, the rest is still wrong Dear NISZ LibreOffice Team, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug repro 7.6 - still not fixed even though lots of theme work has landed. |