Sjur N?rsteb? Moshagen wrote:
> I assume there is a similar reason why Unicode combining chars also
> behave erroneous? Test (still on the Mac):
>
> Select one of the Unicode key layouts (North S?mi, Norwegian Extended,
> USA Extended), and type the following: 'c' followed by 'Shift-Alt-c'.
> While Alt-c gives the dead key cedilla (which can combine with a c as
> the next input char to give ?) in standard MacOS/Cocoa/Carbon apps,
> Shift-Alt-c gives the combining diacritic that combines with the
> preceeding char to produce a new char (which may or may not be an
> existing precomposed char in Unicode).
>
> If you do the above in the styled view in XXE, the normal dead key will
> give you nothing (as explained in the previous mail), while the
> combining diacritic will give you a square, and make the cursor be badly
> disaligned.
I'm sure that this problem will disappear the day XXE becomes an
InputMethod active client, just like the Swing text components.
And no, I'm not surprised by "the combining diacritic will give you a
square, and make the cursor be badly disaligned": the combining
diacritic is probably a Unicode character of its own which has no
displayable glyph in any font and therefore which has a null width.
> Thanks a lot again for the quick turnaround! Looking forward to see your
> fix included in the regular download:-)
Of course, this will be the case. As David Mundie guessed it, the
'Alt-(' problem was just a very simple bug.
