https://bugs.documentfoundation.org/show_bug.cgi?id=163906

            Bug ID: 163906
           Summary: DOCX DOC: Special Footnote signs multiply each time
                    file is opened after saving
           Product: LibreOffice
           Version: 24.8.3.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

When opening a .doc or .docx file created in LO which contains a special
footnote after it was saved, the chosen special footnote sign at the bottom of
the page is typed a second time next to the original one. If the file is opened
and saved multiple times, more and more signs will be added to the original
one.
If the file contains multiple special footnotes, sometimes extra signs will be
added the the footnote sign in the main text as well.

To reproduce:
1. Create a doc or docx file. Type some text.
2. Insert -> Footnotes and Endnotes -> Inset Special Footnote/Endnote.
3. Choose "Character", and type an asterix (*) as the chosen character at the
adjacent field. Press Confirm.
4. Type some text as the footnote.
5. Save the file, close it and re-open it.

Expected results:
- The footnote at the bottom of the page should be marked with one asterix.

Actual results:
- The footnote at the bottom of the page is marked with two asterixes. If the
file will be changed, saved, closed and opened again, the footnote will contain
three asterixes, and so on.
Extra signs can be deleted manually from the footnote, but they come back after
saving and re-openning,

For extra bugginess:
1. Add a second special footnote to the file at the same manner, this time
marked with two asterixes (**) as the chosen character. Upon re-opening, note
that some new assterixes were added not only to the footnotes at the bottom of
the page, but also to one of the footnote signs at the main text.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to