Description: NNBSP (U+202F Narrow No-Break SPace) in Mongolian texts fail to change the form of the letters following them as they should if LibreOffice using fallback font to render the text. The problem disappears when the author or the reader explicitly chooses a Mongolian font. Steps to Reproduce: 1. Download a test file from https://bug490534.bmoattachments.org/attachment.cgi?id=374937 2. Open with LibreOffice Actual Results: The first line does not specified the font, NNBSP is rendered with default font and surrounding letter failed to jion, the second line is specified using Mongolian Baiti, NNBSP is rendered with Mongolian Baiti and surrounding letter joined with that. Expected Results: When NNBSP is surrounded by Mongolian/Manchu letters, this sbace should rendered with the same font used for Mongolian text to make the surrounding letter always works as expected. Reproducible: Always User Profile Reset: No Additional Info: Version: 5.3.3.1 (x64) Build ID: 46360c72c4823cefeaa85af537fba22bd568da7e CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; Locale: zh-CN (zh_CN); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Created attachment 133056 [details] Screenshot
@Volga: Fallback fonts arent universally perfect for all languages, i would assume, so i wouldnt blame the issue on the fallback font. @Khaled: Any ideas what this should be classified under?
I opened the html in LibO and I am not seeing anything at all. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha1+ Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 5th 2016
(In reply to Buovjaga from comment #3) > I opened the html in LibO and I am not seeing anything at all. > > Arch Linux 64-bit, KDE Plasma 5 > Version: 5.4.0.0.alpha1+ > Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68 > CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; > Locale: fi-FI (fi_FI.UTF-8); Calc: group > Built on May 5th 2016 Be sure you got Mongolian Baiti, Noto Sans Mongolian and other fonts support Mongolian scripts before you confirmed.
If you don’t use Windows, you can get Mongolian Baiti from here: http://abkai.net/fonts/monbaiti.ttf
(In reply to Volga from comment #5) > If you don’t use Windows, you can get Mongolian Baiti from here: > http://abkai.net/fonts/monbaiti.ttf I installed the font. Now I see the second line and it is like in your screenshot. First line remains empty. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha1+ Build ID: 8891472e1f9c5e452a4e8d55241eeba118274092 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 12th 2016
You can also run LibO on the VM to reproduce: https://dev.windows.com/en-us/microsoft-edge/tools/vms/
Ok, confirmed. Version: 5.4.0.0.alpha1+ (x64) Build ID: bbe579a47845e56caf05ae7ab9fdf49319f5647c CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2017-04-30_00:10:55 Locale: fi-FI (fi_FI); Calc: group
In this case NNBSP should be treated the same as ZWJ/ZWNJ to make Mongolian letters always presented joining.
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Volga, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Volga: Is this issue still reproducible?
Created attachment 167621 [details] Screenshot 2 (In reply to Kevin Suo from comment #12) > Volga: Is this issue still reproducible? Yes, It is. The problem still happen with fallback fonts, Firefox 83.0 have no problem.
I confirm this bug still exists: LibreOffice 7.3.7.2 on Fedora 36.
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d4653fa961b1aa1cd4bf568e7d1fe50ae97df484 tdf#107612: Include NNBSP and Mongolian characters in the same fallback run It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Khaled Hosny committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/0f67027dbf3774687a558127427ff26796f00328 tdf#107612: Include NNBSP and Mongolian characters in the same fallback run It will be available in 7.6.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.