A single glyph on screen can consist of multiple code points. What LibreOffice basically does, or tries to do at least, is follow http://unicode.org/reports/tr29/ and it should work like so... a) The cursor keys skip over a full grapheme b) A "delete" deletes a full grapheme c) A backspace however, chips away a single codepoint at a time d) A alt+cursor key moves a single code-point at a time Which is all very well and good, but when we move a single code-point into a glyph our cursor positioning is fairly rubbish and not very helpful. The bengali KA+HALANT+TTA+HALANT+RA, i.e. 5 codepoints gives "ক্ট্র" which is a good example of this. I've no idea if there's any handy foo in opentype for determining the correct cursor position inside a gsub'ed glyph. Even if there is/isn't. It'd be nice to come up with... a) a better calculation for the cursor position in these gsub'ed cases b) a better cursor itself for helping out when trying to dig into a combining sequence. I saw a lovely demo of something like this from SIL, perhaps it was a WorldPad demo or something of that nature (http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=WorldPadDownload)
*** Bug 42324 has been marked as a duplicate of this bug. ***
I'm marking this to block rtl-meta bug at it affects also on RTL languages (see bug 42324).
OpenType’s GDEF table can have so ligature carets values that specify the horizontal cursor positions inside a ligatures (so not as sophisticated as the Graphite one, though I think Graphite2 dropped support for that), but very few fonts include this. What applications like Firefox do is to simply divide the width the ligature on the number of its characters.
** 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.0.5 or 5.1.0) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
So though we are using single glyphs in the document area, the input fields in the find toolbar and find & replace dialog are using single codepoints.
So alt+cursor key moves by single code-points, but alt+shift+cursor key doesnt allow you to select single code-points.
Reporter/others: Please try specifying conditions under which you would consider this bug resolved, and/or reproducible behavior which is not good enough (including how the cursor looks, hopefully with screenshots or photoshopped screenshots).
Dear Caolán McNamara, 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
Created attachment 184036 [details] bengali code point test In the attachment, one can navigate the code points with Alt + cursor. Since what I assume is the fix for bug 83581, situation has changed: Up to LO 7.4, Alt + cursor navigation would make the caret jump back and forth. In 7.5, the caret doesn't "dance" (but some keypresses still won't give a visual clue of progression through the combined glyph). Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: da3dd48eaf9086f8ab28d6a6655f9a638e51433a CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
I think the situation now is good as it can be. We handle ligatures, and inserting cursor inside a grapheme cluster is not something OpenType has support for (older version of Graphite had, but the later libgraphite2 versions dropped it).