Bug 120121 - Forced LTR when using bullets and starting with ltr lang
Summary: Forced LTR when using bullets and starting with ltr lang
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: text:rtl
Depends on:
Blocks: RTL-CTL
  Show dependency treegraph
 
Reported: 2018-09-26 06:57 UTC by Shay G
Modified: 2019-05-15 08:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Impress file showing the bug (11.72 KB, application/vnd.oasis.opendocument.presentation)
2018-09-27 11:28 UTC, Shay G
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shay G 2018-09-26 06:57:43 UTC
Hi,

Reproduce:
1) Set paragraph to RTL and align to right 
2) Add bullets
3) Start a new bullet line with LTR char and the rest is RTL chars. 

LTR is forced on that line, regardless of setting.

Use this line for example:
Linux: מערכת הפעלה מצויינת
Comment 1 Shay G 2018-09-27 11:28:58 UTC
Created attachment 145211 [details]
Impress file showing the bug
Comment 2 Eyal Rozenberg 2018-10-15 13:38:58 UTC
Can't reproduce this with a 6.2.0.0 nightly.

Reporter, can you attach a screenshot?
Comment 3 Xisco Faulí 2018-11-15 12:40:23 UTC
(In reply to Eyal Rozenberg from comment #2)
> Can't reproduce this with a 6.2.0.0 nightly.
> 
> Reporter, can you attach a screenshot?

Dear Shay G,
Please provide a screenshot as requested in comment 2...
Comment 4 QA Administrators 2019-05-15 02:57:21 UTC Comment hidden (obsolete)
Comment 5 Shay G 2019-05-15 04:06:00 UTC
Seem to be working as it should on v6.1.6. You can close.
Comment 6 Xisco Faulí 2019-05-15 08:07:22 UTC
(In reply to Shay G from comment #5)
> Seem to be working as it should on v6.1.6. You can close.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.