Summary: | FILESAVE: DOC save breaks correct Normal style font and font size in Word for Mac 2011 & 2016 ver 15 | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | mitja <mitja.masten> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | cpae, iplaw67, paul.jowett, philipz85 |
Priority: | medium | Keywords: | filter:doc |
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | BSA | ||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 112753 | ||
Attachments: | DOC (identic) documents created with: LibreOffice 4.0.5, Word for Windows 2003and Pages 5.0.1. DOC document created with Libre shows incorrect font when opened in Word for Mac 2011, others not. |
Description
mitja
2014-06-23 16:11:32 UTC
This is likely a Mac only issue, so i'm passing it on to our Mac team. Hi all, thanks for the report. I can confirm your finding. Open LO 4.3RC1 write some text in default style (have default style set to another font that Times New Roman). Save as .doc file. Open with Word 2011 on OSX -> Text appears in Times New Roman. Confirmed for a new doc and for the docs provided by user. I'm not an expert about font usage, so maybe if Word's default font is indeed Times New Roman this could be expected behavior? Not sure. Will need some dev input on this. Setting to NEW, since confirmed. Platform OSX. I must highlight that currently this issue affects Mac users using Word for Mac 2011 only, but such issue can affect also future versions of Word for Windows if Microsoft makes some changes in loading DOC format as they made in Word for Mac. I have to mention that this issue appeared in Word for Mac update 14.3.6 (approx. november 2013). There was no problem regarding font issue in Word for Mac ver. 14.3.5 or below. I also think this is not Mac only issue. Yes, it currently affects Word for Mac users only, but DOC documents that affects those users are created in any platform (Win, Mac or Linux) using word processor that derives from Open Office. Any DOC document created with older versions of OpenOffice affects those Word for Mac users. I tested e.g. older OpenOffice 3.1.1 for Windows and the same issue appears, so it could probably be some old "bug" or minor inconsistency in OpenOffice DOC export engine. Mitja, thanks for this additional information. Should be most helpful once the right person with needed insight is on this. Hi. Is there something new going on regarding this issue? I think interoperability issues are important for unproblematic and smooth coexistence. Or else majority of users "justifiably" says that OOo / LO is not good as it spoils the document (when opening MS doc of course). The problem regarding DOC documents and Default Paragraph Style (Normal Style in Word), saved in OOo or LO, still persists when saving DOC files in Libre Office 5. Even more, when opening such file does not affect only Word for Mac 2011 version 14.3.6+, but even newer Word for Mac 2016. Can anyone please take a look at this issue when saving DOC files with OO/LO? Apparently there is something going on with Word for Mac DOC "importer" from version 14.3.6 and on. But that affects only DOC files created with OO/LO and Microsoft is probably not interested to solve this issue as I reported this problem to them also. Can anyone please take a look at this issue. It is interoperability issue and far from negligible! ** 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! Warm Regards, QA Team MassPing-UntouchedBug Tested with LO 6.2.0. And the issue is still there, when oppening with Word for Mac 2016 ver 15.22. This is quite an important basic compatibility issue to me, that has wide impact on interoperability and should have been resolved years ago. But now as soon as possible. Namely, every file, saved either with Open Office or LO 6.2 is stored somewhere. And eventhough the issue is resolved in eg. LO 6.3, all files stored to .DOC with earlier LO/OOo versions are “infected” already. I suggest informing Microsoft that their Mac version cannot read documents that work in the Word version. Better to fix the problem at the source. (In reply to Justin L from comment #10) > I suggest informing Microsoft that their Mac version cannot read documents > that work in the Word version. Better to fix the problem at the source. MS was already informed years ago. I wonder if they read their forum or care about this. However, there is something with LO also, which writes .DOC file in some different way than expected! This part can't be fixed by MS. I tried other Office solutions too (Pages, ...) and no one produced a file with such effect, except OOo/LO. Dear mitja, 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 Dear mitja, 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 |