Description: Impress's parenthesis rendering is wrong in Korean texts. I am reporting it very late because I was busy with various situations. While preparing for the LibreOffice Conference slides in 2020, 2021, and this year, I found that the Korean text with parenthesis rendering was wrong in LibreOffice. Korean is a CJK cultural sphere, but special characters rendering such as parentheses like Western text, unlike Chinese and Japanese. Unlike Chinese and Japanese, Korean text with parentheses is not adjusted to avoid widening between letters. Example1) Requirements for Hangul Text Layout and Typography 한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항 https://w3c.github.io/klreq/#inter-char-rest Example2) Punctuations as an environment ofHangeul Typography http://koreantypography.org/wp-content/uploads/thesis/kst_j4_3.pdf Steps to Reproduce: 1. open Impress 2. input Korean text with parentheses 3. render Korean text with parentheses Actual Results: Rendered to adjust the space between Korean and parentheses Expected Results: Rendered that there is no space between Korean and parentheses Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 10; OS: Mac OS X 13.5.2; UI render: Skia/Metal; VCL: osx Locale: ko-KR (ko_KR.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 6d61e34e5623eab8f735344b0e659d834f6069e0 CPU threads: 10; OS: Mac OS X 13.5.2; UI render: Skia/Metal; VCL: osx Locale: ko-KR (ko_KR.UTF-8); UI: ko-KR Calc: threaded
Created attachment 189634 [details] Impress korean text with parentheses test file Impress korean text with parentheses test file
Created attachment 189635 [details] LibreOffice Impress slide01 screenshot - korean text with parentheses rendering is wrong LibreOffice Impress slide01 screenshot - korean text with parentheses rendering is wrong
Created attachment 189636 [details] LibreOffice Impress slide02 screenshot - korean text with parentheses rendering is wrong LibreOffice Impress slide02 screenshot - korean text with parentheses rendering is wrong
Created attachment 189637 [details] MS Powerpoint slide01 screenshot - korean text with parentheses rendering works correctly MS Powerpoint slide01 screenshot - korean text with parentheses rendering works correctly
Created attachment 189638 [details] MS Powerpoint slide02 screenshot - korean text with parentheses rendering works correctly MS Powerpoint slide02 screenshot - korean text with parentheses rendering works correctly
Created attachment 189639 [details] OpenOffice Impress slide01 screenshot - korean text with parentheses rendering is wrong OpenOffice Impress slide01 screenshot - korean text with parentheses rendering is wrong. The bug is inherited from OpenOffice.
Created attachment 189641 [details] OpenOffice Impress slide02 screenshot - korean text with parentheses rendering is wrong. OpenOffice Impress slide02 screenshot - korean text with parentheses rendering is wrong. The bug is inherited from OpenOffice.
Thanks for the report! Reproduced in recent trunk build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e3c961e6a3917d95534652e0f982918cc1079015 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Confirmed that on MS Office.com, opening the example document saved as XLSX does not have the excessive spacing. A workaround is to got to "Format > Paragraph > Asian Typography" and turn off "Apply spacing between Asian and non-Asian text", but is that a good workaround in your opinion, or is that too wide-ranging? Should a solution only affect the spacing around parentheses and brackets? And if turning that setting off is the right solution, should it be off by default for Paragraphs in Korean, i.e. what is requested in bug 136663? I see you have already commented there a few years ago. Please also see Khaled's question in bug 136663 comment 9, maybe you can answer.
Dear DaeHyun Sung, 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 DaeHyun Sung, 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
I think this should be fixed. *** This bug has been marked as a duplicate of bug 136663 ***
This is still affect LibreOffice 25.8.4, By copying texts from the test file I can confirm that bug 136663 is fixed with Writer and Calc, but still not resolved in Impress and Draw. Version: 25.8.4.2 (X86_64) Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded
Jonathan, can you give a hand?