User Details
- User Since
- Dec 19 2020, 10:20 AM (206 w, 5 d)
- Availability
- Available
Oct 22 2022
Apr 26 2022
catch the newest version
full git formatted patch here: https://fars.ee/LN-i.patch
Apr 23 2022
Apr 14 2022
Thanks, good explanation!
It is hard to find a word for exact description.
Thus just keep the original verb and add 比特 to confirm 位 is binary bits.
Apr 13 2022
Apr 22 2021
Thanks for your review!
Apr 21 2021
Feb 25 2021
Fix that, thanks for your review.
I recently switched to a new input method program and lost my preference historys, resulting in these homophonic errors.
Feb 22 2021
Feb 21 2021
Feb 8 2021
Done all comments.
Partly understand, so 'core' means 'core-memory', and for nowadays just 'memory'.
Feb 5 2021
Jan 28 2021
Jan 26 2021
OK, I only edited documents and notes, no code changes.
Jan 25 2021
Jan 10 2021
I think the main work of listed translation update has been completed, and other minor problems will be corrected in the future patch.
Jan 6 2021
Jan 5 2021
Jan 1 2021
Dec 30 2020
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
Dec 28 2020
gniibe received another patch from Debian.
Dec 26 2020
Got that, thank you :-)
Any other suggestion?
Dec 24 2020
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
use poedit to rebuild it
Dec 23 2020
patch of libgpg-error/po/zh_CN.po
D516: po: Update simplified Chinese translation po/zh_CN.po
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.
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.
Thank you for your review!
:-)
And how to mark this revision passed?
Dec 22 2020
In Chinese, “密钥” make a general reference to secret keys, public keys and key-pairs, it has a broad meaning.
Dec 21 2020
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
:-)