Problem description: RTF file created in MS Office opens with no table formatting. Steps to reproduce: 1. Open attached file in LibO Current behavior: Table format is broken Expected behavior: Right table formating Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0
File was not attached so here is a link to it http://www.ex.ua/view_storage/559344749396
If you open this file in MS Word Viewer, it opens the file with table formatting kept, but displays the following warning (translating from Russian, so wording may be different in English version): "The table in the document is damaged. To restore the table contents: select it and choose the command "Convert to text" in the "Table" menu."
Created attachment 67722 [details] The RTF file (In reply to comment #1) > File was not attached so here is a link to it > http://www.ex.ua/view_storage/559344749396 Attached file directly here, so that it does not get lost. However, I had to change the filename (so this was the reason why attaching it did not work first).
(In reply to comment #3) > Created attachment 67722 [details] > The RTF file > > (In reply to comment #1) > > File was not attached so here is a link to it > > http://www.ex.ua/view_storage/559344749396 > > Attached file directly here, so that it does not get lost. > However, I had to change the filename (so this was the reason > why attaching it did not work first). Thank you, I'll know it for a future.
As mentioned in the commnet 2, even MS Word Viewer thinks that the table is damaged. Of course, we could do better job but this is rather a corner case and it can't block the release => lowering the severity a bit.
Reproduced in Libo 4.0 Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7) Win7 32bits. Yves
Created attachment 95017 [details] Repaired document
I close this bug report as RESOLVED INVALID because the attached document is corrupted. After repairing the file in Word 2010 the table is formatted properly in the following builds: - Libreoffice 4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72 - Libreoffice 4.2.1.1 Build ID: d7dbbd7842e6a58b0f521599204e827654e1fb8b - Libreoffice 4.3.0.0.alpha0 ID: 95700a2d7d09893fe16aadb406e93bf7164f7422 Feel free to open this bug report again if you find that the bug is still reproducible under some special circumstances, etc.