Apache OpenOffice (AOO) Bugzilla – Issue 21263
winword characters before footnote anchor
Last modified: 2013-08-07 14:38:26 UTC
WinWord characters inserted before footnote anchor appare after when document is imported in OOo. For Example in WinWord I have this footnote sample (1) Some FootNote text where "(" is manualy inserted before the automatic note number "1" and ") Some FootNote text" may be interpreted as a footnote text, at large. OOo render it so: 1 () Some FootNote text and there is no way to insert something before the automatic note number.
Created attachment 10342 [details] RTF sample
reassigned to mru
MRU->AMA: perhaps something for successor of 2.0... In WW you have the possibility to enter a character manually in front of the number in the footnote text (and that for every footnote individually).
Yes, I see. You may input not only one character, you may insert several lines before the footnote number and you're able to copy or delete it!? Our concept is like a paragraph numbering, Word's concept is like a field which is initially at the first position of the footnote. So we need a similiar field type in OpenOffice Later.
Compare with issue 90838. We should also think about an "after" text in order to generate () []... around the anchor.
Sorry! compare with issue 90842!
*** Issue 90842 has been marked as a duplicate of this issue. ***
As rgb said on issue 90842, the problem is different. The summary of this issue is misleading. It should be changed from «winword characters before footnote anchor» to something like «Footnote mark prefix is inserted after the mark when importing WinWord documents». The problem as described in the original description, and in attachment 10342 [details], concerns the footnote mark, in the footnote area. This is a purely import problem, as OOo permits to define characters, before and after the footnote mark (well, maybe it didn't, back in 2003). issue 90842 really concerns the footnote anchor, in the text area. OOo does not yet permit to define characters, before and after it, which is the subject of the issue. I'm reopening issue 90842.