Haha, it would be quite a mess if $ and @ triggered binary. I see no reason to kick the file to binary if the ascii code < 128?
On Thu, Nov 5, 2015 at 3:46 PM, <sky5w...@gmail.com> wrote: > No difference besides num bytes with or without the embedded Ascii > characters 2 and 6. > I add this 1 line to my file and it triggers binary?! > [Asc2]+"123 "+[Asc6][CR+LF] > > c:\tryfossil>fossil test-looks-like-utf myfile.txt > File "myfile.txt" has 121343 bytes. > Starts with UTF-8 BOM: no > Starts with UTF-16 BOM: no > Looks like UTF-8: yes > Has flag LOOK_NUL: no > Has flag LOOK_CR: yes > Has flag LOOK_LONE_CR: no > Has flag LOOK_LF: yes > Has flag LOOK_LONE_LF: no > Has flag LOOK_CRLF: yes > Has flag LOOK_LONG: no > Has flag LOOK_INVALID: yes > Has flag LOOK_ODD: no > Has flag LOOK_SHORT: no > > On Thu, Nov 5, 2015 at 3:21 PM, Warren Young <w...@etr-usa.com> wrote: > >> On Nov 5, 2015, at 11:37 AM, sky5w...@gmail.com wrote: >> > >> > I am also trapped with this binary file detection for the egregious use >> of ascii characters 2 and 6 in my code. :( >> >> What does “fossil test-looks-like-utf filename” say for that file? >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
