-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 An afterthought, and to get back to the original problem: The fact that source-highlight users didn't stumble upon the unicode problem earlier may be that AFAIK for source-highlight, a string from a source file in means the same string out, without doing much more than pre- and suffixing it with the appropriate tags (I'm oversimplifying here, but that's my "good enough" mental model of how it works). So, why does the OP experience this issue? As the output is HTML, may it be that the HTML is simply bearing the wrong encoding in <head>? If so, perhaps this can be fixed w/o much hassle around making source-highlight Unicode capable? (Not a solution for eternity, though.)
Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuySgYACgkQ0qFE1uHKpVekqgCghDV29H76A0+FfB0w4LtBkDi1 kWEAn1JBTo+K9o+auHLVvMhq+59WshBw =sY8o -----END PGP SIGNATURE----- _______________________________________________ Help-source-highlight mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-source-highlight
