> This comment appears to have been stripped out, does that mean that we > now *do* try to demangle keywords on utf16? Good point. I guess the comment should stay. Though really... I'm not sure what we should do with utf16 files. Currently the RCS keywords just won't be resolved, with no warning for the user! I guess we could resolve them, if we had a reliable way of detecting UTF-16?
