I don't think that we need to fix things here. Important is that the WKD import uses a filter which imports only keys with the requested mail address. However, if a key with the same fingerprint already exists it will be merged.

What I found: When the page is served by the server, it omits "charset=utf-8" part. This is the issue.

Thanks for fixing.

There won't be any semantic changes for obvious reasons.

Thanks for reporting.

The first thing is a problem of the GNU makeinfo tool. Can't be fixed int the source.

But then again: The three other apostrophes that occur in the text are represented by single quote characters. Maybe sticking to ASCII characters is the better fix after all.

Typographically the apostrophe character ’ is a different character than the single quote character '. So, the correct fix would be to fix the probably wrong encoded apostrophe instead of replacing it by a single quote character.

Changed the tags and the title.

Fixed in libgpg-error.

Thanks for you patches. Most of them applied cleanly despite that I delayed processing them for half a year.

There are reasons why we don't used pcsc-shared by default; for example: Not all OpenPGP cards support reading the current verification state (whether a PIN has already been entered) and thus we use a local cache for this. Other shared applications may change the state behind our back or even switch to another application on the card. Thus we use the safe way.

Thanks

The primary version of that script is in libgpg-error. Thus it needs to be fixed therefirst.

I would prefer to store legacy manuals on the web server. That is the easier solution.

@werner, because we have talked about it:

It would be convenient if the -c option could be easily set in the gpg-agent.conf or in some configuration file for pinentry. The workaround that I use now to create a script that I can then use as pinentry-program is extra work because it requires an additional script.

Well, as I've said in the comment above, there doesn't seem to be any correction towarads --passphrase-fd not requiring --pinentry-mode loopback (still works withou)... and --no-default-keyring still gives the impression that it would be needed (while --no-keyring works as well).

Please don't, if you really feel like tha tis not resolved please re-open this ticket.

@werner shall I open a new ticket for the remaining stuff?

The changes do not seem to touch anything I've mentoned in (1)?

Yes, --no-keyring should enough for the subset of gpg commands which do not need keys.

I think the behavior makes perfect sense for Unix but the default delimiter for .txt in Windows is \r\n.

The OP wants to do symmetric encryption. This isn't about the passphrase that protects a key.

Yes, we read up to the first LF. This has been the traditional way of PGP2 and is still used by mail programs like Mutt.

I'm guessing gpg in Unix has stripped the \n if present? I don't have access to a real Unix system at the moment.

I see that problem but gpg has traditionally not interpreted the passphrase in any way. Right, for Windows we could strip the CR but I fear that this might break other users scripts/passphrases. However there should be a warning in the manual.

I have rather created D536 as IMO the timeout should be changed, not the documentation.

Actually we considerto remove this feature from the GUI because with the global config we have a more versatile feature now.

Won't be done because the expectations of users are different on whether they use ssh-agent or gpg-agent. And it breaks scripts

Done. FWIW. in 2.3 symcryptrun will be removed entirely.

See also https://gitlab.com/openpgp-wg/webkey-directory/-/issues/3 which is the same issue.

Sorry, we won't apply such changes. A couple of years we did this and all we earned were a few extra bugs aqnd useless diffs. Further many of those changes are in files which will be updated from upstream time to time and your chnages would be lost.

OK, I only edited documents and notes, no code changes.

Thanks. However, we need to go over the list one by one to decide this. For example
"http://gnupg.org/.well-known/openpgpkey/hu/12345678" is actually expected to return a 404 and test code may very well use http:

This ambiguity appears to be the cause of a recent epic (and to me, largely incomprehensible) thread on gnupg-users. It would be great to have the WKD guidance about fallback strategy be much more explicit. Any room for ambiguity here leads to different outcomes from different WKD clients, and quite a bit of confused discussion by their users.

In T5189#140595, @gniibe wrote:

Please note that many error messages are defined in: https://dev.gnupg.org/source/libgpg-error/browse/master/po/zh_CN.po
and https://dev.gnupg.org/source/gnupg/browse/master/po/zh_CN.po

Sorry, in case you already know that.

May I ask that how to get a new complete clean po file.
I'm not familiar with gettext.
The old one is confusing, and I think maybe I should completely clean the messy.
Really a big project.

Frankly, I more or less forgot about these help files. The German version for sure needs an update as weel.

In T5189#140595, @gniibe wrote:

Please note that many error messages are defined in: https://dev.gnupg.org/source/libgpg-error/browse/master/po/zh_CN.po
and https://dev.gnupg.org/source/gnupg/browse/master/po/zh_CN.po

Sorry, in case you already know that.

In T5189#140594, @gniibe wrote:

For D515, I will also apply it to master.

Before that, I'd like to confirm an editorial change of mine:

• Remove an extra space before new line (two places)

Please and thanks, I imitated the English edition format :-)

• Remove a comment for use case of the file
  • If needed, we could have support of another locale(s) with Chinese language: zh_HK, zh_SG, etc.
  • It is not us, but it's users who decide which locale is better for them
    • E.g., my friend in Düsseldorf uses ja_JP locale
  • So, it's technically better not to address restriction in a translation

for that, I think you best keep that.
Use a locale to distinguish Chinese users always cause problems.
There isn't a big difference between the written language. And small region always lack translations.
Singapore's users who use simplified Chinese always use zh_CN if there is no a specific zh_SG.
And the traditional Chinese users from HK SAR and MC SAR sometimes use the translation for Taiwan Province.
So when translate it, the tip remiand you must consider all the users from anywhere.

Please note that many error messages are defined in: https://dev.gnupg.org/source/libgpg-error/browse/master/po/zh_CN.po
and https://dev.gnupg.org/source/gnupg/browse/master/po/zh_CN.po

For D515, I will also apply it to master.

Applied D514 to master, with an editorial change (removing extra space before newline).

also update doc/help.zh_TW.txt by the way
D515: update gnupg doc/help.zh_TW.txt

upload the v2 patch and create a revision
D514: update gnupg doc/help.zh_CN.txt
waiting for review
:-)

Please not that you can use this interface: https://dev.gnupg.org/differential/
I think that it is better when you update your patch. You can just refer a patch from this task by:

In T5189#140362, @gniibe wrote:

Do you call gpg-agent as 'Gpg 代理'? IIUC, it is better keep it as is (gpg-agent), because it is the name of the program.

If translated, 'keygrip' should be different word to 'fingerprint', because 'fingerprint' is used as a technical term of OpenPGP.

Do you call gpg-agent as 'Gpg 代理'? IIUC, it is better keep it as is (gpg-agent), because it is the name of the program.

Thanks.