Apache OpenOffice (AOO) Bugzilla – Issue 3790
RTF: Import Word 97-2000 RTF for Drawing Objects (Shapes)
Last modified: 2017-05-20 10:45:34 UTC
When I import the document above, the format is substantially different than the original. The first paragraph should be aligned with the first box. It takes more than one page when it should take only one.
Created attachment 1300 [details] Original word document .
Created attachment 1301 [details] Screenshot of the document under Microsoft Word
Another issue: the form elements of Word are not translated to form elments of Openoffice.org. Instead, user-defined fields appear in the document.
Reassigned to Michael.
The attached document is nor Word-format, it is RTF. So there textboxes from MS drawing tools in the document, they are fully ignored on import, because import of drawings from RTF is not implemented at all (and will not be in the future; too high effort). MRU->CMC: After import, the graphic in the header misses completely. Is this fixible in the RTF filter?
Hmm! Seem to have quite serious issues importing any graphics generated in word at all.
Yes, we simply don't have implement importing this type of graphic in our rtf handling.
Unfortunately this isn't going to get implemented in a hurry.
*** Issue 4130 has been marked as a duplicate of this issue. ***
*** Issue 6935 has been marked as a duplicate of this issue. ***
*** Issue 6865 has been marked as a duplicate of this issue. ***
*** Issue 9037 has been marked as a duplicate of this issue. ***
Any progress on this subject? Would it be possible to reconsider the implementation now?
Issue 10379, Issue 11610, and Issue 12414 are all duplicates of this bug. I have a company where our DTP department is standardized on RTF, and embedded images are almost a requirement (We can't lose the image after saving like OOo 1.0.3 does now). Once this is implemented, I can switch us over to OOo. I can't contribute code right now, sorry. What can I do to help get this fixed?
*** Issue 11610 has been marked as a duplicate of this issue. ***
Sadly the only thing that can affect this is an implementation for such graphic element import. Hopefully we can get something for OOo 2.0 in this area.
*** Issue 12485 has been marked as a duplicate of this issue. ***
*** Issue 12414 has been marked as a duplicate of this issue. ***
*** Issue 8487 has been marked as a duplicate of this issue. ***
*** Issue 14627 has been marked as a duplicate of this issue. ***
*** Issue 21711 has been marked as a duplicate of this issue. ***
*** Issue 21748 has been marked as a duplicate of this issue. ***
reopen to reassign
cmc->mmaher: Longstanding requirement to property implement drawing support for rtf. As you know the subset of this for proper import and export of (at least) inline graphics is implemented (thats for you hub), which will please at lot of people, but the drawings are still not implemented
Created attachment 15634 [details] rtf that cannot be opened with writer. It is a simple form with lines and fields.
I added a form that I believe matches this issue. It cannot be opened in my current version of OOo. ver 1.1.1
*** Issue 30814 has been marked as a duplicate of this issue. ***
Because of a shortage of resources we have to retarget this issue to OOo later.
according to http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7690 this issue will be set to OOoLater
*** Issue 37030 has been marked as a duplicate of this issue. ***
Yes everything here looks very similar to the effects reported in issue 37030. Even the funny looing screenshot is similar for content of "dss_face_sheet.rtf" copied into a writer document. OS --> NEW, bedause issue 37030 was a WIN-issue. By the way, I checked with 2.0 (1.9.m56) English version WIN XP: [680m56(Build8814)] and had to learn that that version crashes if I try to copy (<cntrl-c> <cntrl-c> ) the content of "dss_face_sheet.rtf" from WORD2000 to OOo Rainer
ama -> flr: Please have a look.
*** Issue 39539 has been marked as a duplicate of this issue. ***
*** Issue 39949 has been marked as a duplicate of this issue. ***
*** Issue 42776 has been marked as a duplicate of this issue. ***
*** Issue 49471 has been marked as a duplicate of this issue. ***
*** Issue 41238 has been marked as a duplicate of this issue. ***
*** Issue 51607 has been marked as a duplicate of this issue. ***
*** Issue 55476 has been marked as a duplicate of this issue. ***
*** Issue 55241 has been marked as a duplicate of this issue. ***
*** Issue 56011 has been marked as a duplicate of this issue. ***
*** Issue 62452 has been marked as a duplicate of this issue. ***
*** Issue 63023 has been marked as a duplicate of this issue. ***
*** Issue 63242 has been marked as a duplicate of this issue. ***
*** Issue 63302 has been marked as a duplicate of this issue. ***
*** Issue 63352 has been marked as a duplicate of this issue. ***
*** Issue 64666 has been marked as a duplicate of this issue. ***
I think it is a pitty that shapes in RTF documents won't be realized. It is a reason that we switched back to MS Word in one department of our company. A special program is using RTF output with a company letter form which contains shapes (Logo). So the output is not formatted in a proper way.
*** Issue 66081 has been marked as a duplicate of this issue. ***
*** Issue 68061 has been marked as a duplicate of this issue. ***
Workaround: open in WordViewer, select all, copy and paste into OOo...
reassigning to hbrinkm
To hbrinkm: This Issue already more than 4 years old and have many duplicates. Please consider to target this for next OOo 2.2 If possible. Thanks
*** Issue 71949 has been marked as a duplicate of this issue. ***
Our goal is to bring the RTF import to the same quality as the binary Word import. If we are not completely mistaken we should be able to provide this with our new filter project.
*** Issue 75333 has been marked as a duplicate of this issue. ***
*** Issue 79716 has been marked as a duplicate of this issue. ***
I just used a vote on this issue. I normally can find a workaround for our users for the various things they need to do in their jobs. But when files won't open or import, we are kind of dead in the water. One hates to tell users that you have to keep a copy of Word around for importing RTF.
Dear developers, judging by the number of dupes (approx 25) it looks to be in high demand. Any chance to resolve this issue in 2.4? Thanks a lot for your attention. WBR, K. Palagin.
*** Issue 82417 has been marked as a duplicate of this issue. ***
*** Issue 82416 has been marked as a duplicate of this issue. ***
hbrinkm, are we on track for 3.0 with this issue? Thanks.
*** Issue 88275 has been marked as a duplicate of this issue. ***
The docx import consumed all resources we had in the interop area. So we have to move the target again. Please send any complaints to Redmond.
I would just like to add my voice to the chorus of those who would like this issue resolved. I agree that the docx issue is more important, but it would sure be nice to have full RTF support too. (I have a feeling my voice is more likely to be heard here than in Redmond) We have some vendor provided applications that in the absence of Word will generate RTF output that only seems to work with Word. These files do not open well with WordPad or Word Viewer either. Unfortunately, these users will be an exception to our OO.org only policy in our company. Thank you to everyone who is working on this project.
I understand the strategic choice, however I think this is quite "Microsoft wins" one. The OOXML is not-so-hot issue so far. Even MSOffice users understand, that .docx files are problematic for previous versions of Office. I understand however, that implementing this crap will take years. I'm afraid that Microsoft won this battle, because instead of having decent RTF support and excellent DOC/XLS support, we will have 50% RTF and 75% DOC/XLS support and forever-doomed partial OOXML support. Everything available but nothing perfect. I think there should be one REALLY good "bridging" format. And considering the amount of work done and consequences (Sun ODF plugin), the format is DOC rather than DOCX.
The target "3.x" should indicate that we are planning to fix that in the near future, but not in 3.0.
rtf, doc and docx are bascically the same format with different syntax. Our current filters (rtf,doc) are built on separate code. Our plan is to have one filter in the future for all formats (with different preprocessing of course). This filter will be based on the docx filter so that this effort will pay out for us in the long run even it is invested in a format that *today* isn't "hot".
Okay, I understand.
*** Issue 90081 has been marked as a duplicate of this issue. ***
May be possible do next thing for fast compatibility : on load - it's not fully displayed (while no import procedure) , but stil exist in document in source form and on save to same format it's will retain untouched, so when opening on other side they will have pictures, but in OOO that simple not displayed
*** Issue 96975 has been marked as a duplicate of this issue. ***
*** Issue 100752 has been marked as a duplicate of this issue. ***
*** Issue 101253 has been marked as a duplicate of this issue. ***
*** Issue 104597 has been marked as a duplicate of this issue. ***
*** Issue 113308 has been marked as a duplicate of this issue. ***
how many years need to implement "not to touch unsupported blocks" ? - won't realize - simple leave intact unparsable block
Reset the assignee to the default "issues@openoffice.apache.org".