Download it now!
Bug 107595 - wrong RTF export of text frame positioned relative to page
Summary: wrong RTF export of text frame positioned relative to page
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
4.4 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:rtf
Depends on:
Blocks: RTF
  Show dependency treegraph
Reported: 2017-05-03 12:57 UTC by Christian Nieber
Modified: 2018-06-18 02:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

example with text object (13.29 KB, application/vnd.oasis.opendocument.text)
2017-05-03 12:57 UTC, Christian Nieber

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Nieber 2017-05-03 12:57:18 UTC
Created attachment 133029 [details]
example with text object

The text box in the example is positioned relative to the page and anchored in a paragraph. When exported to RTF, it is written with shape properties posrelh=3 and posrelv not specified, i.e. the offsets are instead interpreted relative to paragraph and the box is positioned too far down and right.
It would come out correct if it exported posrelh=1 and posrelv=1.
Other types of relative positions are probably also wrong in RTF.
Comment 1 Xisco Faulí 2017-05-03 15:08:00 UTC
Confirmed in

Build ID: 597a2f5d5bd37443262b0775b8439bc3502aef1b
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; 
Locale: es-ES (ca_ES.UTF-8); Calc: group

The import part of the textbox was implemented in 9835a5823e0f559aabbc0e15ea126c82229c4bc7
Comment 2 QA Administrators 2018-06-18 02:42:25 UTC
** Please read this message in its entirety before responding **

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

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

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:

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

Warm Regards,
QA Team