Created attachment 120755 [details] Test Files (odt, odp, ods) The New Tai Lue script has 4 vowels occurring to the left of the consonant: - U+19B5 NEW TAI LUE VOWEL SIGN E - U+19B6 NEW TAI LUE VOWEL SIGN AE - U+19B7 NEW TAI LUE VOWEL SIGN O - U+19BA NEW TAI LUE VOWEL SIGN AY Whether in Writer, Calc, or Impress, it is not possible to place cursor before any of the above pre-vowel via arrow keys or mouse clicks. The cursor will only fall after the pre-vowel or before the *preceding* char. Furthermore, when the cursor is before the preceding char, pressing <Del> will delete *both that char & the pre-vowel*. The only workaround is to use <Alt> + arrow keys to go between the pair, but this is not even possible in Calc. This means some shared module of LO fails to implement the correct character properties of these 4 chars, thinking they are combining chars. According to Unicode 8.0, released on 2015-06-17, all 4 are assigned a general category of 'Lo' (Letter, other) & not 'Mc' (Mark, combining). See http://unicode.org/versions/Unicode8.0.0/ Sections A, F, & M for the latest encoding model of the New Tai Lue script. See also http://www.unicode.org/Public/8.0.0/ucd/UnicodeData.txt for the actual character properties in the UCD. This problem is attested in the following builds & OS: - LibO 5.0.3.2 in XP Mode (32-bit English Windows XP Professional SP3) on 64-bit English Windows 7 Ultimate SP1 - LibO 5.0.3.2 on 32-bit English Windows Vista Business SP2 - LibO 5.0.3.2 on 32-bit English Windows 7 Professional SP1 - LibO 4.4.5.2 on 64-bit English Windows 7 Ultimate SP1 (NB: Windows 7 has bugs in its own New Tai Lue renderer that combine with the above cursor placement defect in LO, making it difficult to see the defect in isolation. It would be best to conduct the following on other OS first before getting to Windows 7.) Steps to reproduce bug: 1. download & install Nokyung font from https://github.com/silnrsi/font-nokyung/releases/download/v1.3/silnrsi-font-nokyung-13.zip 2. unzip attached zip archive 3. open test-cursor.odt 4. on line 1, move cursor between chars 2 & 3 via arrow keys or mouse click * 5. on line 3, move cursor between chars 1 & 2 via arrow keys or mouse click * 6. on line 4, move cursor between chars 1 & 2 via arrow keys or mouse click * 7. on last line, move cursor between chars 3 & 4 via arrow keys or mouse click * * expected result for steps 4-7: cursor placed between chars in concern * actual result: cursor CANNOT be placed between those chars -- BUG!!! 8. repeat steps 4-7 by using <Alt> + arrow keys: cursor placed between chars 9. on line 1, place cursor before char 2 & press <Del> ** 10. on line 3, place cursor before char 1 & press <Del> ** 11. on line 4, place cursor before char 1 & press <Del> ** 12. on last line, place cursor before char 3 & press <Del> ** ** expected result for steps 9-12: char after cursor deleted ** actual result: *two* chars after cursor deleted -- BUG!!! 13. repeat steps 3-12 with test-cursor.odp: same results 14. repeat steps 3-12 with test-cursor.ods, equating line no. to row no.: - same results save step 8, which only makes column wider/narrower; - cursor still cannot be placed between chars in concern Pls. implement the 4 aforementioned chars as full chars, not combining chars, & fix this defect ASAP. Thanks!
Problem also attested in the following builds & OS: - LibO 5.0.2.2 in 32-bit Ubuntu 15.10 VirtualBox on 32-bit English Windows Vista Business SP2 (NB: The rendering engine of Ubuntu 15.10 is still rendering New Tai Lue logically (i.e., not yet updated to Unicode 8.0). This interferes with the above cursor placement defect in LO, making it difficult to see the defect in isolation. It would be best to reproduce the bug on other OS first before getting to Ubuntu 15.10.)
Reproduced. Doesn't seem to be "graphics stack" (VCL), so setting component to general "LibreOffice" Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd Threads 4; Ver: Windows 6.1; Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18 Locale: fi-FI (fi_FI)
** 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-20170103
Dear yutgor, 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 nrs, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug