debconf template: checking of my english for the (source) package dtc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear debian-l10n-english people,
I would like to know if any of you would be so kind as to check the
spelling and wording of my english template attached to this message for
my package dtc.
The english original template is written by me which is non-english
native speaker, and I believe there are still many mistakes remaining
in it. A review would be much appreciated, especially considering that
there might be some "standard" wordings and that some people submitted
bugs against those templates.
dtc already includes de.po es.po fr.po it.po, they have been written by
individuals that also translated the rest of the control panel (all the
*strings.php files). I will send it for checking by these translators
later when the English is checked, so the strings wont get fuzzy again.
language translated fuzzy untranslated
- -----------------------------------------------------
de 42 23
es 46 19
fr 42 23
it 42 23
Please send the updated file to me Thomas Goirand <thomas@goirand.fr>,
or even better register to the developer mailing list sending a mail
to dtcdev-subscribe@gplhost.sg to subscribe, and then send the patch
to this list.
That the latest version of DTC is always available using CVS:
cvs -d :pserver:anonymous@gplhost.com:/var/lib/cvs co dtc
and that best for us is if you send a patch against it using:
cvs diff -u >my_translation.patch
Please, the -u flag is very important so your patch can be read by a
human and be reviewed.
dtc.template and dtc-postfix-courier are the same, do not waste your
time to read both, check only one, and overwrite the second with a cp so
it can be included in your diff. If any of you know a way so there could
be only one file (like I did for the master.* for example), I'd be happy
to know.
The last upload of DTC in SID is broken as then set -e in
the debian/master.config made it fail. This will be corrected asap,
in the mean time, please use the source package, remove the set -e in
the config script if you want to test dtc.
Thanks for reading, and thanks in advance if you decide to help us,
Thomas Goirand
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF8R9Sl4M9yZjvmkkRAoZ7AKC2Gnv+E2bBqDtOirZpaGl3qakXCgCg2MQ/
qBPw2YkDx5vlHHqNpp+DxYM=
=GD3u
-----END PGP SIGNATURE-----
Template: dtc/conf_mysqlhost
Type: string
Default: localhost
_Description: MySQL hostname:
Enter the hostname or ip do you want to use to connect to your MySQL server. If
the MySQL server runs locally, then you can safely leave the default to
localhost.
Template: dtc/conf_mysqllogin
Type: string
Default: root
_Description: MySQL Login:
Enter the MySQL root login. DTC needs it to access to your MySQL table in order
to grant privileges to it's users. It's suggested that you add a user specialy
for dtc that has the rights for modifying grant tables, but root is also
working.
Template: dtc/conf_mysqlpass
Type: password
_Description: MySQL Password:
Please enter your MySQL root password so DTC can connect to MySQL and
add/remove databases.
Template: dtc/conf_mysqldb
Type: string
Default: dtc
_Description: DTC database name:
DTC save all it's hosting information in a database automatically created. You
should enter it's name here.
Template: dtc/conf_mysql_change_root
Type: boolean
Default: false
_Description: Change MySQL root?
When installing mysql-server package under Debian, the default installed root
password for database access is an empty password. DTC can change that root
password for you if you didn't change it before. If you have setup a root
password for MySQL before, or if you are just upgrading DTC to a newer version,
you might don't need to setup a new root password. If your root MySQL password
is not set yet, then you can ask DTC to change it with the root password you
just entered. Please note that if DTC can't connect with root, then install
will fail.
Template: dtc/main_domainname
Type: string
Default: example.com
_Description: Domain name:
Enter the first domain name you want DTC to administrate. This domain name will
be used for installing the root admin and customer web control panel of DTC (on
one of this domain subdomains).
Template: dtc/dtc_adminsubdomain
Type: string
Default: dtc
_Description: DTC root panel subdomain:
Enter the subdomain you want DTC to install it's control panel.
Template: dtc/conf_ipaddr
Type: string
Default: 192.168.0.2
_Description: Primary IP address:
Enter your primary IP address here. This IP will be used for the domain name
you just provided, and will be used as default for most DTC variables. In case
of NAT, please enter your EXTERNAL IP address.
Template: dtc/conf_hostingpath
Type: string
Default: /var/www/sites
_Description: Path for hosted domains:
This path is where you want DTC to store all hosted domains files (mail and web
files)?
.
Please note that apache's standard installation setup /var/www as the apache
web area (document root). Remove this manually in your /etc/apache/httpd.conf
(or in /etc/apache2) if you choose /var/www/sites as DTC's hosting area.
Template: dtc/conf_chroot_path
Type: string
Default: /var/lib/dtc/chroot_template
_Description: Path where to build the chroot environment:
Please enter the path where you want DTC to build the cgi-bin chroot
environment template.
Template: dtc/conf_admlogin
Type: string
Default: dtc
_Description: Main domain admin name:
DTC has to bind an admin for each of it's domains. Please enter the admin name
for the domain name holding the control panel installation.
Template: dtc/conf_admpass
Type: password
Default:
_Description: Main domain admin password:
Please give the main domain's administrator a password. Note that access to the
control panel is to be managed manually in /var/www/sites/.htpasswd currently
(or in an other path if you decided not to use /var/www as your hosting root
path).
Template: dtc/conf_mta_type
Type: select
Choices: postfix, qmail
_Description: Mail Transfer Agent Type:
Select the type of MTA that planed to use with DTC. Please not that this
software must be installed BEFORE installing DTC otherwise some of the install
script parts could be skiped and so your configuration will not be fully done.
If you didn't setup any MTA (Postfix or Qmail), then you must finish the setup
of DTC, install your MTA, and dpkg-reconfigure dtc.
Template: dtc/conf_use_cyrus
Type: boolean
Default: false
_Description: Use cyrus mail system?
If you are using the Cyrus for mail delivery, imap and MTA, you should inform
the DTC installer about it. This assumes that you are also using Postfix as MTA
(and not Qmail).
Template: dtc/conf_apache_version
Type: select
Choices: 2, 1
_Description: Apache version to configure:
DTC now supports both Apache and Apache2, but you need to tell which of them
you want to use/configure, as both could be run at the same time under Debian.
Template: dtc/conf_use_nated_vhosts
Type: boolean
Default: false
_Description: Use nated vhosts?
It's possible that DTC generates apache files to use a LAN IP address that your
server is using. If your server is in the LAN behind a firewall that does NAT
and port redirections of the public IP(s) address(es) to your server, then you
must ask to generate nated vhosts here, otherwise (if your server is connected
directly to the internet with a public static IP) leave it to default which is
to use a public static IP.
.
Note that in the case of a dynamic IP address, using NAT and port forwarding is
the only way to use DTC (because apache vhost file wont need to be regenerated
at each IP change).
Template: dtc/conf_nated_vhosts_ip
Type: string
Default: 192.168.0.2
_Description: NATed LAN IP:
This is the LAN (local area network) IP of your server, so DTC can generate all
the vhosts of Apache using this IP.
Template: dtc/conf_gen_ssl_cert
Type: boolean
Default: false
_Description: Generate OpenSSL certificate for DTC?
If you decide generate a certificate, then DTC will generate an self signed
OpenSSL certificate for you, so you can enjoy browsing the panel with Secure
Socket Layer connections.
.
You can later upgrade to a root CA certificate by using
/usr/share/dtc/etc/ssl/new.cert.csr when buying the certificate from a trusted
SSL provider. You will then change /usr/share/dtc/etc/ssl/new.cert.cert by a
real certificate.
.
Note that even you ask to generate the certificate, DTC will also activate SSL
directly and generate the apache config to use HTTPS url for the panel, if you
don't, it will leave the value stored in the database (which is not to use SSL
at the first install).
.
As well, note that DTC will never overrite a previously generated certificate.
If you wish to regenerate it, you need to remove all the files in
/usr/share/dtc/etc/ssl.
Template: dtc/conf_cert_passphrase
Type: password
_Description: DTC certificate passphrase:
To generate a certificate request and a certificate, OpenSSL needs you enter a
password. Please type it here.
Template: dtc/conf_cert_countrycode
Type: string
Default: FR
_Description: DTC SSL certificate 2 letters country code:
Please enter the 2 letter country code of your server location. Example: AU,
UK, US, FR, DE, etc.
Template: dtc/conf_cert_locality
Type: string
Default: Paris
_Description: DTC SSL certificate city name:
Please enter the city name of your server location.
Template: dtc/conf_cert_organization
Type: string
Default: GPLHost
_Description: DTC SSL certificate organization name:
Please enter your organization name.
Template: dtc/conf_cert_unit
Type: string
Default: no-unit
_Description: DTC SSL certificate organization unit:
Please enter your organization unit name.
Template: dtc/conf_cert_email
Type: string
_Description: DTC SSL certificate email address:
Please enter your certificate email address.
Template: dtc/conf_cert_challenge_pass
Type: password
_Description: DTC SSL certificate challenge pass:
Please enter your certificate challenge password.
Template: dtc/conf_upgrade_pear
Type: boolean
Default: true
_Description: Update pear installation?
You can ask DTC to check your pear installation during install. This REQUIRES a
network connection to the internet. If you can't do so here, please check that
you have the following PEAR modules up-to-date: Crypt_CBC and Auth_SASL. The
files should be in /usr/share/php if you want to check.
Template: dtc/conf_dnsbl_list
Type: string
Default: sbl-xbl.spamhaus.org,list.dsbl.org,relays.ordb.org
_Description: DNSBL (DNS BlackList) list:
Please enter the list of preferred DNSBL servers to add to your Postfix mail
server configuration.
Template: dtc/conf_eth2monitor
Type: string
_Description: Network devices to monitor:
Please enter here all the network devices you wish to be monitored by the
RRDTools graphing.
Template: dtc/conf_report_setup_stat
Type: boolean
Default: true
_Description: Allow to report anonymous statistic to GPLHost?
You can help GPLHost to know how many DTC setup has been done, by reporting
your installation to it's web site. No data will be collected except the
operating system (Debian in your case), IP address of the setup (the IP is used
as an identifier so GPLHost don't account upgrades and/or reinstallations, it
will never be used for commercial purpose). You have to be connected to
internet and wget must be installed to do the report.
Template: dtc/conf_omit_dev_mknod
Type: boolean
Default: false
_Description: Skip mknod calls when building chroot template?
In some environment, like Linux vServer, mknod is not allowed to be executed.
For that reason, it's possible to skip the creation of the dev null, random and
urandom devices during the chroot template creation.
Reply to: