Note: this no longer crashes XEmacs. It probably doesn't cause a problem in
practice, as anybody who really wants to work with charsets would use the
fontconfig facilities rather than playing with the string representation.
Currently (XEmacs 21.5.35) use of FcNameUnparse is protected by deleting any
FC_CHARSET property first. It would be nice to determine if this is
necessary.
History
Date
User
Action
Args
2014-10-18 11:28:48
stephen
set
messages:
+ msg2535 severity: inconvenience -> inelegant title: Track down "charset" crash in FcNameUnparse -> Track down "charset" problem in FcNameUnparse