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.

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.

Ok, I will use 'gpg-agent'.

In T5189#140364, @gniibe wrote:

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

It is really hard to translate 'keygrip'. First I think it is a unique identity code of the card, just like the fingerprint to a key. Could you explain that to me? How about use “匙柄”, like the WinAPI's “句柄”, or use “标识符”?

And any other suggestion?

v2 patch will submit soon after solve those problems.

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:

{Dxxx}

notation.

( I'm not native Chinese speaker. I only keep learning by 看电视学中文 of NHK in Japan).

Keygrip is an identifier which is used by gpg-agent for keys. It is a specific term for gpg-agent.
Keys under gpg-agent control are placed in .gnupg/private-keys-v1.d/<KEYGRIP>.key.
For me, "匙柄" sounds good.
Perhaps, it would be also good not to translate it, because gpg has an option --with-keygrip.

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

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

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

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)
• 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

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.

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.

I will modify these later weeks, thanks for remind.

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.

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.

patch of libgpg-error/po/zh_CN.po
D516: po: Update simplified Chinese translation po/zh_CN.po

Thank you for your effort. I'll review.

For PO file editing, what I use (for Japanese Translation) is:

• Emacs PO mode: https://www.emacswiki.org/emacs/PoMode

There are actually tools for PO file editing:
http://docs.translatehouse.org/projects/localization-guide/en/latest/guide/tools/trans_editors.html

For PO file editing, what I use (for Japanese Translation) is:

• Emacs PO mode: https://www.emacswiki.org/emacs/PoMode

There are actually tools for PO file editing:
http://docs.translatehouse.org/projects/localization-guide/en/latest/guide/tools/trans_editors.html

Thank you, I pick up 'poedit' now :-)

And patch of libgpg-error/po/zh_TW.po
D517: po: Update traditional Chinese translation po/zh_TW.po

Pushed the change for libgpg-error zh_CN.po.

It takes time for me. I need some rest today. :-)

It's in rE9b288ec583c0: po: Update Simplified Chinese Translation..

Reviewed D517 and pushed it as rE621446d3c859: po: Update Traditional Chinese Translation..

And, for the maintenance of GnuPG, it is better that it is checked by native speakers. I hope @chyen will keep update for zh_TW locale.

For D515, I think that there is similar issue, and I received another patch from Debian.

In T5189#140669, @gniibe wrote:

Reviewed D517 and pushed it as rE621446d3c859: po: Update Traditional Chinese Translation..

Thanks！

And, for the maintenance of GnuPG, it is better that it is checked by native speakers. I hope @chyen will keep update for zh_TW locale.

Hope he/she could help with that.

In T5189#140671, @gniibe wrote:

For D515, I think that there is similar issue, and I received another patch from Debian.

OK, D515: update gnupg doc/help.zh_TW.txt closed now.

gnupg/po/zh_CN.po sitll on working, too many entries.

Hope he/she could help with that.

Well, in general I only translate strings I encountered, and from my daily usage seems most strings in GnuPG and related software are already translated :)

I think that there is similar issue, and I received another patch from Debian.

I'm willing to have a look, but I didn't find the Debian's patch. Mind to give a pointer?

update for gnupg po/zh_CN.po
D518: po: Update Simplified Chinese translation po/zh_CN.po
the update is so big, so please review when you are free, and do not be push
thanks for all help

And Happy New Year 2021 !!!

Sorry, I didn't read your message above, and it's applied and pushed to master, due to exactly same reason (it's so big).
It's easier (at least for me), when it's in git repo.

Please check following translations:

"do not detach from the console"
"do not use the internal CCID driver"
"do not use a reader's pinpad"

Those are explanation for the options to instruct gpg-agent or scdaemon, not do something.
It's not a text to users.

rG6850f21d08b2: po: Fix Simplified Chinese Translation. is a fix for adjusting columns; The number means the number of columns.
rGf4a8be0950ea: po: Fix Simplified Chinese Translation. is a fix for:

• SETERROR is a command name of pinentry which should not be translated.
• The message is expected to be displayed in four lines.

In T5189#140853, @gniibe wrote:

Please check following translations:

"do not detach from the console"
"do not use the internal CCID driver"
"do not use a reader's pinpad"

Those are explanation for the options to instruct gpg-agent or scdaemon, not do something.
It's not a text to users.

I have fix that in D520: gnupg po: Fix Simplified Chinese Translation
If you have any other suggestions, please tell me to fix all of them in this patch to avoid lengthy git history.
Thank you :-)

D520 is accepted by me.
If you will have another fixes, please go ahead.
Or else, I'll commit the change to master of GnuPG.