A$Y,242-gEE (  7 @, Im H 0 1 h2 D '"<+-h;=%Z%&$@630j .$4<I;I 2+%^&I%D[t7 2 5(.^EF &  !6!@"IX"H"0"#j$E)+ +,+ ,<,-Z,;,,,,=-%O-%u-&-$-@-7(.1`.../.$.4/<C/</J/02'0%Z0'00I01#1B1Z1s1171.% <,-;=2?! 38 :4'9@*>"#0$6+)&A 51(/7  Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! (Need %d more bytes) 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) " "%s": preference for cipher algorithm %s ASCII armored output forced. Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? Change (N)ame, (C)omment, (E)mail or (Q)uit? Cipher: Email address: IDEA cipher unavailable, optimistically attempting to use %s instead Key generation canceled. 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.Not a valid email address Please don't put the email address into the real name or the comment 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. Reset Code not or not anymore available 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.User ID "%s": already minimized WARNING: 2 files with confidential information exists. WARNING: cipher algorithm %s not found in recipient preferences WARNING: forcing symmetric cipher %s (%d) violates recipient preferences WARNING: message was encrypted with a weak key in the symmetric cipher. WARNING: using experimental cipher algorithm %s 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. 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 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. armor header: armor: %s can't gen prime with pbits=%u qbits=%u canceledcannot avoid weak key for symmetric cipher; tried %d times! cipher algorithm %d%s is unknown or disabled cipher extension `%s' not loaded due to unsafe permissions create ascii armored outputdearmoring failed: %s enarmoring failed: %s encrypting a message in --pgp2 mode requires the IDEA cipher encryption only with symmetric cipherfailed to initialize the TrustDB: %s failed to store the creation date: %s failed to store the fingerprint: %s forcing symmetric cipher %s (%d) violates recipient preferences honor the PKA record set on a key when retrieving keyshonor the preferred keyserver URL set on the keyinvalid armorinvalid armor header: invalid armor: line longer than %d characters invalid personal cipher preferences key %s: secret key with invalid cipher %d - skipped operation is not possible without initialized secure memory please enter an optional but highly suggested email addressquoted printable character in armor - probably a buggy MTA has been used reading public key failed: %s repair damage from the pks keyserver during importselected cipher algorithm is invalid the IDEA cipher plugin is not present too many cipher preferences unable to use the IDEA cipher for all of the keys you are encrypting to. unexpected armor: unimplemented cipher algorithmunknown armor header: unknown cipher algorithmuse strict OpenPGP behaviorusing cipher %s you may not use cipher algorithm `%s' while in %s mode Project-Id-Version: gnupg Report-Msgid-Bugs-To: FULL NAME POT-Creation-Date: 2009-09-02 18:19+0200 PO-Revision-Date: 2010-03-17 16:39+0000 Last-Translator: Robert Readman Language-Team: English (United Kingdom) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Launchpad-Export-Date: 2011-02-05 03:51+0000 X-Generator: Launchpad (build 12309) Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! (Need %d more bytes) You need a user ID to identify your key; the software constructs the user ID from the Real Name, Comment and E-mail Address in this form: "Heinrich Heine (Der Dichter) " "%s": preference for cypher algorithm %s ASCII armoured output forced. Change (N)ame, (C)omment, (E)-mail or (O)kay/(Q)uit? Change (N)ame, (C)omment, (E)-mail or (Q)uit? Cypher: E-mail address: IDEA cypher unavailable, optimistically attempting to use %s instead Key generation cancelled. N to change the name. C to change the comment. E to change the e-mail address. O to continue with key generation. Q to to quit the key generation.Not a valid e-mail address Please don't put the e-mail address into the real name or the comment Please wait while entropy is being gathered. Do some work to help improve the quality of the entropy and to prevent being bored. Reset Code is not available any more. 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 any more. So do this only if this self-signature is for some reason not valid and a second one is available.User ID "%s": already minimised WARNING: 2 files with confidential information exist. WARNING: cypher algorithm %s not found in recipient preferences WARNING: forcing symmetric cypher %s (%d) violates recipient preferences WARNING: message was encrypted with a weak key in the symmetric cypher. WARNING: using experimental cypher algorithm %s 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, use the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. 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 e-mail) that the e-mail 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 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 unauthorised 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 e-mail address invalid. armour header: armour: %s can't generate prime with pbits=%u qbits=%u cancelledcannot avoid weak key for symmetric cypher; tried %d times! cypher algorithm %d%s is unknown or disabled cypher extension `%s' not loaded due to unsafe permissions create ASCII armoured outputdearmouring failed: %s enarmouring failed: %s encrypting a message in --pgp2 mode requires the IDEA cypher encryption only with symmetric cypherfailed to initialise the TrustDB: %s could not store the creation date: %s could not store the fingerprint: %s forcing symmetric cypher %s (%d) violates recipient preferences honour the PKA record set on a key when retrieving keyshonour the preferred keyserver URL set on the keyinvalid armourinvalid armour header: invalid armour: line longer than %d characters invalid personal cypher preferences key %s: secret key with invalid cypher %d - skipped operation is not possible without initialised secure memory please enter an optional but highly suggested e-mail addressquoted printable character in armour - probably a buggy MTA has been used could not read public key: %s repair damage from the PKS keyserver during importselected cypher algorithm is invalid the IDEA cypher plug-in is not present too many cypher preferences unable to use the IDEA cypher for all of the keys you are encrypting to. unexpected armour: unimplemented cypher algorithmunknown armour header: unknown cypher algorithmuse strict OpenPGP behaviourusing cypher %s you may not use cypher algorithm `%s' while in %s mode