When exporting to a Microsoft Word document, there is an extra format character inserted at the beginning of a heading. Depending on how you view the document, it is a heading or a number.
Steps to Reproduce:
1. Open Libreoffice Writer and write some text. Press Control+1 to make it a heading level 1.
2. Save two coppies of the document, one as DOCX and the other as ODT.
3. If you open both documents in LibreOffice Writer and select preview in web browser, there is a 1. at the beginning of each heading you insert which shouldn't be there in the word dOCX. This is not visible when previewing the ODT.
4. If you open the docx in word, there is a bullet that is interpreted before the line. You cannot see this visually. I noticed it because I use a screen reader. Even though the bullet is invisible, the screen reader reads the bullet semantics from the document for some reason. You can notice it visually by moving the cursor to the left of the first physical character in the line. This only works in Microsoft Word.
These bits of evidence make me think that some extraneous formatting is being exported when saving as docx.
NO bullet or number when exporting.
User Profile Reset: Yes
Build ID: 1:6.4.4-1
CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
For 3 in the steps to reproduce. You need to close the word DOCX and reopen it before previewing it in the web browser to notice this bug. Also, I used Firefox on Linux as well as LibreOffice on Linux. Word was used on Windows 10 and was major version 2016 and minor release 2003.
In my bug description, I said "Depending on how you view the document, it is a heading or a number". I meant to say "Depending on how you view the document, it is a bullet or a number".
I confirm it with
Version: 126.96.36.199.beta1 (x64)
Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
I think it's related to bug 107683 or perhaps a duplicate of it.
(In reply to Dieter from comment #3)
> I think it's related to bug 107683 or perhaps a duplicate of it.
I'm fairly sure this is a duplicate of that one.
*** This bug has been marked as a duplicate of bug 107683 ***