Steps to reproduce:
1. .rtf format
Platform (if different from the browser):
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Created attachment 59105 [details]
Please actually describe the bug.
Can't open clear .RTF format in 4.5.1. writer as it was made in earlear
ver. Everything is unformated.
For example in v. 3.3.4 everything allright...
27.03.2012 10:23, firstname.lastname@example.org написал:
> Urmas<email@example.com> changed:
> What |Removed |Added
> Status|UNCONFIRMED |RESOLVED
> Resolution| |INVALID
> --- Comment #1 from Urmas<firstname.lastname@example.org> 2012-03-26 23:23:25 PDT ---
> Please actually describe the bug.
DO NOT REPLY TO BUGZILLA NOTIFICATIONS.
RTF file you attached is corrupted.
But underlying problem should be fixed now.
There are still problems opening the attached sample file with LibreOffice 184.108.40.206. Some of them, esp. the mixed character encoding, seem to be caused by corruption of the RTF file (see comment #3); others, like the page layout, seem to be caused by LibreOffice 220.127.116.11 itself. But for these RTF page layout problems, there are some very similar bug reports with better documentation and *valid* RTF sample files, especially Bug 48442 - "Incorrect displaying attached rtf document", which has a very similar RTF sample file.
Therefore I propose to close this (present) bug report again as RESOLVED/DUPLICATE (or RESOLVED/INVALID, see comment #3); fixing bug 48442 will most probably also fix the remaining page layout issues reported here.
@Sergey, Urmas, Miklós:
What do you think? Should we close this bug report in favour of bug 48442?
Created attachment 60795 [details]
How the sample file looks within LO 18.104.22.168 on MacOS X
Improved the summary to make it easier to find this bug when searching for duplicates. I hope my proposal is OK; feel free to change if necessary.
Hint: Also similar to bug 49403. (It's hard to say if any of these bugs is a
real duplicate; this would need good understanding of the RTF format, and is
beyond my horizon. We will know if one of them is fixed: if bug B goes away
after fixing bug A, it was a duplicate ...)
There were many frame-related RTF import fixes during the last year, so I'm not picking a random one of them to mark this bug as a duplicate.
But in general, the provided RTF file is not valid, so as long as we don't crash on it, we're fine. Closing as "not a bug". (I also assume -- based on comment 3 -- that there was an original bugdoc as well, which is indeed fixed now.)
Migrating Whiteboard tags to Keywords: (rtf_filter -> filter:rtf)