KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.17
System : Linux localhost 2.6.18-419.el5 #1 SMP Fri Feb 24 22:47:42 UTC 2017 x86_64
User : nobody ( 99)
PHP Version : 5.2.17
Disable Function : NONE
Directory :  /usr/share/locale/zh_TW/LC_MESSAGES/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //usr/share/locale/zh_TW/LC_MESSAGES/gnupg.mo
%+Jb-bbmcvddXeqeeeeef!f2>f7qf2f#fDg.EgItg7gghh7hOhihhhhhh+i&4i#[i(ii"iij( jIjbj$jjj&jj,k@k]k!tkkkkkkll*l?l\lnlllll*l"m]3mBmm/m=n(Un.~n3n!n(o,oGo'Oowoooooo,
p'7p_p{p"ppppBp=6qtq"q%q&q!r%%r"Kr#nr'r rrr
s*s?sWs(hs$sss#st"tAt!`ttt tt&t%uDu,Pu4}uuvvvvv'w(wDwbwtww w'ww"wx;x-Lx(zx0x2xHy	PyZzgztzzzzAz/${0T{\{1{|D)|-n|0|.|I|*F}+q}'}}}}}~0~I~^~e~~3~4~-~-'.>$G	l	v
?4΀:>]{Ɓ#&
(1&Zł7΂6-=%k39Ń0<0Gm@>+5=a"х
:&a#t /ކ߇H-B$p'8&5.S5*.0&C,j
͊؊8#$Ha"h.HS"($E
S;%َ81$jЏ_{בBNdw%֒ޒ	.%T* !70Y'<"
,-/Z1",ߕ"2/b ~( Ȗ
*1L`yۗ"~И+G= 1%ؙEEoI  ڛ7'Ü>*c/NNE,"#3-W+)&۟'Ǣݢ*+F,r3ӣ1ߣ('#P+t"+ä" 3?G%ȥۥ< Z}{/(0X!٩ީ!&<Us%ԪݪJjG-9mO0/(5X'.-$!1S$o,(߱-L_/Liv*+ @Yu	6%Ѵ7Irɵ><1{=I45j#=?DK@+Ѹ1N/I~Iȹ55H;~?B<=Hz-ûH:ļ<߼B)_C:ͽ.>72v=<@$FeHU-K2y1I@(>iKB@75x,*7.>,m004 12Rh*&:1a#2>)*=0DMu"&!
3/>cc%D,,q52_(






	
(A%Z")+5Ohw
.
B#f
!(7`w" =,Z'.%27HYn:>?;\%54=
P;^<	1E_x:+&<cy-;
()?^z1*B,[H
4?Vc0$=%Rx '#8Kbz'&#&C&j"9KU%$&$8U'\$-@4u
$!#5LD`+/
(":%]%$
.;Tp2	'!IY/t+$&-$T'y,,
>" a$,IJN"# ;!\~*-$F'k ."+)2#\-65/;k";0"6%Y/2!:3 n!!(+8(a!~402<6o)9
&5G\HB0Ll#*He
	.8Sl'.'Vh(q2! ,*WZ
x
$) 0%O%u,23.&b"1!
/Mb%%

	

" 0#Qu&x	)</E`6,;>V-.F"\-+&*5E6{!&$=O2dIF?Wj##)!Mo$*2.K`*
:%V|$#&$43E%y*%	-&	T	h	}		
			9	
5.
-d
"

 


% ?5`$+4%7!]*(0
$
&-
.T
-
*

:m+G2/O%F1#1U!r(-/,M	z") ,FO#l#!"-':FIA
	)<Lk ! BWk#
$8 Lm	66#R v*G
Un -,#=\ x
DFSEDE%Ak767=T>$7<K7F &G
^$i##*X)s  /(!X"t",##H#l# # #!# #"$23$2f$2$'$1$2&%>Y%;% %%&&+&"I&#l&%&&$&&'''C'$_''!'"''$(,(K(#c((( (()(")=)T)t))))))
)*"*<*R*b*r*"* *+*"+b#+P++B+N1,2,2,8,,-2L-!--0-#--.2.I.`.=.0.$./2/Q/V/s/M/D/ 0$60$[0$0$0$0$01 31T1s11&11&12%(2(N2w22(2%223&83_3}3.33'3!4*4$64*[4455555(
636M6i6y666%66(6$7D71Z7177737M*8x89
9*999:L :6m:9:p:AO;;E;&;,<#D<;h<"<"<<= =0=K=f=~===== =I>?[>>)A?#k??1????;?5$@5Z@ @@@@@"A'.A'VA/~A'AAAB&BP/B2B)B#B/C81C,jCDCJCA'D;iD)D>DEE,E)3E*]E/E&E E.F/F$EFjF{F!F*FFG4G&G*H/9H;iH7H5H5I6II!I-I3IJ*$JOJiJJJ*J JJK+K;DKKDL#QL,uL&L?L	MNMMNN$NEN 6OWOiOOOOTPQ<QQQkQQQQ^Q.RGR\RvR$R)R	RRRS55SlkS$S+S%)TFOT2T@T#
U&.U6UU6U6U&U9!V,[V9V'VV"
W-W
KW%VW|WWW WW&W& X&GX"nXwX+	Y(5Y^Y&vY"Y#YYLY0FZEwZHZ[[C[B[u:\\\\.](]>]^U^_C$_Eh_0__&_$`&?`&f`&``abbScnccccc c-c1)d-[dd&dd+d&e9-e-ge9e-e0e.f6Hf ffff&f&g&5g)\ggglii&i0iik%kAkHk`k#zkkk%kk/lClRlaljlIlfl*:mem5&nB\n)n)n,n0 o-Qo0o(op%qqq
r,r-Jr7xr:rr$s s8tPt_t!u@uVucu0u1u/u"v%5v%[vvvv;v&w*w3Jw}~wxw@ux7x:x=)y7gy+y)y:y 0zJQzNz<z.({.W{K{K{N|6m|1|B|A}R[}9}=}'&~EN~~!E>B+6;*'f:4ɀ443BhFN]A)*ɂ,?!?a<<ރ<9X33Ƅ00+0\-333#+W8(2 )-)W:76ʎA<CH#ɏ&#-8;fo*D=-35oG
Ĕ
Ҕ
)5>M
Zh-$Ε*-(LCuؖ31L~ D!
!
/=M]m}	ИӘ,3Jd"{)ؙ"7%B]&%ǚ)*='T|;AћC=W%&Ҝ>8	OY
p:~D,$I*nמ0!@Sfs,ʟ+ݟ@	J#W{ "
Ӡ<;Si
{(#NWn	{͢"AQ#n6$ɣ )&9,`,0 "8[&v&$ĥ)//Cs	

*.E4 z&§#;Nat%ШF Jk٩A6#x'Ī'ͪ	0#Tr.yȫ(	&D9[ܬ+2AR2ޭ;,X2(3	*=h)5˯ggi#Ѱ#)*C*n00ʱ""(A j')/ݲ+
09<j*1ҳ1'6'^6116!!X!z$36$,*Q3|6$'+=S$$۷*'&6N<ĸ35'Q6y9*E[lccVo%ƻ 
* D,e&ż&)#=a%x 	ɽ*@Vr$ܾ)>Z#a0.$
4)^au",++#ImD;,:L:%%
2Ol(# &
&1Xu'*%	AKj9"
2#8V=>*%Ci2(0&1Fx",(("Kc{(
/^+C 2S b!!,*0[h$(	?'I
q'&
"'J]w%<$T(y/>K'6-1+My$0 =2^/&+"3,V!$$*!'fI9#A(P7y&=',1T(-4/.d
23(%)N%x"#4"X:{DF"B	eo*Ib	'1Edw0
85T+%-)G
qJ49"F+i5!=YsQQIdBK8=:v6:=#Aa%'55'5]82)
H.S"&&gB>Axq\7
h	^=KU!>a]6d[V hh+Bv(N
SWJ2
rS`"N<xja_3Y_7L>$BH
DkmEj!RU]sC6n`EZ	 jyQ	;Q;^mj+,AT+*8!9_?Qm/w(W+R@X^zG{"JpV/e?-$F.]4-YX%]3.#Qsslvb)"Ct'|Pa`sw)w'ZR oMb\=n%XM[*R%wPKzzK0/y8kE!CirDexV&D/hTo7^Y567"kdr*:)#
s1JO$0lM:S~u,H'f(czO1i<e}ttv!n0_4O5'RI1=JNy)A#f@GBV9?wq&lF9] (`F8xeu&L%HY0pEvccmE[S);n+j2@@;86~,{.3XiS~&8/c2HFGD3<	,[QdWt_#vdO*ltbox*M49~ HXUL[6UN	7W\~q|U:9aTq1GPTa5\bo
A:bN#{pp?}Ig-CfePZ.K%u;'>mIfJ}2
Gupyo=AB0Zdg4L5l.$,I`Kk$-iY}<y|?
Z{h"VTgrqz^iCck=O-|:
MfPuLg(<|@D\r&35>2
}{Wn1FI4
Enter the user ID.  End with an empty line: 
Not enough random bytes available.  Please do some other work to give
the OS a chance to collect more entropy! (Need %d more bytes)

Pick an image to use for your photo ID.  The image must be a JPEG file.
Remember that the image is stored within your public key.  If you use a
very large picture, your key will become very large as well!
Keeping the image close to 240x288 is a good size to use.

Supported algorithms:

You need a user ID to identify your key; the software constructs the user ID
from the Real Name, Comment and Email Address in this form:
    "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>"

                aka "%s"               using %s key %s
              imported: %lu             unchanged: %lu
           new subkeys: %lu
          new user IDs: %lu
          not imported: %lu
          w/o user IDs: %lu
         "%s": preference for cipher algorithm %s
         "%s": preference for compression algorithm %s
         "%s": preference for digest algorithm %s
         (subkey on main key ID %s)         It is not certain that the signature belongs to the owner.
         The signature is probably a FORGERY.
         There is no indication that the signature belongs to the owner.
         This could mean that the signature is forged.
        new signatures: %lu
      "%s"
      Card serial no. =      Key fingerprint =      Subkey fingerprint:      secret keys read: %lu
      skipped new keys: %lu
      user IDs cleaned: %lu
     Subkey fingerprint:    signatures cleaned: %lu
   (%c) Finished
   (%c) Toggle the authenticate capability
   (%c) Toggle the encrypt capability
   (%c) Toggle the sign capability
   (%d) DSA (set your own capabilities)
   (%d) DSA (sign only)
   (%d) DSA and Elgamal (default)
   (%d) Elgamal (encrypt only)
   (%d) RSA (encrypt only)
   (%d) RSA (set your own capabilities)
   (%d) RSA (sign only)
   (0) I will not answer.%s
   (1) I have not checked at all.%s
   (1) Signature key
   (2) Encryption key
   (2) I have done casual checking.%s
   (3) Authentication key
   (3) I have done very careful checking.%s
   new key revocations: %lu
  %d = I do NOT trust
  %d = I don't know or won't say
  %d = I trust fully
  %d = I trust marginally
  %d = I trust ultimately
  Unable to sign.
  aka "%s"
  m = back to the main menu
  q = quit
  s = skip this key
  secret keys imported: %lu
 (main key ID %s) (non-exportable) (non-revocable) Primary key fingerprint: secret keys unchanged: %lu
"%s" not a key ID: skipping
"%s" was already locally signed by key %s
"%s" was already signed by key %s
# List of assigned trustvalues, created %s
# (Use "gpg --import-ownertrust" to restore them)
%d Admin PIN attempts remaining before card is permanently locked
%d bad signatures
%d keys processed (%d validity counts cleared)
%d marginal(s) needed, %d complete(s) needed, %s trust model
%d signatures not checked due to errors
%d signatures not checked due to missing keys
%d user IDs without valid self-signatures detected
%lu keys cached (%lu signatures)
%lu keys cached so far (%lu signatures)
%lu keys processed so far
%s ...
%s does not support handler version %d
%s does not yet work with %s
%s encrypted data
%s encrypted session key
%s encryption will be used
%s is the new one
%s is the unchanged one
%s keys may be between %u and %u bits long.
%s keysizes must be in the range %u-%u
%s makes no sense with %s!
%s not allowed with %s!
%s signature, digest algorithm %s
%s.
%s/%s encrypted for: "%s"
%s/%s signature from: "%s"
%s: There is limited assurance this key belongs to the named user
%s: There is no assurance this key belongs to the named user
%s: directory does not exist!
%s: error reading free record: %s
%s: error reading version record: %s
%s: error updating version record: %s
%s: error writing dir record: %s
%s: error writing version record: %s
%s: failed to append a record: %s
%s: failed to create hashtable: %s
%s: failed to create version record: %s%s: failed to zero a record: %s
%s: invalid file version %d
%s: invalid trustdb
%s: invalid trustdb created
%s: keyring created
%s: not a trustdb file
%s: skipped: %s
%s: skipped: public key already present
%s: skipped: public key is disabled
%s: trustdb created
%s: unknown suffix
%s: version record with recnum %lu
%s:%d: deprecated option "%s"
%s:%d: invalid export options
%s:%d: invalid import options
%s:%d: invalid keyserver options
%s:%d: invalid list options
%s:%d: invalid verify options
%u-bit %s key, ID %s, created %s(No description given)
(Probably you want to select %d here)
(This is a sensitive revocation key)
(sensitive)(unless you specify the key by fingerprint)
(you may have used the wrong program for this task)
* The `sign' command may be prefixed with an `l' for local signatures (lsign),
  a `t' for trust signatures (tsign), an `nr' for non-revocable signatures
  (nrsign), or any combination thereof (ltsign, tnrsign, etc.).
--clearsign [filename]--decrypt [filename]--edit-key user-id [commands]--encrypt [filename]--lsign-key user-id--output doesn't work for this command
--sign --encrypt [filename]--sign --symmetric [filename]--sign [filename]--sign-key user-id--store [filename]--symmetric --encrypt [filename]--symmetric --sign --encrypt [filename]--symmetric [filename]-k[v][v][v][c] [user-id] [keyring]... this is a bug (%s:%d:%s)
1 bad signature
1 signature not checked due to a missing key
1 signature not checked due to an error
1 user ID without valid self-signature detected
10 translator see trustdb.c:uid_trust_string_fixed@
(See the man page for a complete listing of all commands and options)
@
Examples:

 -se -r Bob [file]          sign and encrypt for user Bob
 --clearsign [file]         make a clear text signature
 --detach-sign [file]       make a detached signature
 --list-keys [names]        show keys
 --fingerprint [names]      show fingerprints
@
Options:
 @Commands:
 ASCII armored output forced.
Admin commands are allowed
Admin commands are not allowed
Admin-only command
Answer "yes" (or just "y") if it is okay to generate the sub key.Answer "yes" if it is okay to delete the subkeyAnswer "yes" if it is okay to overwrite the fileAnswer "yes" if you really want to delete this user ID.
All certificates are then also lost!Answer "yes" if you want to sign ALL the user IDsAnswer "yes" or "no"Are you sure that you want to sign this key with your
key "%s" (%s)
Are you sure you still want to add it? (y/N) Are you sure you still want to revoke it? (y/N) Are you sure you still want to sign it? (y/N) Are you sure you want to appoint this key as a designated revoker? (y/N) Are you sure you want to delete it? (y/N) Are you sure you want to replace it? (y/N) Are you sure you want to use it? (y/N) AuthenticateBAD signature from "%s"CA fingerprint: CRC error; %06lX - %06lX
Can't check signature: %s
Can't edit this key: %s
Can't open `%s': %s
CancelCardholder's given name: Cardholder's surname: Certificates leading to an ultimately trusted key:
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? Change (N)ame, (C)omment, (E)mail or (Q)uit? Change the preferences of all user IDs (or just of the selected ones)
to the current list of preferences.  The timestamp of all affected
self-signatures will be advanced by one second.
Changing expiration time for a subkey.
Changing expiration time for the primary key.
Cipher: Command expects a filename argument
Command> Comment: Compression: Create a designated revocation certificate for this key? (y/N) Create a revocation certificate for this key? (y/N) Create a revocation certificate for this signature? (y/N) Critical preferred keyserver: Critical signature notation: Critical signature policy: Current allowed actions: Current recipients:
DSA keypair will have %u bits.
Delete this good signature? (y/N/q)Delete this invalid signature? (y/N/q)Delete this key from the keyring? (y/N) Delete this unknown signature? (y/N/q)Deleted %d signature.
Deleted %d signatures.
Detached signature.
Digest: Displaying %s photo ID of size %ld for key %s (uid %d)
Do you really want to delete the selected keys? (y/N) Do you really want to delete this key? (y/N) Do you really want to do this? (y/N) Do you really want to revoke the entire key? (y/N) Do you really want to revoke the selected subkeys? (y/N) Do you really want to revoke this subkey? (y/N) Do you really want to set this key to ultimate trust? (y/N) Do you want to issue a new signature to replace the expired one? (y/N) Do you want to promote it to a full exportable signature? (y/N) Do you want to promote it to an OpenPGP self-signature? (y/N) Do you want to sign it again anyway? (y/N) Do you want your signature to expire at the same time? (Y/n) ERROR: Email address: EncryptEnter Admin PIN: Enter JPEG filename for photo ID: Enter New Admin PIN: Enter New PIN: Enter PIN: Enter an optional description; end it with an empty line:
Enter new filenameEnter number(s), N)ext, or Q)uit > Enter passphrase
Enter passphrase: Enter the name of the key holderEnter the new passphrase for this secret key.

Enter the required value as shown in the prompt.
It is possible to enter a ISO date (YYYY-MM-DD) but you won't
get a good error response - instead the system tries to interpret
the given value as an interval.Enter the size of the keyEnter the user ID of the addressee to whom you want to send the message.Enter the user ID of the designated revoker: Enter your preferred keyserver URL: Error reading backup key from `%s': %s
Error: Combined name too long (limit is %d characters).
Error: Double spaces are not allowed.
Error: Login data too long (limit is %d characters).
Error: Only plain ASCII is currently allowed.
Error: Private DO too long (limit is %d characters).
Error: The "<" character may not be used.
Error: URL too long (limit is %d characters).
Error: invalid characters in preference string.
Error: invalid formatted fingerprint.
Error: invalid length of preference string.
Error: invalid response.
Expired signature from "%s"Features: File `%s' exists. Give the name of the file to which the signature appliesGo ahead and type your message ...
Good signature from "%s"Hash: Hint: Select the user IDs to sign
Hit return when ready or enter 'c' to cancel: How carefully have you verified the key you are about to sign actually belongs
to the person named above?  If you don't know what to answer, enter "0".
How much do you trust that this key actually belongs to the named user?
I have checked this key casually.
I have checked this key very carefully.
I have not checked this key at all.
IDEA cipher unavailable, optimistically attempting to use %s instead
If you like, you can enter a text describing why you issue this
revocation certificate.  Please keep this text concise.
An empty line ends the text.
If you want to use this untrusted key anyway, answer "yes".In general it is not a good idea to use the same key for signing and
encryption.  This algorithm should only be used in certain domains.
Please consult your security expert first.Invalid character in comment
Invalid character in name
Invalid command  (try "help")
Invalid key %s made valid by --allow-non-selfsigned-uid
Invalid passphrase; please try againInvalid selection.
Is this correct? (y/N) Is this okay? (y/N) Is this photo correct (y/N/q)? It is NOT certain that the key belongs to the person named
in the user ID.  If you *really* know what you are doing,
you may answer the next question with yes.
It's up to you to assign a value here; this value will never be exported
to any 3rd party.  We need it to implement the web-of-trust; it has nothing
to do with the (implicitly created) web-of-certificates.Key %s is already revoked.
Key available at: Key does not expire at all
Key expires at %s
Key generation canceled.
Key generation failed: %s
Key has been compromisedKey has only stub or on-card key items - no passphrase to change.
Key is no longer usedKey is protected.
Key is revoked.Key is supersededKey is valid for? (0) Key not changed so no update needed.
KeyringKeyserver no-modifyLanguage preferences: Login data (account name): Make off-card backup of encryption key? (Y/n) N  to change the name.
C  to change the comment.
E  to change the email address.
O  to continue with key generation.
Q  to to quit the key generation.NOTE: %s is not available in this version
NOTE: %s is not for normal use!
NOTE: This key is not protected!
NOTE: a key's S/N does not match the card's one
NOTE: backup of card key saved to `%s'
NOTE: creating subkeys for v3 keys is not OpenPGP compliant
NOTE: key has been revokedNOTE: no default option file `%s'
NOTE: old default options file `%s' ignored
NOTE: primary key is online and stored on card
NOTE: secondary key is online and stored on card
NOTE: secret key %s expired at %s
NOTE: sender requested "for-your-eyes-only"
NOTE: signature key %s expired %s
NOTE: simple S2K mode (0) is strongly discouraged
NOTE: trustdb not writable
Name may not start with a digit
Name must be at least 5 characters long
Need the secret key to do this.
NnCcEeOoQqNo corresponding signature in secret ring
No help availableNo help available for `%s'No reason specifiedNo subkey with index %d
No such user ID.
No trust value assigned to:
No user ID with hash %s
No user ID with index %d
Not a valid email address
Note that this key cannot be used for encryption.  You may want to use
the command "--edit-key" to generate a subkey for this purpose.
Note: This key has been disabled.
Note: This key has expired!
Nothing deleted.
Nothing to sign with key %s
OpenPGP card no. %s detected
OpenPGP card not available: %s
Overwrite? (y/N) Owner trust may not be set while using an user provided trust database
PIN callback returned error: %s
PIN for CHV%d is too short; minimum length is %d
PIN not correctly repeated; try againPlease correct the error first
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
Please don't put the email address into the real name or the comment
Please enter a domain to restrict this signature, or enter for none.
Please enter a new filename. If you just hit RETURN the default
file (which is shown in brackets) will be used.Please enter an optional commentPlease enter name of data file: Please enter the depth of this trust signature.
A depth greater than 1 allows the key you are signing to make
trust signatures on your behalf.
Please enter the passhrase; this is a secret sentence 
Please fix this possible security flaw
Please insert the card and hit return or enter 'c' to cancel: Please note that the factory settings of the PINs are
   PIN = `%s'     Admin PIN = `%s'
You should change them using the command --change-pin
Please note that the shown key validity is not necessarily correct
unless you restart the program.
Please remove selections from the secret keys.
Please remove the current card and insert the one with serial number:
   %.*s
Please repeat the last passphrase, so you are sure what you typed in.Please report bugs to <gnupg-bugs@gnu.org>.
Please select at most one subkey.
Please select exactly one user ID.
Please select the reason for the revocation:
Please select the type of key to generate:
Please select what kind of key you want:
Please select where to store the key:
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Please specify how long the signature should be valid.
         0 = signature does not expire
      <n>  = signature expires in n days
      <n>w = signature expires in n weeks
      <n>m = signature expires in n months
      <n>y = signature expires in n years
Please use the command "toggle" first.
Please wait, entropy is being gathered. Do some work if it would
keep you from getting bored, because it will improve the quality
of the entropy.
Possible actions for a %s key: Preferred keyserver: Primary key fingerprint:Private DO data: Pubkey: Public key is disabled.
Quit without saving? (y/N) RSA modulus missing or not of size %d bits
RSA prime %s missing or not of size %d bits
RSA public exponent missing or larger than %d bits
Real name: Really create the revocation certificates? (y/N) Really create? (y/N) Really delete this self-signature? (y/N)Really move the primary key? (y/N) Really remove all selected user IDs? (y/N) Really remove this user ID? (y/N) Really revoke all selected user IDs? (y/N) Really revoke this user ID? (y/N) Really sign all user IDs? (y/N) Really sign? (y/N) Really update the preferences for the selected user IDs? (y/N) Really update the preferences? (y/N) Reason for revocation: %s
Repeat passphrase
Repeat passphrase: Repeat this PIN: Replace existing key? (y/N) Replace existing keys? (y/N) Requested keysize is %u bits
Revocation certificate created.
Revocation certificate created.

Please move it to a medium which you can hide away; if Mallory gets
access to this certificate he can use it to make your key unusable.
It is smart to print this certificate and store it away, just in case
your media become unreadable.  But have some caution:  The print system of
your machine might store the data and make it available to others!
Save changes? (y/N) Secret key is available.
Secret parts of primary key are not available.
Secret parts of primary key are stored on-card.
Select the algorithm to use.

DSA (aka DSS) is the Digital Signature Algorithm and can only be used
for signatures.

Elgamal is an encrypt-only algorithm.

RSA may be used for signatures or encryption.

The first (primary) key must always be a key which is capable of signing.Set preference list to:
Sex ((M)ale, (F)emale or space): SignSign it? (y/N) Signature does not expire at all
Signature expired %s
Signature expires %s
Signature expires at %s
Signature is valid for? (%s) Signature made %s
Signature made %s using %s key ID %s
Signature notation: Signature policy: SsEeAaQqSubkey %s is already revoked.
Syntax: gpg [options] [files]
Check signatures against known trusted keys
Syntax: gpg [options] [files]
sign, check, encrypt or decrypt
default operation depends on the input data
The minimum trust level for this key is: %s

The random number generator is only a kludge to let
it run - it is in no way a strong RNG!

DON'T USE ANY DATA GENERATED BY THIS PROGRAM!!

The self-signature on "%s"
is a PGP 2.x-style signature.
The signature is not valid.  It does make sense to remove it from
your keyring.The signature will be marked as non-exportable.
The signature will be marked as non-revocable.
There are no preferences on a PGP 2.x-style user ID.
This JPEG is really large (%d bytes) !
This command is not allowed while in %s mode.
This is a secret key! - really delete? (y/N) This is a signature which binds the user ID to the key. It is
usually not a good idea to remove such a signature.  Actually
GnuPG might not be able to use this key anymore.  So do this
only if this self-signature is for some reason not valid and
a second one is available.This is a valid signature on the key; you normally don't want
to delete this signature because it may be important to establish a
trust connection to the key or another key certified by this key.This key belongs to us
This key has been disabledThis key has expired!This key is due to expire on %s.
This key is not protected.
This key may be revoked by %s key %sThis key probably belongs to the named user
This key was revoked on %s by %s key %s
This signature can't be checked because you don't have the
corresponding key.  You should postpone its deletion until you
know which key was used because this signing key might establish
a trust connection through another already certified key.This signature expired on %s.
This will be a self-signature.
This would make the key unusable in PGP 2.x.
To be revoked by:
To build the Web-of-Trust, GnuPG needs to know which keys are
ultimately trusted - those are usually the keys for which you have
access to the secret key.  Answer "yes" to set this key to
ultimately trusted
Total number processed: %lu
URL to retrieve public key: UncompressedUnknown signature type `%s'
Usage: gpg [options] [files] (-h for help)Usage: gpgv [options] [files] (-h for help)Use this key anyway? (y/N) User ID "%s" is expired.User ID "%s" is not self-signed.User ID "%s" is revoked.User ID "%s" is signable.  User ID is no longer validWARNING: WARNING: "%s" is a deprecated command - do not use it
WARNING: "%s" is a deprecated option
WARNING: %s overrides %s
WARNING: 2 files with confidential information exists.
WARNING: This is a PGP 2.x-style key.  Adding a designated revoker may cause
         some versions of PGP to reject this key.
WARNING: This is a PGP2-style key.  Adding a photo ID may cause some versions
         of PGP to reject this key.
WARNING: This key has been revoked by its designated revoker!
WARNING: This key has been revoked by its owner!
WARNING: This key is not certified with a trusted signature!
WARNING: This key is not certified with sufficiently trusted signatures!
WARNING: This subkey has been revoked by its owner!
WARNING: Using untrusted key!
WARNING: We do NOT trust this key!
WARNING: Weak key detected - please change passphrase again.
WARNING: `%s' is an empty file
WARNING: a user ID signature is dated %d seconds in the future
WARNING: appointing a key as a designated revoker cannot be undone!
WARNING: cipher algorithm %s not found in recipient preferences
WARNING: digest algorithm %s is deprecated
WARNING: encrypted message has been manipulated!
WARNING: forcing compression algorithm %s (%d) violates recipient preferences
WARNING: forcing digest algorithm %s (%d) violates recipient preferences
WARNING: forcing symmetric cipher %s (%d) violates recipient preferences
WARNING: invalid size of random_seed file - not used
WARNING: key %s contains preferences for unavailable
WARNING: key %s may be revoked: fetching revocation key %s
WARNING: key %s may be revoked: revocation key %s not present.
WARNING: keyserver handler from a different version of GnuPG (%s)
WARNING: keyserver option `%s' is not used on this platform
WARNING: message was encrypted with a weak key in the symmetric cipher.
WARNING: message was not integrity protected
WARNING: multiple signatures detected.  Only the first will be checked.
WARNING: no user ID has been marked as primary.  This command may
              cause a different user ID to become the assumed primary.
WARNING: nothing exported
WARNING: options in `%s' are not yet active during this run
WARNING: potentially insecure symmetrically encrypted session key
WARNING: program may create a core file!
WARNING: recipients (-r) given without using public key encryption
WARNING: secret key %s does not have a simple SK checksum
WARNING: signature digest conflict in message
WARNING: signing subkey %s has an invalid cross-certification
WARNING: signing subkey %s is not cross-certified
WARNING: the signature will not be marked as non-exportable.
WARNING: the signature will not be marked as non-revocable.
WARNING: this key might be revoked (revocation key not present)
WARNING: unable to %%-expand notation (too large).  Using unexpanded.
WARNING: unable to %%-expand policy URL (too large).  Using unexpanded.
WARNING: unable to %%-expand preferred keyserver URL (too large).  Using unexpanded.
WARNING: unable to refresh key %s via %s: %s
WARNING: unable to remove temp directory `%s': %s
WARNING: unable to remove tempfile (%s) `%s': %s
WARNING: unsafe enclosing directory ownership on configuration file `%s'
WARNING: unsafe enclosing directory ownership on extension `%s'
WARNING: unsafe enclosing directory ownership on homedir `%s'
WARNING: unsafe enclosing directory permissions on configuration file `%s'
WARNING: unsafe enclosing directory permissions on extension `%s'
WARNING: unsafe enclosing directory permissions on homedir `%s'
WARNING: unsafe ownership on configuration file `%s'
WARNING: unsafe ownership on extension `%s'
WARNING: unsafe ownership on homedir `%s'
WARNING: unsafe permissions on configuration file `%s'
WARNING: unsafe permissions on extension `%s'
WARNING: unsafe permissions on homedir `%s'
WARNING: using experimental cipher algorithm %s
WARNING: using experimental digest algorithm %s
WARNING: using experimental public key algorithm %s
WARNING: using insecure memory!
WARNING: using insecure random number generator!!
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
What keysize do you want? (%u) When you sign a user ID on a key, you should first verify that the key
belongs to the person named in the user ID.  It is useful for others to
know how carefully you verified this.

"0" means you make no particular claim as to how carefully you verified the
    key.

"1" means you believe the key is owned by the person who claims to own it
    but you could not, or did not verify the key at all.  This is useful for
    a "persona" verification, where you sign the key of a pseudonymous user.

"2" means you did casual verification of the key.  For example, this could
    mean that you verified the key fingerprint and checked the user ID on the
    key against a photo ID.

"3" means you did extensive verification of the key.  For example, this could
    mean that you verified the key fingerprint with the owner of the key in
    person, and that you checked, by means of a hard to forge document with a
    photo ID (such as a passport) that the name of the key owner matches the
    name in the user ID on the key, and finally that you verified (by exchange
    of email) that the email address on the key belongs to the key owner.

Note that the examples given above for levels 2 and 3 are *only* examples.
In the end, it is up to you to decide just what "casual" and "extensive"
mean to you when you sign other keys.

If you don't know what the right answer is, answer "0".You are about to revoke these signatures:
You are using the `%s' character set.
You can't change the expiration date of a v3 key
You can't delete the last user ID!
You did not specify a user ID. (you may use "-r")
You don't want a passphrase - this is probably a *bad* idea!

You don't want a passphrase - this is probably a *bad* idea!
I will do it anyway.  You can change your passphrase at any time,
using this program with the option "--edit-key".

You have signed these user IDs on key %s:
You may not add a designated revoker to a PGP 2.x-style key.
You may not add a photo ID to a PGP2-style key.
You may not make an OpenPGP signature on a PGP 2.x key while in --pgp2 mode.
You must select at least one key.
You must select at least one user ID.
You must select exactly one key.
You need a Passphrase to protect your secret key.

You need a passphrase to unlock the secret key for
user: "%s"
You need a passphrase to unlock the secret key for user:
"%.*s"
%u-bit %s key, ID %s, created %s%s
You selected this USER-ID:
    "%s"

You should specify a reason for the certification.  Depending on the
context you have the ability to choose from this list:
  "Key has been compromised"
      Use this if you have a reason to believe that unauthorized persons
      got access to your secret key.
  "Key is superseded"
      Use this if you have replaced this key with a newer one.
  "Key is no longer used"
      Use this if you have retired this key.
  "User ID is no longer valid"
      Use this to state that the user ID should not longer be used;
      this is normally used to mark an email address invalid.
Your current signature on "%s"
has expired.
Your current signature on "%s"
is a local signature.
Your decision? Your selection? Your selection? (enter `?' for more information): Your system can't display dates beyond 2038.
However, it will be correctly handled up to 2106.
[  full  ][  undef ][ expired][ revoked][ unknown][User ID not found][filename][marginal][not set][revocation][self-signature][ultimate][uncertain]`%s' already compressed
`%s' is not a JPEG file
`%s' is not a regular file - ignored
`%s' is not a valid character set
`%s' is not a valid long keyID
`%s' is not a valid signature expiration
access to admin commands is not configured
action `%s' not supported with keyserver scheme `%s'
add a key to a smartcardadd a photo IDadd a revocation keyadd a subkeyadd a user IDambiguous option `%s'
anonymous recipient; trying secret key %s ...
armor header: armor: %s
assuming %s encrypted data
assuming bad signature from key %s due to an unknown critical bit
assuming signed data in `%s'
bad MPIbad URIbad certificatebad keybad passphrasebad public keybad secret keybad signaturebe somewhat more quietbinarybuild_packet failed: %s
cCcaching keyring `%s'
can't access %s - invalid OpenPGP card?
can't access `%s': %s
can't close `%s': %s
can't connect to `%s': %s
can't create `%s': %s
can't create backup file `%s': %s
can't create directory `%s': %s
can't create lock for `%s'
can't disable core dumps: %s
can't do this in batch mode
can't do this in batch mode without "--yes"
can't gen prime with pbits=%u qbits=%u
can't generate a prime with less than %d bits
can't handle public key algorithm %d
can't handle text lines longer than %d characters
can't lock `%s'
can't open `%s'
can't open `%s': %s
can't open signed data `%s'
can't open the keyringcan't put a policy URL into v3 (PGP 2.x style) signatures
can't put a policy URL into v3 key (PGP 2.x style) signatures
can't put notation data into v3 (PGP 2.x style) key signatures
can't put notation data into v3 (PGP 2.x style) signatures
can't query passphrase in batch mode
can't read `%s': %s
can't stat `%s': %s
can't use a symmetric ESK packet due to the S2K mode
can't write `%s': %s
canceledcancelled by user
cancel|cancelcannot appoint a PGP 2.x style key as a designated revoker
cannot avoid weak key for symmetric cipher; tried %d times!
card is permanently locked!
card-no: change URL to retrieve keychange a CA fingerprintchange a card's PINchange card holder's namechange card holder's sexchange data on a cardchange the expiration date for the key or selected subkeyschange the language preferenceschange the login namechange the ownertrustchange the passphrasecheck signatureschecking created signature failed: %s
checking the trustdb
checksum errorcipher algorithm %d%s is unknown or disabled
cipher extension `%s' not loaded due to unsafe permissions
colon missingcompletes-needed must be greater than 0
conflicting commands
could not parse keyserver URL
create ascii armored outputcreated: %screation timestamp missing
data not saved; use option "--output" to save it
dearmoring failed: %s
decrypt data (default)decryption failed: %s
decryption okay
delete selected subkeysdelete selected user IDsdelete signatures from the selected user IDsdeleting keyblock failed: %s
depth: %d  valid: %3d  signed: %3d  trust: %d-, %dq, %dn, %dm, %df, %du
directory `%s' created
disable keydisableddo not make any changesenable keyenarmoring failed: %s
encrypt dataencrypted with %lu passphrases
encrypted with %s key, ID %s
encrypted with %u-bit %s key, ID %s, created %s
encrypted with 1 passphrase
encrypted with unknown algorithm %d
encrypting a message in --pgp2 mode requires the IDEA cipher
encryption only with symmetric ciphererror creating `%s': %s
error creating keyring `%s': %s
error creating passphrase: %s
error finding trust record in `%s': %s
error getting current key info: %s
error getting new PIN: %s
error in `%s': %s
error in trailer line
error reading `%s': %s
error reading application data
error reading fingerprint DO
error reading keyblock: %s
error reading secret keyblock "%s": %s
error retrieving CHV status from card
error writing keyring `%s': %s
error writing public keyring `%s': %s
error writing secret keyring `%s': %s
existing key will be replaced
expiredexpired: %sexpires: %sexport keysexport keys to a key serverexporting secret keys not allowed
external keyserver calls are not supported in this build
external program calls are disabled due to unsafe options file permissions
failed to initialize the TrustDB: %s
failed to rebuild keyring cache: %s
failed to store the creation date: %s
failed to store the fingerprint: %s
failed to store the key: %s
femalefetch the key specified in the card URLfile close errorfile create errorfile delete errorfile existsfile open errorfile read errorfile rename errorfile write errorflag the selected user ID as primaryforcedforcing symmetric cipher %s (%d) violates recipient preferences
fstat of `%s' failed in %s: %s
fstat(%d) failed in %s: %s
fullgeneral errorgenerate PGP 2.x compatible messagesgenerate a new key pairgenerate a revocation certificategenerate new keysgenerating key failed
generating new key
generating the deprecated 16-bit checksum for secret key protection
gpg-agent is not available in this session
gpg-agent protocol version %d is not supported
iImMqQsSimport keys from a key serverimport/merge keysimporting secret keys not allowed
input line %u too long or missing LF
input line longer than %d characters
invalidinvalid S2K mode; must be 0, 1 or 3
invalid argumentinvalid armorinvalid armor header: invalid armor: line longer than %d characters
invalid clearsig header
invalid dash escaped line: invalid default preferences
invalid default-cert-level; must be 0, 1, 2, or 3
invalid export options
invalid fingerprintinvalid hash algorithm `%s'
invalid import options
invalid item `%s' in preference string
invalid keyringinvalid keyserver options
invalid keyserver protocol (us %d!=handler %d)
invalid list options
invalid min-cert-level; must be 1, 2, or 3
invalid packetinvalid passphraseinvalid personal cipher preferences
invalid personal compress preferences
invalid personal digest preferences
invalid radix64 character %02X skipped
invalid root packet detected in proc_tree()
invalid structure of OpenPGP card (DO 0x93)
invalid value
invalid verify options
it is strongly suggested that you update your preferences and
key "%s" not found on keyserver
key "%s" not found: %s
key %s has no user IDs
key %s marked as ultimately trusted
key %s occurs more than once in the trustdb
key %s was created %lu second in the future (time warp or clock problem)
key %s was created %lu seconds in the future (time warp or clock problem)
key %s: "%s" %d new signatures
key %s: "%s" %d new subkeys
key %s: "%s" %d new user IDs
key %s: "%s" %d signature cleaned
key %s: "%s" %d signatures cleaned
key %s: "%s" %d user ID cleaned
key %s: "%s" %d user IDs cleaned
key %s: "%s" 1 new signature
key %s: "%s" 1 new subkey
key %s: "%s" 1 new user ID
key %s: "%s" not changed
key %s: "%s" revocation certificate added
key %s: "%s" revocation certificate imported
key %s: PGP 2.x style key - skipped
key %s: PKS subkey corruption repaired
key %s: accepted as trusted key
key %s: accepted non self-signed user ID "%s"
key %s: already in secret keyring
key %s: can't locate original keyblock: %s
key %s: can't read original keyblock: %s
key %s: direct key signature added
key %s: doesn't match our copy
key %s: duplicated user ID detected - merged
key %s: invalid revocation certificate: %s - rejected
key %s: invalid revocation certificate: %s - skipped
key %s: invalid self-signature on user ID "%s"
key %s: invalid subkey binding
key %s: invalid subkey revocation
key %s: new key - skipped
key %s: no public key - can't apply revocation certificate
key %s: no public key for trusted key - skipped
key %s: no subkey for key binding
key %s: no subkey for key revocation
key %s: no subkey for subkey binding signature
key %s: no subkey for subkey revocation signature
key %s: no user ID
key %s: no user ID for signature
key %s: no valid user IDs
key %s: non exportable signature (class 0x%02X) - skipped
key %s: not protected - skipped
key %s: public key "%s" imported
key %s: public key not found: %s
key %s: removed multiple subkey binding
key %s: removed multiple subkey revocation
key %s: revocation certificate at wrong place - skipped
key %s: secret key imported
key %s: secret key not found: %s
key %s: secret key with invalid cipher %d - skipped
key %s: secret key without public key - skipped
key %s: skipped subkey
key %s: skipped user ID "%s"
key %s: subkey signature in wrong place - skipped
key %s: unexpected signature class (0x%02X) - skipped
key %s: unsupported public key algorithm
key %s: unsupported public key algorithm on user ID "%s"
key already exists
key export failed: %s
key generation completed (%d seconds)
key has been created %lu second in future (time warp or clock problem)
key has been created %lu seconds in future (time warp or clock problem)
key is not flagged as insecure - can't use it with the faked RNG!
key not found on keyserver
key operation not possible: %s
keyblock resource `%s': %s
keyring `%s' created
keyserver communications error: %s
keyserver did not send VERSION
keyserver errorkeyserver internal error
keyserver receive failed: %s
keyserver refresh failed: %s
keyserver search failed: %s
keyserver send failed: %s
keyserver timed out
keysize invalid; using %u bits
keysize rounded up to %u bits
line too longlist all available datalist and check key signatureslist key and user IDslist keyslist keys and fingerprintslist keys and signatureslist preferences (expert)list preferences (verbose)list secret keysmake a detached signaturemake timestamp conflicts only a warningmake_keysig_packet failed: %s
malemalformed CRC
malformed GPG_AGENT_INFO environment variable
malformed user idmarginalmarginals-needed must be greater than 1
max-cert-depth must be in the range from 1 to 255
menu to change or unblock the PINmove a backup key to a smartcardmove a key to a smartcardmoving a key signature to the correct place
nNnested clear text signatures
network errornevernever     new configuration file `%s' created
next trustdb check due at %s
nono = sign found in group definition `%s'
no cardno corresponding public key: %s
no default secret keyring: %s
no entropy gathering module detected
no handler for keyserver scheme `%s'
no keyserver action!
no keyserver known (use option --keyserver)
no need for a trustdb check
no need for a trustdb check with `%s' trust model
no need for a trustdb update with `%s' trust model
no remote program execution supported
no revocation keys found for "%s"
no secret key
no secret subkey for public subkey %s - ignoring
no signed data
no such user idno ultimately trusted keys found
no valid OpenPGP data found.
no valid addressees
no writable keyring found: %s
no writable public keyring found: %s
no writable secret keyring found: %s
not a detached signature
not an OpenPGP cardnot encryptednot forcednot processednot supportednote: random_seed file is empty
note: random_seed file not updated
oOokay, we are the anonymous recipient.
okay|okayold encoding of the DEK is not supported
old style (PGP 2.x) signature
operation is not possible without initialized secure memory
option file `%s': %s
original file name='%.*s'
ownertrust information cleared
ownertrust value missingpassphrase generated with unknown digest algorithm %d
passphrase not correctly repeated; try againplease do a --check-trustdb
please enter an optional but highly suggested email addressplease see http://www.gnupg.org/faq.html for more information
please use "%s%s" instead
please wait while key is being generated ...
preference `%s' duplicated
premature eof (in CRC)
premature eof (in trailer)
premature eof (no CRC)
print the card statusproblem handling encrypted packet
problem with the agent - disabling agent use
prompt before overwritingprotection algorithm %d%s is not supported
protection digest %d is not supported
public and secret key created and signed.
public key %s is %lu second newer than the signature
public key %s is %lu seconds newer than the signature
public key %s not found: %s
public key decryption failed: %s
public key does not match secret key!
public key encrypted data: good DEK
public key is %s
public key not foundpublic key of ultimately trusted key %s not found
qQquitquit this menuquoted printable character in armor - probably a buggy MTA has been used
re-distribute this key to avoid potential algorithm mismatch problems
read error in `%s': %s
reading from `%s'
reading options from `%s'
reading public key failed: %s
reading stdin ...
reason for revocation: refreshing %d keys from %s
refreshing 1 key from %s
remove keys from the public keyringremove keys from the secret keyringrenaming `%s' to `%s' failed: %s
requesting key %s from %s
requesting key %s from %s server %s
resource limitresponse does not contain the RSA modulus
response does not contain the RSA public exponent
response does not contain the public key data
revocation comment: revoke key or selected subkeysrevoke selected user IDsrevoke signatures on the selected user IDsrevokedrevoked by your key %s on %s
revoked: %srounded up to %u bits
save and quitsearch for keys on a key serversearching for "%s" from %s
searching for "%s" from %s server %s
secret key "%s" not found: %s
secret key already stored on a card
secret key not availablesecret key parts are not available
secret parts of key are not available
select subkey Nselect user ID Nselected certification digest algorithm is invalid
selected cipher algorithm is invalid
selected compression algorithm is invalid
selected digest algorithm is invalid
sending key %s to %s
sending key %s to %s server %s
set preference list for the selected user IDsshow admin commandsshow key fingerprintshow selected photo IDsshow this helpsign a keysign a key locallysign or edit a keysign selected user IDs [* see below for related commands]sign selected user IDs locallysign selected user IDs with a non-revocable signaturesign selected user IDs with a trust signaturesignature verification suppressed
signatures created so far: %lu
signed by your key %s on %s%s%s
signing failed: %s
signing:skipped "%s": %s
skipped "%s": duplicated
skipped: public key already set
skipped: public key already set as default recipient
skipped: secret key already present
skipping block of type %d
skipping v3 self-signature on user ID "%s"
standalone revocation - use "gpg --import" to apply
standalone signature of class 0x%02x
storing key onto card failed: %s
subpacket of type %d has critical bit set
symmetric encryption of `%s' failed: %s
system error while calling external program: %s
take the keys from this keyringtextmodethe IDEA cipher plugin is not present
the given certification policy URL is invalid
the given preferred keyserver URL is invalid
the given signature policy URL is invalid
the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
the trustdb is corrupted; please run "gpg --fix-trustdb".
there is a secret key for public key "%s"!
this is a PGP generated Elgamal key which is not secure for signatures!this key has already been designated as a revoker
this may be caused by a missing self-signature
this message may not be usable by %s
this platform requires temporary files when calling external programs
timestamp conflicttoggle between the secret and public key listingstoggle the signature force PIN flagtoo many cipher preferences
too many compression preferences
too many digest preferences
too many entries in pk cache - disabled
trust database errortrust record %lu is not of requested type %d
trust record %lu, req type %d: read failed: %s
trust record %lu, type %d: write failed: %s
trust: %strustdb rec %lu: lseek failed: %s
trustdb rec %lu: write failed (n=%d): %s
trustdb transaction too large
trustdb: lseek failed: %s
trustdb: read failed (n=%d): %s
trustdb: sync failed: %s
ultimateunable to display photo ID!
unable to execute external program
unable to execute program `%s': %s
unable to execute shell `%s': %s
unable to open JPEG file `%s': %s
unable to read external program response: %s
unable to set exec-path to %s
unable to update trustdb version record: write failed: %s
unable to use the IDEA cipher for all of the keys you are encrypting to.
unable to use unknown trust model (%d) - assuming %s trust model
uncompressed|noneundefinedunexpected armor: unexpected dataunimplemented cipher algorithmunimplemented pubkey algorithmunknownunknown cipher algorithmunknown compress algorithmunknown configuration item `%s'
unknown default recipient "%s"
unknown digest algorithmunknown key protection algorithm
unknown option `%s'
unknown packet typeunknown protection algorithm
unknown pubkey algorithmunknown signature classunknown versionunnatural exit of external program
unspecifiedunsupported URIunusable pubkey algorithmunusable public keyunusable secret keyupdate all keys from a keyserverupdate failed: %s
update secret failed: %s
update the trust databaseusage: %susage: gpg [options] use as output fileuse canonical text modeuse option "--delete-secret-keys" to delete it first.
use strict OpenPGP behavioruse this user-id to sign or decryptuser ID "%s" is already revoked
user ID: "%s"
using %s trust model
using cipher %s
using subkey %s instead of primary key %s
validity: %sverboseverification of Admin PIN is currently prohibited through this command
verify CHV%d failed: %s
verify a signatureverify the PIN and list all dataweak keyweak key created - retrying
weird size for an encrypted session key (%d)
will not run with insecure memory due to %s
writing direct signature
writing key binding signature
writing public key to `%s'
writing secret key stub to `%s'
writing secret key to `%s'
writing self signature
writing to `%s'
writing to stdout
wrong secret key usedyYyesyou can only clearsign with PGP 2.x style keys while in --pgp2 mode
you can only detach-sign with PGP 2.x style keys while in --pgp2 mode
you can only encrypt to RSA keys of 2048 bits or less in --pgp2 mode
you can only make detached or clear signatures while in --pgp2 mode
you can update your preferences with: gpg --edit-key %s updpref save
you can't sign and encrypt at the same time while in --pgp2 mode
you cannot appoint a key as its own designated revoker
you cannot use --symmetric --encrypt while in %s mode
you cannot use --symmetric --encrypt with --s2k-mode 0
you cannot use --symmetric --sign --encrypt while in %s mode
you cannot use --symmetric --sign --encrypt with --s2k-mode 0
you found a bug ... (%s:%d)
you may not use %s while in %s mode
you may not use cipher algorithm `%s' while in %s mode
you may not use compression algorithm `%s' while in %s mode
you may not use digest algorithm `%s' while in %s mode
you must use files (and not a pipe) when working with --pgp2 enabled.
|AN|New Admin PIN|A|Admin PIN|FD|write status info to this FD|NAME|encrypt for NAME|N|New PIN|N|set compress level N (0 disables)|[file]|make a clear text signature|[file]|make a signature|algo [files]|print message digests||Please enter the PIN%%0A[sigs done: %lu]Project-Id-Version: gnupg 1.4.2
Report-Msgid-Bugs-To: gnupg-i18n@gnupg.org
POT-Creation-Date: 2006-08-01 13:07+0200
PO-Revision-Date: 2005-07-29 09:49+0800
Last-Translator: Jedi <Jedi@Jedi.org>
Language-Team: Chinese (traditional) <zh-l10n@linux.org.tw>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

輸入使用者 ID. 以空白列結束: 
隨機位元組不夠多. 請多做一些有的沒的事情, 
這樣作業系統纔能蒐集到更多的亂數! (還需要 %d 位元組)

請挑選一張圖片來當成妳的照片 ID. 這張圖片一定要是 JPEG 圖檔纔行.
請記住這張圖片會被存放在妳的公鑰裡. 如果妳挑了非常大的圖片的話,
妳的金鑰也會變成非常地大!
盡量把圖片尺寸控制在 240x288 左右, 會是個非常理想的大小.

已被支援的演算法:

妳需要一個使用者 ID 來辨識妳的金鑰; 這個軟體會用真實姓名,
註釋和電子郵件地址組合成使用者 ID 如下:
    "Ke-Huan Lin (Jedi) <Jedi@Jedi.org>"

                亦即 "%s"               使用 %s 金鑰 %s
                已匯入: %lu              未改變的: %lu
              新的子鑰: %lu
         新的使用者 ID: %lu
              未被匯入: %lu
       沒有使用者的 ID: %lu
         "%s": 編密演算法 %s 的偏好設定
         "%s": 壓縮演算法 %s 的偏好設定
         "%s": 摘要演算法 %s 的偏好設定
         (在主鑰 ID %s 上的子鑰)         這份簽章並不屬於這個持有者
         這個簽章很有可能是 *偽造的*.
         沒有證據指出這個簽章屬於這個持有者.
         這很有可能表示這個簽章是被偽造的.
              新的簽章: %lu
      "%s"
      卡片序號 =      金鑰指紋 =                子鑰指紋:          被讀取的私鑰: %lu
        已跳過的新金鑰: %lu
 已被清除掉的使用者 ID: %lu
               子鑰指紋:      已被清除掉的簽章: %lu
   (%c) 已完成
   (%c) 切換鑑定性能
   (%c) 切換加密性能
   (%c) 切換簽署性能
   (%d) DSA (妳自己設定性能)
   (%d) DSA (僅能簽署用)
   (%d) DSA 和 Elgamal (預設)
   (%d) Elgamal (僅能加密用)
   (%d) RSA (僅能加密用)
   (%d) RSA (妳自己設定性能)
   (%d) RSA (僅能簽署用)
   (0) 我不作答.%s
   (1) 我根本沒有檢查過.%s
   (1) 簽署用金鑰
   (2) 加密用金鑰
   (2) 我隨意檢查過了.%s
   (3) 憑證用金鑰
   (3) 我非常小心地檢查過了.%s
          新的金鑰撤銷: %lu
  %d = 我*不*信任
 %d = 我不知道或不想說
  %d = 我完全信任
  %d = 我勉強信任
  %d = 我徹底信任
  無法簽署.
  亦即 "%s"
 m = 回到主選單
  q = 離開
 s = 跳過這把金鑰
          已匯入的私鑰: %lu
 (主要金鑰 ID %s) (不可匯出) (不可撤銷)                主鑰指紋:          未改變的私鑰: %lu
"%s" 並非金鑰 ID: 正跳過
"%s" 已經被金鑰 %s 在本地簽署了
"%s" 已經被金鑰 %s 簽署了
# 相對應的信任值清單被建立於 %s
# (請用 "gpg --import-ownertrust" 來取回它們)
%d 管理者個人識別碼 (PIN) 試圖在卡片被永久鎖定前遺留下來
%d 個損壞的簽章
已經處理了 %d 把金鑰 (共計已解決了 %d 份有效性)
%d 個勉強信任以及 %d 個完全信任是 %s 信任模型的最小需求
有 %d 份簽章因為某些錯誤而未被檢查
有 %d 份簽章因為遺失金鑰而未被檢查
偵測到 %d 個沒有有效自我簽章的使用者 ID
檢查了 %lu 份金鑰 (共 %lu 份簽章)
目前檢查了 %lu 份金鑰 (共 %lu 份簽章)
已有 %lu 把金鑰被處理了
%s ...
%s 並不支援經手程式 (handler) 版本 %d
%s 還沒辦法跟 %s 一起運作
%s 加密過的資料
%s 加密過的階段金鑰
%s 加密將被採用
%s 是新的那一個
%s 是沒有改變的那一個
%s 金鑰的長度可能介於 %u 位元和 %u 位元之間.
%s 金鑰尺寸一定要介於 %u 到 %u 之間
%s 跟 %s 放在一起沒有意義!
%s 不被允許跟 %s 併用
%s 簽章, 摘要演算法 %s
%s.
%s/%s 已經加密給: "%s"
%s/%s 簽章來自: "%s"
%s: 祇能有限的保證這把金鑰真的屬於叫這個名字的使用者
%s: 沒法保證這把金鑰真的屬於叫這個名字的使用者
%s: 目錄不存在!
%s: 讀取自由記錄時錯誤: %s
%s: 讀取版本記錄時錯誤: %s
%s: 更新版本記錄時錯誤: %s
%s: 寫入目錄記錄時錯誤: %s
%s: 寫入版本記錄時錯誤: %s
%s: 附加某筆記錄時失敗: %s
%s: 建立雜湊表失敗: %s
%s: 建立版本記錄失敗: %s%s: 記錄歸零時失敗: %s
%s: 無效的檔案版本 %d
%s: 無效的信任資料庫
%s: 建立了無效的信任資料庫
%s: 鑰匙圈已建立
%s: 不是一個信任資料庫檔案
%s: 已跳過: %s
%s: 已跳過: 公鑰已經存在了
%s: 已跳過: 公鑰已經被禁用了
%s: 建立了信任資料庫
%s: 未知的副檔名
%s: 記錄編號為 %lu 的版本記錄
%s:%d: 不建議使用的選項 "%s"
%s:%d: 無效的匯出選項
%s:%d: 無效的匯入選項
%s:%d: 無效的金鑰伺服器選項
%s:%d: 無效的清單選項
%s:%d: 無效的驗證選項
%u 位元長的 %s 金鑰, ID %s, 建立於 %s(沒有給定描述)
(也許妳會想要在這裡選擇 %d)
(這是把機密的撤銷金鑰)
(機密的)(除非妳用指紋指定了金鑰)
(也許妳選錯程式來做這件事了)
* 這個 `sign' 指令也可以在前面加上一個 `l' 字母, 來表示本地簽章 (lsign),
  加上 `t' 的話就是信任簽章 (tsign), 加上 `nr' 的話就是不可撤銷簽章
  (nrsign), 當然也可以任意組合這些選項 (像是 ltsign, tnrsign 等等.).
--clearsign [檔名]--decrypt [檔名]--edit-key 使用者ID [指令]--encrypt [檔名]--lsign-key 使用者ID--output 在這個命令中沒有作用
--sign --encrypt [檔名]--sign --symmetric [檔名]--sign [檔名]--sign-key 使用者ID--store [檔名]--symmetric --encrypt [檔名]--symmetric --sign --encrypt [檔名]--symmetric [檔名]-k[v][v][v][c] [使用者ID] [鑰匙圈]... 這是個瑕疵 (%s:%d:%s)
1 個損壞的簽章
有 1 份簽章因為遺失金鑰而未被檢查
有 1 份簽章因為某個錯誤而未被檢查
偵測到 1 個沒有有效自我簽章的使用者 ID
10 譯者請參見 trustdb.c:uid_trust_string_fixed@
(請參照線上說明頁面來取得所有命令和選項的完整清單)
@
範例:

 -se -r Bob [檔案]          對 Bob 這個使用者簽署及加密
 --clearsign [檔案]         做出明文簽章
 --detach-sign [檔案]       做出分離式簽章
 --list-keys [名字]         顯示金鑰
 --fingerprint [名字]       顯示指紋
@
選項:
 @指令:
 已強迫使用 ASCII 封裝過的輸出.
允許使用管理者指令
未允許使用管理者指令
限管理者使用的指令
如果妳覺得產生子鑰可以的話, 就回答 "yes" (或者祇要 "y").如果刪除這把子鑰沒問題的話就回答 "yes"如果覆寫這個檔案沒有問題的話就回答 "yes"如果妳真的想要刪除這個使用者 ID 的話就回答 "yes".
所有的憑證在那之後也都會失去!如果妳想要簽署 *所有* 使用者 ID 的話就回答 "yes"請回答 "yes" 或 "no"妳真的確定要用妳的金鑰 "%s" (%s)
來簽署這把金鑰嗎
妳確定仍然想要增加嗎? (y/N) 妳確定妳仍然想要撤銷它嗎? (y/N) 妳仍然想要簽署它嗎? (y/N) 妳確定要指派這把金鑰為指定撤銷者嗎? (y/N) 妳確定要刪除它嗎? (y/N) 妳確定要取代它嗎? (y/N) 妳確定要用它嗎? (y/N) 鑑定*損壞* 的簽章來自於 "%s"憑證中心 (CA) 指紋: CRC 錯誤; %06lX - %06lX
無法檢查簽章: %s
無法編輯這把金鑰: %s
無法開啟 `%s': %s
取消卡片持有者的教名: 卡片持有者的姓氏: 被徹底信任金鑰的憑證:
變更姓名(N), 註釋(C), 電子郵件地址(E)或確定(O)/退出(Q)? 變更姓名(N), 註釋(C), 電子郵件地址(E)或退出(Q)? 變更所有 (或祇有被選取的那幾個) 使用者 ID 的偏好成現用的偏好清單.
所有受到影響的自我簽章的時間戳記都會增加一秒鐘.
正在變更某把次鑰的使用期限.
正在變更主鑰的使用期限.
編密法: 這項指令應該要拿一個檔名當作參數
指令> 註釋: 壓縮: 要為這把金鑰建立一份指定撤銷憑證嗎? (y/N) 要為這把金鑰建立一份撤銷憑證嗎? (y/N) 要為這份簽章建立一份撤銷憑證嗎? (y/N) 執意偏好的金鑰伺服器: 關鍵簽章標記: 關鍵簽章原則: 目前可進行的動作: 目前的收件者:
DSA 金鑰對會有 %u 位元長.
刪除這個完好的簽章嗎? (y/N/q)刪除這個無效的簽章嗎? (y/N/q)要從鑰匙圈裡刪除這把金鑰嗎? (y/N) 刪除這個未知的簽章嗎? (y/N/q)已經刪除了 %d 個簽章.
已經刪除了 %d 個簽章.
分離的簽章.
摘要: 正在顯示 %s 照片 ID, 其尺寸為 %ld, 屬於金鑰 %s (uid %d) 的照片
妳真的想要刪除被選擇的金鑰嗎? (y/N) 妳真的要刪除這把金鑰嗎? (y/N) 妳真的想要這麼做嗎? (y/N) 妳真的想要撤銷這整把金鑰嗎? (y/N) 妳真的想要撤銷這些被選擇的次鑰嗎? (y/N) 妳真的想要撤銷這把次鑰嗎? (y/N) 請問妳是否真的想把這把金鑰設成徹底信任呢? (y/N) 妳想要發佈一份新的簽章來取代已過期的那一個嗎? (y/N) 妳是否想要把他升級成可以完全匯出的簽章? (y/N) 妳是否想要將它升級成 OpenPGP 自我簽章? (y/N) 妳仍然想要再次簽署它嗎? (y/N) 妳想要讓妳的簽章也在同一個時候過期嗎? (Y/n) 錯誤: 電子郵件地址: 加密請輸入管理者個人識別碼 (PIN): 輸入要當作相片 ID 的 JPEG 檔名: 請輸入新的管理者個人識別碼 (PIN): 請輸入新的個人識別碼 (PIN): 請輸入個人識別碼 (PIN): 請輸入選用的描述; 以空白列結束:
請輸入新的檔名請輸入數字, N)ext, 或 Q)uit > 請輸入密語
請輸入密語: 請輸入金鑰持有人的名字輸入要給這把私鑰用的新密語.

請輸入提示裡所要求的數值.
妳可以輸入 ISO 日期格式 (YYYY-MM-DD), 但是不會得到良好的錯誤回應 -
反之, 系統會試著把給定的數值中斷成若干片段.請輸入金鑰的尺寸輸入妳要遞送的訊息接收者的使用者 ID.輸入指定撤銷者的使用者 ID: 請輸入妳的偏好金鑰伺服器 URL: 從 `%s' 讀取備份金鑰時發生錯誤: %s
錯誤: 合併後的名字太長 (上限是 %d 個字元).
錯誤: 並不允許使用連續兩個以上的空格.
錯誤: 登入資料太長 (上限是 %d 個字元).
錯誤: 目前祇允許使用單純的 ASCII 字元.
錯誤: 私人的 DO 太長 (上限是 %d 個字元).
錯誤: 不能使用 "<" 字元.
錯誤: URL 太長 (上限是 %d 個字元).
錯誤: 偏好設定字串中含有無效的字元
錯誤: 指紋格式化無效.
錯誤: 偏好設定字串的長度無效
錯誤: 無效的回應.
過期的簽章來自於 "%s"特點: 檔案 `%s' 存在. 請給定簽章所要套用的檔案名稱請開始鍵入妳的訊息 ...
完好的簽章來自於 "%s"雜湊: 提示: 選擇使用者 ID 來加以簽署
準備好時請按下 [Enter], 或者輸入 'c' 以取消: 妳有多謹慎檢查正要簽署的金鑰確實屬於上面那個人的名字呢?
如果妳不知道這個問題的答案, 請輸入 "0".
妳有多信任這把金鑰真的屬於叫這個名字的使用者?
我隨意檢查過這把金鑰了.
我非常小心地檢查過這把金鑰了.
我根本沒有檢查過這把金鑰.
IDEA 編密法不可用, 我們樂觀地試著改以 %s 代替
妳也可以輸入一串文字來描述為甚麼發佈這份撤銷憑證的理由.
請讓這段文字保持簡明扼要.
鍵入空白列以結束這段文字.
如果妳無論如何想要使用這把未被信任的金鑰, 請回答 "yes".通常來說用同一把金鑰簽署及加密並不是個好主意.
這個演算法應該祇被用於特定的情況下.
請先聯絡妳的安全專家.註釋含有無效的字符
姓名含有無效的字符
無效的指令  (試試看 "help")
無效的金鑰 %s 可以藉由 --allow-non-selfsigned-uid 而生效
無效的密語; 請再試一次無效的選擇.
以上正確嗎? (y/N) 這樣可以嗎? (y/N) 這張照片正確嗎? (y/N/q) 這把金鑰並 *不* 確定屬於使用者 ID 裡的那個人.
除非妳 **真的** 知道自己在做甚麼,
否則妳最好在下一個問題回答 no
在這裡指派的數值完全是看妳自己決定; 這些數值永遠不會被匯出給其他人.
我們需要它來實施信任網絡; 這跟 (自動建立起的) 憑證網絡一點關係也沒有.金鑰 %s 已經被撤銷了.
可用的金鑰於: 金鑰完全不會過期
金鑰將會在 %s 過期
已取消金鑰產生.
產生金鑰失敗: %s
金鑰已經被洩漏了金鑰祇剩下殘骸或者祇含有卡上 (on-card) 金鑰項目 - 沒有可變更的密語.
金鑰不再被使用了金鑰被保護了.
金鑰已經被撤銷了.金鑰被代換了金鑰的有效期限是多久? (0) 金鑰沒有變更所以不需要更新.
鑰匙圈金鑰伺服器無修改介面語言偏好設定:  登入資料 (帳號名稱): 是否要為加密用金鑰建立卡外備份? (Y/n) N  修改姓名.
C  修改註釋.
E  修改電子郵件位址.
O  繼續產生金鑰.
Q  中止產生金鑰.注意: %s 在本版中無法使用
請注意: 一般情況下不會用到 %s!
注意: 這把金鑰沒有被保護!
請注意: 某份金鑰的序號 (S/N) 與卡片的序號並不吻合
請注意: 卡片金鑰的備份已儲存至 `%s'
請注意: 對 v3 金鑰製造子鑰會失去 OpenPGP 相容性
請注意: 金鑰已經被撤銷了請注意: 沒有預設選項檔 `%s'
請注意: 舊有的預設選項檔 `%s' 已被忽略
請注意: 主鑰在線上且已存放於卡片上了
請注意: 次鑰在線上且已存放於卡片上了
請注意: 私鑰 %s 在 %s 過期了
請注意: 寄件者要求了 "妳應該祇用眼睛看"
請注意: 簽章金鑰 %s 已於 %s 過期
請注意: 強烈不建議使用單純的 S2K 模式 (0)
請注意: 信任資料庫不可寫入
姓名不可以用數字開頭
姓名至少要有五個字符長
要有私鑰纔能這麼做.
NnCcEeOoQq在私鑰圈裡沒有一致的簽章
沒有可用的說明`%s' 沒有可用的說明未指定原因索引 %d 沒有對應到次鑰
沒有這個使用者 ID.
下列項目沒有對應的信任值:
雜湊 %s 沒有對應到使用者 ID
索引 %d 沒有對應到使用者 ID
不是有效的電子郵件地址
請注意這把金鑰不能用於加密之用.  也許妳會想藉由 "--edit-key" 
指令來產生加密用的次鑰.
請注意: 這把金鑰已經被禁用了.
請注意: 這把金鑰已經過期了!
沒有東西被刪除.
沒有東西可以讓金鑰 %s 簽署
偵測到 OpenPGP 卡片編號 %s
沒有可用的 OpenPGP 卡片: %s
是否覆寫? (y/N) 使用使用者所提供的信任資料庫時可能無法設定主觀信任
個人識別碼 (PIN) 收回時傳回錯誤: %s
用於 CHV %d 的個人識別碼 (PIN) 太短; 長度最少要有 %d
個人識別碼 (PIN) 再次輸入時沒有正確重複; 請再試一次請先訂正錯誤
請判斷妳有多信任這位使用者確實驗證其他使用者的金鑰
(像是查對身份證, 或從不同的來源檢查指紋等...)的能力
請不要把電子郵件地址放進妳的真實姓名或註釋裡
請輸入約束此簽章的網域, 若無請直接按下 [Enter].
請輸入一個新的檔名. 如果妳直接按下了 Enter, 那麼
就會使用預設的檔案 (顯示在括號中).請輸入選用的註釋請輸入資料檔的名稱: 請輸入此信任簽章的深度.
深度大於 1 的話就表示妳信任這把正被簽署的金鑰,
同時也信任這把金鑰所簽署的信任簽章.
請輸入密語; 這是一個秘密的句子 
請修補這個可能的安全性裂縫
請插入卡片並按下 [Enter], 或者輸入 'c' 以取消: 請注意個人識別碼 (PIN) 的出廠設定值為
   PIN = `%s'     管理者 (Admin) PIN = `%s'
妳應該用 --change-pin 指令來加以變更
請注意顯示出來的金鑰有效性不需要更正,
除非妳重新執行程式.
請從私鑰中移除選擇.
請移除現用中的卡片並插入下列序號的卡片:
   %.*s
請再次輸入最後的密語, 以確定妳到底鍵進了些甚麼.請向 <gnupg-bugs@gnu.org> 回報程式瑕疵.
請至多選擇一把次鑰.
請精確地選擇一個使用者 ID.
請選擇撤銷的原因:
請選擇妳要產生的金鑰種類:
請選擇妳要使用的金鑰種類:
請選擇要把金鑰存放在哪裡:
請指定這把金鑰的有效期限是多久.
         0 = 金鑰不會過期
      <n>  = 金鑰在 n 天後會過期
      <n>w = 金鑰在 n 週後會過期
      <n>m = 金鑰在 n 月後會過期
      <n>y = 金鑰在 n 年後會過期
請指定這份簽章的有效期限是多久.
         0 = 簽章不會過期
      <n>  = 簽章在 n 天後會過期
      <n>w = 簽章在 n 週後會過期
      <n>m = 簽章在 n 月後會過期
      <n>y = 簽章在 n 年後會過期
請先使用 "toggle" 指令.
請稍待片刻, 系統此時正在蒐集亂數. 如果妳會覺得無聊的話,
不妨做些別的事, 這樣子甚至能夠讓亂數的品質更好.
%s 金鑰可能的動作: 偏好的金鑰伺服器:                主鑰指紋:私人的 DO 資料: 公鑰: 公鑰被禁用了.
要不儲存就離開嗎? (y/N) RSA 模組缺漏或者尺寸並非 %d 位元
RSA 質數 %s 缺漏或者尺寸並非 %d 位元
RSA 公用指數缺漏或者大於 %d 位元
真實姓名: 真的要建立撤銷憑證嗎? (y/N) 真的要建立嗎? (y/N) 真的要刪除這個自我簽章嗎? (y/N)真的要移動主要金鑰嗎? (y/N) 真的要移除所有被選擇的使用者 ID 嗎? (y/N) 真的要移除這個使用者 ID 嗎? (y/N) 真的要撤銷所有被選擇的使用者 ID 嗎? (y/N) 真的要撤銷這個使用者 ID 嗎? (y/N) 真的要簽署所有的使用者 ID 嗎? (y/N) 真的要簽署嗎? (y/N)真的要更新所選使用者 ID 的偏好嗎? (y/N) 真的要更新偏好嗎? (y/N) 撤銷原因: %s
請再輸入一次密語
請再輸入一次密語: 請再次輸入個人識別碼 (PIN): 是否要取代既有的金鑰? (y/N) 是否要取代既有的金鑰? (y/N) 妳所要求的金鑰尺寸是 %u 位元
已建立撤銷憑證.
已建立撤銷憑證.

請把這個檔案搬移到另一個妳能夠將之藏起來的媒介上;
如果有人能夠取得這份憑證的話, 那麼他也能夠讓妳的
金鑰無法繼續使用. 把這份憑證列印出來再藏到別的地
方也是很好的方法, 以免妳的儲存媒介損毀而無法讀取.
但是千萬小心: 妳的機器上的列印系統可能會在列印過
程中把這些資料暫存在某個其他人也能夠看得到的地方!
要儲存變更嗎? (y/N) 私鑰可用.
主鑰的私鑰部分沒辦法取用.
主鑰的私鑰部分存放於卡上 (on-card).
請選擇要使用的演算法.

DSA (亦即 DSS) 是數位簽章演算法 (Digital Signature Algorithm),
祇能用於簽署.

Elgamal 是祇能用於加密的演算法.

RSA 可以被用來簽署及加密.

第一把 (主要的) 金鑰一定要含有能用於簽署的金鑰.設定偏好清單至:
性別 ((M)ale, (F)emale 或留空): 簽署是否要簽署? (y/N) 簽章完全不會過期
這份簽署已經在 %s 過期了
這份簽署在 %s 過期
簽章將會在 %s 過期.
簽章的有效期限是多久? (%s) 由 %s 建立的簽章
由 %s 建立的簽章, 使用 %s 金鑰 ID %s
簽章標記: 簽章原則: SsEeAaQq次鑰 %s 已經被撤銷了.
語法: gpg [選項] [檔案]
用已知的受信任金鑰來檢查簽章
語法: gpg [選項] [檔案]
簽署, 檢查, 加密或解密
預設的操作會依輸入資料而定
這把金鑰的最小信任等級為: %s

這個隨機數字產生器根本就是七拼八湊出來的鳥東西 -
它根本就不是強而有力的亂數產生器!

*** 絕對不要把這個程式產生的任何資料拿來用!! ***

"%s" 裡的自我簽章
是 PGP 2.x 型態的簽章.
這份簽章無效. 把它從妳的鑰匙圈裡移去相當合理.這份簽章會被標記成不可匯出.
這份簽章會被標記成不可撤銷.
PGP 2.x 型態的使用者 ID 沒有偏好.
這個 JPEG 檔案真的很大 (%d 位元組) !
在 %s 模式中不允許使用這個指令.
這是一把私鑰! - 真的要刪除嗎? (y/N) 這是一份和這個金鑰使用者 ID 相繫的簽章. 通常
把這樣的簽章移除不會是個好點子. 事實上 GnuPG
可能從此就不能再使用這把金鑰了. 所以祇有在這
把金鑰的第一個自我簽章因某些原因無效, 而第二
個還可用的情況下纔這麼做.這是一份在這把金鑰上有效的簽章; 通常妳不會想要刪除這份簽章,
因為要跟別的金鑰建立起信任連結, 或由這把金鑰所簽署的金鑰憑證
會是一件相當重要的事.這把金鑰是屬於我們自己的
這把金鑰已經被禁用了這把金鑰已經過期了!這把金鑰將在 %s 過期.
這把金鑰沒有被保護.
這把金鑰可能被 %s 金鑰 %s 撤銷了 這把金鑰很可能屬於叫這個名字的使用者
這把金鑰已經在 %s 時被 %s 金鑰 %s 給撤銷了
這份簽章無法被檢驗, 因為妳沒有符合的金鑰. 妳應該延緩刪除它,
直到妳知道哪一把金鑰被使用了; 因為這把來簽署的金鑰可能透過
其他已經驗證的金鑰建立了一個信任連結.這份簽署已經在 %s 過期了.
這將會是一份自我簽章.
這會讓這把金鑰在 PGP 2.x 模式下不可使用.
將被撤銷:
要建立起信任網絡, GnuPG 需要知道哪些金鑰是被徹底信任的 -
那些金鑰通常就是妳有辦法存取到私鑰的. 回答 "yes" 來將這些
金鑰設成被徹底信任的
總共被處理的數量: %lu
取回公鑰的 URL: 未被壓縮未知的簽章種類 `%s'
用法: gpg [選項] [檔案] (或用 -h 求助)用法: gpgv [選項] [檔案] (或用 -h 求助)無論如何還是使用這把金鑰嗎? (y/N) 使用者 ID "%s" 已經過期了.使用者 ID "%s" 未經自我簽署.使用者 ID "%s" 已經被撤銷了.使用者 ID "%s" 可被簽署.使用者 ID 不再有效了警告: 警告: "%s" 是個被反對使用的指令 - 別再用了
警告: "%s" 選項已不建議使用
警告: %s 會使得 %s 失效
警告: 2 個檔案存在有互相矛盾的資訊.
警告: 這是一把 PGP2 型態的金鑰.
      增加指定撤銷者可能會導致某些版本的 PGP 駁回這把金鑰.
警告: 這是一把 PGP2 型態的金鑰.
      增加照片 ID 可能會導致某些版本的 PGP 駁回這把金鑰.
警告: 這把金鑰已經被它的指定撤銷者給撤銷了!
警告: 這把金鑰已經被它的持有人撤銷了!
警告: 這把金鑰並非以受信任的簽章所認證!
警告: 這把金鑰並非以足夠信任的簽章所認證!
警告: 這把子鑰已經被它的持有人撤銷了!
警告: 正在使用不被信任的金鑰!
警告: 我們 *不* 信任這把金鑰!
警告: 偵測到金鑰薄弱 - 請再更換密語一次.
警告: `%s' 是一個空檔案
警告: 有一份使用者 ID 簽章的日期標記為 %d 秒後的未來
警告: 一旦把某把金鑰指派為指定撤銷者後, 就無法反悔了!
警告: 收件者偏好設定中找不到編密演算法 %s
警告: 摘要演算法 %s 已不建議使用
警告: 加密過的訊息已經被變造了!
警告: 強迫使用壓縮演算法 %s (%d) 會違反收件者偏好設定
警告: 強迫使用 %s (%d) 摘要演算法會違反收件者偏好設定
警告: 強迫使用對稱式編密法 %s (%d) 會違反收件者偏好設定
警告: random_seed 檔案大小無效 - 不予採用
警告: 金鑰 %s 含有不可用的偏好設定
警告: 金鑰 %s 可能被撤銷了: 正在取回撤銷金鑰 %s
警告: 金鑰 %s 可能被撤銷了: 撤銷金鑰 %s 未出現.
警告: 金鑰伺服器經手程式 (handler) 係來自不同版本的 GnuPG (%s)
警告: 金鑰伺服器選項 `%s' 並未用於此平台
警告: 訊息被以對稱式編密法的弱金鑰加密了.
警告: 訊息未受到完整的保護
警告: 偵測到多重簽章. 祇有第一個簽章纔會被核選.
警告: 沒有任何使用者 ID 已被標示為主要 ID. 這項指令可能
      會導致不同的使用者 ID 被當成主要 ID.
警告: 沒有匯出任何東西
警告: 在 `%s' 裡的選項於這次執行期間並沒有被啟用
警告: 以可能並不安全的對稱式加密過的階段金鑰
警告: 程式可能會傾印出核心檔!
警告: 給定的收件者 (-r) 未使用公鑰加密
警告: 私鑰 %s 並沒有任的何單一 SK 加總檢查
警告: 簽章摘要與訊息不一致
警告: 正要簽署的子鑰 %s 有無效的交叉憑證
警告: 正要簽署的子鑰 %s 未經交叉認證
警告: 這份簽章不會被標記為不可匯出.
警告: 這份簽章不會被標記成不可撤銷.
警告: 這把金鑰可能已被撤銷了 (撤銷金鑰未出現)
警告: 標記 %% 無法擴張 (太大了). 現在使用未擴張的.
警告: 原則 URL 的 %% 無法擴張 (太大了). 現在使用未擴張的.
警告: 偏好金鑰伺服器 URL 的 %% 無法擴張 (太大了). 現在使用未擴張的.
警告: 無法更新金鑰 %s 於 %s: %s
警告: 無法移除暫存目錄 `%s': %s
警告: 無法移除暫存檔 (%s) `%s': %s
警告: 組態檔案 `%s' 的封入目錄所有權並不安全
警告: 延伸模組 `%s' 的封入目錄所有權並不安全
警告: 家目錄 `%s' 的封入目錄所有權並不安全
警告: 組態檔案 `%s' 的封入目錄權限並不安全
警告: 延伸模組 `%s' 的封入目錄權限並不安全
警告: 家目錄 `%s' 的封入目錄權限並不安全
警告: 組態檔案 `%s' 的所有權並不安全
警告: 延伸模組 `%s' 的所有權並不安全
警告: 家目錄 `%s' 的所有權並不安全
警告: 組態檔案 `%s' 的權限並不安全
警告: 延伸模組 `%s' 的權限並不安全
警告: 家目錄 `%s' 的權限並不安全
警告: 正在使用實驗性的編密演算法 %s
警告: 正在使用實驗性的摘要演算法 %s
警告: 正在使用實驗性的公鑰演算法 %s
警告: 正在使用不安全的記憶體!
警告: 正在使用不安全的隨機數字產生器!!
我們需要產生大量的隨機位元組. 這個時候妳可以多做一些事情
(像是敲打鍵盤, 移動滑鼠, 讀寫硬碟之類的)
這會讓隨機數字產生器有更多的機會獲得夠多的亂數.
妳想要用多大的金鑰尺寸? (%u) 當妳在某把金鑰上簽署某個使用者 ID, 妳首先必須先驗證那把
金鑰確實屬於那個使用者 ID 上叫那個名字的人. 這對那些知道
妳多小心驗證的人來說很有用.

"0" 表示妳不能提出任何特別的主張來表明
    妳多仔細驗證那把金鑰

"1" 表示妳相信這把金鑰屬於那個主張是主人的人,
    但是妳不能或沒有驗證那把金鑰.
    這對那些祇想要 "個人的" 驗證的人來說很有用,
    因為妳簽署了一把擬似匿名使用者的金鑰.

"2" 表示妳真的仔細驗證了那把金鑰.
    例如說, 這能表示妳驗證了這把金鑰的指紋和
    使用者 ID, 並比對了照片 ID.

"3" 表示妳真的做了大規模的驗證金鑰工作.
    例如說, 這能表示妳向金鑰持有人驗證了金鑰指紋,
    而且妳透過附帶照片而難以偽造的文件 (像是護照)
    確認了金鑰持有人的姓名與金鑰上使用者 ID 的一致,
    最後妳還 (透過電子郵件往來) 驗證了金鑰上的
    電子郵件位址確實屬於金鑰持有人.

請注意上述關於等級 2 和 3 的例子 "祇是" 例子而已.
最後, 還是得由妳自己決定當妳簽署其他金鑰時,
甚麼是 "漫不經心", 而甚麼是 "超級謹慎".

如果妳不知道應該選甚麼答案的話, 就選 "0".妳正在撤銷這些簽章:
妳正在使用 `%s' 字元集.
妳不能變更 v3 金鑰的使用期限
妳不能刪除最後一個使用者 ID!
妳沒有指定一個使用者 ID. (妳可能得用 "-r")
妳不想要用密語 - 這大概是個 *糟* 點子!

妳不想要有密語 - 這個想法實在是 **遭透了**!
我仍然會照妳想的去做. 妳任何時候都可以變更妳的密語,
僅需要再次執行這個程式, 並且使用 "--edit-key" 選項即可.

妳已經簽署了金鑰 %s 上的這些使用者 ID:
妳不可以把指定撤銷者增加到 PGP2 型態的金鑰裡.
妳不可以把照片 ID 增加到 PGP2 型態的金鑰裡.
妳不能在 --pgp2 模式下, 拿 PGP 2.x 金鑰做出 OpenPGP 簽章.
妳至少必須選擇一把金鑰.
妳至少得選擇一個使用者 ID.
妳一定祇得選擇一把金鑰.
妳需要一個密語來保護妳的私鑰.

妳需要用密語來解開下列使用者的
私鑰: "%s"
妳需要用密語來解開下列使用者的私鑰:
"%.*s"
%u 位元長的 %s 金鑰, ID %s, 建立於 %s%s
妳選擇了這個使用者 ID:
    "%s"

妳應該為這份憑證指定一個原因.
根據情境的不同, 妳應該可以從這個清單中選出一項:
  "金鑰已經被洩漏了"
      如果妳相信有某個未經許可的傢伙取得了妳的私鑰的話,
      就選這個.
  "金鑰被代換了"
      如果妳把妳的金鑰換成新的了, 就選這個.
  "金鑰不再被使用了"
      如果妳已經撤回了這把金鑰, 就選這個.
  "使用者 ID 不再有效了"
      如果這個使用者 ID 不再被使用了, 就選這個;
      這通常用來表示某個電子郵件位址不再有效了.
妳目前在 "%s" 的簽章
已經過期了.
妳目前在 "%s" 的簽章
是一份本地簽章.
妳的決定是甚麼? 妳要選哪一個? 妳的選擇是? (輸入 `?' 以取得更多資訊): 妳的系統無法顯示 2038 年以後的日期.
不過, 它可以正確處理直到 2106 年之前的年份.
[  完全  ][ 未定義 ][ 已過期 ][ 已撤銷 ][  未知  ][找不到使用者 ID][檔名][  勉強  ][未設定][撤銷][自我簽章][  徹底  ][ 不確定 ]`%s' 已經被壓縮了
`%s' 不是一個 JPEG 圖檔
`%s' 不是一個標準的檔案 - 已略過
`%s' 不是一個有效的字元集
`%s' 不是一個有效的長式金鑰 ID
`%s' 不是一個有效的簽章使用期限
取用管理者指令尚未被組態過
動作 `%s' 並未被金鑰伺服器方案 (scheme) `%s' 所支援
加入某把金鑰至智慧卡增加一個照片 ID增加一把撤銷金鑰增加一把次鑰增加一個使用者 ID不明確的選項 `%s'
匿名收件者; 正在嘗試使用私鑰 %s ...
封裝檔頭: 封裝: %s
假定 %s 為加密過的資料
假設金鑰 %s 的損壞簽章導因於某個未知的關鍵位元
假設被簽署的資料在 `%s'
損壞的 MPI損壞的 URI損壞的憑證損壞的金鑰錯誤的密語損壞的公鑰損壞的私鑰損壞的簽章盡量安靜些二進制build_packet 失敗: %s
cC正在快取鑰匙圈 `%s'
無法存取 %s - 無效的 OpenPGP 卡片?
無法存取 `%s': %s
無法關閉 `%s': %s
無法連接至 `%s': %s
無法建立 `%s': %s
無法建立備份檔案 `%s': %s
無法建立目錄 `%s': %s
無法為 `%s' 建立鎖定
無法讓系統停止傾印核心檔: %s
無法在批次模式中這樣做
沒有 "--yes" 就沒辦法在批次模式中這麼做
無法以 %u 位元長的 p 以及 %u 位元長的 q 產生質數
無法產生少於 %d 位元的質數
無法操作公開金鑰演算法 %d
無法處理長於 %d 字符的文字列
無法鎖定 `%s'
無法開啟 `%s'
無法開啟 `%s': %s
無法開啟被簽署過的資料 `%s'
沒辦法開啟鑰匙圈無法在 v3 (PGP 2.x 型態) 的簽章內放入原則 URL
無法在 v3 (PGP 2.x 型態) 的金鑰簽章內放入原則 URL
無法在 v3 (PGP 2.x 型態) 的金鑰簽章內放入標記資料
無法在 v3 (PGP 2.x 型態) 的簽章內放入標記資料
無法在批次模式中查詢密語
無法讀取 `%s': %s
無法取得檔案 `%s' 的資訊: %s
因為處於 S2K 模式下而無法使用對稱式 ESK 封包
無法寫入 `%s': %s
已取消由使用者取消了
cancel|cancel無法將 PGP 2.x 型態的金鑰指派為指定撤銷者
無法避免對稱式編密法的弱金鑰; 已經試了 %d 次了!
卡片已被永久鎖住了!!
卡片編號: 變更要取回金鑰的 URL變更某個憑證中心 (CA) 指紋變更某張卡片的個人識別碼 (PIN)變更卡片持有人的名字變更卡片持有者的性別變更卡片上的資料從金鑰或所選的次鑰中變更使用期限變更介面語言偏好設定變更登入姓名更改主觀信任更改密語檢查簽章檢查已建立的簽章時發生錯誤: %s
正在檢查信任資料庫
加總檢查錯誤編密演算法 %d%s 未知或已停用了
編密法延伸模組 `%s' 因為權限不安全而未被載入
冒號缺漏completes-needed 一定要大於 0
指令彼此矛盾
無法剖析金鑰伺服器 URI
建立以 ASCII 封裝過的輸出建立於: %s建立的時間戳印缺漏
資料未被儲存; 請用 "--output" 選項來儲存它們
解開封裝失敗: %s
資料解密 (預設)解密失敗: %s
解密成功
刪除所選的次鑰刪除所選的使用者 ID從所選的使用者 ID 中刪除簽章刪除金鑰區塊時失敗了: %s
深度: %d  有效: %3d  已簽署: %3d  信任: %d-, %dq, %dn, %dm, %df, %du
目錄 `%s' 已建立
禁用金鑰已禁用不要做任何改變啟用金鑰進行封裝失敗: %s
加密資料已用 %lu 個密語加密了
已用 %s 金鑰, ID %s 加密了
已用 %u 位元長的 %s 金鑰,  ID %s, 建立於 %s 加密了
已用 1 個密語加密了
以未知的演算法 %d 加密過
在 --pgp2 模式下加密訊息需要 IDEA 編密法
僅使用對稱式編密法來加密建立 `%s' 時發生錯誤: %s
建立鑰匙圈 `%s' 時發生錯誤: %s
建立密語的時候發生錯誤: %s
在 `%s' 中尋找信任記錄時出錯: %s
取得現用金鑰資訊時發生錯誤: %s
取得新的個人識別碼 (PIN) 時出錯: %s
在 `%s' 中出錯: %s
結尾列有問題
讀取 `%s' 時發生錯誤: %s
讀取應用程式資料時出錯
讀取指紋 DO 時出錯
讀取金鑰區塊時發生錯誤: %s
讀取私鑰區塊 "%s" 時出錯: %s
從卡片取回 CHV 狀態時出錯
寫到鑰匙圈 `%s' 時發生錯誤: %s
寫入公鑰鑰匙圈 `%s' 時發生錯誤: %s
寫入私鑰鑰匙圈 `%s' 時發生錯誤: %s
既有的金鑰將被取代
已過期已過期: %s過期: %s匯出金鑰把金鑰匯出至某個金鑰伺服器上未被允許匯出私鑰
本版並不支援外部金鑰伺服器叫用
因為不安全的檔案權限選項, 而禁用了外部程式叫用
信任資料庫啟始失敗: %s
重新建立鑰匙圈快取失敗: %s
存放創生資料失敗: %s
存放指紋失敗: %s
存放金鑰失敗: %s
女性從卡片 URL 取回指定的金鑰檔案關閉錯誤檔案建立錯誤檔案刪除錯誤檔案已存在檔案開啟錯誤檔案讀取錯誤檔案更名錯誤檔案寫入錯誤把所選的使用者 ID 標為主要強迫使用強迫使用 %s (%d) 對稱式編密法會違反收件者偏好設定
`%s' 的 fstat 失敗於 %s: %s
fstat(%d) 失敗於 %s: %s
完全一般性錯誤產生 PGP 2.x 相容性訊息產生一份新的金鑰對產生一份撤銷憑證產生新的金鑰產生金鑰時失敗
正在產生新的金鑰
正在產生私鑰保護會用到的舊式 16 位元加總檢查
gpg-agent 在此階段無法使用
gpg-agent 協定版本 %d 未被支援
iImMqQsS從某個金鑰伺服器上匯入金鑰匯入/合併金鑰未被允許匯入私鑰
輸入列 %u 太長或者列末的 LF 遺失了
輸入列比 %d 字符還長
無效無效的 S2K 模式; 一定要是 0, 1 或 3
無效的參數無效的封裝無效的封裝檔頭: 無效的封裝: 列長超出 %d 字符
無效的明文簽章檔頭
無效的破折號逸出列: 無效的預設偏好
無效的 default-cert-level; 一定要是 0, 1, 2 或 3
無效的匯出選項
無效的指紋無效的 `%s' 雜湊演算法
無效的匯入選項
偏好字串中含有無效的 `%s' 項目
無效的鑰匙圈無效的金鑰伺服器選項
無效的金鑰伺服器協定 (我們用 %d != 經手程式 %d)
無效的清單選項
無效的 min-cert-level; 一定要是 1, 2 或 3
無效的封包無效的密語無效的個人編密法偏好
無效的個人壓縮偏好
無效的個人摘要偏好
無效的 64 進位字符 %02x 被跳過了
在 proc_tree() 中偵測到無效的 root 封包
OpenPGP 卡片的格式無效 (DO 0x93)
無效的數值
無效的驗證選項
我們強烈建議妳更新妳的偏好設定, 並
在金鑰伺服器上找不到金鑰 "%s"
金鑰 "%s" 找不到: %s
金鑰 %s 沒有使用者 ID
金鑰 %s 已被標記成徹底信任了
金鑰 %s 在信任資料庫中出現了不止一次
金鑰 %s 已經在 %lu 秒後的未來製造出來了 (可能是因為時光旅行或時鐘的問題)
金鑰 %s 已經在 %lu 秒後的未來製造出來了 (可能是因為時光旅行或時鐘的問題)
金鑰 %s: "%s" %d 個新的簽章
金鑰 %s: "%s" %d 個新的子鑰
金鑰 %s: "%s" %d 個新的使用者 ID
金鑰 %s: "%s" 已清除掉 %d 份簽章
金鑰 %s: "%s" 已清除掉 %d 份簽章
金鑰 %s: "%s" 已清除掉 %d 個使用者 ID
金鑰 %s: "%s" 已清除掉 %d 個使用者 ID
金鑰 %s: "%s" 1 個新的簽章
金鑰 %s: "%s" 1 個新的子鑰
金鑰 %s: "%s" 1 個新的使用者 ID
金鑰 %s: "%s" 沒有被改變
金鑰 %s: 已新增 "%s" 撤銷憑證
金鑰 %s: "%s" 撤銷憑證已被匯入
金鑰 %s: PGP 2.x 樣式的金鑰 - 已跳過
金鑰 %s: PKS 子鑰的訛誤已被修復
金鑰 %s: 如受信任的金鑰般被接受了
金鑰 %s: 非自我簽署的使用者 ID "%s" 已被接受
金鑰 %s: 已經在私鑰鑰匙圈中了
金鑰 %s: 無法定位原始的金鑰區塊: %s
金鑰 %s: 無法讀取原始的金鑰區塊: %s
金鑰 %s: 已新增直接金鑰簽章
金鑰 %s: 跟我們的副本不吻合
金鑰 %s: 偵測到重複的使用者 ID - 已合併
金鑰 %s: 無效的撤銷憑證: %s - 已駁回
金鑰 %s: 無效的撤銷憑證: %s - 已跳過
金鑰 %s: 使用者 ID "%s" 有無效的自我簽章
金鑰 %s: 無效的附帶子鑰
金鑰 %s: 無效的子鑰撤銷
金鑰 %s: 新的金鑰 - 已跳過
金鑰 %s: 沒有公鑰 - 無法套用撤銷憑證
金鑰 %s: 受信任的金鑰沒有公鑰 - 已跳過
金鑰 %s: 沒有子鑰可供附帶
金鑰 %s: 沒有子鑰可供金鑰撤銷
金鑰 %s: 沒有子鑰可供附子鑰簽章之用
金鑰 %s: 沒有子鑰可供子鑰撤銷簽章使用
金鑰 %s: 沒有使用者 ID
金鑰 %s: 簽章沒有使用者 ID
金鑰 %s: 沒有有效的使用者 ID
金鑰 %s: 不可匯出的簽章 (等級 0x%02X) - 已跳過
金鑰 %s: 未被保護 - 已跳過
金鑰 %s: 公鑰 "%s" 已被匯入
金鑰 %s: 找不到公鑰: %s
金鑰 %s: 多重附帶子鑰已被移除
金鑰 %s: 多重子鑰撤銷已移除
金鑰 %s: 撤銷憑證在錯誤的地方 - 已跳過
金鑰 %s: 私鑰被匯入了
金鑰 %s: 找不到私鑰: %s
金鑰 %s: 私鑰使用了無效的編密法 %d - 已跳過
金鑰 %s: 祇有私鑰而沒有公鑰 - 已跳過
金鑰 %s: 子鑰已跳過
金鑰 %s: 使用者 ID "%s" 已跳過
金鑰 %s: 子鑰簽章在錯誤的地方 - 已跳過
金鑰 %s: 非預期的簽章等級 (0x%02X) - 已跳過
金鑰 %s: 未被支援的公鑰演算法
金鑰 %s: 使用者 ID "%s" 使用了未被支援的公鑰演算法
金鑰已存在
金鑰匯出時失敗: %s
金鑰產生已完工 (%d 秒)
金鑰已經在 %lu 秒後的未來製造出來了 (可能是因為時光旅行或時鐘的問題)
金鑰已經在 %lu 秒後的未來製造出來了 (可能是因為時光旅行或時鐘的問題)
金鑰未被標示為不安全 - 不能夠拿來跟假的隨機數字產生器併用!
在金鑰伺服器上找不到金鑰
不可能進行金鑰操作: %s
金鑰區塊資源 `%s': %s
鑰匙圈 `%s' 已建立
金鑰伺服器通訊出錯: %s
金鑰伺服器並未送出版本 (VERSION)
金鑰伺服器錯誤金鑰伺服器內部出錯
從金鑰伺服器接收時失敗: %s
從金鑰伺服器更新時失敗: %s
從金鑰伺服器中搜尋時失敗: %s
送至金鑰伺服器時失敗: %s
金鑰伺服器逾時
金鑰尺寸無效; 改用 %u 位元
金鑰尺寸增大到 %u 位元
列太長列出所有可用的資料列出並檢查金鑰簽章列出金鑰和使用者 ID列出金鑰列出金鑰和指紋列出金鑰和簽章列出偏好 (專家模式)列出偏好 (囉唆模式)列出私鑰建立一份分離式簽章僅把時間戳印矛盾視為警告make_keysig_packet 失敗: %s
男性CRC 被變造過
被變造的 GPG_AGENT_INFO 環境變數
被變造過的使用者 ID勉強marginals-needed 一定要大於 1
max-cert-depth 一定要介於 1 和 255 之間
變更或解凍個人識別碼 (PIN) 的選單移動某把備份金鑰至智慧卡移動某把金鑰至智慧卡正在把金鑰的簽章搬移到正確的位置去
nN多層明文簽章
網路錯誤永遠不會永遠不過期新的設定檔 `%s' 被建立了
下次信任資料庫檢查將於 %s 進行
no在群組定義 `%s' 裡找不到 = 記號
沒有卡片沒有相對應的公鑰: %s
沒有預設的私鑰鑰匙圈: %s
偵測不到亂數蒐集模組
沒有金鑰伺服器方案 (scheme) `%s' 的經手程式 (handler)
沒有金鑰伺服器動作!
沒有已知的金鑰伺服器 (使用 --keyserver 選項)
不需要檢查信任資料庫
在 `%s' 信任模型中並不需要檢查信任資料庫
在 `%s' 信任模型中並不需要更新信任資料庫
沒有已支援的遠端程式執行
沒有找到 "%s" 用的撤銷金鑰
沒有私鑰
公鑰 %s 沒有相對應的私鑰 - 正在忽略
沒有被簽署過的資料
沒有這個使用者 ID沒有找到任何徹底信任的金鑰
找不到有效的 OpenPGP 資料.
沒有有效的地址
找不到可寫的鑰匙圈: %s
找不到可寫的公鑰鑰匙圈: %s
找不到可寫的私鑰鑰匙圈: %s
不是一份分離的簽章
這不是 OpenPGP 卡片未被加密不強迫使用未被處理未被支援請注意: random_seed 檔案是空的
請注意: random_seed 檔案未被更新
oO很好, 我們就是匿名收件者.
okay|okay不支援舊式的 DEK 編碼
舊型 (PGP 2.x) 簽章
尚未啟用安全的記憶體前, 不可能進行操作
選項檔 `%s': %s
原始的檔名 ='%.*s'
主觀信任資訊已經被清除
主觀信任值缺漏密語係以未知的摘要演算法 %d 所產生
密語再次輸入時沒有正確重複; 請再試一次請做一次 --check-trustdb
請輸入選用 (但強烈建議使用) 的電子郵件位址請參考 http://www.gnupg.org/faq.html 上進一步的資訊
請改以 "%s%s" 代替
公鑰正被產生中, 請稍候 ...
偏好設定 `%s' 重複了
檔案未預期的結束 (CRC 的部分未結束)
檔案未預期的結束 (於結尾處)
檔案未預期的結束 (沒有 CRC 的部分)
列印卡片狀態處理加密的封包有問題
代理程式的問題 - 正在停用代理程式
覆寫前先詢問保護演算法 %d%s 未被支援
保護摘要 %d 未被支援
公鑰和私鑰已經被建立及簽署了.
公鑰 %s 比簽章還要新了 %lu 秒
公鑰 %s 比簽章還要新了 %lu 秒
找不到公鑰 %s: %s
公鑰解密失敗: %s
公鑰與私鑰並不吻合!
公鑰加密過的資料: 完好的 DEK
公鑰為 %s
找不到公鑰徹底信任金鑰 %s 的公鑰沒有被找到
qQquit離開這個選單封裝裡出現被引號括住的可列印字符 - 可能是有瑕疵的送信程式造成的
重新散佈此金鑰, 以避免潛在的演算法不一致問題.
讀取 `%s' 錯誤: %s
正在從 `%s' 讀取中
從 `%s' 讀取選項
讀取公鑰時失敗: %s
正在從標準輸入讀取 ...
撤銷原因: 正在更新 %d 份金鑰自 %s
正從 %s 更新 1 份金鑰
從公鑰鑰匙圈裡移去金鑰從私鑰鑰匙圈裡移去金鑰把 `%s' 重新新命成 `%s' 時失敗: %s
正在請求金鑰 %s 自 %s
正在請求金鑰 %s 自 %s 伺服器 %s
資源限制回應中未包含 RSA 系數
回應中未包含 RSA 公用指數
回應中未包含公鑰資料
撤銷註釋: 撤銷金鑰或所選的次鑰撤銷所選的使用者 ID從所選的使用者 ID 上撤銷簽章已撤銷被妳的金鑰 %s 於 %s 所撤銷了
已撤銷: %s加大到 %u 位元
儲存並離開在某個金鑰伺服器上搜尋金鑰正在搜尋 "%s" 於 %s
正在搜尋 "%s" 於 %s 伺服器 %s
找不到私鑰 "%s": %s
私鑰已經存放於卡片上了
無法取用私鑰私鑰部分無法取用
私鑰部分無法取用
選擇次鑰 N使用者 ID 選了 N所選的憑證摘要演算法無效
所選的編密演算法無效
所選的壓縮演算法無效
所選的摘要演算法無效
遞送金鑰 %s 至 %s
遞送金鑰 %s 至 %s 伺服器 %s
設定所選使用者 ID 的偏好清單顯示管理者指令顯示金鑰指紋顯示所選的照片 ID顯示這份線上說明簽署某把金鑰僅在本地簽署某把金鑰簽署或編輯某把金鑰簽署所選的使用者 ID [* 請參見底下有關的註解]僅在本地簽署所選的使用者 ID用不可撤銷的簽章來簽署所選的使用者 ID用信任簽章來簽署所選的使用者 ID簽章驗證已被抑制
目前建立的簽章: %lu
已被妳的金鑰 %s 於 %s%s%s 簽署了
簽署時失敗了: %s
簽署:已跳過 "%s": %s
已跳過 "%s": 重複了
已跳過: 公鑰已經被設過了
已跳過: 公鑰已經被設成預設收件者
已跳過: 私鑰已經存在
正在跳過 %d 型態的區塊
正在跳過使用者 ID "%s" 的 v3 自我簽章
獨立撤銷 - 請用 "gpg --import" 來套用
等級 0x%02x 的獨立簽章
儲存金鑰到卡片上時失敗: %s
%d 類別的子封包設定了關鍵位元
`%s' 的對稱式加密失敗: %s
叫用外部程式時發生系統錯誤: %s
從這個鑰匙圈裡取用金鑰文字模式IDEA 編密法外掛模組不存在
給定的的憑證原則 URL 無效
給定的偏好金鑰伺服器 URL 無效
給定的簽章原則 URL 無效
簽章無法被驗證.
請記住簽章檔 (.sig 或 .asc)
應該是第一個命令列給定的檔案.
信任資料庫損毀了; 請執行 "gpg --fix-trustdb".
公鑰 "%s" 有相對應的私鑰!
這是由 PGP 產生的 ElGamal 金鑰, 用於簽章並不安全!這把金鑰已被指定為撤銷者了
這可能是由於遺失自我簽章所導致的後果
這個訊息對 %s 來說無法使用
在這個作業平台上叫用外部程式時需要暫存檔
時間戳印有矛盾在私鑰清單和公鑰清單間切換切換簽章強制個人識別碼 (PIN) 的旗標編密偏好過多
壓縮偏好過多
摘要偏好過多
pk 快取裡有太多項目 - 已禁用
信任資料庫錯誤信任記錄 %lu 不是所請求的類別 %d
信任記錄 %lu, 請求類別 %d: 讀取失敗: %s
信任記錄 %lu, 類別 %d: 寫入失敗: %s
信任: %s信任資料庫記錄 %lu: 本地搜尋失敗: %s
信任資料庫記錄 %lu: 寫入失敗 (n=%d): %s
信任資料庫更動量過大
信任資料庫: 本地搜尋失敗: %s
信任資料庫: 讀取失敗 (n=%d): %s
信任資料庫: 同步化失敗: %s
徹底無法顯示照片 ID!
無法執行外部程式
無法執行程式 `%s': %s
無法執行 shell `%s': %s
無法開啟 JPEG 圖檔 `%s': %s
無法讀取外部程式回應: %s
無法把執行檔路徑設成 %s
無法更新信任資料庫版本記錄: 寫入失敗: %s
妳正要用來加密的所有金鑰都不能使用 IDEA 編密法.
無法使用未知的信任模型 (%d) - 現在採用 %s 信任模型
uncompressed|none|未被壓縮|無未定義未預期的封裝: 未預期的資料未被採用的編密演算法未被採用的公鑰演算法未知未知的編密演算法未知的壓縮演算法未知的組態項目 `%s'
未知的預設收件者 "%s"
未知的摘要演算法未知的金鑰保護演算法
未知的選項 `%s'
未知的封包型態未知的保護演算法
未知的公鑰演算法未知的簽章層級未知的版本外部程式不自然地離開
未特定未被支援的 URI無法使用的公鑰演算法不可用的公鑰不可用的私鑰從某個金鑰伺服器上更新所有的金鑰更新失敗: %s
更新私鑰失敗: %s
更新信任資料庫用法: %s用法: gpg [選項] 當作輸出檔案來使用使用標準的文字模式請先以 "--delete-secret-keys" 選項來刪除它.
使用嚴謹的 OpenPGP 行為使用這個使用者 ID 來簽署或解密使用者 ID "%s" 已經被撤銷了
使用者 ID: "%s"
正在使用 %s 信任模型
正在使用編密法 %s
正在使用次鑰 %s 來替換主鑰 %s
有效性: %s囉唆模式管理者個人識別碼 (PIN) 之驗證目前在此指令中被禁止了
驗證 CHV %d 失敗: %s
驗證某份簽章驗證個人識別碼 (PIN) 並列出所有的資料金鑰薄弱建立了弱金鑰 - 正在重試
加密過的階段金鑰 (%d) 尺寸詭異
因為 %s 而不會在不安全的記憶體中執行
正在寫入直接簽章
正在寫入附鑰簽章
正在將公鑰寫至 `%s'
正在寫入私鑰 stub 至 `%s'
正在將私鑰寫至 `%s'
正在寫入自我簽章
正在寫到 `%s'
正在寫入到標準輸出
用了錯誤的私鑰yYyes妳在 --pgp2 模式下祇能夠使用 PGP 2.x 型態的金鑰來做明文簽署
妳在 --pgp2 模式下祇能夠使用 PGP 2.x 型態的金鑰來做分離簽署
在 --pgp2 模式中, 妳祇能以 2048 位元以下的 RSA 金鑰加密
妳祇有在 --pgp2 模式下纔能做出分離式或明文簽章
妳可以像這樣更新妳的偏好設定: gpg --edit-key %s updpref save
妳在 --pgp2 模式下時, 不能同時簽署和加密
妳不能指派某把金鑰為它自己的指定撤銷者
妳不能在 %s 模式中使用 --symmetric --encrypt
妳不能在 --s2k-mode 0 中使用 --symmetric --encrypt
妳不能在 %s 模式中使用 --symmetric --sign --encrypt
妳不能在 --s2k-mode 0 中使用 --symmetric --sign --encrypt
妳找到一個瑕疵了 ... (%s:%d)
妳不能夠將 %s 用於 %s 模式中
妳不該將編密演算法 `%s' 用於 %s 模式中
妳不該將壓縮演算法 `%s' 用於 %s 模式中
妳不該將摘要演算法 `%s' 用於 %s 模式中
啟用 --pgp2 時妳祇應該使用檔案, 而非管道
|AN|New Admin PIN|A|Admin PIN|檔案描述|把狀態資訊寫入此檔案描述|名字|以「名字」作為加密對象|N|New PIN|N|設定壓縮等級為 N (0 表示不壓縮)|[檔案]|建立一份明文簽章|[檔案]|建立一份簽章|演算法 [檔案]|印出訊息摘要||請輸入 PIN%%0A[簽署完成: %lu]

Anon7 - 2021