Summary: | FILEOPEN: TABLE in MSO2007 .docx with extra row at the bottom | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | sasha.libreoffice |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | alexpikptz, LibreOffice, mst.fdo, sasha.libreoffice |
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | filter:docx | ||
i915 platform: | i915 features: | ||
Attachments: |
original docx document
previous attachment, saved as pdf, using msWord 2007 |
Description
sasha.libreoffice
2012-05-07 03:34:01 UTC
Created attachment 61133 [details]
previous attachment, saved as pdf, using msWord 2007
"LibreOffice 3.5.3.2 (RC2) German UI/Locale [Build-ID: 235ab8a-3802056-4a8fed3-2d66ea8-e241b80] on German WIN7 Home Premium (64bit) opens the document much faster and looking much better than MS WORD viewer. But MS WORD Viewer shows 37 pages, LibO 41, ... I limit this bug report to an obvious Table problem I observe: LibO adds an extra row below table contents in every table. Old problem, visible with LibO 3.3.3 and OOo 3.3, so inherited from OOo. @sasha What the heck means "incorrect"? You shoud know better ;-) Please feel free to submit additional Reports for separate problems you see (Paragraph line spacing and several more). @Michael: Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug > What the heck means "incorrect"? You shoud know better ;-)
I created this bugreport for not forget to verify this problem in future, because original bugreport is closed.
LO 4.1.1 no more works slowly and there are 37 pages as in Word. But I can confirm some mistakes still exist: e.g. tables on pages 32 -> 37 are placed on right side (while they are on the left one in Word) and tables on pages 2-3-4 are shown in wrong positions, too. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.