Dear Debian maintainer,

On Saturday, April 21, 2007, I sent you a notification about the beginning of a 
review
action on debconf templates for webcalendar.

Then, I sent you a bug report with rewritten templates and annoucing
the beginning of the second phase of this action: call for translation
updates.

Translators have been working hard and here is now the result of their efforts.

Please consider using it EVEN if you committed files to your
development tree as long as they were reported.

The attached tarball contains:

- debian/changelog with the list of changes
- debian/control with rewrites of packages' descriptions
- debian/<templates> with all the rewritten templates file(s)
- debian/po/*.po with all PO files (existing ones and new ones)

As said, please use *at least* the PO files as provided here,
preferrably over those sent by translators in their bug reports. All
of them have been checked and reformatted. In some cases, formatting
errors have been corrected.

The patch-nopo file contains a patch for the templates and control file(s).

Please note that this patch applies to the templates and control
file(s) of your package as of Saturday, April 21, 2007. If your package was 
updated
in the meantime, I may have updated my reference copy....but I also
may have missed that. This is indeed why I suggested you do not
modified such files while the review process was running,
remember..:-)

It is now safe to upload a new package version with these changes.

Please notify me of your intents with regards to this. 

There is of course no hurry to update your package but feel free to
contact me in case you would need sponsoring or any other action to
fix this.



-- 


Attachment: patch.tar.gz
Description: Binary data

--- 
/home/bubulle/travail/debian/rewrite/TRANS/webcalendar/webcalendar.old/debian/webcalendar.templates
 2007-04-18 08:07:37.349652306 +0200
+++ 
/home/bubulle/travail/debian/rewrite/TRANS/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/TRANS/webcalendar/webcalendar.old/debian/control
       2007-04-18 08:07:37.349652306 +0200
+++ 
/home/bubulle/travail/debian/rewrite/TRANS/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.

Attachment: signature.asc
Description: Digital signature

Reply via email to