Thus said Stephan Beal on Tue, 08 Jul 2014 23:50:40 +0200: > Interesting question/option, but i have no answer. Something to > possibly consider?
Or perhaps just making the documentation more clear that all files must be valid UTF-8. There is already an option to control how encodings are handled, and it is versionable (which means that I can include it with the repository so others won't get warnings if they modify it). I see the setting mentions it here, but I don't recall ever reading anything that indicated that I would get a warning for invalid UTF-8. http://fossil-scm.org/index.html/help/setting This could just be a tool acclimation problem on my part. :-) Andy -- TAI64 timestamp: 4000000053bc6b46 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users