Dear Debian maintainer,

On Thursday, November 29, 2007, I sent you a notification about the beginning 
of a review
action on debconf templates for roxen4.

Then, I sent you a bug report with rewritten templates and announcing
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.rfr file contains a patch for the templates and control
file(s) alone.

Please note that this patch applies to the templates and control
file(s) of your package as of Thursday, November 29, 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

--- roxen4.old/debian/templates 2007-11-24 09:13:11.766273058 +0100
+++ roxen4/debian/templates     2007-12-19 07:27:23.346140445 +0100
@@ -1,123 +1,125 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [EMAIL PROTECTED] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 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)...
+_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 administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+ 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)...
+_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 administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+ 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-24 09:13:11.766273058 +0100
+++ roxen4/debian/control       2007-12-16 11:09:03.471563875 +0100
@@ -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 WebWerver - binaries
+ The Roxen WebServer is very powerful and easy to maintain.
+ The server 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
- application.
+ 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 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 Challenger web server - documentation
+ The Roxen WebServer is very powerful and easy to maintain.
+ The server 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 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 server's documentation.
--- roxen4.old/debian/changelog 2007-11-24 09:13:11.766273058 +0100
+++ roxen4/debian/changelog     2008-01-05 19:56:40.373279369 +0100
@@ -1,3 +1,19 @@
+roxen4 (4.0.425-8) UNRELEASED; urgency=low
+
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+    english team as part of the Smith review project. Closes: #457026
+  * [Debconf translation updates]
+  * Portuguese. Closes: #457581
+  * Spanish; Castilian. Closes: #452927
+  * French. Closes: #458121
+  * Finnish. Closes: #458240
+  * Galician. Closes: #458538
+  * Vietnamese. Closes: #459000
+  * Russian. Closes: #459309
+  * Czech. Closes: #459327
+
+ -- Christian Perrier <[EMAIL PROTECTED]>  Sat, 05 Jan 2008 19:56:40 +0100
+
 roxen4 (4.0.425-7) unstable; urgency=low
 
   * New Spanish, German, Portuguese and French debconf template

Attachment: signature.asc
Description: Digital signature

Reply via email to