[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFR] templates://webcalendar/{webcalendar.templates}



Kevin Coyner wrote:
> Christian Perrier wrote......
[reinstating some context I feel like pontificating about]
>> I would
>> personnally prefer "multi-user" if English uses the same conventions
>> than French for such constructions of words (use a hyphen between two
>> vowels but no hyphens between a vowel and a consonant).         
         
Alas, it's nothing so predictable.  Noun+noun coinages tend to start
as "foo bar" and slide gradually towards "foo-bar" and then "foobar"
over time, as the combination becomes established as a single
familiar term in its own right.

>> @@ -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.
>>
>> I hope that I'm correct here...
>
> Please consider the following:
...
>   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 are required.
> + or as an event calendar viewable by visitors. Either MySQL, PostgreSQL,
> + Oracle, DB2, Interbase, or ODBC is required.
> 
> I presume only one DB will be used at a time in normal usage. Adding
> the word 'Either' and keeping 'is' makes it clear that the user must
> make a single DB choice. Using the word 'are' implies that all DB's
> are required.

Unfortunately the styleguides that insist on strict number-agreement
would also disapprove of "Either X, Y or Z"; I'd recommend avoiding
the issue with "It requires X, Y or Z". 

> Still looking at the templates file. Saw a couple small things there
> that I'll send comments on soon.         

There are a couple of other minor changes in my patch: making
template questions into complete sentences, turning "PHP-Based" into
"PHP-based"...
-- 
JBR
Ankh kak! (Ancient Egyptian blessing)

--- ../webcalendar.old/debian/webcalendar.templates	2007-04-21 12:35:07.000000000 +0100
+++ debian/webcalendar.templates	2007-04-21 23:21:26.000000000 +0100
@@ -1,55 +1,58 @@
 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?
+_Description: Should webcalendar 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.
+ authenticating users. You can use HTTP authentication logins instead
+ and use Apache to manage logins. This 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.
+ 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.
+ 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
--- ../webcalendar.old/debian/control	2007-04-21 12:35:09.000000000 +0100
+++ debian/webcalendar/control	2007-04-21 23:12:49.000000000 +0100
@@ -14,8 +14,8 @@
 Depends: ${misc:Depends}, libapache-mod-php4 | libapache2-mod-php4, php4-mysql | php4-pgsql, apache | apache2 | apache-ssl | apache-perl, ucf (>= 0.28), dbconfig-common
 Suggests: php4-cli
 Recommends: mysql-client | postgresql-client, mysql-server | postgresql
-Description: PHP-Based multi-user calendar
+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 MySQL, PostgreSQL,
+ Oracle, DB2, Interbase, or ODBC.
Template: webcalendar/conf/db_persistent
Type: boolean
Default: false
_Description: Should webcalendar use persistent connections?
 Using persistent connections can improve performance on heavily loaded
 websites by using a previously opened SQL connection.

Template: webcalendar/conf/use_http_auth
Type: boolean
Default: false
_Description: Should webcalendar use HTTP auth?
 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 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, 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 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: 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 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
 like to automatically configure or 'other' if you don't use Apache or plan on
 configuring Apache yourself.

Template: webcalendar/conf/restart_webserver
Type: boolean
Default: false
_Description: Should ${webserver} be restarted?
 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
Type: string
Description: Webservers to be restarted:
 (This is for internal use only)

Source: webcalendar
Section: web
Priority: optional
Maintainer: Elizabeth Bevilacqua <lyz@princessleia.com>
Uploaders: Rafael Laboissiere <rafael@debian.org>
Build-Depends: debhelper (>= 4.1.16), po-debconf, dpatch
Build-Depends-Indep: html2text
Standards-Version: 3.7.2
XS-Vcs-Svn: svn://svn.debian.org/svn/collab-maint/ext-maint/webcalendar/
XS-Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/ext-maint/webcalendar/

Package: webcalendar
Architecture: all
Depends: ${misc:Depends}, libapache-mod-php4 | libapache2-mod-php4, php4-mysql | php4-pgsql, apache | apache2 | apache-ssl | apache-perl, ucf (>= 0.28), dbconfig-common
Suggests: php4-cli
Recommends: mysql-client | postgresql-client, mysql-server | postgresql
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. It requires MySQL, PostgreSQL,
 Oracle, DB2, Interbase, or ODBC.

Reply to: