Bug 67867 - FORMATTING: Vertical writing in fontwork - line breaks are wrong
Summary: FORMATTING: Vertical writing in fontwork - line breaks are wrong
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: FontWork-WordArt
  Show dependency treegraph
 
Reported: 2013-08-07 13:08 UTC by bugquestcontri
Modified: 2018-01-29 10:35 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Test kit: odp file and txt file with Japanese characters for testing. (12.73 KB, application/zip)
2013-08-07 13:08 UTC, bugquestcontri
Details
odp-file with detailed explanations and fontwork samples (56.97 KB, application/vnd.oasis.opendocument.presentation)
2014-07-29 13:24 UTC, bugquestcontri
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bugquestcontri 2013-08-07 13:08:10 UTC
Created attachment 83781 [details]
Test kit: odp file and txt file with Japanese characters for testing.

Problem description: 
Creating a fontwork in Japanese using vertical writing,rotating the fontwork by 90deg and inserting a line break moves the column which should appear left to the right side.

Even in latin character vertical writing the colums are in the wrong order after creating a line break

Steps to reproduce:
1. Create a fontwork
2. edit fontwork text and enter a japanese text and click outside the font work => all is correct
3. select the text in the fontwork and format to vertical writing (I have button for this)
4. insert a line break
=> columns are in the wrong order

or when using latin character test:
1. Create a fontwork
2. select the text in the fontwork and format to vertical writing (I have button for this)
3. insert a line break
=> columns are in the wrong order

I expect the same for Chinese and other double-byte languages.

If I remember it right, the line break in fontwork was correct in 3.6.6 or 4.0.3 however I don't have this file anymore.


Current behavior:
Line break in in vertically written fontwork places new column to the right instead of the left side. 

Expected behavior:
In vertical writing the line break creates the new line left of the original line


              
Operating System: Windows XP
Version: 4.0.4.2 release
Comment 1 bugquestcontri 2013-08-19 01:38:08 UTC
In the same version as oriiginal report (4.0.4.2) I just made a test in Draw and Writer and observed the same bug.


Test in Version: 4.1.0.4
Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 (Portable)

In Impress, Draw and Writer I observe the same bug.
Comment 2 ign_christian 2014-07-04 05:12:28 UTC
Hello..just a ping.. Is it still reproduce in LO 4.2.5.2 or 4.3.0.2 ?

And please change status according to the last situation
Comment 3 bugquestcontri 2014-07-05 06:34:53 UTC
I have not yet upgraded to 4.2.5.2 (long biz trip since the new release) but made a test in 4.2.4.2

Procedure as described above.

Result: the same.

Changed status to NEW and hope this is correct.
Comment 4 bugquestcontri 2014-07-29 13:22:20 UTC
Made now a test in LibO 4.2.4.2 / XP/SP3 (OS is unchanged from previous reports.

The result is the same. Nevertheless I created a odp-file with detailed explanations inside including a mockup made by screenshot on how the fontwork needs to look like.
Comment 5 bugquestcontri 2014-07-29 13:24:12 UTC
Created attachment 103644 [details]
odp-file with detailed explanations and fontwork samples
Comment 6 QA Administrators 2015-09-04 02:48:27 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2016-09-20 10:29:32 UTC Comment hidden (obsolete)
Comment 8 Xisco Faulí 2017-06-08 09:40:19 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-01-02 10:14:37 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2018-01-29 10:35:35 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180129