[Etoys-notify] [JIRA] Resolved: (SQ-195) Composite characters not displayed correctly

jira at immuexa.com jira at immuexa.com
Wed Apr 29 18:21:46 EDT 2009

     [ http://tracker.immuexa.com/browse/SQ-195?page=all ]
Scott Wallace resolved SQ-195:

     Resolution: Complete
    Fix Version: M1: first alpha (may)
                     (was: triage)

Known manifestations of the problem are worked around with etoys updates 2155buddyFix-bf and 2156composeTitle-bf.

> Composite characters not displayed correctly
> --------------------------------------------
>          Key: SQ-195
>          URL: http://tracker.immuexa.com/browse/SQ-195
>      Project: squeakland
>         Type: Bug
>   Components: etoys-sugar
>     Reporter: team
>     Priority: Eventual
>      Fix For: M1: first alpha (may)

> From TRAC Ticket #8351 (bert, sept 2008)
> 8.2-759: was sharing with a buddy having an umlaut in his name ("grün"). Sugar does not normalize the nick name (#6125) which makes it show up decomposed ("gru?n") in Etoys. Pango would correctly render this.
> (yoshiki) SugarBuddy class>>fromDictionary: has a composeAccents send, but the problem takes different control path?
> (bert) The composeAccents send is only used for authorName not for the Buddy itself ... I'll fix. Should this be added to other places where we get strings from sugar?
> (yoshiki) I cannot tell all possible implications, but the other end should be ok if we just compose to precomposed chars when possible,
> (bert) Worked around be manually composing the name as received from the presence service (2155buddyFix-bf). Same thing for the activity title as found in the datastore metadata (2156composeTitle-bf).
> Ideally, Sugar should normalize all its strings (#6125).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

More information about the Etoys-notify mailing list