--- Begin Message ---
Package: isdnutils
Severity: normal
Tags: patch
Hi,
There are a lot of problems with your debconf templates. Full patches
are attached and my comments are following.
Please note that (i) I'm not a native-speaker, so some of my rephrasing
may not be correct English, and (ii) I haven't changed your *.config
files according to the new templates.
Most of my comments are detailed in the developers-reference
(http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-config-mgmt)
=== ipppd.templates ===
> Template: ipppd/ispwontdoit
> Type: note
>-_Description: ISP dialup config exists already
>+_Description: ISP dialup config already exists
suggested rephrasing
> Template: ipppd/whichif
> Type: string
> Default: ippp0
>-_Description: Which interface should be configured?
>+_Description: Interface to configure:
Badly formatted prompt for a "string" template.
>- Which interface should debconf configure?
>- .
The long description should give facts, not prompting the user once
again (and usually repeating exactly what is in the short description
with some different words).
>- Most people will say "ippp0" here, as that is the default for a connection
>+ Most people should say "ippp0" here, as that is the default for a connection
suggested rephrasing
> However, some people have special requirements, and they may choose
>- another interface that debconf will configure (e.g. because they don't
>+ another interface to configure automatically (e.g. because they don't
> want this connection to be the default gateway).
> .
>- Note that debconf will currently only configure at most one interface.
>- Enter "none" if you do not want debconf to configure anything for ipppd.
>+ Note that only one interface can be configured automatically.
>+ Leave the field blank if you do not want to configure anything for ipppd.
The user is not expected to know the name of the configuration system.
You should avoid talking about "debconf", but use words such as
"automatically", "configuration process", etc.
> Template: ipppd/wrongif
> Type: note
>-_Description: wrong interface name
>+_Description: Wrong interface name
typo
> Template: ipppd/ispphone
> Type: string
>-_Default: manual
>+Default: manual
This string should not be translatable. If I translate it to French, it
will be "manuel", but this value is not dealt with in your scripts.
>-_Description: What is your ISP's telephone number?
>+_Description: ISP's telephone number:
Badly formatted prompt for a "string" template.
>- What telephone number(s) must be dialed in order to connect
>- to your Internet service provider (ISP)?
>+ A phone number has to be dialed in order to connect
>+ to your Internet service provider (ISP).
The long description should give facts, not prompting the user once
again (and usually repeating exactly what is in the short description
with some different words).
> Enter the telephone number here, including dialing prefixes,
>- area codes, and so on. Enter the number without any spaces.
>+ area codes, and so on. The number should not contain any spaces.
suggested rephrasing.
>- You can enter multiple telephone numbers. If you do so then
>- separate them with spaces.
>+ You can enter multiple telephone numbers, separated with spaces.
suggested rephrasing.
>- Enter the word "manual" or leave the field blank if you want
>- to configure the connection manually.
>+ Leave the field blank if you want to configure the connection manually.
This kind of sentence is a pity for translators. Most of them will
probably translate "manual", which is not a value your script deals
with. You should only use blank field.
> Template: ipppd/eaz
> Type: string
> Default: 0
>-_Description: What is your local MSN?
>+_Description: Local MSN:
Badly formatted prompt for a "string" template.
> When making a call with ISDN, the MSN (phone number) that is originating
>- the call must be given in the call-setup message. While usually a wrong
>- MSN will be replaced by the main MSN for the ISDN line, especially on
>- PABXes a wrong MSN (often the extension number in this case) will cause
>+ the call must be given in the call-setup message. While a wrong MSN will
>+ usually be replaced by the main MSN for the ISDN line, especially on
>+ PABXes, a wrong MSN (often the extension number in this case) will cause
> the call-setup to fail. So, it is best to enter the correct local MSN
> here.
suggested rephrasing.
> Template: ipppd/isplogin
> Type: string
>-_Description: What is the user name for logging into your ISP?
>+_Description: User name for logging into your ISP:
Badly formatted prompt for a "string" template.
>- Most (all?) ISPs need a user name and password for authenticating you as a
>+ Most ISPs need a user name and password for authenticating you as a
I don't like this kind of unknown assumptions. Just use "Most", it's
enough.
> Template: ipppd/isppasswd
> Type: password
>-_Description: What is the password for logging into your ISP?
>+_Description: Password for logging into your ISP:
Badly formatted prompt for a "string" template.
>- Until it is deleted, it will still be used! This may cause conflicts.
>+ Until it is deleted, it will still be used. This may cause conflicts.
3 times: please do not express fealings or overinsist on something.
> Template: ipppd/oldipupdown
> Type: note
>-_Description: old /etc/ppp/ip-up.d and ip-down.d scripts still exist
>+_Description: Old /etc/ppp/ip-up.d and ip-down.d scripts still exist
typo
>-_Description: (re)start ipppd by hand
>+_Description: (Re)start ipppd manually
Upper case letter missing. You should try to be consistent within your
templates: either "manually" or "by hand", not both.
> There is no /etc/init.d/isdnutils on your system; hence you will have to
>- stop and start any ipppd daemons by hand.
>+ stop and start any ipppd daemons manually.
see above.
> Template: ipppd/isdnutilsinitbad
> Type: note
>-_Description: error running isdnutils init script
>+_Description: Error running isdnutils init script
typo
=== isdnlog.templates ===
>-Template: isdnlog/intro
>-Type: text
>-_Description: Entering isdnlog configuration
>- For correct isdnlog functioning, isdnlog needs to be configured with a
>- number of settings. These are some or all (depending on the level you have
>- configured debconf with) of:
>- .
>- - country this is used for setting a number of defaults,
>- e.g. what rate tables to use for calculating
>- the cost of a call.
>- .
>- - country prefix what is used to indicate an international number
>- .
>- - country code the phone number for your country
>- (e.g. 49 for Germany)
>- .
>- - areacode prefix what is used to indicate an areacode,
>- if applicable in your country. Usually a 0 .
>- .
>- - areacode what your local areacode is (if applicable)
>- .
>- After installation, you may have to edit /etc/isdn/isdnlog.isdnctrl0
>- before isdnlog can work properly, although that file is set up with
>- reasonable defaults for most cases.
>- .
>- If you previously had /etc/isdn/isdnlog.isdnctrl0, that will be preserved.
This template is a typical debconf abuse and must be removed. You are
not configuring anything, just repeating what will (or will not!) be in
the future questions.
> Template: isdnlog/country
> Type: select
>+#flag:translate:9
> __Choices: AT, CH, DE, ES, FR, LU, NL, NO, other
only "other" should be marked as translatable
>-Default: DE
>+# Translators: If your 2-letter code country is in the following list:
>+# "AT, CH, DE, ES, FR, LU, NL, NO"
>+# translate this string by this code. Otherwise, just write "other" (but
>+" do not translate it.
>+_Default: other[ default country]
This field should be marked as translatable, as the default country in
French is probably not the same as the default country in german.
DE is not a good default for an English-speaking template (should be UK,
US, etc., so in this case, "other").
>-_Description: What country is this system in?
>+_Description: Country:
Badly formatted prompt for a "string" template.
> Template: isdnlog/country_manual
> Type: string
>-_Description: Enter the ISO two-letter code for your country
>+_Description: ISO two-letter code of your country:
Badly formatted prompt for a "string" template.
>- This can't really be used for setting any defaults, but maybe some day...
>+ This can't really be used for setting any defaults, but maybe some day.
unneeded punctuation. It just gives the impression that the maintainer
is bored.
> Template: isdnlog/countryprefix
> Type: string
> Default: +
>-_Description: What is used to indicate an international number?
>+_Description: Prefix for international number:
Badly formatted prompt for a "string" template.
> Template: isdnlog/countrycode
> Type: string
> Default: 49
>-_Description: What is the countrycode for your country?
>+_Description: Code of your country:
> e.g. ${default_countrycode} for ${default_country}
see above
> Template: isdnlog/areaprefix
> Type: string
> Default: 0
>-_Description: What is used to indicate an areacode, if applicable?
>+_Description: Prefix for areacode, if applicable:
see above
> Template: isdnlog/areacode
> Type: string
>-_Description: What is your local areacode, if applicable?
>+_Description: Local areacode, if applicable:
see above
> Template: isdnlog/isdnrate-daemon
>-Type: select
>-Choices: no, yes
>-Default: no
>+Type: boolean
>+Default: false
This template must be a boolean template
> _Description: Run isdnrate as a daemon?
> isdnrate is a utility to calculate the costs of a connection to a given
> phone number, used e.g. for LCR systems to find the cheapest carrier on a
> call-by-call basis. Having it run as a daemon speeds things up as then it
>- only has to load all the data just once.
>+ has to load all the data only once.
"only" and "just" is too much.
> This is only for people with special requirements, such as those using the
>- isdn2h323 package. Hence most people should say "no".
>+ isdn2h323 package. Hence most people should not choose this option.
"no" should not be used even for boolean templates, as some frontends
present a checkbox instead of a yes/no choice.
=== isdnutils-base.templates ===
>-Template: isdnutils/no_ipppd_selected
>-Type: note
>-_Description: isdnutils is now split up
>- The old isdnutils package is now split up into smaller parts: isdnutils
>- ipppd isdnutils-xtools isdnutils-doc isdnvboxserver isdnvboxclient isdnlog
>- isdnlog-data libcapi20-3 isdnactivecards pppdcapiplugin isdneurofile
>- .
>- This allows you to better select what parts you want installed, almost no
>- one needs everything. Unfortunately there's no way of automatically
>- selecting those parts you need.
>- .
>- You have ipppX interfaces configured, but you have not selected ipppd to
>- be installed. This can be dangerous (leaving you with no way of obtaining
>- ipppd), so aborting the installation of this new isdnutils.
>- .
>- If you really mean to not have ipppd, please remove the ipppd.* files from
>- /etc/isdn/, stop any ipppX interfaces, and reinstall isdnutils.
>- .
>- If you used dselect, please select (+) ipppd, and any of the other parts
>- you might need (e.g. isdnlog, isdnvbox, isdnutils-xtools), although those
>- should have been selected automatically. If you used apt-get, use 'apt-get
>- install isdnutils ipppd isdnlog ...'; you may need to run 'apt-get -f
>- install' first to configure any other packages that were unpacked but not
>- yet configured.
potato -> etch transitions are not supported, this template should
therefore be removed.
> Template: isdnutils/firmware
> Type: select
>-_Choices: none, ISAR.BIN
>+#flag:translate:1
>+__Choices: none, ISAR.BIN
ISAR.BIN should not be translatable.
> Default: none
>-_Description: Does firmware need to be loaded?
>+_Description: Firmware to load:
Badly formatted prompt for a "select" template.
> Some ISDN cards can't function properly until firmware has been
> downloaded. Notable example is the Sedlbauer SpeedFax+ PCI or Siemens
>- I-Surf, which need ISAR.BIN to be loaded. (I don't know of any others at
>- this time.) Choose "ISAR.BIN" if this is necessary. If you don't know what
>- I'm talking about, choose "none".
>+ I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
>+ necessary. If you don't know what to answer here, choose "none".
Do not use first person. It really gives the user an imature image of
the program.
> Template: isdnutils/firmwarecards
> Type: string
>-_Description: Which ISDN card numbers have to be loaded with the firmware?
>+_Description: ISDN card numbers to load with the firmware:
Badly formatted prompt for a "string" template.
> Template: isdnutils/isdnvbox-cronweekly
> Type: note
>-_Description: You have an (old) isdnvbox cron.weekly script
>+_Description: isdnvbox cron.weekly script found
suggested rephrasing (should be a title)
=== isdnvboxserver.template ===
> Template: isdnvboxserver/msn
> Type: string
>-_Description: What number should vbox answer?
>+_Description: Number that vbox should answer:
Badly formatted prompt for a "string" template.
>-Default: quit
>[...]
> Vbox must know what number to listen to. Depending on your country's ISDN
> system, this may or may not include the areacode. It is usually without
> the leading 0.
> .
>- Enter `quit' (or leave it blank) if you want to configure by hand, not via
>- debconf. Also enter `quit' if you already have an existing (working) vbox
>+ Leave the field blank if you want to configure it by hand.
>+ or if you already have an existing (working) vbox
Once again, this kind of values are a pity for translators. You should
also not refer to debconf.
>-Template: isdnvboxserver/doityourself
>-Type: note
>-_Description: You've chosen not to use debconf for isdnvboxserver
>- If you change your mind, run "dpkg-reconfigure isdnvboxserver". To
>- finalize isdnvboxserver, you need to ensure that vboxgetty is running from
>- inittab, and that vboxd will run out of inetd.
This template is a debconf abuse.
> Template: isdnvboxserver/rings
> Type: string
> Default: 4
>-_Description: After how many rings should vbox pick up the line?
>+_Description: Number of rings for vbox to pick up the line:
Badly formatted prompt for a "string" template.
> One ring is about 5 seconds. You can fine-tune the number of rings for
> certain phonenumbers manually, e.g. any salesmen you know the number of
> (or calls without caller-ID) can be dumped into the answering machine
>- after one ring. See `man vbox.conf' for more info.
>+ after one ring. See `man vbox.conf' for more information.
suggested rephrasing.
> Template: isdnvboxserver/attachmsg
>-Type: select
>-Choices: yes, no
>-Default: yes
>+Type: boolean
>+Default: true
This template should be a boolean template.
> _Description: Should the message be attached to the email?
> When a message is recorded, an email notification is sent. If that email
>- should contain the message as an attachment, choose "yes" here. Note: the
>- attachment can be large!
>+ should contain the message as an attachment, choose this option.
>+ .
>+ Note: the attachment can be large.
suggested rephrasing (in order to avoid interface assumption for a
boolean template).
> Template: isdnvboxserver/daemonuser
> Type: string
> Default: vboxdaemonuser
>-_Description: As what user should the answering machine run?
>+_Description: User who runs the answering machine:
suggested rephrasing.
> Template: isdnvboxserver/nosuchuser
> Type: text
>-_Description: The user ${Daemonuser} doesn't exist on the system.
>+_Description: User ${Daemonuser} doesn't exist on the system
Badly formatted title.
>- Enter a valid user name here that's known to the system.
>+ The user who runs the answering machine should be a valid user name
>+ that's known to the system.
You are asking to enter "here" a valid user, but there is nothing to
enter for this kind of templates.
> Template: isdnvboxserver/user
> Type: string
>-_Description: What username may connect to the vbox server?
>+_Description: Username which may connect to the vbox server:
Badly formatted prompt for a "string" template.
> Template: isdnvboxserver/password
> Type: password
>-_Description: Enter the password for ${User} here.
>+_Description: Password for ${User}:
> Please don't use ':' in it! The way it is stored cannot handle this.
Badly formatted prompt for a "password" template.
> Template: isdnvboxserver/spoolrename
> Type: note
>-_Description: spool directory renamed
>+_Description: Spool directory renamed
typo
> Template: isdnvboxserver/dup3spool
> Type: note
>-_Description: two obsolete spool directories detected
>+_Description: Two obsolete spool directories detected
typo
> Template: isdnvboxserver/dupspool
> Type: note
>-_Description: two spool directories detected
>+_Description: Two spool directories detected
typo
> Template: isdnvboxserver/spoolcreate
> Type: note
>-_Description: spool directory created
>+_Description: Spool directory created
typo
> Template: isdnvboxserver/vboxnodir
> Type: note
>-_Description: No home directory!
>+_Description: No home directory
Avoid to over-insist on something.
> Template: isdnvboxserver/vboxnouser
> Type: note
>-_Description: User doesn't exist!
>- The user `${USER}' doesn't exist on the system! Please rerun the
>+_Description: User doesn't exist
>+ The user `${USER}' doesn't exist on the system. Please rerun the
see above.
> Template: isdnvboxserver/doinit
>-Type: select
>-Choices: yes, no
>-Default: yes
>+Type: boolean
>+Default: true
> _Description: Should vboxgetty be enabled?
>- vboxgetty is in /etc/inittab, but not yet enabled. Answering `yes' here
>- will enable it once this package is fully configured. Choose `no' if you
>- want to tweak it manually.
>+ vboxgetty is in /etc/inittab, but not yet enabled. Choosing this option
>+ will enable it once this package is fully configured. Refuse this option
>+ if you want to tweak it manually.
This template should be a boolean template, with rephrasing to avoid
interface assumption.
> Template: isdnvboxserver/adduserdone
> Type: note
>-_Description: user `vbox' created
>+_Description: User `vbox' created
typo
> Template: isdnvboxserver/adduserfailed
> Type: note
>+#flag:translate!:3
> _Description: Failed to create user `vbox'
> For optimal operation of vbox, a user `vbox' should be created, in group
> `dialout'. However, creating that user failed with the following error(s):
> .
> ${MSG}
${MSG} should not be translatable.
>- Please remedy this problem by hand, and then rerun the configuration with
>+ Please remedy this problem manually, and then rerun the configuration with
"by hand" or "manually" consistency.
>- You will have to fix this by hand.
>+ You will have to fix this manually.
see above.
>- You will have to fix this by hand.
>+ You will have to fix this manually.
see above.
> Template: isdnvboxserver/dummy
> Type: note
>-_Description: isdnvboxserver is being configured.
>- Note to translators: no need to translate this, not shown to users.
>+Description: for internal use
If there is nothing to translate, then it should not be marked as
translatable. The string "for internal use" avoid lintian checking this
template.
Cheers,
--
Thomas Huriaux
--- ipppd.templates.orig 2006-07-18 13:35:30.000000000 +0200
+++ ipppd.templates 2006-07-18 14:51:21.000000000 +0200
@@ -1,6 +1,6 @@
Template: ipppd/ispwontdoit
Type: note
-_Description: ISP dialup config exists already
+_Description: ISP dialup config already exists
The files device.${IPPP0} and ipppd.${IPPP0} already exist. Therefore the
ipppd configuration phase won't touch anything there, as it looks like
it's already been configured.
@@ -14,49 +14,45 @@
Template: ipppd/whichif
Type: string
Default: ippp0
-_Description: Which interface should be configured?
- Which interface should debconf configure?
- .
- Most people will say "ippp0" here, as that is the default for a connection
+_Description: Interface to configure:
+ Most people should say "ippp0" here, as that is the default for a connection
to an ISP. The default gateway will be ippp0.
.
However, some people have special requirements, and they may choose
- another interface that debconf will configure (e.g. because they don't
+ another interface to configure automatically (e.g. because they don't
want this connection to be the default gateway).
.
- Note that debconf will currently only configure at most one interface.
- Enter "none" if you do not want debconf to configure anything for ipppd.
+ Note that only one interface can be configured automatically.
+ Leave the field blank if you do not want to configure anything for ipppd.
Template: ipppd/wrongif
Type: note
-_Description: wrong interface name
+_Description: Wrong interface name
You can only give names starting with "ippp" followed by a number between
0 and 63.
Template: ipppd/ispphone
Type: string
-_Default: manual
-_Description: What is your ISP's telephone number?
- What telephone number(s) must be dialed in order to connect
- to your Internet service provider (ISP)?
+Default: manual
+_Description: ISP's telephone number:
+ A phone number has to be dialed in order to connect
+ to your Internet service provider (ISP).
.
Enter the telephone number here, including dialing prefixes,
- area codes, and so on. Enter the number without any spaces.
+ area codes, and so on. The number should not contain any spaces.
.
- You can enter multiple telephone numbers. If you do so then
- separate them with spaces.
+ You can enter multiple telephone numbers, separated with spaces.
.
- Enter the word "manual" or leave the field blank if you want
- to configure the connection manually.
+ Leave the field blank if you want to configure the connection manually.
Template: ipppd/eaz
Type: string
Default: 0
-_Description: What is your local MSN?
+_Description: Local MSN:
When making a call with ISDN, the MSN (phone number) that is originating
- the call must be given in the call-setup message. While usually a wrong
- MSN will be replaced by the main MSN for the ISDN line, especially on
- PABXes a wrong MSN (often the extension number in this case) will cause
+ the call must be given in the call-setup message. While a wrong MSN will
+ usually be replaced by the main MSN for the ISDN line, especially on
+ PABXes, a wrong MSN (often the extension number in this case) will cause
the call-setup to fail. So, it is best to enter the correct local MSN
here.
.
@@ -66,14 +62,14 @@
Template: ipppd/isplogin
Type: string
-_Description: What is the user name for logging into your ISP?
- Most (all?) ISPs need a user name and password for authenticating you as a
+_Description: User name for logging into your ISP:
+ Most ISPs need a user name and password for authenticating you as a
valid user before allowing access. Enter the user name here. The password
will be asked for next.
Template: ipppd/isppasswd
Type: password
-_Description: What is the password for logging into your ISP?
+_Description: Password for logging into your ISP:
The password you give here will be entered into /etc/ppp/pap-secrets and
/etc/ppp/chap-secrets together with the username.
@@ -109,7 +105,7 @@
those changes in the 00-ipppd file (which is the new name). After that,
please delete the old 00-isdnutils file.
.
- Until it is deleted, it will still be used! This may cause conflicts.
+ Until it is deleted, it will still be used. This may cause conflicts.
Template: ipppd/oldipdown
Type: note
@@ -119,28 +115,28 @@
those changes in the 99-ipppd file (which is the new name). After that,
please delete the old 99-isdnutils file.
.
- Until it is deleted, it will still be used! This may cause conflicts.
+ Until it is deleted, it will still be used. This may cause conflicts.
Template: ipppd/oldipupdown
Type: note
-_Description: old /etc/ppp/ip-up.d and ip-down.d scripts still exist
+_Description: Old /etc/ppp/ip-up.d and ip-down.d scripts still exist
The /etc/ppp/ip-up.d/00-isdnutils and /etc/ppp/ip-down.d/99-isdnutils
files from the old isdnutils package still exist. If you changed those
files at some point, you may need to redo those changes in the 00-ipppd
and 99-ipppd files (which are the new names). After that, please delete
the old 00-isdnutils and 99-isdnutils files.
.
- Until they are deleted, they will still be used! This may cause conflicts.
+ Until they are deleted, they will still be used. This may cause conflicts.
Template: ipppd/noisdnutilsinit
Type: note
-_Description: (re)start ipppd by hand
+_Description: (Re)start ipppd manually
There is no /etc/init.d/isdnutils on your system; hence you will have to
- stop and start any ipppd daemons by hand.
+ stop and start any ipppd daemons manually.
Template: ipppd/isdnutilsinitbad
Type: note
-_Description: error running isdnutils init script
+_Description: Error running isdnutils init script
The /etc/init.d/isdnutils script ran with errors. Please check the
installation of the isdnutils-base package; reinstall it if necessary.
Perhaps moving /etc/init.d/isdnutils.dpkg-dist (if it exists) to
--- isdnlog.templates.orig 2006-07-18 13:35:34.000000000 +0200
+++ isdnlog.templates 2006-07-18 14:25:28.000000000 +0200
@@ -1,42 +1,20 @@
-Template: isdnlog/intro
-Type: text
-_Description: Entering isdnlog configuration
- For correct isdnlog functioning, isdnlog needs to be configured with a
- number of settings. These are some or all (depending on the level you have
- configured debconf with) of:
- .
- - country this is used for setting a number of defaults,
- e.g. what rate tables to use for calculating
- the cost of a call.
- .
- - country prefix what is used to indicate an international number
- .
- - country code the phone number for your country
- (e.g. 49 for Germany)
- .
- - areacode prefix what is used to indicate an areacode,
- if applicable in your country. Usually a 0 .
- .
- - areacode what your local areacode is (if applicable)
- .
- After installation, you may have to edit /etc/isdn/isdnlog.isdnctrl0
- before isdnlog can work properly, although that file is set up with
- reasonable defaults for most cases.
- .
- If you previously had /etc/isdn/isdnlog.isdnctrl0, that will be preserved.
-
Template: isdnlog/country
Type: select
+#flag:translate:9
__Choices: AT, CH, DE, ES, FR, LU, NL, NO, other
-Default: DE
-_Description: What country is this system in?
+# Translators: If your 2-letter code country is in the following list:
+# "AT, CH, DE, ES, FR, LU, NL, NO"
+# translate this string by this code. Otherwise, just write "other" (but
+" do not translate it.
+_Default: other[ default country]
+_Description: Country:
This is used for setting a number of defaults, e.g. what rate tables to
use for calculating the cost of a call.
Template: isdnlog/country_manual
Type: string
-_Description: Enter the ISO two-letter code for your country
- This can't really be used for setting any defaults, but maybe some day...
+_Description: ISO two-letter code of your country:
+ This can't really be used for setting any defaults, but maybe some day.
.
Note that you will probably have to edit /etc/isdn/isdn.conf before
isdnlog will be able to work.
@@ -44,32 +22,31 @@
Template: isdnlog/countryprefix
Type: string
Default: +
-_Description: What is used to indicate an international number?
+_Description: Prefix for international number:
Template: isdnlog/countrycode
Type: string
Default: 49
-_Description: What is the countrycode for your country?
+_Description: Code of your country:
e.g. ${default_countrycode} for ${default_country}
Template: isdnlog/areaprefix
Type: string
Default: 0
-_Description: What is used to indicate an areacode, if applicable?
+_Description: Prefix for areacode, if applicable:
Template: isdnlog/areacode
Type: string
-_Description: What is your local areacode, if applicable?
+_Description: Local areacode, if applicable:
Template: isdnlog/isdnrate-daemon
-Type: select
-Choices: no, yes
-Default: no
+Type: boolean
+Default: false
_Description: Run isdnrate as a daemon?
isdnrate is a utility to calculate the costs of a connection to a given
phone number, used e.g. for LCR systems to find the cheapest carrier on a
call-by-call basis. Having it run as a daemon speeds things up as then it
- only has to load all the data just once.
+ has to load all the data only once.
.
This is only for people with special requirements, such as those using the
- isdn2h323 package. Hence most people should say "no".
+ isdn2h323 package. Hence most people should not choose this option.
--- isdnutils-base.templates.orig 2006-07-18 13:35:40.000000000 +0200
+++ isdnutils-base.templates 2006-07-18 15:11:42.000000000 +0200
@@ -1,42 +1,17 @@
-Template: isdnutils/no_ipppd_selected
-Type: note
-_Description: isdnutils is now split up
- The old isdnutils package is now split up into smaller parts: isdnutils
- ipppd isdnutils-xtools isdnutils-doc isdnvboxserver isdnvboxclient isdnlog
- isdnlog-data libcapi20-3 isdnactivecards pppdcapiplugin isdneurofile
- .
- This allows you to better select what parts you want installed, almost no
- one needs everything. Unfortunately there's no way of automatically
- selecting those parts you need.
- .
- You have ipppX interfaces configured, but you have not selected ipppd to
- be installed. This can be dangerous (leaving you with no way of obtaining
- ipppd), so aborting the installation of this new isdnutils.
- .
- If you really mean to not have ipppd, please remove the ipppd.* files from
- /etc/isdn/, stop any ipppX interfaces, and reinstall isdnutils.
- .
- If you used dselect, please select (+) ipppd, and any of the other parts
- you might need (e.g. isdnlog, isdnvbox, isdnutils-xtools), although those
- should have been selected automatically. If you used apt-get, use 'apt-get
- install isdnutils ipppd isdnlog ...'; you may need to run 'apt-get -f
- install' first to configure any other packages that were unpacked but not
- yet configured.
-
Template: isdnutils/firmware
Type: select
-_Choices: none, ISAR.BIN
+#flag:translate:1
+__Choices: none, ISAR.BIN
Default: none
-_Description: Does firmware need to be loaded?
+_Description: Firmware to load:
Some ISDN cards can't function properly until firmware has been
downloaded. Notable example is the Sedlbauer SpeedFax+ PCI or Siemens
- I-Surf, which need ISAR.BIN to be loaded. (I don't know of any others at
- this time.) Choose "ISAR.BIN" if this is necessary. If you don't know what
- I'm talking about, choose "none".
+ I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
+ necessary. If you don't know what to answer here, choose "none".
Template: isdnutils/firmwarecards
Type: string
-_Description: Which ISDN card numbers have to be loaded with the firmware?
+_Description: ISDN card numbers to load with the firmware:
If you have more than one card, enter the number of the card(s) that have
to be loaded with the firmware, starting with 1, separated by commas. If
you have only one card, the obvious answer here is "1". If you have two
@@ -44,7 +19,7 @@
Template: isdnutils/isdnvbox-cronweekly
Type: note
-_Description: You have an (old) isdnvbox cron.weekly script
+_Description: isdnvbox cron.weekly script found
In early versions of isdnutils 3.1pre1b, when upgrading from 3.0 the
/etc/cron.weekly/isdnutils script was renamed to isdnvbox. Unfortunately,
when isdnvbox was split up into isdnvboxserver and isdnvboxclient, the
--- isdnvboxserver.templates.orig 2006-07-18 13:35:46.000000000 +0200
+++ isdnvboxserver.templates 2006-07-18 14:40:28.000000000 +0200
@@ -1,75 +1,68 @@
Template: isdnvboxserver/msn
Type: string
-Default: quit
-_Description: What number should vbox answer?
+_Description: Number that vbox should answer:
Vbox must know what number to listen to. Depending on your country's ISDN
system, this may or may not include the areacode. It is usually without
the leading 0.
.
- Enter `quit' (or leave it blank) if you want to configure by hand, not via
- debconf. Also enter `quit' if you already have an existing (working) vbox
+ Leave the field blank if you want to configure it by hand.
+ or if you already have an existing (working) vbox
configuration from the time when this was still part of isdnutils (unless
you want to create a new configuration).
-Template: isdnvboxserver/doityourself
-Type: note
-_Description: You've chosen not to use debconf for isdnvboxserver
- If you change your mind, run "dpkg-reconfigure isdnvboxserver". To
- finalize isdnvboxserver, you need to ensure that vboxgetty is running from
- inittab, and that vboxd will run out of inetd.
-
Template: isdnvboxserver/rings
Type: string
Default: 4
-_Description: After how many rings should vbox pick up the line?
+_Description: Number of rings for vbox to pick up the line:
One ring is about 5 seconds. You can fine-tune the number of rings for
certain phonenumbers manually, e.g. any salesmen you know the number of
(or calls without caller-ID) can be dumped into the answering machine
- after one ring. See `man vbox.conf' for more info.
+ after one ring. See `man vbox.conf' for more information.
Template: isdnvboxserver/attachmsg
-Type: select
-Choices: yes, no
-Default: yes
+Type: boolean
+Default: true
_Description: Should the message be attached to the email?
When a message is recorded, an email notification is sent. If that email
- should contain the message as an attachment, choose "yes" here. Note: the
- attachment can be large!
+ should contain the message as an attachment, choose this option.
+ .
+ Note: the attachment can be large.
Template: isdnvboxserver/daemonuser
Type: string
Default: vboxdaemonuser
-_Description: As what user should the answering machine run?
+_Description: User who runs the answering machine:
vboxd runs with the privileges of a normal (non-root) user. This is
typically your non-root login name. This user must be a member of the
`dialout' group.
Template: isdnvboxserver/nosuchuser
Type: text
-_Description: The user ${Daemonuser} doesn't exist on the system.
- Enter a valid user name here that's known to the system.
+_Description: User ${Daemonuser} doesn't exist on the system
+ The user who runs the answering machine should be a valid user name
+ that's known to the system.
Template: isdnvboxserver/user
Type: string
-_Description: What username may connect to the vbox server?
+_Description: Username which may connect to the vbox server:
To listen to messages using vbox (from the isdnvboxclient package), you
need a username and password. Enter the username here. This does not have
to be a user on the system itself.
Template: isdnvboxserver/password
Type: password
-_Description: Enter the password for ${User} here.
+_Description: Password for ${User}:
Please don't use ':' in it! The way it is stored cannot handle this.
Template: isdnvboxserver/spoolrename
Type: note
-_Description: spool directory renamed
+_Description: Spool directory renamed
The spool directory `${OLDSPOOL}' has been renamed to `${NEWSPOOL}' for
consistency's sake. This should have no other consequences.
Template: isdnvboxserver/dup3spool
Type: note
-_Description: two obsolete spool directories detected
+_Description: Two obsolete spool directories detected
The directories `${OLDSPOOL1}' and `${OLDSPOOL2}' (which aren't used
anymore in the standard configuration), and the new spool directory
`${NEWSPOOL}' all exist. The old directories will no longer be used;
@@ -78,7 +71,7 @@
Template: isdnvboxserver/dupspool
Type: note
-_Description: two spool directories detected
+_Description: Two spool directories detected
The old spool directory `${OLDSPOOL}' and the new spool directory
`${NEWSPOOL}' both exist. The old directory will no longer be used; please
manually move any messages from there to the new directory (if any), and
@@ -86,7 +79,7 @@
Template: isdnvboxserver/spoolcreate
Type: note
-_Description: spool directory created
+_Description: Spool directory created
The spool directory `${NEWSPOOL}' has been created, which is necessary for
proper working of vbox.
@@ -104,41 +97,41 @@
Template: isdnvboxserver/vboxnodir
Type: note
-_Description: No home directory!
+_Description: No home directory
The home directory `${DIR}' for user `${USER}' doesn't exist. This means
that the file `${DIR}/.vbox.conf' cannot be created.
Template: isdnvboxserver/vboxnouser
Type: note
-_Description: User doesn't exist!
- The user `${USER}' doesn't exist on the system! Please rerun the
+_Description: User doesn't exist
+ The user `${USER}' doesn't exist on the system. Please rerun the
configuration with `dpkg-reconfigure isdnvboxserver' to enter another
username, or after creating the user.
Template: isdnvboxserver/doinit
-Type: select
-Choices: yes, no
-Default: yes
+Type: boolean
+Default: true
_Description: Should vboxgetty be enabled?
- vboxgetty is in /etc/inittab, but not yet enabled. Answering `yes' here
- will enable it once this package is fully configured. Choose `no' if you
- want to tweak it manually.
+ vboxgetty is in /etc/inittab, but not yet enabled. Choosing this option
+ will enable it once this package is fully configured. Refuse this option
+ if you want to tweak it manually.
Template: isdnvboxserver/adduserdone
Type: note
-_Description: user `vbox' created
+_Description: User `vbox' created
A user `vbox' was created, in group `dialout'. This is used as the ID that
the vbox daemons run under.
Template: isdnvboxserver/adduserfailed
Type: note
+#flag:translate!:3
_Description: Failed to create user `vbox'
For optimal operation of vbox, a user `vbox' should be created, in group
`dialout'. However, creating that user failed with the following error(s):
.
${MSG}
.
- Please remedy this problem by hand, and then rerun the configuration with
+ Please remedy this problem manually, and then rerun the configuration with
`dpkg-reconfigure isdnvboxserver'.
Template: isdnvboxserver/devfs_inittab
@@ -149,7 +142,7 @@
name is used in inittab while devfs is not mounted, or the non-devfs name
is used while devfs is mounted.
.
- You will have to fix this by hand.
+ You will have to fix this manually.
Template: isdnvboxserver/devfs_vboxgettyconf
Type: note
@@ -159,9 +152,8 @@
(/dev/isdn/ttyIxx) name is used in vboxgetty.conf while devfs is not
mounted, or the non-devfs name is used while devfs is mounted.
.
- You will have to fix this by hand.
+ You will have to fix this manually.
Template: isdnvboxserver/dummy
Type: note
-_Description: isdnvboxserver is being configured.
- Note to translators: no need to translate this, not shown to users.
+Description: for internal use
signature.asc
Description: Digital signature
--- End Message ---
