Issue 102278 - Wrong placement of vertical text in combined cells of imported .doc
Summary: Wrong placement of vertical text in combined cells of imported .doc
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 3.1
Hardware: All All
: P4 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: regression
Depends on:
Reported: 2009-05-27 07:27 UTC by bormant
Modified: 2017-05-20 11:19 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

test file for vertical-text-in-combined-cells (28.50 KB, application/msword)
2009-05-27 07:28 UTC, bormant
no flags Details
screenshot for vertical-text-in-combined-cells (8.93 KB, image/png)
2009-05-27 07:29 UTC, bormant
no flags Details
another sample file (22.00 KB, application/msword)
2009-05-27 08:04 UTC, kpalagin
no flags Details
illustrating screenshot (33.31 KB, image/png)
2009-05-27 08:05 UTC, kpalagin
no flags Details
text wraps by height of top row in combined cell (5.91 KB, image/png)
2009-05-27 08:22 UTC, bormant
no flags Details
Exported DOC file, created in OO.o 3.1.0 (10.50 KB, text/plain)
2009-05-27 16:06 UTC, fyva
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bormant 2009-05-27 07:27:03 UTC
.doc has a table with vertically combined cells. These cells contain vertical 
right aligned text.

After import text starts and aligned in top half of combined cell then goes to 
bottom half of cell. In another words combined cell behaves as two linked in 
wrong order frames.

OOo.2.4.2 works correct in this case.
Comment 1 bormant 2009-05-27 07:28:34 UTC
Created attachment 62558 [details]
test file for vertical-text-in-combined-cells
Comment 2 bormant 2009-05-27 07:29:15 UTC
Created attachment 62559 [details]
screenshot for vertical-text-in-combined-cells
Comment 3 oc 2009-05-27 07:42:31 UTC
wrong component
Comment 4 kpalagin 2009-05-27 08:04:58 UTC
Created attachment 62561 [details]
another sample file
Comment 5 kpalagin 2009-05-27 08:05:45 UTC
Created attachment 62562 [details]
illustrating screenshot
Comment 6 kpalagin 2009-05-27 08:07:17 UTC
As described - see attached "wrong-direction.PNG".
Comment 7 bormant 2009-05-27 08:22:59 UTC
Created attachment 62563 [details]
text wraps by height of top row in combined cell
Comment 8 michael.ruess 2009-05-27 13:56:09 UTC
MRU->OS: this looks like a formatting problem in the table. When resizing the
table column containing the vertical text it will look ok even after Undo. So
the table import seems "not guilty" this time ;-)
Adding OD to CC.
Comment 9 kpalagin 2009-05-27 14:09:15 UTC
Lotus Symphony opens the file even better than Word Viewer.
Comment 10 fyva 2009-05-27 16:04:36 UTC
If the file was created in OO.o, exported to DOC and then again imported to
OO.o, then no problem, without touching the text or the column width. This bug
appears only when importing a file created in (a version of) Word. OO.o has only
initial support for files created in Word, don't forget it. If someone make an
initial support for Corel Draw in OO.o Draw, are you going to demand the full
support and eternally file bugs of the imperfect filter? Of cource, it is
imperfect, it would be imperfect by definition and will never be perfect.
Comment 11 fyva 2009-05-27 16:06:22 UTC
Created attachment 62587 [details]
Exported DOC file, created in OO.o 3.1.0
Comment 12 fyva 2009-05-27 16:23:42 UTC
If you preview or print the first attached file, there is no corruption of the
vertical text. This is a bug with updating the screen.
Comment 13 Oliver Specht 2010-02-04 12:01:42 UTC
Target changed to 3.x
Comment 14 Mathias_Bauer 2011-02-17 15:18:00 UTC
According to our new regression issue handling for the 3.4 relrease the field
priority is now used as the order we want to work on them, no longer as a
"severity". The high number of regressions in the WW8 filters makes it necessary
to prioritize them as we won't be able to fix all of them for 3.4. We decided to
first focus on the export. Thus most regressions in the import filter now get
priority "P4", what means that they will be reevaluated in the next release cycle.
Comment 15 Marcus 2017-05-20 11:19:45 UTC
Reset assigne to the default "".