Two different but related problems:
(1) Task: In the middle of text in the Arial font, I need to insert a circled number 1. This character exists in the Wingdings font (decimal 129).
Attempt: I do Insert>Symbol and choose the Wingdings font. However, the character grid shows the characters from Arial, not from Wingdings. If I hover the cursor over character 129, I can see the circled 1 in the box on the right, and if I click on it, the correct character is inserted. However, this isn't very useful if I don't already know that the circled 1 is character 129. So far as I can tell, this bug occurs whenever the font in question is a "symbol" font (i.e. a font identified in the font header as a symbol font, in which the character encoding starts at hex F020) unless it is the Windows Symbol font.
Pain-in-the-neck workaround: In order for the grid to show the Wingding symbols, I first have to select the Wingding font (either from the font list on the toolbar or from Format>Font) and then do Insert>Symbol. This shouldn't be necessary.
(2) Task: In the middle of my text, I need the c-caron character (č). This character is not part of the (default) Western codepage, but is included in the Central European codepage.
Attempt: I do Format>Font, and in the "Script" box I select Central European. Now I do Insert>Symbol. The č correctly appears in the grid (although when I hover the cursor over it, the box on the right displays the Western codepage character è instead). But when I click on the č, it is è that appears in my note instead.
Pain-in-the-neck workaround: After I have inserted the character (è in the example), I have to select it, do Format>Font again, and again change the script to Central European. Finally, I have a č.
These are a real pain, because I often need weird characters like these.
Yehuda, I can reproduce both
Yehuda, I can reproduce both bugs. These bugs are from the RTF engine we use. We cannot fix them in 7.x release. We will try to get them fixed in the next major upgrade. Thanks.
Oh well
:(
Yehuda N. Falk
Associate Professor of English Linguistics
The Hebrew University of Jerusalem
U-NI-CO-DE!
U-NI-CO-DE! U-NI-CO-DE! (one more vote)
Unicode only partial solution
Unicode wouldn't solve the symbol-encoded font problem, but it would fix the code-page problem. (My word processor, WordPerfect, is also resisting a move to Unicode.)
Yehuda N. Falk
Associate Professor of English Linguistics
The Hebrew University of Jerusalem