Jul 29 2022
It is unlikely that the tofu stuff will get into widespread use in the 2.2 version - if at all.
Jan 22 2022
Jan 20 2022
Jan 10 2022
That seems to (mostly) work partially fix PowerShell pipeline output at least:
Oct 1 2021
Sep 29 2021
Hello again Werner,
Ok, but the problem is that by default CMD command windows do not use any Unicode set of characters, and their default font is 'Raster characters' and the typical display of characters inside these windows, at least for Italian people because this was the default since MS-DOS age, is to only consider using MS-DOS ASCII codepage 850, not Unicode.
And this is also why before showing the error message I ran the command mode.
Anyway because of the 2 characters getting displayed instead of single expected 'è' (whose character code is 0x82) I can also tell you that by using Charmap.exe again (just in case you may not know it allows display of any Unicode or Raster font characters and their hexadecimal codes) and so switching its default font from System (Unicode) to 8514oem (raster, corresponding to 8514oem.fon) I've been able to determine which should be the 2 wrong displayed characters hexadecimal codes : 'Ã' (0xC3), and '¨' (0xA8) but here obviously both characters cannot be represented correctly because this site is using 'Segoe UI' font, which is Unicode too.
So the only main way to check that I identified the correct characters will be if you (or someone else you know) with another Windows client run Charmap.exe switch font to 8514oem (raster) and check that displayed characters corresponding to 0xC3 and 0xA8 are the same that got displayed in the error message bitmap I provided (a part from probably being able to find where in Italian messages localization rather then in source code those 2 characters have been used incorrectly).
P.S. Because in a past similar bug about Italian localization I saw a comment from you about this kind of option, please just let me know in case you think I might possibly be able to help you to review involved 'GPG' Italian error message(s) for this bug.
Sep 28 2021
That pretty much looks like the other errors you have with Unicode characters - which we can't replicate.
Aug 13 2021
Jul 6 2021
Jun 17 2021
Thank you.
Thank you.
I apply Diff1487 then Diff1488.
Jun 15 2021
Jun 14 2021
Thank you. Here are my comments.
Hi, I updated the whole file, PLZ review. https://dev.gnupg.org/D533
Jun 13 2021
Thank you for your suggestion and making a patch.
Sorry, I think, it is more official to update from 把密钥导出到一个公钥服务器上 to 将密钥导出到一个公钥服务器上 in the Chinese doc scenario. 😄😄😄😄
Jun 11 2021
Jun 10 2021
Pushed the change.
Considering the history of the translation, I concluded that it should be:
把密钥导出到一个公钥服务器上
(the typo was G-A where B-A was expected.)
@guzhongren
This is not GitHub, so, if you want, you need to learn how to submit your change in the form of patch, by using git.
Jun 9 2021
Clone and checkout the branch as usual with Git. There is no web editor etc like you might know from github. For your request we need to wait for someone to check your request.
May 8 2021
Apr 15 2021
Thank you. Merged and pushed.
Apr 10 2021
Feb 1 2021
Thanks for the feedback. I sadly forgot to include the italian translations of GpgOL in the installer. So they will only be part of the next relase.
Jan 29 2021
Problem solved in Gpg4win 3.1.15 version! I think it can be closed!
Jan 23 2021
Hi,
you can close this tickets, the Italian translation has already been uploaded successfully. Don't import anything to GnuPG. Thanks a lot!
Jan 22 2021
Argh! I had added the translation to GpgOL but forgot to list the file in our installer. So it will only be part of the next version.
Jan 5 2021
Nov 3 2020
The whole TOFU stuff hash not yet been fully translated because there are conceptional problems with the way the code works.
Oct 10 2020
Hello,
I finished the Italian translation of the GnuPg 2.2 file.
I need help, can you please update the source project with this translation? I am a beginner, unable to do this.
I attach files translated into Italian
Oct 6 2020
Oct 3 2020
The name field is marked as optional but it is mandatory. This should be fixed.
Sep 30 2020
Hi,
I corrected all the accents. I created a PR here https://github.com/gpg/gpg4win/pull/3
Jul 2 2020
Your welcome.