--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: isdnutils: [debconf_rewrite] Debconf templates and debian/control review
- From: Christian Perrier <bubulle@debian.org>
- Date: Wed, 07 Oct 2009 07:01:37 +0200
- Message-id: <20091007050137.18793.83079.reportbug@mykerinos.kheops.frmug.org>
Package: isdnutils
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Friday, September 18, 2009, I notified you of the beginning of a review process
concerning debconf templates for isdnutils.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading isdnutils with these changes
right now.
The second phase of this process will begin on Saturday, October 10, 2009, when I will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Saturday, October 31, 2009. Please avoid uploading a package with fixed or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Sunday, November 01, 2009, I will contact you again and will send a final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- isdnutils.old/debian/ipppd.templates 2009-09-18 18:26:24.196589117 +0200
+++ isdnutils/debian/ipppd.templates 2009-10-07 06:57:24.160341625 +0200
@@ -1,47 +1,53 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
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 an 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.
@@ -58,26 +64,26 @@
.
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.
+ by your telecommunication providing company.
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 account name:
+ Most ISPs require an account 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 with the account name.
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 +91,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 +99,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 +137,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-10-07 06:58:29.452341062 +0200
@@ -1,52 +1,63 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
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, Luxembourg, Netherlands, Norway, Spain, Switzerland, other
+# Translators:
+# Please choose among
+# "Austria, France, Germany, Luxembourg, 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 costs of 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 special setups, such as for an
+ ISDN-to-H.323 gateway.
--- isdnutils.old/debian/isdnutils-base.templates 2009-09-18 18:26:24.292403255 +0200
+++ isdnutils/debian/isdnutils-base.templates 2009-10-07 06:56:02.660341307 +0200
@@ -1,19 +1,28 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
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 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) in need
+ of firmware.
+ .
+ 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-10-07 06:56:03.800341094 +0200
@@ -1,13 +1,22 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: isdnvboxserver/msn
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 +24,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 username.
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:
+ Connections to the answering machine (using the vbox program provided
+ by the isdnvboxclient package) will be prompted for a username and
+ password.
+ .
+ The username you define here does not have to correspond to a login
+ account on this system.
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
- that the file `${DIR}/.vbox.conf' cannot be created.
+ 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 +98,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 +108,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
--- isdnutils.old/debian/control 2009-09-18 18:26:24.292403255 +0200
+++ isdnutils/debian/control 2009-10-07 07:00:56.584340118 +0200
@@ -12,38 +12,30 @@
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.
+Description: ISDN utilities - dependency package
+ This package depends on the most frequently used components for an
+ ISDN system using an internal adapter; they are not required for an
+ external adapter.
+ .
+ The isdnutils suite 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 select what is needed automatically. This
+ dependency package just ensures the most important components are
+ installed, and can be safely removed again once that is done.
+ .
+ The component packages involved are:
+ * isdnutils-base: the basic set of ISDN utilities;
+ * ipppd: for networking over ISDN with syncPPP;
+ * isdnlog: for logging ISDN calls (and much more);
+ * isdnutils-xtools: graphical utilities (xisdnload and xmonisdn);
+ * isdnvboxclient: ISDN answering machine client;
+ * isdnvboxserver: ISDN answering machine server.
+ .
+ It also suggests the following optional extras:
+ * capiutils: CAPI utilities;
+ * isdneurofile: for file transfer over the EUROFILE protocol;
+ * isdnutils-doc: additional documentation;
+ * pppdcapiplugin: a CAPI plugin for the normal PPP daemon.
Package: isdnutils-base
Priority: optional
@@ -52,33 +44,24 @@
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)
+Description: ISDN utilities - minimal set
+ This package provides the basic set of ISDN utilities needed to make use
+ of an ISDN card. For more complete functionality, install the isdnutils
+ dependency package.
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.
+Description: ISDN utilities - graphical tools
+ This package provides xmonisdn and xisdnload, which are graphical tools
+ for ISDN. Each in its own way gives a visual indication of the status of
+ the ISDN lines, so that (for example) it is obvious when there is a
+ connection.
+ .
+ They have been split out into a separate package to allow the others
+ in the suite to avoid dependencies on the X Window System.
Package: ipppd
Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390
@@ -86,29 +69,30 @@
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.
+Description: ISDN utilities - PPP daemon
+ This package provides the specially modified version of the Point to
+ Point Protocol daemon needed to connect to the Internet through an
+ internal ISDN card. It also supports dial-in connections from Windows
+ clients.
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.
+Description: ISDN utilities - connection logger
+ This package provides a set of utilities that can log ISDN connections and
+ 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.
+Description: ISDN utilities - connection logger data
+ This package provides data related to call pricing, area codes, etcetera,
+ in various countries, and is only useful with isdnlog.
Package: isdnutils-doc
Architecture: all
@@ -116,22 +100,21 @@
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.
+Description: ISDN utilities - documentation
+ This package includes the FAQ and other miscellaneous documentation
+ for the ISDN utilities suite, in English and German.
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
+Description: ISDN utilities - answering machine dependency package
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.
+ This package depends for convenience on both the vbox server (with which
+ the messages are recorded) and the client (with which you listen to them).
Package: isdnvboxclient
Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390
@@ -139,14 +122,13 @@
Depends: ${shlibs:Depends}, sox | nas-bin | alsa-utils, ${misc:Depends}
Suggests: isdnvboxserver
Replaces: isdnutils (<<1:3.1pre1b-0)
-Description: ISDN answering machine, client
+Description: ISDN utilities - 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.
+ This package provides the vbox client, with which you can listen to the
+ messages recorded by a vbox server (either running on the same machine or
+ accessible over the network).
Package: isdnvboxserver
Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390
@@ -154,12 +136,12 @@
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
+Description: ISDN utilities - 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
+ This package provides the vbox server, which must 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.
@@ -168,13 +150,11 @@
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
+Description: ISDN utilities - tools for CAPI-capable 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
@@ -182,14 +162,13 @@
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: isdnutils (<<1:3.1pre1b-0), libcapi20, libcapi20-2
Conflicts: libcapi20, libcapi20-2
-Description: libraries for CAPI support
+Description: ISDN utilities - CAPI support libraries
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
+ CAPI-capable applications such as fax systems. 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.
+ This package will be installed automatically if needed.
Package: libcapi20-dev
Architecture: alpha amd64 arm armeb armel armeb armel hppa i386 ia64 m68k mips mipsel powerpc ppc64 sparc s390
@@ -197,42 +176,38 @@
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
+Description: ISDN utilities - CAPI development libraries
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
+ CAPI-capable applications such as fax systems. 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.
+ This package provides files needed for development of CAPI-aware software.
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.
+Description: ISDN utilities - pppd plug-in for CAPI support
+ Some ISDN cards can be used by CAPI utilities - for instance the AVM
+ passive cards, when a module from the AVM website is loaded.
.
- See /usr/share/doc/pppdcapiplugin/* for some (rudimentary) info.
+ This package provides a plug-in for the regular PPP daemon to use CAPI
+ on such cards.
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.
+Description: ISDN utilities - active ISDN card support
+ This package provides firmware and firmware-loading utilities for active
+ ISDN cards (the Eicon, Eicon Diva, IBM Active 2000, ICN, or PCBIT-D cards).
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).
+Description: ISDN utilities - EUROFILE support
+ This package provides tools for sending/receiving files over an ISDN
+ connection via the EUROFILE protocol, which is not used much outside of
+ Germany (or even inside it).
--- End Message ---