On 3/29/17, The Tick <the.t...@gmx.com> wrote:
> 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?

The default formatting for comments is Wiki markup.  You can change
this for each repo using the Admin/Timeline menu.

Fossil users usually do not follow the Git convention of providing a
one-line description on the check-in, followed by a blank line and
logs of additional comments.  That just never has caught on.  You can
do that, though.  Notice on the Admin/Timeline page the "Truncate
Comment At First Blank Line" setting.

>
> 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.

Fossil will use UTF-8.  So if you want Fossil to display the &copy;
correctly, you'll want to insert it as UTF-8.  Apparently gvim is
using some codepage of some kind.  So if you want &copy; to display in
gvim, you have to use the the appropriate codepage value.  These are
incompatible requirements.  You have to choose one or the other.

Most of the world is using UTF-8 now.

>
> 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?
>

You could use the three-character ASCII sequence "(C)" instead of the
one-character &copy; symbol.  Or, you can simply spell out the word
"Copyright".  I do the latter.

-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to