[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [nmh-commits] [SCM] The nmh Mail Handling System branch, master, upd
From: |
Ralph Corderoy |
Subject: |
Re: [nmh-commits] [SCM] The nmh Mail Handling System branch, master, updated. 1.8-RC1-9-g68228e3c |
Date: |
Mon, 02 Jan 2023 15:56:13 +0000 |
Hi Ken,
> man/burst.man: re-word to avoid ‘digestifying’, etc.
...
> when the email is sent out about the change I get them a little
> mangled because the script that notifies about changes doesn't mark
> that email as UTF-8.
Agreed, it doesn't. They arrive as valid UTF-8 here which show just
fine so I hadn't noticed a problem, but it's clearly wrong. I expect
it's a bug in the script but have forgotten where is it to be found.
> It looks like you CAN mark the encoding of commits using the config
> variable i18n.commitEncoding, although this suggests the default is
> UTF-8 and when I look at all the commit encodings they are blank, so
> maybe I don't quite understand it?
git-commit(1) covers it. The default for the log message is UTF-8. If
the i18n.commitEncoding you gave is set then its value is copied into
the commit's header. If that header isn't present then the log message
is UTF-8.
> I don't know if that would change the encoding marked in the
> notification email.
I doubt it. I think the script probably pre-dates the popularity of
UTF-8. :-)
--
Cheers, Ralph.