Re: Git Commit Signature Encoding

> Hi Philippe,
> 
> thanks for getting back to me so quickly! And sorry for not providing all the details right away.
> 
> I'm using Git 2.30.0.windows.1 (I believe that's the latest), gpg 2.2.27 (installed via gpg4win 3.1.15), and PowerShell 7.1.1. You might have seen my second email to the list in which I described that setting the OutputEncoding in PowerShell to UTF-8 fixed at least the display of the é (and probably all other umlauts and special printable characters). The signature output from git show --show-signatur is still printing the ^M carriage return character at the end of each line:
> 
> commit 69022a47744fcb3801572ac5d14295bcab274295 (HEAD -> master)
> gpg: Signature made 26.01.2021 17:55:36 W. Europe Standard Time^M
> gpg:                using RSA key 3848D5B2A3D45419D7F564F97802B995CDB4A2EF^M
> gpg: Good signature from "René Schumacher <rene.schumacher@microsoft.com>" [ultimate]^M
> gpg:                 aka "René Schumacher <reneschu@microsoft.com>" [ultimate]^M
> Author: René Schumacher <reneschu@microsoft.com>
> Date:   Tue Jan 26 17:55:36 2021 +0100
> 
>      another commit with signature
> 
> diff --git a/file1.txt b/file1.txt
> index a7f8d9e..6ddadea 100644
> --- a/file1.txt
> +++ b/file1.txt
> @@ -1 +1,2 @@
>   bla
> +blub
> 
> Since git verify-commit does not have those carriage return characters, I'm still wondering where they might come from.
> 
> Cheers,
> René