Issue 101451

Summary: WW8: table imported with wrong position on ubuntu linux
Product: Writer Reporter: arghil <arghil>
Component: open-importAssignee: michael.ruess
Status: CLOSED FIXED QA Contact: issues@sw <issues>
Severity: Trivial    
Priority: P2 CC: hancock, issues, jbf.faure
Version: OOo 3.1 RC2Keywords: regression
Target Milestone: ---   
Hardware: PC (x86_64)   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 101565    
Attachments:
Description Flags
Sample file with 2 tables
none
After import to OOo 3.0 (it's ok)
none
After import to OOo 3.1RC2
none
Picture of document with table missing none

Description arghil 2009-04-30 12:14:20 UTC
OOo 3.1 RC2 after the conversion is assigning incorrect colors to the table.
Comment 1 arghil 2009-04-30 12:16:03 UTC
Created attachment 61914 [details]
Sample file with 2 tables
Comment 2 arghil 2009-04-30 12:19:53 UTC
Created attachment 61915 [details]
After import to OOo 3.0 (it's ok)
Comment 3 arghil 2009-04-30 12:20:44 UTC
Created attachment 61916 [details]
After import to OOo 3.1RC2
Comment 4 michael.ruess 2009-05-04 12:31:43 UTC
It is not that the colors are not imported; the table's position is wrong. See,
when opening the table's properties via Navigator.

MRU->HBRINKM: I was only able to see this on ubuntu with our 64bit builds. The
table's position is imported with 16 cm from left. Thus the table is not
displayed in the visible area of a page.
Comment 5 michael.ruess 2009-05-25 12:15:59 UTC
*** Issue 101718 has been marked as a duplicate of this issue. ***
Comment 6 michael.ruess 2009-05-25 12:16:25 UTC
*** Issue 102107 has been marked as a duplicate of this issue. ***
Comment 7 michael.ruess 2009-05-25 13:10:54 UTC
*** Issue 102004 has been marked as a duplicate of this issue. ***
Comment 8 michael.ruess 2009-05-29 09:39:55 UTC
*** Issue 102342 has been marked as a duplicate of this issue. ***
Comment 9 michael.ruess 2009-05-29 09:43:18 UTC
This one becomes more and more popular, so I raise the target to 3.2.
Comment 10 michael.ruess 2009-05-29 10:36:28 UTC
*** Issue 102335 has been marked as a duplicate of this issue. ***
Comment 11 eric.savary 2009-06-01 14:02:36 UTC
*** Issue 102385 has been marked as a duplicate of this issue. ***
Comment 12 rene 2009-06-02 15:34:33 UTC
mru: after this is a regression in 3.1 and important, shoudn't this be 3.1.1
instead?
Comment 13 eric.savary 2009-06-03 21:13:52 UTC
*** Issue 102481 has been marked as a duplicate of this issue. ***
Comment 14 eric.savary 2009-06-03 21:14:51 UTC
*** Issue 102481 has been marked as a duplicate of this issue. ***
Comment 15 eric.savary 2009-06-06 09:49:29 UTC
*** Issue 102555 has been marked as a duplicate of this issue. ***
Comment 16 openoffice 2009-06-09 10:19:45 UTC
showstopper for 3.1.1 => set prio and target accordingly
Comment 17 openoffice 2009-06-10 15:17:37 UTC
Sending        ww8par2.cxx
Committed revision 272825.
Comment 18 eric.savary 2009-06-10 16:05:58 UTC
*** Issue 102649 has been marked as a duplicate of this issue. ***
Comment 19 eric.savary 2009-06-13 21:21:30 UTC
*** Issue 102751 has been marked as a duplicate of this issue. ***
Comment 20 eric.savary 2009-06-16 11:24:27 UTC
*** Issue 102832 has been marked as a duplicate of this issue. ***
Comment 21 terriabraham 2009-06-16 18:52:15 UTC
So now that this is fixed, what's next? Is it fixed so that it won't happen 
again but too bad about the documents already messed up or is there a fix that 
fixes the tables in existing documents.

and how do I get the fix?

thanks
Comment 22 openoffice 2009-06-17 09:14:40 UTC
@terriabraham: This is fixed in CWS hb311fixes01 which is now ready for QA and is planned to be released with OOo 
3.1.1. See http://wiki.services.openoffice.org/wiki/OOoRelease311 for the release schedule.

If you want to get the fix as soon as possible you can grab one of the developer snapshots. To find out which 
release to get, you can scan http://planet.go-oo.org for entries called "EIS - OOO310_xyz ready for use" to find out 
the milestone where hb311fixes01 is integrated. Then scan for entries called "Gullfoss - New: OOo-DEV 3.1.1 
Developer Snapshot (build OOO310_xyz) available". You will find the download link in that entry.
Comment 23 eric.savary 2009-06-17 10:37:51 UTC
*** Issue 102852 has been marked as a duplicate of this issue. ***
Comment 24 eric.savary 2009-06-17 17:06:04 UTC
*** Issue 102880 has been marked as a duplicate of this issue. ***
Comment 25 eric.savary 2009-06-18 15:51:40 UTC
*** Issue 102915 has been marked as a duplicate of this issue. ***
Comment 26 eric.savary 2009-06-22 11:12:55 UTC
*** Issue 102996 has been marked as a duplicate of this issue. ***
Comment 27 michael.ruess 2009-06-22 11:17:26 UTC
*** Issue 102996 has been marked as a duplicate of this issue. ***
Comment 28 michael.ruess 2009-06-28 15:09:16 UTC
*** Issue 103171 has been marked as a duplicate of this issue. ***
Comment 29 michael.ruess 2009-06-29 09:14:58 UTC
*** Issue 103171 has been marked as a duplicate of this issue. ***
Comment 30 michael.ruess 2009-06-29 10:23:36 UTC
Reassigned to MRU.
Comment 31 michael.ruess 2009-06-29 10:25:08 UTC
Verified fix in CWS hb311fixes01.
Comment 32 eric.savary 2009-07-01 12:10:14 UTC
*** Issue 103239 has been marked as a duplicate of this issue. ***
Comment 33 eric.savary 2009-07-01 12:10:48 UTC
*** Issue 103239 has been marked as a duplicate of this issue. ***
Comment 34 caolanm 2009-07-03 15:28:56 UTC
btw, same as issue 101109 which was fixed on the 3.2 branch
Comment 35 rene 2009-07-04 13:41:23 UTC
The wrong_lands_table.doc from issue  sti102004ll doesn't open correctly.

So either
 - issue is not really a dup1licate of this one here
 - this issue is not really fixed

reopening
Comment 36 michael.ruess 2009-07-06 10:59:51 UTC
MRU->RENE:
please do not reopen fixed issues as long as there is no proof for the fact that
the fix is definitely wrong. 
In issue 102004you have attached two different documents showing two different
problems. Document a.doc is the thing handled here. Document
wrong_lands_table.doc seems to show a special problem importing a table in RTL
context. Please file a new issue for this special problem.
Do not re-open issue 102004 as long as there are two different documents
attached to it.
Thanks for your patience. 
Comment 37 michael.ruess 2009-07-06 11:00:30 UTC
Back to verified.
Comment 38 rene 2009-07-06 14:02:57 UTC
> Do not re-open issue 102004 as long as there are two different documents
> attached to it.

Actualkly, I will, because the bugreport *was* about wrong_lands_table.doc.
That you don't read linked bugs is not my problem, but the initial bug was
filed for wrong_lands_table.doc
Comment 39 rene 2009-07-06 14:25:06 UTC
... and as you can't remove an attachement....

In issue 102004 I was just forwarding the debian bug 1:1, and against your
reading the initial filing was about wrong_lands_table.doc. That someone
"hijacked" it with a.odt thinking it's the same bug is bad, but not avoidable
wioth some users.
Comment 40 eric.savary 2009-07-07 13:47:48 UTC
*** Issue 103383 has been marked as a duplicate of this issue. ***
Comment 41 michael.ruess 2009-07-12 09:07:02 UTC
*** Issue 103459 has been marked as a duplicate of this issue. ***
Comment 42 eric.savary 2009-07-13 10:23:38 UTC
*** Issue 103491 has been marked as a duplicate of this issue. ***
Comment 43 michael.ruess 2009-07-27 09:02:39 UTC
*** Issue 103821 has been marked as a duplicate of this issue. ***
Comment 44 michael.ruess 2009-07-27 10:24:06 UTC
Checked fix in OOO310m16.
Comment 45 eric.savary 2009-08-11 16:37:10 UTC
*** Issue 104162 has been marked as a duplicate of this issue. ***
Comment 46 pramathesh 2009-08-17 13:15:50 UTC
I encountered the same issue on Openoffice 3.0.1 on Ubuntu Jaunty 9.04 32-bit
version.

Table in document has left margin set outside right margin boundaries so the
table is invisible

Pramathesh
Comment 47 pramathesh 2009-08-17 13:16:48 UTC
Created attachment 64212 [details]
Picture of document with table missing
Comment 48 eric.savary 2009-08-27 09:28:16 UTC
*** Issue 104540 has been marked as a duplicate of this issue. ***
Comment 49 michael.ruess 2009-08-27 09:31:35 UTC
*** Issue 104540 has been marked as a duplicate of this issue. ***
Comment 50 eric.savary 2009-10-28 18:42:31 UTC
*** Issue 106395 has been marked as a duplicate of this issue. ***