Bug 76834

Summary:	[FORMATTING] RTL text rendered incorrectly when presenting on Windows
Product:	LibreOffice	Reporter:	Shimi Chen <shimi.chen>
Component:	Impress	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	philipz85, shimons
Priority:	medium
Version:	Inherited From OOo
Hardware:	All
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	43808, 103610
Attachments:	example odp of the bug example odp of the bug with arabic instead of hebrew

Description Shimi Chen 2014-03-31 13:07:44 UTC

Created attachment 96654 [details]
example odp of the bug

When using Impress to present an odp file containing RTL text on Windows, It is at best displayed in LTR directionality and at worst completely messed up.

I tested on Linux and Windows (both with LO 4.2.2.1). The bug only shows up on Windows. On Linux everything is rendered correctly as far as I could tell (which is misleading when making and testing a presentation on Linux to present on a Windows box).

Attached is a simple example file of the bug.

Note that it does not matter on which platform the presentation is made, it will display incorrectly on Windows, and only in full-screen presentation mode.

Screenshots:

Windows edit mode (ok) - http://imgur.com/80THCNM
Linux edit mode (ok) - http://imgur.com/rFXKnjA
Windows present mode (bad) - http://imgur.com/kBfT7NN
Linux present mode (ok) - http://imgur.com/wwogfMx

Comment 1 Shimi Chen 2014-03-31 14:16:43 UTC

Created attachment 96661 [details]
example odp of the bug with arabic instead of hebrew

Comment 2 Yousuf Philips (jay) (retired) 2014-09-30 05:24:20 UTC

Hello Shimi,

Thank you for reporting the bug. I can confirm that in slide show mode the arabic is not shown correctly in 4.3.3.

Version: 4.3.3.0.0+
Build ID: bb21fe6d0a59df7f2c639c60e5e2aca0db9111ce
TinderBox: Win-x86@42, Branch:libreoffice-4-3, Time: 2014-09-23_23:29:45

Comment 3 QA Administrators 2016-09-20 10:18:42 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice
(5.1.5 or 5.2.1 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20160920

Comment 4 Shimi Chen 2016-10-31 09:36:03 UTC

Still occurs in 5.2.2.2.0 (Windows 8 x64).

Comment 5 Shimi Chen 2017-03-08 09:30:55 UTC

Seems like this bug is fixed with the new renderer in 5.3.