Bug 52303 - Problem with linespacing in RTF document
Summary: Problem with linespacing in RTF document
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Blocks: RTF-Paragraph
  Show dependency treegraph
Reported: 2012-07-20 10:54 UTC by ccc1ced
Modified: 2017-10-22 21:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

a rtf document create with libreoffice (3.47 KB, application/msword)
2012-07-20 10:54 UTC, ccc1ced

Note You need to log in before you can comment on or make changes to this bug.
Description ccc1ced 2012-07-20 10:54:08 UTC
Created attachment 64425 [details]
a rtf document create with libreoffice

Problem description: I save with libreoffice a writer document with fixed linespacing 0,28cm in a Rich Text Format, when I reopened it, the linespacing is single.
with openoffice it works fine.

Steps to reproduce:
1. write some line of text in a writer document, format with fixed linespacing 0,28cm and save with libreoffice in a Rich Text Format document
2. reopen it with libreoffice

Current behavior: text is formatted with single linspacing

Expected behavior: text should be formatted with fixed linespecing 0,28 cm as openoffice do.

Platform (if different from the browser): windows xp, windows7
Browser: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Comment 1 Urmas 2012-07-21 10:09:26 UTC
Try 3.5.5.
Comment 2 Roman Eisele 2012-07-21 16:29:14 UTC
This is a Writer issue, therefore changed 'Component' accordingly.
Comment 3 Roman Eisele 2012-07-23 15:22:36 UTC
Thank you very much for testing again!

Original reporter (ccc1ced@yahoo.ie) changed status to RESOLVED/FIXED, probably after testing with LibreOffice 3.5.5, as Urmas suggested in comment #1.

I can confirm that the linespacing is correct (fixed linespacing 0.28cm) when I open the sample file with LibreOffice

Therefore I set the status to VERIFIED/WORKSFOME (not /FIXED, because there is no special fix for this issue; therefore we prefert /WORKSFORME in this case).