Apache OpenOffice (AOO) Bugzilla – Issue 16944
Vertical text in table gets horizontal when importing from MS word
Last modified: 2013-08-07 14:41:36 UTC
importing a MS word document the table vertical titles are not imported correctly. (see the attached file)
Created attachment 7750 [details] document for testing
confirmed running OOo 1.1 RC1, Win98, with attached document doc1.zip [->doc1.doc]
Reassigned to MRU
I reconfirmed in both 1.0.3 and 1.1 RC 1 with original user doc and with a simple .doc with a 1-cell table with rotated text (In Word, right-click in text | Text Direction | click button with text running upward then OK). Specifically, the rotated table text is imported as non-rotated text. (Issue Status was Unconfirmed, yet Description claims it was confirmed. Thought I'd double check before changing Status.
SBA->FME: Talked to AMA on this. It's your turn first (cell-wise vertical writing) before CMC can do something in the filter.
FME: Set type to 'feature'.
I am trying to understand what happened to this issue. It sounds like someone looked into the import filter DEFECT and couldn't see how to achieve it without "cell-wise vertical text". So the issue was re-cast as a request for a new "cell-wise vertical text" FEATURE. I assert that OOo in general and this case in specific can function indefinitely without "cell-wise vertical text". OOo already has "style-wise vertical text". Why can't the import filter simply detect the vertical text, create (on demand, and cache indexed by rotation angle and original table cell paragraph style) a derived style differing only from the original table cell paragraph style in that it adds the rotation. In any case, it seems to me that the behavior is still defective. Isn't the product designed to support all the common features of the MS formats? In what sense is the failure to represent this one not a DEFECT?
FME: We are going to implement the cell wise vertical formatting soon, because the character attribute 'rotation' does not give you the results you want (try it and you will see). The 'rotation' character attribute is designed for vertical text within a horizontal environment (or vice versa). Adding more vertical text will increase the current (horizontal) line size and the environment will grow in y direction. This is not what you want. If 'cell wise vertical formatting' is implemented, the filter can make use of this function. [...] In any case, it seems to me that the behavior is still defective. Isn't the product designed to support all the common features of the MS formats? In what sense is the failure to represent this one not a DEFECT [...] Yes, we want to support all the common features of the MS format. Therefore all the common features have to be implemented in the Writer core. The 'vertical cell formatting feature' currently is not implemented in the writer core. This leads to the result, that we have to implement a FEATURE. If there was a bug in our current implementation, this would be a DEFECT. Please be patient, this issue will be addressed for OOo 2.0.
.
*** Issue 19477 has been marked as a duplicate of this issue. ***
*** Issue 14449 has been marked as a duplicate of this issue. ***
Add keyword ms_interoperability. Utomo > FME: is this same Issue or not with Issue 3056 ? Thanks
FME->Utomo: Yes, looks like a duplicate.
*** Issue 7058 has been marked as a duplicate of this issue. ***
*** Issue 23435 has been marked as a duplicate of this issue. ***
FME: Duplicate of internal #103484#.
*** Issue 25284 has been marked as a duplicate of this issue. ***
*** Issue 25623 has been marked as a duplicate of this issue. ***
*** Issue 25714 has been marked as a duplicate of this issue. ***
FME: This issue is for 270° rotation of text in writer tables (Asian layout). For 90° rotation of text in table cells, please see issue 25140.
*** Issue 3056 has been marked as a duplicate of this issue. ***
SBA: Verified in CWS vertcell.
SBA: Set to verified.
seen good in 680_m47 closing
We are almost there.. this is the sample from the bug number 19477 I submitted a year ago.. The current 2.0 builds work MUCH better than the 1.1.X versions. However, I am attaching examples of where progress stands on this issue.
Created attachment 18373 [details] Sample doc from bug 19477 that shows the current problem..
Created attachment 18374 [details] PDF output from Word 2000 of sample.doc.
Created attachment 18375 [details] PDF output from OO 1.9.56 of sample.doc.
SBA-> cowmixtoo: It makes no sense to add comments and attachments to a closed issue unless you misuse the issue tracking system disk quota to keep some of your precious documents forever :-) If you read the comments above (FME, Aug 7 2003 and FME March 11 2004), you can easily see that this one here does not solve all problems and that the follow-up issue is issue 25140. So if you think you can tell things that we are not aware of yet, then take on that one. Thank you for your comprehension.