Apache OpenOffice (AOO) Bugzilla – Issue 26964
RTF: Vertical Cell merging in tables not imported correctly
Last modified: 2017-05-20 11:22:09 UTC
mmaher: RTF Tables in which cells in the same column have been merged are not imported correctly.
Created attachment 14062 [details] RTF Table created in OO with column cells merged
MM: setting target
ama -> flr: Please have a look.
The RTF control for vertical merge \clvmgf and \clvmrg are currently not supported. E.g. the RTF document {\rtf1 \trowd \clvmgf\cellx1000 \cellx2000 \pard\intbl A\cell \pard\intbl B\cell \row \trowd \clvmrg\cellx1000 \cellx2000 \pard\intbl C\cell \pard\intbl \cell \row } should result in a table +---+---+ | A | B | + +---+ | | D | +---+---+ When implementing this feature beware of the cell borders. E.g. MS-Word takes the bottom border from the last cell merged. E.g. {\rtf1 \trowd \clvmgf\cellx1000 \cellx2000 \pard\intbl A\cell \pard\intbl B\cell \row \trowd \clvmrg\clbrdrb\brdrdb\cellx1000 \cellx2000 \pard\intbl C\cell \pard\intbl D\cell \row } results in the table ("===" indicates the drawn border) +---+---+ | A | B | + +---+ | | D | =====---+
*** Issue 60582 has been marked as a duplicate of this issue. ***
reassigning to hbrinkm
*** Issue 75898 has been marked as a duplicate of this issue. ***
Will the problem be decided?
And what about the decision? It's very important issue.
*** Issue 100736 has been marked as a duplicate of this issue. ***
I've verified that defect still exists in v3.1.0. RTF with vertical merged cells is written correctly, but merge attribute is lost in import. Issue 87169 is a duplicate of this issue.
*** Issue 103505 has been marked as a duplicate of this issue. ***
This issue is still present in OOo-Dev_DEV300_m53_Win32Intel version.
*** Issue 96873 has been marked as a duplicate of this issue. ***
*** Issue 87169 has been marked as a duplicate of this issue. ***
*** Issue 104139 has been marked as a duplicate of this issue. ***
*** Issue 104687 has been marked as a duplicate of this issue. ***
*** Issue 105370 has been marked as a duplicate of this issue. ***
I have just verified the problem is in 3.2.1 as well.
Reset assigne to the default "issues@openoffice.apache.org".