Package: webcalendar
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Saturday, April 21, 2007, I notified you of the beginning of a review process
concerning debconf templates for webcalendar.
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 are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading webcalendar with these changes right now.
The second phase of this process will begin on Tuesday, May 08, 2007, 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
Sunday, May 20, 2007. Please avoid uploading a package with fixed or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
On Monday, May 21, 2007, 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: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
---
/home/bubulle/travail/debian/rewrite/INTENT/webcalendar/webcalendar.old/debian/webcalendar.templates
2007-04-18 08:07:37.349652306 +0200
+++
/home/bubulle/travail/debian/rewrite/INTENT/webcalendar/webcalendar/debian/webcalendar.templates
2007-04-21 13:59:39.711813473 +0200
@@ -2,54 +2,57 @@
Type: boolean
Default: false
_Description: Use persistent connections?
- Using persistent connections can improve performance on heavily loaded
- websites by using a previously opened sql connection.
+ Using persistent connections can improve the performance on heavily loaded
+ websites by using a previously opened SQL connection.
Template: webcalendar/conf/use_http_auth
Type: boolean
Default: false
-_Description: Use HTTP auth?
- Webcalendar by default uses the database's webcal_user table for
- authenticating users. You can use HTTP auth logins instead and use Apache
- to manage logins but will still have to add users to webcalendar.
+_Description: Use HTTP authentication?
+ WebCalendar by default uses the database's webcal_user table for
+ authenticating users. You can use HTTP authentication logins
+ instead and use Apache to manage logins. That will still require adding
+ the users to WebCalendar.
Template: webcalendar/conf/single_user_mode
Type: boolean
Default: false
-_Description: Should webcalendar be installed in single user mode?
- Webcalendar can be installed in single user mode or multiuser mode. If it
- is installed in single user mode, you won't need to login. It isn't
- recommended that you install in single user mode unless you are running
- this on a personal server protected by a firewall.
+_Description: Should WebCalendar be installed in single user mode?
+ WebCalendar can be installed in single user mode or multiuser mode. If it
+ is installed in single user mode, no login will be required.
+ .
+ Using the single user mode is not recommended unless the software runs
+ on a personal server protected by a firewall.
Template: webcalendar/conf/single_user_login
Type: string
-_Description: Name of the webcalendar user:
- If you have installed webcalendar in single user mode, you need to specify
+_Description: Name of the WebCalendar user:
+ If WebCalendar is installed in single user mode, you need to specify
the name of the user to connect as.
Template: webcalendar/status/debconf_managed
Type: boolean
Default: true
-_Description: Allow debconf to manage settings.conf?
- You can allow debconf to manage your settings.conf or you can manage your
- settings manually.
+_Description: Manage settings.conf automatically?
+ The configuration program for the package can manage the settings.conf
+ file but you may prefer managing your settings yourself.
Template: webcalendar/note/admin_user
Type: note
-_Description: Webcalendar administrative user
- After installing the tables for your sql database you will have access to
- webcalendar using the standard admin user. It is STRONGLY suggested that
- you change the password after logging in. The default login and password
- is admin:admin.
+_Description: Password change needed for the WebCalendar administrative user
+ After installing the tables for the SQL database you will have access
+ to WebCalendar using the standard administrative user. It is STRONGLY
+ suggested that you change the password after logging in.
+ .
+ The default login and password are 'admin:admin'.
Template: webcalendar/conf/httpd_conf
Type: multiselect
_Choices: apache2, apache, apache-ssl, apache-perl, other
Default: apache2
_Description: Web server to configure:
- Apache can be automatically configured to use webcalendar by creating links in
- /etc/{apache-version}/conf.d/. Select all the versions of Apache you would
+ Apache can be automatically configured to use WebCalendar by creating links in
+ /etc/{apache-version}/conf.d/. Select all the versions of Apache you would
like to automatically configure or 'other' if you don't use Apache or plan on
configuring Apache yourself.
@@ -57,8 +60,8 @@
Type: boolean
Default: false
_Description: Should ${webserver} be restarted?
- Remember that in order to activate the new configuration, ${webserver} has
- to be restarted. You can also restart ${webserver} by manually executing
+ In order to activate the new configuration, ${webserver} has to be
+ restarted. You can also restart ${webserver} by manually executing
'invoke-rc.d ${webserver} restart'.
Template: webcalendar/store/webservers_to_be_restarted
---
/home/bubulle/travail/debian/rewrite/INTENT/webcalendar/webcalendar.old/debian/control
2007-04-18 08:07:37.349652306 +0200
+++
/home/bubulle/travail/debian/rewrite/INTENT/webcalendar/webcalendar/debian/control
2007-04-21 11:35:52.803016501 +0200
@@ -18,4 +18,4 @@
WebCalendar is a PHP-based calendar application that can be configured
as a single-user calendar, a multi-user calendar for groups of users,
or as an event calendar viewable by visitors. MySQL, PostgreSQL, Oracle,
- DB2, Interbase, or ODBC is required.
+ DB2, Interbase, or ODBC are required.
---
/home/bubulle/travail/debian/rewrite/LCFC/webcalendar/webcalendar.old/debian/webcalendar.templates
2007-04-18 08:07:37.349652306 +0200
+++
/home/bubulle/travail/debian/rewrite/LCFC/webcalendar/webcalendar/debian/webcalendar.templates
2007-05-05 10:16:28.913541062 +0200
@@ -1,55 +1,67 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# for an advice to [EMAIL PROTECTED]
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: webcalendar/conf/db_persistent
Type: boolean
Default: false
-_Description: Use persistent connections?
+_Description: Should WebCalendar use persistent connections?
Using persistent connections can improve performance on heavily loaded
- websites by using a previously opened sql connection.
+ websites by using a previously opened SQL connection.
Template: webcalendar/conf/use_http_auth
Type: boolean
Default: false
-_Description: Use HTTP auth?
- Webcalendar by default uses the database's webcal_user table for
- authenticating users. You can use HTTP auth logins instead and use Apache
- to manage logins but will still have to add users to webcalendar.
+_Description: Use HTTP authentication?
+ WebCalendar by default uses the database's webcal_user table for
+ authenticating users. You can use HTTP authentication logins
+ instead and use Apache to manage logins. This will still require adding
+ users to WebCalendar.
Template: webcalendar/conf/single_user_mode
Type: boolean
Default: false
-_Description: Should webcalendar be installed in single user mode?
- Webcalendar can be installed in single user mode or multiuser mode. If it
- is installed in single user mode, you won't need to login. It isn't
- recommended that you install in single user mode unless you are running
- this on a personal server protected by a firewall.
+_Description: Should WebCalendar be installed in single-user mode?
+ WebCalendar can be installed in single-user mode or multi-user mode. If it
+ is installed in single-user mode, no login will be required.
+ .
+ Using the single-user mode is not recommended unless the software runs
+ on a personal server protected by a firewall.
Template: webcalendar/conf/single_user_login
Type: string
-_Description: Name of the webcalendar user:
- If you have installed webcalendar in single user mode, you need to specify
+_Description: Name of the WebCalendar user:
+ If WebCalendar is installed in single-user mode, you need to specify
the name of the user to connect as.
Template: webcalendar/status/debconf_managed
Type: boolean
Default: true
-_Description: Allow debconf to manage settings.conf?
- You can allow debconf to manage your settings.conf or you can manage your
- settings manually.
+_Description: Manage settings.conf automatically?
+ The configuration program for the package can manage the settings.conf
+ file but you may prefer managing these settings manually.
Template: webcalendar/note/admin_user
Type: note
-_Description: Webcalendar administrative user
- After installing the tables for your sql database you will have access to
- webcalendar using the standard admin user. It is STRONGLY suggested that
- you change the password after logging in. The default login and password
- is admin:admin.
+_Description: Password change needed for the WebCalendar administrative user
+ After installing the tables for the SQL database you will have access
+ to WebCalendar using its administrative user. It is strongly
+ suggested that you change the password after logging in.
+ .
+ The default login and password are 'admin:admin'.
Template: webcalendar/conf/httpd_conf
Type: multiselect
_Choices: apache2, apache, apache-ssl, apache-perl, other
Default: apache2
_Description: Web server to configure:
- Apache can be automatically configured to use webcalendar by creating links in
- /etc/{apache-version}/conf.d/. Select all the versions of Apache you would
+ Apache can be automatically configured to use WebCalendar by creating links in
+ /etc/{apache-version}/conf.d/. Select all the versions of Apache you would
like to automatically configure or 'other' if you don't use Apache or plan on
configuring Apache yourself.
@@ -57,8 +69,8 @@
Type: boolean
Default: false
_Description: Should ${webserver} be restarted?
- Remember that in order to activate the new configuration, ${webserver} has
- to be restarted. You can also restart ${webserver} by manually executing
+ In order to activate the new configuration, ${webserver} has to be
+ restarted. You can also restart ${webserver} by manually executing
'invoke-rc.d ${webserver} restart'.
Template: webcalendar/store/webservers_to_be_restarted
---
/home/bubulle/travail/debian/rewrite/LCFC/webcalendar/webcalendar.old/debian/control
2007-04-18 08:07:37.349652306 +0200
+++
/home/bubulle/travail/debian/rewrite/LCFC/webcalendar/webcalendar/debian/control
2007-04-22 08:17:06.029420426 +0200
@@ -17,5 +17,5 @@
Description: PHP-Based multi-user calendar
WebCalendar is a PHP-based calendar application that can be configured
as a single-user calendar, a multi-user calendar for groups of users,
- or as an event calendar viewable by visitors. MySQL, PostgreSQL, Oracle,
- DB2, Interbase, or ODBC is required.
+ or as an event calendar viewable by visitors. It requires either MySQL,
+ PostgreSQL, Oracle, DB2, Interbase, or ODBC.
