fix(developer): use richedit in debug memo to support Egyptian cartouches

[mcdurdin]

RichEdit allows text selection one character past end-of-string, so we need to cater for that as well in passing text ranges to the character grid.

Note: in draft as this uses RichEdit 2.0 which has other spacing issues for complex scripts (e.g. Khmer), need to be basing on RichEdit 4.1 preferably.

Fixes: #12454

User Testing

• TEST_KMN_DEBUGGER: In Keyman Developer, open a Keyman .kmn keyboard, and press F5 to start the debugger. Run through a number of normal operations in the debugger, selecting text, typing, etc, and look for any unexpected display issues or anomalies. Pass this test if no issues are encountered.

• TEST_LDML_DEBUGGER: In Keyman Developer, open or create a Keyman LDML keyboard, and press F5 to start the debugger. Run through a number of normal operations in the debugger, selecting text, typing, etc, and look for any unexpected display issues or anomalies. Pass this test if no issues are encountered.

[keymanapp-test-bot]

User Test Results

Test specification and instructions

• ✅ TEST_KMN_DEBUGGER (PASSED) (notes)
• ✅ TEST_LDML_DEBUGGER (PASSED) (notes)

Test Artifacts

• Developer
  • Keyman Developer
  • Compiler Regression Tests
  • kmcomp.zip
• Keyboards
  • Test Keyboards

[dinakaranr]

Test Results

I tested this issue with the attached "18.0.117-alpha-test-12464" build on the Windows 10 and 11 OS. I'm sharing my observation here.

• TEST_KMN_DEBUGGER (failed): 

1. I installed the Keyman developer 18.0.117-alpha-test-12464 version and then started the configuration.
2. On Keyman Developer, navigate to the "Keyboard" tab and then click the *.kmn link button to navigate to the build tab.
3. Click the "Complie Keyboard" button.
4. Click the "Start Debugging" button.
5. Debugger mode was opened.
6. Press the a, b, c, and e keys in an empty box.
7. I tested the above steps for the "gff_amharic" keyboard and then observed the square box appeared.
   Please take a look at the screenshot below.

• TEST_LDML_DEBUGGER (failed): 
  I installed the Keyman developer 18.0.117-alpha-test-12464 version and then started the configuration.
  On Keyman developer: 

1. Create a new LDML project. 
2. Navigate to the "Keyboards" tab.
3. Click the *.xml link button to open the "View Source" *.xml file content.
4. Navigation moved to the *.xml tab.
5. Copy and paste any standard LDML keyboard content. (e.g. imperial_aramaic) 
6. Save the changes.
7. Press the F5 key to start the debugging mode.
8. The debugger box appeared below the "view source" code.
9. Press the a, b, c, and e keys in an empty box.
10. I tested the above steps for the "imperial_aramaic" keyboard and then observed the square box appeared.
    Please refer to the screenshot below.

Note: This same project works well using the Keyman 18.0.122 alpha build. there is no square box appearing when typing a text.

[mcdurdin]

@dinakaranr I think this is happening because you haven't selected a font for the test or 'characters' in the keyboard. If you choose an appropriate font (right-click on the test window to change font), you should find the characters displaying correctly. If you don't have an appropriate font available, you could install the font that is referenced in the corresponding .kps file, and use that.

@keymanapp-test-bot retest

[rc-swag]

lgtm

[dinakaranr]

Test Results

Okay. Thank you for the clarification. I retested this issue with the attached "18.0.117-alpha-test-12464" build on the Windows 10 and 11 OS. 

• TEST_KMN_DEBUGGER (Passed):

1. I installed the Keyman developer 18.0.117-alpha-test-12464 version and then started the configuration.
2. On Keyman Developer, navigate to the "Keyboard" tab and then click the *.kmn link button to navigate to the build tab.
3. Click the "Complie Keyboard" button.
4. Click the "Start Debugging" button.
5. Debugger mode was opened.
6. Press the a, b, c, and e keys in an empty box.
7. Select an appropriate font for the keyboard. (Noto serif Ethiopic - gff_amharic)
8. I tested the above steps for the "gff_amharic" keyboard and then observed the text appeared

• TEST_LDML_DEBUGGER (Passed):
  I installed the Keyman developer 18.0.117-alpha-test-12464 version and then started the configuration.
  On Keyman developer: 

1. Create a new LDML project. 
2. Navigate to the "Keyboards" tab.
3. Click the *.xml link button to open the "View Source" *.xml file content.
4. Navigation moved to the *.xml tab.
5. Copy and paste any standard LDML keyboard content. (e.g. imperial_aramaic) 
6. Save the changes.
7. Press the F5 key to start the debugging mode.
8. The debugger box appeared below the "view source" code.
9. Select an appropriate font for the keyboard.(Noto Sans Imperial - imperial_aramaic)
10. Press the a, b, c, and e keys in an empty box.
11. I tested the above steps for the "imperial_aramaic" keyboard and observed text appeared.
    Please take a look at the screenshot below.

[keyman-server]

Changes in this pull request will be available for download in Keyman version 18.0.124-alpha