When opening the docx file in latest LO the text is not aligned the same as in word.
Steps to Reproduce:
1.Open file in word, see how it looks normal.
2.Open file in latest LO, see how text is not aligned.
Text is not aligned as it is in word.
Text should be aligned as it is in word.
User Profile Reset: No
Created attachment 163940 [details]
File having issues
Created attachment 163958 [details]
Comparison MSO 2010 and LibreOffice 7.1 master
Build ID: 58937aa4a50ecd681382f03331340da4c843b01e
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default;
Locale: ca-ES (ca_ES.UTF-8)
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Version 184.108.40.206.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
This was wrongly reported and confirmed.
Classic mistake is to report "see file in MSO".
Xisco usually asks if this happens also with font installed, but I guess with so many unneeded reports, it can slip.
This is a problem with LO replacement of font Mishawaka Bold.
Comparison is too small so not seen that.
We have a separate bug for LO replacement of well-known fonts.
I think that Mishawaka Bold is not one of them.
Meaning that solution is to choose personal replacement in LO table.
I close with assumption that Mishawaka Bold is not installed.
If it is, that's another issue - but which is may already be reported, not for this specific font but for a problem, so search.
<w:font w:name="Mishawaka Bold">
<w:altName w:val="Times New Roman"/>
<w:sig w:usb0=" .......>
http://www.officeopenxml.com/WPfonts.php says that "the application look for the closest match to the referenced font, using the following pieces of information, in descending priority...:
I think that MSO uses this and shows Times New Roman when Mishawaka Bold is not available. It doesn't seem embedded.
Dear Rhys Young,
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!