unicode word joiner character (WJ U+2060) inhibits ligature selection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pango1.0 (Ubuntu) |
Incomplete
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: libpango1.0-0
I've had a guess at the package that is the source of this bug. it seems to be present in gtk widgets at least. Seen in Ubuntu Hardy.
This problem can be reproduced with the standard ubuntu serif font.
1) open the gnome text editor, type 'fi' (eff, eye) - ensure that your font shows them joined with a ligature by inserting a space to see if one or both characters change shape as they separate.
2) remove the space when satisfied so the ligature reforms or select a new font and larger size until you are satisfied and /then/ remove the space to reform the ligature.
3) open the gnome character map, find the word joiner character (WJ) in the general punctuation block, code U+2060 (it might be displayed as a blank oblong).
4) ensure the text area is empty (so the copy button is greyed out).
5) double click the character (or select it then press space), click the copy button next to the text area.
6) place the cursor between the f and the i in the gnome text editor
7) paste the word joiner character at the cursor position, the characters should not revert to the shapes that they had when there was a space between them but should remain joined by a ligature. But pango currently lets the WJ codepoint inhibit ligature selection, this is unexpected and incorrect.
Unicode 5.1 section 16.2 discusses the purpose of U+2060, where it is stated that it should only affect word boundary calculation (removing what would otherwise be a word boundary) and it should be ignored for ligature selection.
"In particular, inserting a word joiner between
two characters has no effect on their ligating and cursive joining behavior. The word joiner
should be ignored in contexts other than word or line breaking."
thank you for your bug report, the issue seems to be an upstream one, could you open the bug on bugzilla.gnome.org where people writting the software will read it? it's not likely somebody will work on that in an ubuntu specific way