Bug 69678

Summary: TABLE: Wrong text position after rotating it in tables
Product: LibreOffice Reporter: sergo
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: barta
Priority: medium    
Version: 4.1.2.2 rc   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Changing the text after putting cursor in the middle of rotated test in the cell

Description sergo 2013-09-22 14:52:34 UTC
Created attachment 86321 [details]
Changing the text after putting cursor in the middle of rotated test in the cell

Problem description: 

Steps to reproduce:
1. Open LibreOffice Writer.
2. Insert a table. The quality of rows and strings does not matter.
3. Write any text into one of cells.
4. Select written text.
5. Select Format->Characters, open Position tab and select rotation (scalling) on 90 degrees.
6. Put the cursor somewhere in the middle of written text between words and put enter.
7. Text must looks as in attachment. The last part which was after cursor goes into the beginnging of the written phrase.
Operating System: openSUSE
Version: 4.1.2.2 rc
Comment 1 sergo 2013-09-22 14:57:40 UTC
It is expected that the text after pressing Enter must be devided in 2 parts. The first part (which was before cursor while pressing Enter) must be in the first (left vertical) line, the last part must goes to 2nd line (right vertical) one.
Comment 2 ign_christian 2013-09-23 05:53:09 UTC
Following bug description, I can't reproduce on LO 4.0.5.2 (Win7 32bit). Perhaps a regression.

(In reply to comment #1)
> It is expected that the text after pressing Enter must be devided in 2
> parts. The first part (which was before cursor while pressing Enter) must be
> in the first (left vertical) line, the last part must goes to 2nd line
> (right vertical) one.
I can confirm there is a weird behavior while doing that. But I think that problem should be separated & reported in new bug report. (if someone has not been reported that yet)
Comment 3 ign_christian 2013-09-23 06:14:39 UTC
Comment 1 = Bug 34436
Comment 4 tommy27 2013-10-11 05:48:02 UTC
I mark it as DUPLICATE as previous comment suggested.
feel free to REOPEN it if you think we are dealing with a different problem.

*** This bug has been marked as a duplicate of bug 34436 ***