The Thai words กลับ and การะกระทำ are incorrectly wrapped as ก|ลับ and การก|ระทำ This problem is especially noticeable as these are very common words in Thai.
@Brian : coud you please provide a sample document where this problem is apparent ?
Samphan: thought you might be interested in this one.
Created attachment 119724 [details] example text of the problem Here is a sample document of nonsense words illustrating the problem. The words are real Thai words, but they are randomly strung together.
Confirmed. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
another word with "ก" that incorrectly wraps. This word actually broke between pages. ลูกา (Luke) wrapped as ลูก|า. Even if the name of the third Gospel is unknown, an "า" can never begin a syllable under any circumstances, ever.
** 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.6 or 5.2.3 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-20161108
Dear Brian Wilson, 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
LibreOffice relies on ICU to break Thai words. ICU uses a greedy dictionary-based longest-matching Thai word-segmentation algorithm, e.g. it stops when found the first possible segmentation "การก|ระ|ทำ" (การก happens to really be a valid Thai word). To fix this issue, one needs to implement a slightly better maximal-matching algorithm in ICU. It will still fail in some other rarer cases anyway. BTW, this kind of problem happens very rarely in real-world Thai because the ambiguous sequences are rare and must be at the end of a line. I never hear a Thai complain about this.
(In reply to Samphan Raruenrom from comment #8) > LibreOffice relies on ICU to break Thai words. ICU uses a greedy > dictionary-based longest-matching Thai word-segmentation algorithm, e.g. it > stops when found the first possible segmentation "การก|ระ|ทำ" (การก happens > to really be a valid Thai word). > > To fix this issue, one needs to implement a slightly better maximal-matching > algorithm in ICU. It will still fail in some other rarer cases anyway. > > BTW, this kind of problem happens very rarely in real-world Thai because the > ambiguous sequences are rare and must be at the end of a line. I never hear > a Thai complain about this. Thanks a lot. Let's close this as notourbug.