Re: [RFR] templates://roxen4/{templates}
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
Wikipedia says Roxen Challenger's downfall was its inadequate
English localisation, so I suppose I should try particularly hard
for this one.
> - http://*:1234/
> + http://www.example.com:<port>/
>
> Use the common example.com example domain. Use <port> instead of
> arbitrary "1234" as example.
s/com/org/
> - where '1234' is the port to listen to. A random port has been created
> - for you to accept. The likelihood of it being occupied is slim, but
> - make sure you want this port before pressing ENTER.
> + where '<port>' is the port to listen to. A random port is proposed
> + by default. It is very probably free for use but you should check this
> + before validating that choice.
Make that:
before accepting this value.
> Template: roxen4/community_identity_missing
[...]
> + A community identity is mandatory to be able to use the automatic update
> + facility.
Phrase it as
A community identity is mandatory for access to the automatic update
facility.
> Template: roxen4/password_missmatch
[...]
> +_Description: Passwords mismatch
> + The password and its confirmation do not match.
>
> Standard "password mismatch" template.
Interpreting that as "(there has been a) password(-related)
mismatch", rather than as an odd sentence, "(the) passwords mismatch
(one another)", I'd prefer:
_Description: Password mismatch
> Template: roxen4/previous_installation_roxen2
[...]
> + Both Roxen 2 and Roxen 4 can coexist on the same server as long as
> + they use different ports.
No need for both "both" and "co-".
> - The administration port is the same as the Roxen2 installation but plus
> - one (ie, ${SERVER_URL}).
> + Roxen 4 is the port that immediately follows Roxen 2 port (${SERVER_URL}).
Better, but unclear. If it's saying you might have:
http://www.example.org:80/ = Roxen2 docroot
http://www.example.org:1234/ = Roxen2 admin UI
http://www.example.org:8080/ = Roxen4 docroot
http://www.example.org:1235/ = Roxen4 admin UI
then I'd phrase it as:
Roxen 2 and Roxen 4 can coexist on the same server as long as
they use different ports.
.
The administrative interface for Roxen 4 will use the same URL as
the equivalent for Roxen 2, but one port number higher:
${SERVER_URL}
(And again, with s/2/3/.)
In the control file:
> -Description: The Roxen Challenger Webserver
> +Description: Roxen Challenger web server - binaries
Only early versions were titled "Challenger"; according to upstream,
it's "Roxen WebServer". This fact is even mentioned within the
following text.
> The Roxen Challenger is a very powerful and easy to maintain web
> server. The server is written in Pike which is C-like but interpreted
> + at runtime. Roxen may be configured via any web browser.
Roxen WebServer is very powerful and easy to maintain; it is written in
Pike (which is C-like but interpreted at runtime) and can be configured
via any web browser.
> The Roxen Challenger server is the foundation of a powerful
> information and communication environment. Challenger is a secure and
> + competent web server. Challenger offers
> + numerous features including a whole suite of
> + commercial and tightly integrated extensions. Challenger is also
> + suitable for powering any web site or intranet
> application.
>
> I'm unsure about "competent"....
Damning with faint praise! I think they mean "reliable".
Roxen is the foundation of a powerful information and communication
environment. It is a secure and reliable web server, offering numerous
features including a whole suite of commercial and tightly integrated
extensions. Roxen is also suitable for powering any web site or intranet
application.
> + This package provides the official version of 'Roxen WebServer'.
How is it "official" when everybody else has version 4.5 and this
claims to be a "beta release" version of 4.0? Say:
This package provides version 4 of Roxen WebServer (formerly
known as Roxen Challenger).
Since users are presumably going to find that name used all over
the place.
> Many parts of the former descriptions were not really suitable for a
> package description but more for a README.Debian file. Removing them.
Especially since these work-in-progress signs went up a couple of
Debian release cycles ago.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../roxen4.old/debian/templates 2007-11-25 12:52:22.000000000 +0000
+++ debian/templates 2007-12-05 14:23:36.000000000 +0000
@@ -1,123 +1,118 @@
Template: roxen4/server_name
Type: string
Default: Administration Interface
-_Description: Server Configuration Name:
- What name to give to the server?
+_Description: Server name:
+ Please enter the name that should be given to the Roxen server.
Template: roxen4/server_url
Type: string
_Description: Administration page URL:
- What URL should roxen4 listen to for the administration server. Should be
- something like:
+ Please enter the URL that should be used to access Roxen's administration
+ server. Example:
.
- http://*:1234/
+ http://www.example.org:<port>/
.
- where '1234' is the port to listen to. A random port has been created
- for you to accept. The likelihood of it being occupied is slim, but
- make sure you want this port before pressing ENTER.
+ where '<port>' is the port to listen to. A random port is proposed
+ by default. It is very probably free for use but you should check this
+ before accepting this value.
Template: roxen4/admin_user
Type: string
Default: administrator
_Description: Administrator username:
- The name of the administrator.
+ Please enter the username for the Roxen server administrator.
Template: roxen4/admin_password
Type: password
+# Translators: do not translate ${SERVER_ADMIN}
_Description: Administrator password:
- Please enter a password for the server administrator
- user (which is ${SERVER_ADMIN}).
+ Please choose a password for the Roxen server administrator
+ (${SERVER_ADMIN}).
Template: roxen4/admin_password_verification
Type: password
-_Description: Administrator password verification:
- Please enter the administration password again.
+_Description: Administrator password confirmation:
Template: roxen4/admin_password_missing
-Type: note
+Type: error
_Description: Empty administrator password
- Unable to accept an empty password!
Template: roxen4/update_system
Type: boolean
Default: false
_Description: Enable built-in update system?
- You may enable the automatic update system. This requires an account in the Roxen
- Community.
+ Roxen offers an automatic update system. To use this feature, you need
+ an account in the Roxen Community.
Template: roxen4/update_system_proxy
Type: boolean
Default: false
_Description: Access update server through proxy?
- This option allows you to access the update server through an HTTP proxy.
+ Please choose whether the update server should be accessed through
+ an HTTP proxy.
Template: roxen4/proxy_host
Type: string
-_Description: Proxy host:
- Host to use as proxy for the connection to the Roxen Community.
+_Description: Proxy server hostname:
Template: roxen4/proxy_port
Type: string
-_Description: Proxy port:
- Port for the HTTP proxy
+_Description: Proxy server port:
Template: roxen4/proxy_value_missing
-Type: note
-_Description: Missing proxy host/port value
- If you specify that you want to use a HTTP proxy to connect via when
- connecting to the Roxen Community, you MUST specify a value! Do over.
+Type: error
+_Description: Empty proxy host or port
Template: roxen4/community_identity
Type: string
_Description: Roxen Community identity:
- Give your Roxen Community identity (your e-mail).
+ Please enter your Roxen Community identity (e-mail address).
.
- Enter 'none' to disable the automatic update system.
+ Entering 'none' will disable the automatic update system.
Template: roxen4/community_identity_missing
-Type: note
+Type: error
_Description: Missing community identity
- You MUST give a community id to be able to use the automatic update
- facility. Do over.
+ A community identity is mandatory for access to the automatic update
+ facility.
Template: roxen4/community_password
Type: password
_Description: Roxen Community password:
- Password for the Roxen Community.
Template: roxen4/community_password_verification
Type: password
-_Description: Roxen Community password verification:
- Please enter the Community password again.
+_Description: Roxen Community password confirmation:
Template: roxen4/password_missmatch
-Type: note
-_Description: Passwords don't match
+Type: error
+_Description: Password mismatch
+ The password and its confirmation do not match.
Template: roxen4/previous_installation_roxen2
Type: note
-_Description: Previous installation (Roxen2) detected
- Roxe 2 seems to be installed. As many values as possible will be taken from
- this configuration, but you still have to give SOME your self. Mostly
- passwords, since they are encrypted and can't be decrypted easily...
- .
- You still have to MANUALLY move any configurations you have for Roxen2 to
- your new Roxen4 server (they CAN coexist as long as you don't use the
- same ports)...
- .
- The administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+_Description: Roxen 2 installation detected
+ Roxen 2 appears to be installed on this host. As many values as
+ possible will be taken from this configuration, but some will need
+ manual intervention, such as passwords.
+ .
+ Roxen 2 and Roxen 4 can coexist on the same server as long as
+ they use different ports.
+ .
+ The administrative interface for Roxen 4 will use the same URL as
+ the equivalent for Roxen 2, but one port number higher:
+ ${SERVER_URL}
Template: roxen4/previous_installation_roxen3
Type: note
-_Description: Previous installation (Roxen3) detected
- Roxen3 seems to be installed. As many values as possible will be taken from
- this configuration, but you still have to give SOME your self. Mostly
- passwords, since they are encrypted and can't be decrypted easily...
- .
- You still have to MANUALLY move any configurations you have for Roxen 3 to
- your new Roxen 4 server (they CAN coexist as long as you don't use the
- same ports)...
- .
- The administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+_Description: Roxen 3 installation detected
+ Roxen 3 appears to be installed on this host. As many values as
+ possible will be taken from this configuration, but some will need
+ manual intervention, such as passwords.
+ .
+ Roxen 3 and Roxen 4 can coexist on the same server as long as
+ they use different ports.
+ .
+ The administrative interface for Roxen 4 will use the same URL as
+ the equivalent for Roxen 3, but one port number higher:
+ ${SERVER_URL}
--- ../roxen4.old/debian/control 2007-11-25 12:52:22.000000000 +0000
+++ debian/control 2007-12-05 14:30:13.000000000 +0000
@@ -13,29 +13,22 @@
Provides: httpd, httpd-cgi, roxen3
Replaces: roxen3
Conflicts: roxen3
-Description: The Roxen Challenger Webserver
- The Roxen Challenger is a very powerful and easy to maintain web
- server. The server is written in Pike which is C-like but interpreted
- at runtime. Roxen may be configured comfortable via any web browser.
+Description: Roxen WebServer - binaries
+ Roxen WebServer is very powerful and easy to maintain; it is written in
+ Pike (which is C-like but interpreted at runtime) and can be configured
+ via any web browser.
.
- The Roxen Challenger server is the foundation of a powerful
- information and communication environment. Challenger is a secure and
- competent web server. If your intention is minimizing your Total Cost
- of Ownership, Challenger is entirely in line. Challenger offers a
- smorgasbord of features, and on top of that, a whole suite of
- commercial and tightly integrated extensions. Challenger is just as
- suitable for powering an any-sized web site, as for an intranet
+ Roxen is the foundation of a powerful information and communication
+ environment. It is a secure and competent web server, offering numerous
+ features including a whole suite of commercial and tightly integrated
+ extensions. Roxen is also suitable for powering any web site or intranet
application.
.
- This is the official version of the new 'Roxen WebServer' (the new
- name of the webserver). This is still a beta release and the old
- configuration files of the server is not fully compatible with this
- version. There will be a conversion script in a later version, but
- until then I'm installing in .../roxen4/ without any automatic config
- transference. You will have to configure the server manually... You
- can still have both the stable (1.3 and 2.1) versions, since they
- don't clash (at least not filesystem wise), but make sure they don't
- try to talk/listen on the same ports!
+ This package provides version 4 of Roxen WebServer (formerly known as
+ Roxen Challenger). Configuration files for older server versions are not
+ fully compatible with this version. Several parts of the server must be
+ configured or migrated manually. The new version can coexist with former
+ versions on the same host.
Package: roxen4-doc
Architecture: all
@@ -44,5 +37,15 @@
Replaces: roxen3-doc
Conflicts: roxen3-doc
Depends: roxen4
-Description: Roxen 4.0 documentation
- Documentation for the Roxen Webserver, v4.0.
+Description: Roxen WebServer - documentation
+ Roxen WebServer is very powerful and easy to maintain; it is written in
+ Pike (which is C-like but interpreted at runtime) and can be configured
+ via any web browser.
+ .
+ Roxen is the foundation of a powerful information and communication
+ environment. It is a secure and competent web server, offering numerous
+ features including a whole suite of commercial and tightly integrated
+ extensions. Roxen is also suitable for powering any web site or intranet
+ application.
+ .
+ This package provides the server's documentation.
Template: roxen4/server_name
Type: string
Default: Administration Interface
_Description: Server name:
Please enter the name that should be given to the Roxen server.
Template: roxen4/server_url
Type: string
_Description: Administration page URL:
Please enter the URL that should be used to access Roxen's administration
server. Example:
.
http://www.example.org:<port>/
.
where '<port>' is the port to listen to. A random port is proposed
by default. It is very probably free for use but you should check this
before accepting this value.
Template: roxen4/admin_user
Type: string
Default: administrator
_Description: Administrator username:
Please enter the username for the Roxen server administrator.
Template: roxen4/admin_password
Type: password
# Translators: do not translate ${SERVER_ADMIN}
_Description: Administrator password:
Please choose a password for the Roxen server administrator
(${SERVER_ADMIN}).
Template: roxen4/admin_password_verification
Type: password
_Description: Administrator password confirmation:
Template: roxen4/admin_password_missing
Type: error
_Description: Empty administrator password
Template: roxen4/update_system
Type: boolean
Default: false
_Description: Enable built-in update system?
Roxen offers an automatic update system. To use this feature, you need
an account in the Roxen Community.
Template: roxen4/update_system_proxy
Type: boolean
Default: false
_Description: Access update server through proxy?
Please choose whether the update server should be accessed through
an HTTP proxy.
Template: roxen4/proxy_host
Type: string
_Description: Proxy server hostname:
Template: roxen4/proxy_port
Type: string
_Description: Proxy server port:
Template: roxen4/proxy_value_missing
Type: error
_Description: Empty proxy host or port
Template: roxen4/community_identity
Type: string
_Description: Roxen Community identity:
Please enter your Roxen Community identity (e-mail address).
.
Entering 'none' will disable the automatic update system.
Template: roxen4/community_identity_missing
Type: error
_Description: Missing community identity
A community identity is mandatory for access to the automatic update
facility.
Template: roxen4/community_password
Type: password
_Description: Roxen Community password:
Template: roxen4/community_password_verification
Type: password
_Description: Roxen Community password confirmation:
Template: roxen4/password_missmatch
Type: error
_Description: Password mismatch
The password and its confirmation do not match.
Template: roxen4/previous_installation_roxen2
Type: note
_Description: Roxen 2 installation detected
Roxen 2 appears to be installed on this host. As many values as
possible will be taken from this configuration, but some will need
manual intervention, such as passwords.
.
Roxen 2 and Roxen 4 can coexist on the same server as long as
they use different ports.
.
The administrative interface for Roxen 4 will use the same URL as
the equivalent for Roxen 2, but one port number higher:
${SERVER_URL}
Template: roxen4/previous_installation_roxen3
Type: note
_Description: Roxen 3 installation detected
Roxen 3 appears to be installed on this host. As many values as
possible will be taken from this configuration, but some will need
manual intervention, such as passwords.
.
Roxen 3 and Roxen 4 can coexist on the same server as long as
they use different ports.
.
The administrative interface for Roxen 4 will use the same URL as
the equivalent for Roxen 3, but one port number higher:
${SERVER_URL}
Source: roxen4
Section: web
Priority: optional
Maintainer: Turbo Fredriksson <turbo@debian.org>
Build-Depends: debhelper (>= 4.0.2)
Standards-Version: 3.7.2
Package: roxen4
Architecture: any
Section: web
Depends: procps, hostname (>= 2.04), pike7.4-mysql | pike7.6-mysql, pike7.4-image | pike7.6-image, debconf (>= 0.5.00) | debconf-2.0, mysql-server, net-tools
Suggests: roxen4-doc, www-browser, php3-cgi, roxen-fonts-iso8859-1 | roxen-fonts-iso8859-2
Provides: httpd, httpd-cgi, roxen3
Replaces: roxen3
Conflicts: roxen3
Description: Roxen WebServer - binaries
Roxen WebServer is very powerful and easy to maintain; it is written in
Pike (which is C-like but interpreted at runtime) and can be configured
via any web browser.
.
Roxen is the foundation of a powerful information and communication
environment. It is a secure and competent web server, offering numerous
features including a whole suite of commercial and tightly integrated
extensions. Roxen is also suitable for powering any web site or intranet
application.
.
This package provides version 4 of Roxen WebServer (formerly known as
Roxen Challenger). Configuration files for older server versions are not
fully compatible with this version. Several parts of the server must be
configured or migrated manually. The new version can coexist with former
versions on the same host.
Package: roxen4-doc
Architecture: all
Section: doc
Provides: roxen3-doc
Replaces: roxen3-doc
Conflicts: roxen3-doc
Depends: roxen4
Description: Roxen WebServer - documentation
Roxen WebServer is very powerful and easy to maintain; it is written in
Pike (which is C-like but interpreted at runtime) and can be configured
via any web browser.
.
Roxen is the foundation of a powerful information and communication
environment. It is a secure and competent web server, offering numerous
features including a whole suite of commercial and tightly integrated
extensions. Roxen is also suitable for powering any web site or intranet
application.
.
This package provides the server's documentation.
Reply to: