Preamble: I *did not* review debian/control for this package. This review is mostly targeted at debconf templates that were just "broken" by the last upload before the package was orphaned. This is one of the packages with the highest number of strings in templates and debconf statistics were badly hit by the last changes (admitedly, the debconf templates before the change had a lot of non compliances with the recommended writing style) There are way too many suggested changes for me to comment. Most of them are quite obvious and targeted for wirting style consistency all over packages. Please find, for review, the debconf templates and packages descriptions for the isdnutils source package. This review will last from Tuesday, September 22, 2009 to Friday, October 02, 2009. Please send reviews as unified diffs (diff -u) against the original files. Comments about your proposed changes will be appreciated. Your review should be sent as an answer to this mail. When appropriate, I will send intermediate requests for review, with "[RFRn]" (n>=2) as a subject tag. When we will reach a consensus, I send a "Last Chance For Comments" mail with "[LCFC]" as a subject tag. Finally, the reviewed templates will be sent to the package maintainer as a bug report, and a mail will be sent to this list with "[BTS]" as a subject tag. Rationale: --- isdnutils.old/debian/ipppd.templates 2009-09-18 18:26:24.196589117 +0200 +++ isdnutils/debian/ipppd.templates 2009-09-18 19:10:25.921343444 +0200 @@ -1,47 +1,44 @@ Template: ipppd/ispwontdoit Type: error -_Description: ISP dialup config already exists - The files device.${IPPP0} and ipppd.${IPPP0} already exist. Therefore the +_Description: ISP dialup configuration already exists + The device.${IPPP0} and ipppd.${IPPP0} files already exist. Therefore, the ipppd configuration phase won't touch anything there, as it looks like - it's already been configured. + it has already been configured. . If it doesn't work yet, and you want to try the automatic configuration, stop all ISDN processes (use "/etc/init.d/isdnutils stop"), remove the files mentioned above, and rerun the configuration with "dpkg-reconfigure - ipppd". After that, restart the ISDN processes: "/etc/init.d/isdnutils + ipppd". After that, restart the ISDN processes with "/etc/init.d/isdnutils start". Template: ipppd/whichif Type: string Default: ippp0 _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. + The default setting should be safe for most configurations. . - However, some people have special requirements, and they may choose - another interface that will be configured (e.g. because they don't - want this connection to be the default gateway). + However, if you have special requirements or want to choose + to configure another interface, please enter it here. . - Note that currently at most one interface can be configured in this manner. - Leave the field blank if you do not want to configure anything now for ipppd. + Leave the field blank if you do not want to configure anything now. Template: ipppd/wrongif Type: error -_Description: Wrong interface name - You can only give names starting with "ippp" followed by a number between +_Description: Invalid interface name + Valid interface names begin 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? +_Description: ISP's telephone number: At least one phone number has to be dialed in order to connect - to your Internet service provider (ISP). + to the Internet service provider (ISP). . - Enter the telephone number here, including dialing prefixes, + Please enter that telephone number here, including dialing prefixes, area codes, and so on, but without any spaces. . - You can enter multiple telephone numbers, separated by spaces. + Multiple telephone numbers may be entered and should be separated by spaces. . Leave the field blank if you want to configure the connection manually. @@ -62,22 +59,22 @@ Template: ipppd/isplogin Type: string -_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. +_Description: ISP user name: + Most ISPs require a user name and password to be provided when + connecting. Template: ipppd/isppasswd Type: password -_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. +_Description: ISP password: + Please enter the password to use when connecting to the ISP. This password + will be kept in /etc/ppp/pap-secrets and + /etc/ppp/chap-secrets together along with the username. Template: ipppd/isploginpapalreadythere Type: error _Description: ISP user name already in pap-secrets The user name you entered for logging into your ISP is already listed in - the /etc/ppp/pap-secrets file. That's not a problem; the existing entry + the /etc/ppp/pap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. @@ -85,7 +82,7 @@ Type: error _Description: ISP user name already in chap-secrets The user name you entered for logging into your ISP is already listed in - the /etc/ppp/chap-secrets file. That's not a problem; the existing entry + the /etc/ppp/chap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. @@ -93,8 +90,8 @@ Type: error _Description: ISP user name already in chap-secrets and pap-secrets The user name you entered for logging into your ISP is already listed in - the chap-secrets and pap-secrets files in /etc/ppp/. That's not a problem; - the existing entries will be commented out, and new entries with the data + the chap-secrets and pap-secrets files in /etc/ppp/. + The existing entries will be commented out, and new entries with the data you just entered will be inserted. Template: ipppd/oldipup @@ -131,7 +128,7 @@ Template: ipppd/noisdnutilsinit Type: error _Description: (Re)start ipppd manually - There is no /etc/init.d/isdnutils on your system; hence you will have to + There is no /etc/init.d/isdnutils on this system; hence you will have to stop and start any ipppd daemons manually. Template: ipppd/isdnutilsinitbad --- isdnutils.old/debian/isdnlog.templates 2009-09-18 18:26:24.672339165 +0200 +++ isdnutils/debian/isdnlog.templates 2009-09-18 19:02:09.349343195 +0200 @@ -1,52 +1,54 @@ Template: isdnlog/country Type: select #flag:translate:9 -__Choices: AT, CH, DE, ES, FR, LU, NL, NO, other -# 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] +Choices-C: AT, FR, DE, LU, NL, NO, ES, CH, other +__Choices: Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other +# Translators: +# Please choose among +# "Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other" +_DefaultChoice: other _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. + Please choose the local country. This will be used to set the rate table to + use for calculating the calls costs Template: isdnlog/country_manual Type: string -_Description: ISO two-letter code for 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. +Description: Country's ISO two-letter code: + Please enter the ISO code of the local country. As no rate + tables are available, this setting will be unused. Template: isdnlog/countryprefix Type: string Default: + -_Description: Prefix for international number: +_Description: Prefix to dial before international number: Template: isdnlog/countrycode Type: string Default: 49 -_Description: Code of your country: - e.g. ${default_countrycode} for ${default_country} +#flag:comment:3 +# Translators: do not translate ${default_countrycode} and ${default_country} +_Description: Country ITU code: + Please enter the international code for the local country. + . + Example: ${default_countrycode} for ${default_country} Template: isdnlog/areaprefix Type: string Default: 0 -_Description: Prefix for areacode, if applicable: +_Description: Prefix for area code, if applicable: Template: isdnlog/areacode Type: string -_Description: Local areacode, if applicable: +_Description: Local area code, if applicable: Template: isdnlog/isdnrate-daemon Type: boolean Default: false _Description: Run isdnrate as a daemon? - isdnrate is a utility to calculate the costs of a connection to a given + The isdnrate utility calculates 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 once. . - This is only for people with special requirements, such as those using the - isdn2h323 package. Hence most people should not choose this option. + This setting is only useful for people with special requirements, such as those using the + isdn2h323 package. --- isdnutils.old/debian/isdnutils-base.templates 2009-09-18 18:26:24.292403255 +0200 +++ isdnutils/debian/isdnutils-base.templates 2009-09-18 18:50:27.730138496 +0200 @@ -4,16 +4,16 @@ __Choices: none, ISAR.BIN Default: none _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 + Some ISDN cards can't function properly until some firmware has been + loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens 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". + necessary. Template: isdnutils/firmwarecards Type: string _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 - cards which both have to be loaded with firmware, enter "1,2". - + If you use more than one card, enter the number of the card(s) that need + the firmware to be loaded. + . + Multiple entries should be separated by commas. Card numbers are integers + where "1" is the first card, "2" the second, etc. --- isdnutils.old/debian/isdnvboxserver.templates 2009-09-18 18:26:24.512406296 +0200 +++ isdnutils/debian/isdnvboxserver.templates 2009-09-18 18:47:40.246137959 +0200 @@ -2,12 +2,12 @@ Type: string Default: quit _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. + Vbox must know what number to listen to. Depending on the country's ISDN + system, this may or may not include the area code. Leading "0" should most + often be dropped. . Leave the field blank if you want to configure by hand, or if you already - have an existing (working) vbox + use an existing (working) vbox configuration from the time when this was still part of isdnutils (unless you want to create a new configuration). @@ -15,64 +15,69 @@ Type: string Default: 4 _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 information. + One ring is about 5 seconds. This setting can later be fine-tuned + for each incoming telephone number, for instance to aggressively + filter some incoming numbers. + . + You should read vbox.conf(5) for more information. Template: isdnvboxserver/attachmsg Type: boolean Default: true -_Description: Should the message be attached to the email? +_Description: Should incoming messages be attached to notification mails? When a message is recorded, an email notification is sent. If that email should contain the message as an attachment, choose the option. - . - Note: the attachment can be large. Template: isdnvboxserver/daemonuser Type: string Default: vboxdaemonuser -_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. +_Description: Run the answering machine as: + The vboxd daemon should run as an unprivileged (non-root) user. It must be + a member of the "dialout" group. Template: isdnvboxserver/nosuchuser Type: text -_Description: User ${Daemonuser} doesn't exist on the system - The user who runs the answering machine should be a valid user name - on this system. +#flag:comment:1 +# Translators, do not translate "Daemonuser" +_Description: ${Daemonuser} unknown + The user you chose does not exist on this machine. You must choose + a valid user name. Template: isdnvboxserver/user Type: string -_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. +_Description: Login for the answering machine: + When clients (using the vbox program provided by the isdnvboxclient + package) connect to the answering machine, they will be prompted with a + user name and password. + . + The user name you define here does not have to be a user on the + system itself. Template: isdnvboxserver/password Type: password +#flag:comment:1,1 +# Translators, do not translate "${User}" _Description: Password for ${User}: - Please don't use ':' in it! The way it is stored cannot handle this. + Please choose the password for the ${User} connection user. Template: isdnvboxserver/vboxnodir Type: error _Description: No home directory - The home directory `${DIR}' for user `${USER}' doesn't exist. This means + The home directory `${DIR}' for user `${USER}' does not exist. This means that the file `${DIR}/.vbox.conf' cannot be created. Template: isdnvboxserver/vboxnouser Type: error -_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 +_Description: Non-existing user + 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: boolean Default: true _Description: Should vboxgetty be enabled? - vboxgetty is in /etc/inittab, but not yet enabled. Choosing this option + A call for vboxgetty is defined 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. @@ -84,7 +89,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. + This problem has to be fixed manually. Template: isdnvboxserver/devfs_vboxgettyconf Type: error @@ -94,7 +99,7 @@ (/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. + This problem has to be fixed manually. Template: isdnvboxserver/dummy Type: note --
Template: ipppd/ispwontdoit Type: error _Description: ISP dialup configuration already exists The device.${IPPP0} and ipppd.${IPPP0} files already exist. Therefore, the ipppd configuration phase won't touch anything there, as it looks like it has already been configured. . If it doesn't work yet, and you want to try the automatic configuration, stop all ISDN processes (use "/etc/init.d/isdnutils stop"), remove the files mentioned above, and rerun the configuration with "dpkg-reconfigure ipppd". After that, restart the ISDN processes with "/etc/init.d/isdnutils start". Template: ipppd/whichif Type: string Default: ippp0 _Description: Interface to configure: The default setting should be safe for most configurations. . However, if you have special requirements or want to choose to configure another interface, please enter it here. . Leave the field blank if you do not want to configure anything now. Template: ipppd/wrongif Type: error _Description: Invalid interface name Valid interface names begin with "ippp" followed by a number between 0 and 63. Template: ipppd/ispphone Type: string Default: manual _Description: ISP's telephone number: At least one phone number has to be dialed in order to connect to the Internet service provider (ISP). . Please enter that telephone number here, including dialing prefixes, area codes, and so on, but without any spaces. . Multiple telephone numbers may be entered and should be separated by spaces. . Leave the field blank if you want to configure the connection manually. Template: ipppd/eaz Type: string Default: 0 _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 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. . This may also be necessary if you want the costs to be registered to one particular MSN, in case you have more than one MSN and this is supported by your telco. Template: ipppd/isplogin Type: string _Description: ISP user name: Most ISPs require a user name and password to be provided when connecting. Template: ipppd/isppasswd Type: password _Description: ISP password: Please enter the password to use when connecting to the ISP. This password will be kept in /etc/ppp/pap-secrets and /etc/ppp/chap-secrets together along with the username. Template: ipppd/isploginpapalreadythere Type: error _Description: ISP user name already in pap-secrets The user name you entered for logging into your ISP is already listed in the /etc/ppp/pap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. Template: ipppd/isploginchapalreadythere Type: error _Description: ISP user name already in chap-secrets The user name you entered for logging into your ISP is already listed in the /etc/ppp/chap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. Template: ipppd/isploginpapchapalreadythere Type: error _Description: ISP user name already in chap-secrets and pap-secrets The user name you entered for logging into your ISP is already listed in the chap-secrets and pap-secrets files in /etc/ppp/. The existing entries will be commented out, and new entries with the data you just entered will be inserted. Template: ipppd/oldipup Type: error _Description: /etc/ppp/ip-up.d/00-isdnutils still exists The /etc/ppp/ip-up.d/00-isdnutils file from the old isdnutils package still exists. If you changed that file at some point, you may need to redo 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. Template: ipppd/oldipdown Type: error _Description: /etc/ppp/ip-down.d/99-isdnutils still exists The /etc/ppp/ip-down.d/99-isdnutils file from the old isdnutils package still exists. If you changed that file at some point, you may need to redo 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. Template: ipppd/oldipupdown Type: error _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. Template: ipppd/noisdnutilsinit Type: error _Description: (Re)start ipppd manually There is no /etc/init.d/isdnutils on this system; hence you will have to stop and start any ipppd daemons manually. Template: ipppd/isdnutilsinitbad Type: error _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 /etc/init.d/isdnutils will also help.
Template: isdnlog/country Type: select #flag:translate:9 Choices-C: AT, FR, DE, LU, NL, NO, ES, CH, other __Choices: Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other # Translators: # Please choose among # "Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other" _DefaultChoice: other _Description: Country: Please choose the local country. This will be used to set the rate table to use for calculating the calls costs Template: isdnlog/country_manual Type: string Description: Country's ISO two-letter code: Please enter the ISO code of the local country. As no rate tables are available, this setting will be unused. Template: isdnlog/countryprefix Type: string Default: + _Description: Prefix to dial before international number: Template: isdnlog/countrycode Type: string Default: 49 #flag:comment:3 # Translators: do not translate ${default_countrycode} and ${default_country} _Description: Country ITU code: Please enter the international code for the local country. . Example: ${default_countrycode} for ${default_country} Template: isdnlog/areaprefix Type: string Default: 0 _Description: Prefix for area code, if applicable: Template: isdnlog/areacode Type: string _Description: Local area code, if applicable: Template: isdnlog/isdnrate-daemon Type: boolean Default: false _Description: Run isdnrate as a daemon? The isdnrate utility calculates 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 once. . This setting is only useful for people with special requirements, such as those using the isdn2h323 package.
Template: isdnutils/firmware Type: select #flag:translate:1 __Choices: none, ISAR.BIN Default: none _Description: Firmware to load: Some ISDN cards can't function properly until some firmware has been loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is necessary. Template: isdnutils/firmwarecards Type: string _Description: ISDN card numbers to load with the firmware: If you use more than one card, enter the number of the card(s) that need the firmware to be loaded. . Multiple entries should be separated by commas. Card numbers are integers where "1" is the first card, "2" the second, etc.
Template: isdnvboxserver/msn Type: string Default: quit _Description: Number that vbox should answer: Vbox must know what number to listen to. Depending on the country's ISDN system, this may or may not include the area code. Leading "0" should most often be dropped. . Leave the field blank if you want to configure by hand, or if you already use 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/rings Type: string Default: 4 _Description: Number of rings for vbox to pick up the line: One ring is about 5 seconds. This setting can later be fine-tuned for each incoming telephone number, for instance to aggressively filter some incoming numbers. . You should read vbox.conf(5) for more information. Template: isdnvboxserver/attachmsg Type: boolean Default: true _Description: Should incoming messages be attached to notification mails? When a message is recorded, an email notification is sent. If that email should contain the message as an attachment, choose the option. Template: isdnvboxserver/daemonuser Type: string Default: vboxdaemonuser _Description: Run the answering machine as: The vboxd daemon should run as an unprivileged (non-root) user. It must be a member of the "dialout" group. Template: isdnvboxserver/nosuchuser Type: text #flag:comment:1 # Translators, do not translate "Daemonuser" _Description: ${Daemonuser} unknown The user you chose does not exist on this machine. You must choose a valid user name. Template: isdnvboxserver/user Type: string _Description: Login for the answering machine: When clients (using the vbox program provided by the isdnvboxclient package) connect to the answering machine, they will be prompted with a user name and password. . The user name you define here does not have to be a user on the system itself. Template: isdnvboxserver/password Type: password #flag:comment:1,1 # Translators, do not translate "${User}" _Description: Password for ${User}: Please choose the password for the ${User} connection user. Template: isdnvboxserver/vboxnodir Type: error _Description: No home directory The home directory `${DIR}' for user `${USER}' does not exist. This means that the file `${DIR}/.vbox.conf' cannot be created. Template: isdnvboxserver/vboxnouser Type: error _Description: Non-existing user 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: boolean Default: true _Description: Should vboxgetty be enabled? A call for vboxgetty is defined 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/devfs_inittab Type: error _Description: Device in inittab doesn't agree with devfs mode The entry for vboxgetty in /etc/inittab uses a device name that does not correspond to the current devfs usage; either a devfs (/dev/isdn/ttyIxx) name is used in inittab while devfs is not mounted, or the non-devfs name is used while devfs is mounted. . This problem has to be fixed manually. Template: isdnvboxserver/devfs_vboxgettyconf Type: error _Description: Device in vboxgetty.conf doesn't agree with devfs mode The device entry in /etc/isdn/vboxgetty.conf uses a device name that does not correspond to the current devfs usage; either a devfs (/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. . This problem has to be fixed manually. Template: isdnvboxserver/dummy Type: note Description: for internal use Note to translators: no need to translate this, not shown to users.
--- isdnutils.old/debian/ipppd.templates 2009-09-18 18:26:24.196589117 +0200 +++ isdnutils/debian/ipppd.templates 2009-09-18 19:10:25.921343444 +0200 @@ -1,47 +1,44 @@ Template: ipppd/ispwontdoit Type: error -_Description: ISP dialup config already exists - The files device.${IPPP0} and ipppd.${IPPP0} already exist. Therefore the +_Description: ISP dialup configuration already exists + The device.${IPPP0} and ipppd.${IPPP0} files already exist. Therefore, the ipppd configuration phase won't touch anything there, as it looks like - it's already been configured. + it has already been configured. . If it doesn't work yet, and you want to try the automatic configuration, stop all ISDN processes (use "/etc/init.d/isdnutils stop"), remove the files mentioned above, and rerun the configuration with "dpkg-reconfigure - ipppd". After that, restart the ISDN processes: "/etc/init.d/isdnutils + ipppd". After that, restart the ISDN processes with "/etc/init.d/isdnutils start". Template: ipppd/whichif Type: string Default: ippp0 _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. + The default setting should be safe for most configurations. . - However, some people have special requirements, and they may choose - another interface that will be configured (e.g. because they don't - want this connection to be the default gateway). + However, if you have special requirements or want to choose + to configure another interface, please enter it here. . - Note that currently at most one interface can be configured in this manner. - Leave the field blank if you do not want to configure anything now for ipppd. + Leave the field blank if you do not want to configure anything now. Template: ipppd/wrongif Type: error -_Description: Wrong interface name - You can only give names starting with "ippp" followed by a number between +_Description: Invalid interface name + Valid interface names begin 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? +_Description: ISP's telephone number: At least one phone number has to be dialed in order to connect - to your Internet service provider (ISP). + to the Internet service provider (ISP). . - Enter the telephone number here, including dialing prefixes, + Please enter that telephone number here, including dialing prefixes, area codes, and so on, but without any spaces. . - You can enter multiple telephone numbers, separated by spaces. + Multiple telephone numbers may be entered and should be separated by spaces. . Leave the field blank if you want to configure the connection manually. @@ -62,22 +59,22 @@ Template: ipppd/isplogin Type: string -_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. +_Description: ISP user name: + Most ISPs require a user name and password to be provided when + connecting. Template: ipppd/isppasswd Type: password -_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. +_Description: ISP password: + Please enter the password to use when connecting to the ISP. This password + will be kept in /etc/ppp/pap-secrets and + /etc/ppp/chap-secrets together along with the username. Template: ipppd/isploginpapalreadythere Type: error _Description: ISP user name already in pap-secrets The user name you entered for logging into your ISP is already listed in - the /etc/ppp/pap-secrets file. That's not a problem; the existing entry + the /etc/ppp/pap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. @@ -85,7 +82,7 @@ Type: error _Description: ISP user name already in chap-secrets The user name you entered for logging into your ISP is already listed in - the /etc/ppp/chap-secrets file. That's not a problem; the existing entry + the /etc/ppp/chap-secrets file. The existing entry will be commented out, and a new entry with the data you just entered will be inserted. @@ -93,8 +90,8 @@ Type: error _Description: ISP user name already in chap-secrets and pap-secrets The user name you entered for logging into your ISP is already listed in - the chap-secrets and pap-secrets files in /etc/ppp/. That's not a problem; - the existing entries will be commented out, and new entries with the data + the chap-secrets and pap-secrets files in /etc/ppp/. + The existing entries will be commented out, and new entries with the data you just entered will be inserted. Template: ipppd/oldipup @@ -131,7 +128,7 @@ Template: ipppd/noisdnutilsinit Type: error _Description: (Re)start ipppd manually - There is no /etc/init.d/isdnutils on your system; hence you will have to + There is no /etc/init.d/isdnutils on this system; hence you will have to stop and start any ipppd daemons manually. Template: ipppd/isdnutilsinitbad --- isdnutils.old/debian/isdnlog.templates 2009-09-18 18:26:24.672339165 +0200 +++ isdnutils/debian/isdnlog.templates 2009-09-18 19:02:09.349343195 +0200 @@ -1,52 +1,54 @@ Template: isdnlog/country Type: select #flag:translate:9 -__Choices: AT, CH, DE, ES, FR, LU, NL, NO, other -# 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] +Choices-C: AT, FR, DE, LU, NL, NO, ES, CH, other +__Choices: Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other +# Translators: +# Please choose among +# "Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other" +_DefaultChoice: other _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. + Please choose the local country. This will be used to set the rate table to + use for calculating the calls costs Template: isdnlog/country_manual Type: string -_Description: ISO two-letter code for 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. +Description: Country's ISO two-letter code: + Please enter the ISO code of the local country. As no rate + tables are available, this setting will be unused. Template: isdnlog/countryprefix Type: string Default: + -_Description: Prefix for international number: +_Description: Prefix to dial before international number: Template: isdnlog/countrycode Type: string Default: 49 -_Description: Code of your country: - e.g. ${default_countrycode} for ${default_country} +#flag:comment:3 +# Translators: do not translate ${default_countrycode} and ${default_country} +_Description: Country ITU code: + Please enter the international code for the local country. + . + Example: ${default_countrycode} for ${default_country} Template: isdnlog/areaprefix Type: string Default: 0 -_Description: Prefix for areacode, if applicable: +_Description: Prefix for area code, if applicable: Template: isdnlog/areacode Type: string -_Description: Local areacode, if applicable: +_Description: Local area code, if applicable: Template: isdnlog/isdnrate-daemon Type: boolean Default: false _Description: Run isdnrate as a daemon? - isdnrate is a utility to calculate the costs of a connection to a given + The isdnrate utility calculates 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 once. . - This is only for people with special requirements, such as those using the - isdn2h323 package. Hence most people should not choose this option. + This setting is only useful for people with special requirements, such as those using the + isdn2h323 package. --- isdnutils.old/debian/isdnutils-base.templates 2009-09-18 18:26:24.292403255 +0200 +++ isdnutils/debian/isdnutils-base.templates 2009-09-18 18:50:27.730138496 +0200 @@ -4,16 +4,16 @@ __Choices: none, ISAR.BIN Default: none _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 + Some ISDN cards can't function properly until some firmware has been + loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens 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". + necessary. Template: isdnutils/firmwarecards Type: string _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 - cards which both have to be loaded with firmware, enter "1,2". - + If you use more than one card, enter the number of the card(s) that need + the firmware to be loaded. + . + Multiple entries should be separated by commas. Card numbers are integers + where "1" is the first card, "2" the second, etc. --- isdnutils.old/debian/isdnvboxserver.templates 2009-09-18 18:26:24.512406296 +0200 +++ isdnutils/debian/isdnvboxserver.templates 2009-09-18 18:47:40.246137959 +0200 @@ -2,12 +2,12 @@ Type: string Default: quit _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. + Vbox must know what number to listen to. Depending on the country's ISDN + system, this may or may not include the area code. Leading "0" should most + often be dropped. . Leave the field blank if you want to configure by hand, or if you already - have an existing (working) vbox + use an existing (working) vbox configuration from the time when this was still part of isdnutils (unless you want to create a new configuration). @@ -15,64 +15,69 @@ Type: string Default: 4 _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 information. + One ring is about 5 seconds. This setting can later be fine-tuned + for each incoming telephone number, for instance to aggressively + filter some incoming numbers. + . + You should read vbox.conf(5) for more information. Template: isdnvboxserver/attachmsg Type: boolean Default: true -_Description: Should the message be attached to the email? +_Description: Should incoming messages be attached to notification mails? When a message is recorded, an email notification is sent. If that email should contain the message as an attachment, choose the option. - . - Note: the attachment can be large. Template: isdnvboxserver/daemonuser Type: string Default: vboxdaemonuser -_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. +_Description: Run the answering machine as: + The vboxd daemon should run as an unprivileged (non-root) user. It must be + a member of the "dialout" group. Template: isdnvboxserver/nosuchuser Type: text -_Description: User ${Daemonuser} doesn't exist on the system - The user who runs the answering machine should be a valid user name - on this system. +#flag:comment:1 +# Translators, do not translate "Daemonuser" +_Description: ${Daemonuser} unknown + The user you chose does not exist on this machine. You must choose + a valid user name. Template: isdnvboxserver/user Type: string -_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. +_Description: Login for the answering machine: + When clients (using the vbox program provided by the isdnvboxclient + package) connect to the answering machine, they will be prompted with a + user name and password. + . + The user name you define here does not have to be a user on the + system itself. Template: isdnvboxserver/password Type: password +#flag:comment:1,1 +# Translators, do not translate "${User}" _Description: Password for ${User}: - Please don't use ':' in it! The way it is stored cannot handle this. + Please choose the password for the ${User} connection user. Template: isdnvboxserver/vboxnodir Type: error _Description: No home directory - The home directory `${DIR}' for user `${USER}' doesn't exist. This means + The home directory `${DIR}' for user `${USER}' does not exist. This means that the file `${DIR}/.vbox.conf' cannot be created. Template: isdnvboxserver/vboxnouser Type: error -_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 +_Description: Non-existing user + 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: boolean Default: true _Description: Should vboxgetty be enabled? - vboxgetty is in /etc/inittab, but not yet enabled. Choosing this option + A call for vboxgetty is defined 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. @@ -84,7 +89,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. + This problem has to be fixed manually. Template: isdnvboxserver/devfs_vboxgettyconf Type: error @@ -94,7 +99,7 @@ (/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. + This problem has to be fixed manually. Template: isdnvboxserver/dummy Type: note
Source: isdnutils Section: utils Priority: extra Maintainer: Debian QA Group <packages@qa.debian.org> Uploaders: Paul Slootman <paul@debian.org> Standards-Version: 3.7.3 Build-Depends: debhelper (>=5), bzip2, libncurses5-dev | libncurses-dev, xutils-dev | imake, tcl8.3-dev, linuxdoc-tools (>=0.9.20), groff, libtool, libxaw7-dev, libreadline5-dev | libreadline-dev, libpcap0.8-dev, autotools-dev, automake1.4, automake1.7, automake1.9, autoconf2.13, autoconf, libssl-dev, psutils, lsb-release, po-debconf Package: isdnutils Priority: optional Architecture: alpha amd64 arm armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Depends: isdnutils-base (= ${binary:Version}), ipppd, isdnlog, isdnutils-xtools, isdnvboxserver, isdnvboxclient, openbsd-inetd | inet-superserver, ${misc:Depends} Suggests: isdnutils-doc, isdneurofile, pppdcapiplugin, capiutils Conflicts: ipppd (<<1:3.1pre1b-23) Description: Most important ISDN-related packages and utilities Note that for an external ISDN adapter, you do NOT need this package or any of the related ones. This is only for use with an internal ISDN adapter. Choosing this package will select the most frequently used components. . The current version of isdnutils is split up into component packages, to make it easier to fine-tune what is installed; hardly anyone needs everything. However, it's not possible to automatically select what is needed This is a dependency package to ease installation, and choosing this selects the most important new packages. After installation, this package can be safely removed. . The component packages selected by this are: isdnutils-base basic set of ISDN utilities. ipppd for networking over ISDN with syncPPP. isdnlog for logging ISDN calls (and much more). isdnutils-xtools for X ISDN apps (currently only xisdnload and xmonisdn) isdnvboxserver ISDN answering machine, things needed on the server system. isdnvboxclient ISDN answering machine, client side (vbox). . Not selected (although dselect will suggest some) are: isdnutils-doc for extensive documentation (basic docs are of course included with each package). isdneurofile file transfer over ISDN with the special eurofile protocol. capiutils CAPI utilies. pppdcapiplugin a plugin for the normal ppp daemon that uses CAPI to communicate over ISDN. libcapi20-3 shared library package needed by CAPI applications (will be selected automatically when needed). libcapi20-dev libcapi20 development files. isdnactivecards firmware for mostly active ISDN cards, and other related tools. Package: isdnutils-base Priority: optional Architecture: alpha amd64 arm armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Pre-Depends: debconf (>= 1.2.9) | debconf-2.0 Depends: udev | makedev (>= 2.3.1-77), ${shlibs:Depends}, lsb-base (>= 1.3-9ubuntu3), ${misc:Depends} Suggests: ipppd, isdnlog, isdnutils-doc, isdnutils-xtools, isdnvboxserver, isdnvboxclient Replaces: isdnutils (<<1:3.1pre1b-23) Description: ISDN utilities, the basic (minimal) set These utilities are the basic set of ISDN utilities that you need when you have an ISDN card installed. For complete functionality comparable to the old isdnutils package, you also need the following packages: . ipppd for networking over ISDN with syncPPP isdnlog for logging ISDN calls (and much more) isdnutils-xtools for X ISDN apps (currently only xisdnload and xmonisdn) isdnutils-doc for extensive documentation (basic docs are of course included with each package) isdnvboxserver ISDN answering machine, things needed on a server system isdnvboxclient ISDN answering machine, client side (vbox) Package: isdnutils-xtools Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Section: x11 Depends: isdnutils-base (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Replaces: isdnutils (<<1:3.1pre1b-0) Description: ISDN utilities that use X These are the graphical utilities for ISDN, xmonisdn and xisdnload. They provide, each in their own way, a visual indication of the status of the ISDN lines, so that it is directly obvious when there is a connection, for example. . This has been separated out of the main isdnutils package so that if you don't run X but do need ISDN, you don't have to include the X libraries unnecessarily. Package: ipppd Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Section: net Depends: isdnutils-base (= ${binary:Version}), debconf (>=1.2.9) | debconf-2.0, ppp, ${shlibs:Depends}, udev | makedev Suggests: pdnsd Replaces: isdnutils (<<1:3.1pre1b-0) Description: PPP daemon for syncPPP over ISDN If you want to connect to the internet over ISDN with an internal ISDN card, you will need this. . Also needed for allowing dialins from Windows PCs over ISDN. Package: isdnlog Architecture: alpha amd64 arm armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Depends: isdnutils-base (= ${binary:Version}), isdnlog-data (>= ${binary:Version}), debconf (>=1.2.9) | debconf-2.0, ${shlibs:Depends}, ${misc:Depends} Replaces: isdnutils (<<1:3.1pre1b-0) Description: ISDN connection logger isdnlog logs all ISDN connections, and can calculate the cost of calls. If sufficient data is available, it can even recommend which alternate carrier would have been cheaper for a given call. For countries where calls are charged per discrete unit, it can disconnect the line just before the next unit starts. Package: isdnlog-data Architecture: all Depends: ${misc:Depends} Recommends: isdnlog (>= ${source:Version}) Description: data for isdnlog users All data related to call pricing, area codes, etc. in various countries. Really only useful when used with isdnlog. Package: isdnutils-doc Architecture: all Section: doc Depends: ${misc:Depends} Conflicts: isdnutils (<<1:3.1pre1b-1) Suggests: isdnutils-base (= ${source:Version}) Description: Extensive documentation for isdnutils This includes the FAQ and other miscellaneous documentation. German-language docs also included. Package: isdnvbox Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Conflicts: isdnutils (<<1:3.1pre1b-1) Depends: isdnvboxclient, isdnvboxserver, ${misc:Depends} Recommends: sox Description: ISDN answering machine, client and server Let your Debian system be your answering machine! Messages can be accessed remotely, automatically emailed, etc. . This package is a helper to install both the client (with which you listen to the messages) and the server (with which the messages are recorded) parts of the software. Package: isdnvboxclient Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Conflicts: isdnutils (<<1:3.1pre1b-1), isdnvbox (<<1:3.1pre1b-2) Depends: ${shlibs:Depends}, sox | nas-bin | alsa-utils, ${misc:Depends} Suggests: isdnvboxserver Replaces: isdnutils (<<1:3.1pre1b-0) Description: ISDN answering machine, client Let your Debian system be your answering machine! Messages can be accessed remotely, automatically emailed, etc. . This is the client part of the software, with which you can listen to the messages. Those messages are recorded on a system with the server part of the software (isdnvboxserver); that system may be elsewhere, as long as it can be connected to via a network. Package: isdnvboxserver Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Conflicts: isdnutils (<<1:3.1pre1b-1),isdnvbox (<<1:3.1pre1b-2) Depends: isdnutils-base (= ${binary:Version}), debconf (>=1.2.9) | debconf-2.0, ${shlibs:Depends}, openbsd-inetd | inet-superserver, udev | makedev, ${misc:Depends} Suggests: isdnvboxclient Replaces: isdnutils (<<1:3.1pre1b-0) Description: ISDN answering machine, server Let your Debian system be your answering machine! Messages can be accessed remotely, automatically emailed, etc. . This is the server part of the software. This is what needs to be installed on the system with the ISDN card. To actually listen to the recorded messages you need the client package (isdnvboxclient) somewhere, not necessarily on the same system. Package: capiutils Architecture: alpha amd64 arm armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Depends: libcapi20-3 (= ${binary:Version}), ${shlibs:Depends}, lsb-base (>= 1.3-9ubuntu3), udev | makedev, ${misc:Depends} Replaces: isdnactivecards (<< 1:3.6.2004-12-19-1) Section: net Description: Utilities for CAPI-capable ISDN cards Some ISDN cards (notably the AVM active cards, and the AVM passive cards when using the proprietary drivers) are accessed via the CAPI interface. The package contains utilities to initialize and get information about these cards. . See /usr/share/doc/capiutils/* for some (rudimentary) info. Package: libcapi20-3 Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Section: libs Depends: ${shlibs:Depends}, ${misc:Depends} Replaces: isdnutils (<<1:3.1pre1b-0), libcapi20, libcapi20-2 Conflicts: libcapi20, libcapi20-2 Description: libraries for CAPI support If you have an ISDN card with which CAPI works, you may be able to use applications that use CAPI, e.g. a fax system. At this point, AVM cards can work with CAPI, as well as some active cards. For the AVM passive cards you need to visit the www.AVM.de website. . If you need this package, it will be installed automatically via dependencies, no need to select it yourself. Package: libcapi20-dev Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Section: libdevel Depends: libcapi20-3 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Replaces: isdnutils (<<1:3.1pre1b-0), libcapi20, libcapi20-2 Conflicts: libcapi20, libcapi20-2 Description: libraries for CAPI support If you have an ISDN card with which CAPI works, you may be able to use applications that use CAPI, e.g. a fax system. At this point, AVM cards can work with CAPI, as well as some active cards. For the AVM passive cards you need to visit the www.AVM.de website. . If you need this package, it will be installed automatically via dependencies, no need to select it yourself. Package: pppdcapiplugin Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Depends: ppp (>=2.3.11), libcapi20-3 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Section: net Description: plugin for pppd to communicate with CAPI-capable ISDN cards Some ISDN cards (notably the AVM passive cards, when a module from the AVM website is loaded) can be used by CAPI utilities. This is a plugin for the regular PPP daemon to use CAPI on such cards. . See /usr/share/doc/pppdcapiplugin/* for some (rudimentary) info. Package: isdnactivecards Architecture: alpha amd64 arm armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Depends: isdnutils-base (= ${binary:Version}), capiutils (>= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Replaces: isdnutils (<<1:3.1pre1b-0) Description: support utilities for active ISDN cards If you have an active ISDN card, you will need things like firmware and the means to load that firmware into that card. The utilities are contained in this package. . See /usr/share/doc/isdnactivecards/* for more information. Package: isdneurofile Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390 Section: comm Depends: isdnutils-base (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Description: ISDN eurofile transfer tool If you want to send / receive files over an ISDN line with the eurofile system, you need this package. Not used much outside of Germany I believe (and not much there either).
Attachment:
signature.asc
Description: Digital signature