Cool. I think a well-defined algorithm for defining a flagged character is important, to get cross-platform/application support and to validate the algo. (Any b

Cool. I think a well-defined algorithm for defining a flagged character is important, to get cross-platform/application support and to validate the algo. (Any bug in the algo is a possible security hole, moreso if people become to trust that any dodgy characters are highlighted). An exposed API to handle UTF8 strings to get count and/or indices of flagged chars would also be useful. Perhaps it could work as an extension to ICU? http://site.icu-project.org/ http://site.icu-project.org/ If nothing else, the "change language within a word" should use a unicode-sane definition of 'word', which ICU would give you. Once you have the two pieces above, adding the colouring etc should be reasonably straightforward. But it'd be a shame if the two pieces above weren't factored out - since I don't think the widespread adoption would follow otherwise.