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

László Németh <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #39 from László Németh <[email protected]> ---
The new Styles field with character styles gives an interoperable way for
shortening the titles in header/footer, including ellipsis and arbitrary text,
see the documentation in the attached tdf32363.docx. (The only difference, that
MSO cannot handle ellipsis/arbitrary text with this method:
https://learn.microsoft.com/en-us/answers/questions/5228103/can-i-shorten-styleref-text-and-add-ellipsis-in-th
– but it can preserve the information for Writer – one of the proposed MSO
workaround is to use white 1 pt text...)

About the ToC: this is clearly a separated problem, by the way in LaTeX, too,
where  \chaptermark/\sectionmark are for the header/footer-only shortening, and
the extra argument of \chapter/\section for both ToC and header/footer:

https://texfaq.org/FAQ-runheadtoobig

For shortening titles for the ToC in Writer, it can be a better solution to use
inline frames with the new style separator interoperability features, than
editing the ToC manually or adding an extra heading with white, 1 pt characters
after the long heading, and removing the long heading from the ToC by direct
paragraph formatting.

To use the style separator interoperability approach easily, create new "Long"
chapter styles based on the existing Heading 1, Heading 2 etc. with disabled
outline level, and use that for the long headings. To set the short headings,
select the first part of the long title, and choose Heading 1 (e.g. by pressing
Ctrl-1). The selected text moved to an inline frame with the requested heading
style immediately, and updating the ToC, it will contain the short titles only.
Example document is attached.

The listed solutions are ISO OOXML/ODF/loext: ODF compliant solutions, can be
base of some more high-level solutions (Writer UI extension, add-on, full style
separator interoperability), so I think, it's possible to close this issue.
Please, file a new issue for the other possible future solutions.

Note: I have examined several other solutions, for example conditional
paragraphs in Writer (they don't work in header/footer correctly), SET
variables (it works in Writer, but not so comfortable and not interoperable
yet), STYLEREF with \* MERGEFORMAT/CHARFORMAT to show the hidden text in MSO
header/footer (it doesn't work in MSO).

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

Reply via email to