> Maybe. Does a "composing_char + a_given_char" = "another_given_char" > in UTF-8 or USC-2? If yes and a table can be found somewhere we can add > an other converter (as FBidiJoint.c). If not we should draw string > char by char and take care of these composing characters (I do not like > so much this solution). A last solution is to use Pango, but it is not > the direction we have taken so far.
I think composing is a little more complicated than this. If I understand correctly the spec. several composing chars can follow a character forming a new character, so that for each composable character there is forms for all combinations of composing chars, but the order of composing chars is irrelevant. So for example "a" + "umlaut" + "cedilla" would be the same as "a" + "cedilla" + "umlaut". So a solution would be to sort all composing characters following a character and map the resulting "substring" to a precomposed character. //Marcus > > Can you send me the fvwm config which allows you to produce > composing_fvwm_bad.jpg. > > Regards, Olivier > -- > Visit the official FVWM web page at <URL:http://www.fvwm.org/>. > To unsubscribe from the list, send "unsubscribe fvwm-workers" in the > body of a message to [EMAIL PROTECTED] > To report problems, send mail to [EMAIL PROTECTED] > -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
