Bug 47081 - FILEOPEN: Linespacing not imported correctly from RTF files
Summary: FILEOPEN: Linespacing not imported correctly from RTF files
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: filter:rtf, regression
Depends on:
Blocks:
 
Reported: 2012-03-07 21:09 UTC by Jim Appleby
Modified: 2015-12-17 12:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test kit (28.57 KB, application/x-zip-compressed)
2012-03-08 22:32 UTC, Rainer Bielefeld Retired
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Appleby 2012-03-07 21:09:43 UTC
Problem description: Linespacing not saving.

Steps to reproduce:  No idea.  Does not affect all documents, even on this machine.

Current behavior:  Line spacing in documents set in LibreOffice rtf files is not saved.  On opening a LibreOffice created rtf, line spacing reverts from "Single" (expected) to "Fixed .18cm" (unexpected) creating overlapping text.

Expected behavior:  Line spacing choice is saved

Platform (if different from the browser): MacBook Pro, Mac OS X.7.3
Comment 1 Rainer Bielefeld Retired 2012-03-07 22:02:03 UTC
@reporter:
Thank you for your report – unfortunately important information is missing.
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that  is really sophisticated please as for Help on a user mailing list
Please:
- Write a meaningful Summary describing exactly what the problem is
- Attach sample documents (source, saved result)
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem (due to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- what EXACTLY is unexpected
  -- how can you know that it's a FILESAVE and not a FILEOPEN problem?
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC (video card, ...)
  -- concerning your OS (Language)
  -- concerning your LibO localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
  -- how you launch LibO and how you opened the sample document
  -- everything else crossing your mind after you read linked texts

Even  if you can not provide all demanded information, every little new information might bring the breakthrough.
Comment 2 Jim Appleby 2012-03-08 19:57:31 UTC
This is the first bug I've filed... sorry I have done such a poor job.
Here is new information:

It affects LibreOffice in Ubuntu as well.

It can be replicated in reverse by:

1. Creating a new Writer file.
2. Typing some lines of text.
3. Selecting all of the text.
4. Go to Format > Paragraph > Indents & Spacing
5. Set Line Spacing to "Fixed" and .07" (.18cm)
6. Ok
7. Save file as rtf
8. Open file

The newly open file will NOT have spacing set to fixed, but to single.

I hope this helps.
Thanks!
Comment 3 Jim Appleby 2012-03-08 20:19:11 UTC
Obviously, the file needs to be closed after step 7 - forgot to add that.
Comment 4 Rainer Bielefeld Retired 2012-03-08 22:32:32 UTC
Created attachment 58217 [details]
Test kit

Modified OS due to reporter's comment

I am pretty sure that it's a FILEOPEN problem.

I created a "sample1.odt", saved from LibO 3.5.1RC2 as "sample1_351.rtf" and from LibO 3.3.0 as sample1_330.rtf.

Both .rtf show Line Spacing 'Fixed' when I reopen with LibO 3.3.0 and and 'Single Line' when I open with LibO 3.5.1 RC2

@Jim Appleby
Can you confirm my results with attached test kit?
Comment 5 Jim Appleby 2012-03-09 07:31:41 UTC
Both test kit rtf files open with single spacing in 3.5.0
Comment 6 Jim Appleby 2012-03-12 18:16:26 UTC
@Rainer Bielefeld - not sure if I should download other versions of office so that I can confirm those results too?  What would be helpful in dealing with this bug?
Comment 7 Roman Eisele 2012-08-23 14:43:08 UTC
Good news (?): I think this bug has been fixed in between -- at least if I understand the bug report correctly (I am not completely sure, comment #2 differs from comment #1).


If I the files from Rainer’s test kit ("sample1.odt", "sample1_330.rtf" and "sample1_351.rtf") with LibreOffice 3.5.6.2 or LibreOffice 3.6.1.1, both on MacOS X 10.6.8 (Intel), all three files show Line Spacing: fixed (0.50cm) for all paragraphs.

Furthermore, if I save "sample1.odt" as RTF file from LibreOffice 3.5.6.2 and open that RTF file again, the line spacing is still fixed / 0.50cm, as expected.

Finally, in comment #2 Jim Appleby used a very special fixed line spacing setting (0.18cm). This works now, too: If I copy Rainer's "sample1.odt", open the new file, set the line spacing of any paragraph to fixed / 0.18cm, and then save the file as RTF file, close it, and open the RTF file again, the paragraph has still the special line spacing fixed / 0.18cm. So even unusual (overlapping) line spacing settings are now correctly saved and read again from/to RTF files.


@Jim Appleby:
Did I understand the problem correctly? And more important: Can you confirm that this bug is fixed now? Just download LibreOffice 3.5.6 (or 3.6.0) and try yourself ...
Thank you very much!


@Rainer Bielefeld:
What do you think: Given the fact that your RTF sample file "sample1_351.rtf" created by LibreOffice 3.5.1 now opens correctly with line spacing fixed / 0.5cm in LibreOffice 3.5.6, I would say this was rather a FILEOPEN problem than a FILESAVE problem. Do you agree?

Then we should change the summary (e.g., to "FILEOPEN: Linespacing not imported correctly from RTF files" or similar) and close this bug as RESOLVED/WORKSFORME.
Thank you!
Comment 8 Roman Eisele 2012-09-07 14:12:48 UTC
Closing this report as RESOLVED/WORKSFORME, because
a) of the results mentioned in comment #7 -- the bug seems fixed
   both in LibO 3.5.6 and 3.6.0;
b) because of the similar/duplicate bug 52303,
   which is already VERIFIED/WORKSFORME.

(In reply to comment #4)
> I am pretty sure that it's a FILEOPEN problem.
Changing the Summary according to Rainer’s comment and my own results.

Feel free to reopen this bug report if you can still reproduce this issue in LibreOffice >= 3.5.6. Thank you!
Comment 9 Robinson Tryon (qubit) 2015-12-17 12:04:35 UTC
Migrating Whiteboard tags to Keywords: (filter:rtf)
Replace rtf_filter -> filter:rtf.
[NinjaEdit]