1) When I did a commit, I formatted the commit message very nicely. After the commit, it's just a big blob of text. That certainly defeats the purpose of making a commit message of any detail.

What is the standard practice with this? Keeping a separate "changelog.txt" where the details are listed? Now I've got another file to keep accurate?

2) My source has a couple of characters like copyright and the multiplication 'x' and I get this message from fossil:

./Guide.tcl contains invalid UTF-8. Use --no-warnings or the "encoding-glob" setting to disable this warning.
Commit anyhow (a=all/c=convert/y/N)?

I set encoding-glob to *.tcl so now the message goes away.

I've read this: http://fossil-users.fossil-scm.narkive.com/6Ci1qs0J/file-contains-invalid-utf-8-but-is-not-utf-8

As that post mentioned, my © symbol remains but fossil shows the file with a black ? in place of the ©.

I use gvim and switching to a different editor is something that will never happen.

I tried saying 'c' for convert and fossil made a new file with "real utf-8" characters in the place of the originals.

The copyright symbol is something that I really want in the source file -- it's in a comment but that is beside the point. It needs to show as a real copyright symbol when the file is edited >and< viewed. As far as I know, gvim does not have a way to convert the goofy "real utf-8" sequence to a copyright symbol so I cannot see the © when I edit the file >nor can I insert a real utf-8 copyright symbol<. Also neither notepad nor another file viewer shows the "real utf-8" copyright symbol correctly in a "converted" file.

Is there any solution to this?

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to