Description: Wrapped RTL text characters within shapes are exported to tagged PDF with incorrect character order. The attached pptx file contains RTL text within a shape. The shape has "Word wrap in text shape" set to true. Exporting the pptx as a tagged PDF should result in the same order of characters regardless of whether word wrap is enabled or not. Steps to Reproduce: 1. Export the pptx as a tagged PDF using File > Export as > Export as PDF > Tagged PDF 2. Select the text within the shape and disable word wrap using Format > Object and Shape > Text > untick Word wrap in text shape 3. Export the pptx again as a tagged PDF using File > Export as > Export as PDF > Tagged PDF Actual Results: The codepoints of the unicode characters within the marked content sequence of the PDF with wrapped text are in the following order: 1579 1578 1576 1575 32 1582 1581 1580 The codepoints of the unicode characters within the marked content sequence of the PDF with no wrap are in the expected order. Expected Results: The codepoints of the unicode characters within the marked content sequence of both PDFs should be in the following order: 1582 1581 1580 32 1579 1578 1576 1575 Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.5.2 Build ID: 6.3.5-3 CPU threads: 8; OS: Linux 5.5; UI render: default; VCL: gtk3; Locale: ar-SA (en_GB.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 160859 [details] Impress file with wrapped RTL text in a shape
Created attachment 160860 [details] Tagged PDF produced from wrapped RTL text in a shape
Created attachment 160861 [details] Tagged PDF produced from RTL text in a shape with no wrap
As I am naive about Arabic, what would be a simple way for me to confirm the problem on my own machine? How can I see the codepoint order in the PDF result? I tried an online service to show unicode codepoints in copied & pasted strings, but I'm not getting consistent and understandable results. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Dear zainab.ali, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear zainab.ali, 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-FollowUp