On Mon, 21 Jan, Jan Nijtmans wrote: > This patch is now in trunk already, but I'm just wondering if the > "unicode-glob"wouldn't better be named "encoding-glob". The > actual purpose of this warning is not whether some file > contains unicode, the fact that the encoding is known > to be not UTF-8 is what's really matters: those files > cannot be displayed correctly in the fossil web UI.
Well, then the question is whether not just allow to commit everything (regardless of the file content) and guess the encoding for display purposes in the web UI. This can be a 2-step approach: First look for a BOM and use that as encoding indicator, if no BOM is present, call the encoding heuristic code from UNIX tool "file" (licensed under a 2-clause BSD license). This code compiles on a variety of platforms and we successfully use it on 32-bit and 64-bit configurations for GNU/Linux, Windows and Solaris to guess the encoding of files at work. Greetings, Stefan -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
