2014-11-11 12:50 GMT+01:00 Stephan Beal <sgb...@googlemail.com>:
> Hi, all,
>
> this just came across the moderation requests...
>
> http://fossil-scm.org/index.html/tktview/5a0a33f31a7a7915bf8e78d0b1395c9879dfc6c5
>
> Management summary: encoding is not honored with the -M FILENAME option to
> commit (which reads the commit message from a file).
>
> If one of the Windows users can point me in the right direction, i'll patch
> this (-M was originally added by me, IIRC).
The convention on Windows is to assume CP1252, unless the file
starts with the UTF-8 BOM. That's exactly what fossil is doing here:
<http://fossil-scm.org/index.html/artifact/cbd7a598c8?ln=1745-1747>
So, make sure that the file starts with the UTF-8 BOM, otherwise
fossil cannot make any valid guess on what encoding is used.
Assuming UTF-8 on windows is wrong, because if it is really CP1252
then that leads to invalid utf-8 byte sequences.
Regards,
Jan Nijtmans
_______________________________________________
fossil-dev mailing list
fossil-dev@lists.fossil-scm.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
