Bug 137127 - FILEOPEN RTF: Control word \up14 in blank table cell leaks into adjacent cell
Summary: FILEOPEN RTF: Control word \up14 in blank table cell leaks into adjacent cell
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Keywords: filter:rtf
Depends on:
Blocks: RTF-Tables
  Show dependency treegraph
Reported: 2020-09-29 13:54 UTC by MikeM
Modified: 2024-04-14 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Two RTF documents demonstrating the issue and a workaround (25.13 KB, application/x-zip-compressed)
2020-09-29 13:54 UTC, MikeM

Note You need to log in before you can comment on or make changes to this bug.
Description MikeM 2020-09-29 13:54:26 UTC
Created attachment 165947 [details]
Two RTF documents demonstrating the issue and a workaround

As I understand it, the \upN control word should only apply within its own bracket-delimited group, but it seems that LibreOffice allows it to leak into the next group under some conditions.  The effect persists until the next group ends.

I have attached a pruned document (Broken.rtf) from a customer that demonstrates the bug, and my modified document (Fixed.rtf) where I simply deleted the \up14 word.  The problem is visible around the "Standardpreis AZV" text.  If you click on it, LibreOffice identifies it as a Superscript.  I think this pushes the rest of the text down, so it no longer fits in the cell.

The group causing the problem looks like this:
{\rtlch\fcs1 \af0\afs20 \ltrch\fcs0 \fs20\up14\lang1031\langfe1033\loch\af0\hich\af0\dbch\af31505\langnp1031\insrsid3419495 \cell }

The problem has been seen on Windows 8.1, Windows Server 2008 R2, and Windows Server 2012 R2.  I have reproduced it with three LibreOffice versions,, and
Comment 1 Dieter 2021-04-16 16:25:15 UTC
Mike, unfortunately nobody could confirm this bug report during the last months. So I'd like to ask, if it is still valid. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 MikeM 2021-04-30 16:46:17 UTC
Dieter, thank you for responding.  The issue is still present in LibreOffice version  Please observe the difference in the way Broken.rtf and Fixed.rtf are displayed, around the "Standardpreis AZV" text.  For now I cannot test version because the Writer application crashes on my Windows Server 2008 R2 machine.
Comment 3 Buovjaga 2022-04-14 13:40:38 UTC

I bisected the change in behaviour with Linux bibisect-43all to range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=934e051b16349a1ab6d2bdd9f03e60aaafcb2ec8..75df7739309ccc5342084e668d9d869620cb3233

I'm not sure the change is a regression as such, so I won't add the keywords.

Arch Linux 64-bit
Version: / LibreOffice Community
Build ID: 9a42c99d7b3e8a8429f14d7d851f3d186fa04594
CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded Jumbo
Built on 14 April 2022
Comment 4 QA Administrators 2024-04-14 03:15:48 UTC
Dear MikeM,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team