The problem is that this resource is stored as char* in Simple.c (see XtNewString() call), but is used as XChar2b* in Tip.c when XtNinternational is True.
The real problem is that simpleWidgetClass has neither XtNinternational, nor XtNencoding resources. simpleWidgetClass still has "XtPointer pad[2]" free, so it should be possible to extend it. Any objections? Another question is why do we actually need those both resources? Encoding is more expressive information, so I suggest to prefer it over international flag. Yet another idea: Tip.c contains a lot of code that manages multiline strings in windows, but the same stuff is done in Label.c and it should be possible for tipWidgetClass to handle only events and timers and use labelWidgetClass to draw the actual string. Any objections on this? Please CC me on reply. Thank you! -- Alexander Pohoyda <[EMAIL PROTECTED]> PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44 _______________________________________________ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
