Created attachment 180251 [details] DOCX file where the problem occurs Open the attached DOCX file. It's a template for an academic conference. In MS Word it opens OK but when I open it in LO Writer the text is imported as subscripted for no apparent reason. This import issue happens both in 7.3 and 7.4 from master. System info: Version: 7.3.3.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Ubuntu package version: 1:7.3.3~rc2-0ubuntu0.21.10.1~lo1 Calc: threaded And also in: Version: 7.4.0.0.alpha1+ / LibreOffice Community Build ID: ad6905f9a09c63712ba0aaffc700923246d21e55 CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL
Created attachment 180252 [details] Screenshot of the file opened in Word
Created attachment 180253 [details] Screenshot of the file opened in Writer
Reason is the font setting "lowered by 0.5pt" in Word. Inside Word modify the Paragraph style "Normal". In that dialog open the "Format" list (bottom left of the dialog) and chose item "Font". In that dialog go to tab "Advanced". In section "Character Spacing" the field "Position" should be "Normal", but is "Lowered" b 0.5pt. That results in the markup <w:position w:val="-1"/> in styles.xml in the docx document. This element is defined in 17.3.2.24 position (Vertically Raised or Lowered Text) in the standard. Apparently LibreOffice is now interpreting this setting somehow, LO 5.4 shows the text normally. But the values in LibreOffice are wrong. It would need 'lower by 4%' and 'Relative font size 100%'. What was the author thinking, making such a setting in Word?
Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 465c3ad95059f0efa13c8027f7383c4d20a5b2ff CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded The Result is : it is viewable in libreoffice writer ,but language is change into portuguese(Brazil).
*** This bug has been marked as a duplicate of bug 126314 ***