Thus said Stephan Beal on Tue, 08 Jul 2014 21:37:50 +0200: > No characters between 128 and 255 are valid UTF-8, to avoid confusion > with the many encodings which use that range.
If no characters between 128 and 255 are valid UTF-8, and they can never be valid UTF-8 characters, and are used by many encodings, why doesn't Fossil simply ignore them when they are committed? I guess I'm confused why they are being treated specially as to warrant either a setting or a prompt to continue. Thanks, Andy -- TAI64 timestamp: 4000000053bc6637 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
