Re: Problems in the po file you sent for translation
-----BEGIN PGP SIGNED MESSAGE-----
1) Choices should be translatable
2) The interrogative form should be avoided (it should be kept for
boolean templates). It then becomes tricky to find a good synopsis.
The less worse is probably "Check server's SSL certificate:" (the
possessive form seems needed here)
Ok, I've updated my template and will send out updated .po files to the
translators (unless someone thinks I should wait some more).
Attached is the updated templates file.
- -- arthur - firstname.lastname@example.org - http://people.debian.org/~adejong --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
_Description: LDAP server URI:
Please enter the Uniform Resource Identifier of the LDAP server. The format
is 'ldap://<hostname_or_IP_address>:<port>/'. Alternatively, 'ldaps://' or
'ldapi://' can be used. The port number is optional.
When using an ldap or ldaps scheme it is recommended to use an IP address to
avoid failures when domain name services are unavailable.
Multiple URIs can be be specified by separating them with spaces.
_Description: LDAP server search base:
Please enter the distinguished name of the LDAP search base. Many sites use
the components of their domain names for this purpose. For example, the
domain "example.net" would use "dc=example,dc=net" as the distinguished name
of the search base.
_Description: LDAP database user:
If the LDAP database requires a login for normal lookups, enter the name of
the account that will be used here. Leave it empty otherwise.
This value should be specified as a DN (distinguished name).
_Description: LDAP user password:
Enter the password that will be used to log in to the LDAP database.
_Description: Use StartTLS?
Please choose whether the connection to the LDAP server should use
StartTLS to encrypt the connection.
__Choices: never, allow, try, demand
_Description: Check server's SSL certificate:
When an encrypted connection is used, a server certificate can be requested
and checked. Please choose whether lookups should be configured to require
a certificate, and whether certificates should be checked for validity:
* never: no certificate will be requested or checked;
* allow: a certificate will be requested, but it is not
required or checked;
* try: a certificate will be requested and checked, but if no
certificate is provided it is ignored;
* demand: a certificate will be requested, required, and checked.
If certificate checking is enabled, at least one of the tls_cacertdir or
tls_cacertfile options must be put in /etc/nss-ldapd.conf.
Choices: aliases, ethers, group, hosts, netgroup, networks, passwd, protocols, rpc, services, shadow
_Description: Name services to configure:
For this package to work, you need to modify your /etc/nsswitch.conf to use
the ldap datasource.
You can select the services that should have LDAP lookups enabled. The
new LDAP lookups will be added as the last datasource. Be sure to review
_Description: Remove LDAP from nsswitch.conf now?
The following services are still configured to use LDAP for lookups:
but the libnss-ldapd package is about to be removed.
You are advised to remove the entries if you don't plan on using LDAP for
name resolution any more. Not removing ldap from nsswitch.conf should, for
most services, not cause problems, but host name resolution could be affected
in subtle ways.
You can edit /etc/nsswitch.conf by hand or choose to remove the entries
automatically now. Be sure to review the changes to /etc/nsswitch.conf if you
choose to remove the entries now.