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

Tracy Logan <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #21 from Tracy Logan <[email protected]> ---
While I am not the original author, I confirm that this bug still exists in the
current version of LO:

Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Mac OS X 12.6.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

This bug also exists in v7.4.0.3 (on Mac OS X 12.6.1) and v7.0.4.2 (on Ubuntu
20.04).

LO 3.3 will not run (an update to it is required for this OS), so I cannot
confirm the earlier assertion (in #6) that this bug is a regression -- however,
FWIW, a similar bug existed in Open Office
(https://bz.apache.org/ooo/show_bug.cgi?id=55088); the description of that Open
Office bug report is:


"The tag for table row header (\trhdr) is being ignored.
The row which is marked with the \trhdr tag should appear at the top of every
page on which the table containing the row appears.
It works in oo 1.1.5 and 1.1.4, but not in 2.0."

This is the exact behavior I'm seeing in LO, which occurs both in the GUI, and
when called with --headless to convert RTF to PDF.

Additional observations (using 7.4.3.2/Mac):

When opening an RTF document with a multi-page table that contains the \trhdr
tag, that tag is indeed ignored; Table Properties... shows the Repeat Heading
checkbox is unchecked.  Checking that box does prefix the specified header row
to each page of the table.  Saving that file in ODT format does preserve that
setting, but saving in RTF does not (no \trhdr tag is present), and emits the
warning that the document may not save correctly.  Exporting as PDF with that
box checked likewise results in the prefixed header on every page.

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

Reply via email to