xca_de.ts

来自「一个精简的CA程序」· TS 代码 · 共 1,958 行 · 第 1/5 页

    <message>
        <source>Please give a name to the new key and select the desired keysize</source>
        <translation>Bitte geben Sie dem Schl眉ssel einen Namen und w盲hlen Sie die gew眉nschte Schl眉ssell盲nge</translation>
    </message>
    <message>
        <source>Key properties</source>
        <translation>Schl眉sseleigenschaften</translation>
    </message>
    <message>
        <source>Name:</source>
        <translation type="obsolete">Name:</translation>
    </message>
    <message>
        <source>Keysize</source>
        <translation>Schl眉ssell盲nge</translation>
    </message>
    <message>
        <source>New Key</source>
        <translation>Neuer Schl眉ssel</translation>
    </message>
    <message>
        <source>&amp;Cancel</source>
        <translation>&amp;Abbrechen</translation>
    </message>
    <message>
        <source>C&amp;reate</source>
        <translation>E&amp;rstellen</translation>
    </message>
    <message>
        <source>Usually 1024 or 2048 bit keys are used</source>
        <translation>Normalerweise werden 1024 oder 2048 bit Schl眉ssel verwendet</translation>
    </message>
    <message>
        <source>The internal name of the new key</source>
        <translation>Interner Name des neuen Schl眉ssels</translation>
    </message>
    <message>
        <source>Name</source>
        <translation>Name</translation>
    </message>
</context>
<context>
    <name>NewX509</name>
    <message>
        <source>Empty Template</source>
        <translation>Leere Vorlage</translation>
    </message>
    <message>
        <source>Certificate request</source>
        <translation>Unterschriftsanfrage</translation>
    </message>
    <message>
        <source>Template</source>
        <translation>Vorlage</translation>
    </message>
    <message>
        <source> change</source>
        <translation>脛ndern</translation>
    </message>
    <message>
        <source>Certificate</source>
        <translation>Zertifikat</translation>
    </message>
    <message>
        <source>Server Template</source>
        <translation>Server Vorlage</translation>
    </message>
    <message>
        <source>Client Template</source>
        <translation>Client Vorlage</translation>
    </message>
    <message>
        <source>CA Template</source>
        <translation>CA Vorlage</translation>
    </message>
    <message>
        <source>You are done with entering all parameters for creating a Certificate.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Welcome to the settings for certificate signing requests.
A signing request needs a private key, so it will be created if there isn&apos;t any unused key available in the key database. This signing request can then be given to a Certification authority while the private key of the request and of the resulting certificate returned from the CA does never leave your computer.</source>
        <translation type="obsolete"></translation>
    </message>
    <message>
        <source>You are done with entering all parameters for generating a Certificate signing request. The resulting request should be exported and send to an appropriate CA for signing it.</source>
        <translation type="obsolete"></translation>
    </message>
    <message>
        <source>Welcome to the settings for Templates.
This templates do not refer to any ASN.1 structure but are used to keep default settings for signing requests and certificates. When creating a Request or Certificate the template can preset the needed fields with default settings.</source>
        <translation type="obsolete"></translation>
    </message>
    <message>
        <source>You are done with entering all parameters for the Template.
After this step the template can be assigned to one of your CAs to be autoatically applied when signing with this CA.</source>
        <translation type="obsolete"></translation>
    </message>
    <message>
        <source>Welcome to the settings for Certificates.
The information for the new Certificate can either be grabbed from a given Certificate-request or be filled in by hand. In the case of not signing a request there needs to be at least one unused key. If this is not the case it will be created. If you want to self-sign a request (unusual but nevertheless possible) you need the private key used to create the request.</source>
        <translation type="obsolete"></translation>
    </message>
    <message>
        <source>
Welcome to the settings for certificate signing requests.

A signing request needs a private key, so it will be created 
if there isn&apos;t any unused key available in the key database. 
This signing request can then be given to a Certification authority 
while the private key of the request and of the resulting certificate 
returned from the CA does never leave your computer.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>
You are done with entering all parameters for generating a Certificate signing 
request. The resulting request should be exported and send to an appropriate CA 
for signing it.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>
Welcome to the settings for Templates.

This templates do not refer to any ASN.1 structure but are used to keep default 
settings for signing requests and certificates. 
When creating a Request or Certificate the template can preset the needed fields 
with default settings.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>
You are done with entering all parameters for the Template.

After this step the template can be assigned to one of your CAs to be autoatically 
applied when signing with this CA.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Welcome to the settings for Certificates.

The information for the new Certificate can either be grabbed from a given 
Certificate-request or be filled in by hand. In the case of not signing a request 
there needs to be at least one unused key. If this is not the case it will be created. 
If you want to self-sign a request (unusual but nevertheless possible) you need the 
private key used to create the request.</source>
        <translation type="unfinished"></translation>
    </message>
</context>
<context>
    <name>NewX509_UI</name>
    <message>
        <source>Template</source>
        <translation>Vorlage</translation>
    </message>
    <message>
        <source>CRL distribution point</source>
        <translation></translation>
    </message>
    <message>
        <source>issuer alternative name</source>
        <translation></translation>
    </message>
    <message>
        <source>subject alternative name</source>
        <translation></translation>
    </message>
    <message>
        <source>Basic Constraints</source>
        <translation></translation>
    </message>
    <message>
        <source>Key identifier</source>
        <translation></translation>
    </message>
    <message>
        <source>Validity</source>
        <translation>G眉ltigkeit</translation>
    </message>
    <message>
        <source>Days</source>
        <translation>Tage</translation>
    </message>
    <message>
        <source>Months</source>
        <translation>Monate</translation>
    </message>
    <message>
        <source>Years</source>
        <translation>Jahre</translation>
    </message>
    <message>
        <source>Key Usage</source>
        <translation></translation>
    </message>
    <message>
        <source>Digital Signature</source>
        <translation></translation>
    </message>
    <message>
        <source>Non Repudiation</source>
        <translation></translation>
    </message>
    <message>
        <source>Key Encipherment</source>
        <translation></translation>
    </message>
    <message>
        <source>Data Encipherment</source>
        <translation></translation>
    </message>
    <message>
        <source>Key Agreement</source>
        <translation></translation>
    </message>
    <message>
        <source>Certificate Sign</source>
        <translation></translation>
    </message>
    <message>
        <source>CRL Sign</source>
        <translation></translation>
    </message>
    <message>
        <source>Encipher Only</source>
        <translation></translation>
    </message>
    <message>
        <source>Decipher Only</source>
        <translation></translation>
    </message>
    <message>
        <source>Extended Key Usage</source>
        <translation></translation>
    </message>
    <message>
        <source>SSL Client</source>
        <translation></translation>
    </message>
    <message>
        <source>SSL Server</source>
        <translation></translation>
    </message>
    <message>
        <source>S/MIME</source>
        <translation></translation>
    </message>
    <message>
        <source>Object Signing</source>
        <translation></translation>
    </message>
    <message>
        <source>SSL CA</source>
        <translation></translation>
    </message>
    <message>
        <source>S/MIME CA</source>
        <translation></translation>
    </message>
    <message>
        <source>Object Signing CA</source>
        <translation></translation>
    </message>
    <message>
        <source>CA Revokation URL</source>
        <translation></translation>
    </message>
    <message>
        <source>Revokation URL</source>
        <translation></translation>
    </message>
    <message>
        <source>SSL server name</source>
        <translation></translation>
    </message>
    <message>
        <source>Certificate renewal URL</source>
        <translation></translation>
    </message>
    <message>
        <source>Comment</source>
        <translation></translation>
    </message>
    <message>
        <source>CA policy URL</source>
        <translation></translation>
    </message>
    <message>
        <source>Base URL</source>
        <translation></translation>
    </message>
    <message>
        <source>Signer</source>
        <translation>Aussteller</translation>
    </message>
    <message>
        <source>Template for the new certificate</source>
        <translation>Vorlage f眉r das neue Zertifikat</translation>
    </message>
    <message>
        <source>Internal name</source>
        <translation>Interner Name</translation>
    </message>
    <message>
        <source>Sign this Certificate signing &amp;request</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Create a &amp;self signed certificate with the serial</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Change the default &amp;extension settings from the template</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>&amp;Generate a new key</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>&amp;Critical</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>&amp;Subject Key Identifier</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>&amp;Authority Key Identifier</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Copy &amp;issuer name</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Copy &amp;e-mail address from subject line</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>C&amp;ritical</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>NewX509_UI</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Signing request</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>A certificate signing request can be signed, even if the private key of the request is not available. This is the intention of a CSR:
Getting signed by a CA certificate, whoes certificate of course must be in the database
Of course you need the private key of the CSR if you want to create a self-signed cert from it.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>If you leave this blank the serial 00 will be used</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>All certificates in your database that can create valid signatures</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>This list contains all certificates with the CA-flag set to true and whoes private key is present in the key-database.
If this list is disabled, you only can create a self-signed certificate.</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>All available templates</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>This list contains all templates from the toplevel template Tab. 
Additionally it contains 4 default templates:
Empy, CA, client, server</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Check this to adjust all details of the certificate</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Source of the subject</source>
        <translation type="unfinished"></translation>
    </message>
    <message>
        <source>Organisation</source>
        <translation type="unfinished">Firma</translation>