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

Re: [RFR] templates://pluxml/{templates}



Christian PERRIER wrote:
>   Please select the web servers that should be configured for PluXml.
> + .
> + Please note that you will have to make sure a PHP interpreter is enabled for
> + the webserver.

Aoid politeness fatigue by taking out the second "Please".  After all,
it's giving a warning, not begging a favour.

Oh, and for consistency: "web server" on the last line.
  
>  _Description: Purge blog data on package removal?
> - PluXml will store all your blog data in /var/lib/pluxml.
> + PluXml will store all blog data in /var/lib/pluxml.
>   .
> - Accepting this option will remove all the blog data when this package is
> + Accepting this option will remove all blog data when this package is
>   purged, which will leave you with a tidy system but may cause data loss if you
>   purge an operational blog.

I spent a while trying to decide whether it was "its blog data" or
"your blog data", but you've got the right answer there.
  
>  Template: pluxml/blog/lang
>  Type: select
> +__Choices: German, English, Spanish, French, Italian, Dutch, Polish, Portuguese, Romanian, Russian
>  Choices-C: de, en, es, fr, it, nl, pl, pt, ro, ru
> +# You must NOT translate this string, but you can change its value.
> +# You should put your language (if it is among the possible choices)
> +# so that it becomes the default for users of that language
> +_Default: English

It's a pity they can only be ordered alphabetically by ISO code.

>  Template: pluxml/blog/title
> +Please choose a title for this blog. It will be displayed on top of each

s/on top/at the top/ to stop it sounding as if it obscures what's
underneath.  Likewise:

>  Template: pluxml/blog/description:
> +Please choose a short description for this blog. It will be displayed as a
>  subtitle in the top of each page and in the browser window title.
            at

>  _Description: Administrator user name:
>   Please enter a name for the administrator account, which will be used to manage
> + PluXml's configuration, users and content. The user name should only
> + contain lowercase ASCII letters.
>  
> Make the second sentence clearer?
> 
> s/username/user name

s/user name/username/ back again.  User names are the personal names
of users; usernames are the strings used to identify accounts.

Also, add a nitpicky Harvard comma after "users".
 
> -Description: Light blog engine using XML files
> +Description: light blog engine using XML files
>   PluXml is a light and simple blog and CMS engine that uses simple XML files
>   to store its data and requires no database. It has all the usual features
>   (static pages, comments, categories, tags, medias, RSS feed...) and supports
>   multiple users, customizable themes and plugins.

The first line repeats "simple".  "Using/uses XML files" gets a bit
repetitive, too.  The upstream "powered by XML!" is straying the other
way into advertspeak, but maybe without the exclamation mark it could
go in the synopsis...

"Medias" is a non-word in English.  Given that PluXml doesn't contain
any media in either the newspapers/radio/TV sense or the floppies/DVDs
sense I would suggest "media management".  Oh, and room for another
Harvard comma after "themes".

Given that there are two quite different kinds of software known by
the same TLA, should we include an expansion of Content Management
System somewhere?  But include the short form in the synopsis.

   Description: light blog/CMS engine powered by XML
    PluXml is a lightweight blogging and Content Management System that uses
    simple XML files to store its data and requires no database. It has all the
    usual features (static pages, comments, categories, tags, media management,
    RSS feed, etc.) and supports multiple users, customizable themes, and
    plugins.
       
ObWhyTheName: I happen to know from blogwatching that it's Plu- for
plume, not plus or pluie or pluche...
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package
diff -ru pluxml-5.2.pristine/debian/control pluxml-5.2/debian/control
--- pluxml-5.2.pristine/debian/control	2013-08-18 21:01:40.000000000 +0100
+++ pluxml-5.2/debian/control	2013-09-14 14:02:57.703662320 +0100
@@ -13,8 +13,9 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, php5
 Recommends: php5-gd
 Suggests: mail-transport-agent
-Description: Light blog engine using XML files
- PluXml is a light and simple blog and CMS engine that uses simple XML files
- to store its data and requires no database. It has all the usual features
- (static pages, comments, categories, tags, medias, RSS feed...) and supports
- multiple users, customizable themes and plugins.
+Description: light blog/CMS engine powered by XML
+ PluXml is a lightweight blogging and Content Management System that uses
+ simple XML files to store its data and requires no database. It has all the
+ usual features (static pages, comments, categories, tags, media managements,
+ RSS feed, etc.) and supports multiple users, customizable themes, and
+ plugins.
diff -ru pluxml-5.2.pristine/debian/templates pluxml-5.2/debian/templates
--- pluxml-5.2.pristine/debian/templates	2013-08-17 22:25:01.000000000 +0100
+++ pluxml-5.2/debian/templates	2013-09-14 14:08:51.037500210 +0100
@@ -6,10 +6,10 @@
  PluXml can run on any web server supporting PHP, but only listed web servers
  can be configured automatically by this package.
  .
- Please note that you will have to make sure a PHP interpreter is enabled for
- your webserver.
- .
  Please select the web servers that should be configured for PluXml.
+ .
+ Note that you will have to make sure a PHP interpreter is enabled for the
+ web server.
 
 Template: pluxml/system/reload-webserver
 Type: boolean
@@ -25,9 +25,9 @@
 Type: boolean
 Default: false
 _Description: Purge blog data on package removal?
- PluXml will store all your blog data in /var/lib/pluxml.
+ PluXml will store all blog data in /var/lib/pluxml.
  .
- Accepting this option will remove all the blog data when this package is
+ Accepting this option will remove all blog data when this package is
  purged, which will leave you with a tidy system but may cause data loss if you
  purge an operational blog.
 
@@ -45,16 +45,14 @@
 
 Template: pluxml/blog/lang
 Type: select
-__Choices: German (de), English (en), Spanish (es), French (fr), Italian (it), Dutch (nl), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru)
+__Choices: German, English, Spanish, French, Italian, Dutch, Polish, Portuguese, Romanian, Russian
 Choices-C: de, en, es, fr, it, nl, pl, pt, ro, ru
-# You must NOT translate this string, but you can change its value. The comment
-# between brackets is used to distinguish this msgid from the one in the
-# Choices list; you do not have to worry about them, but you simply have to
-# choose a msgstr among the language codes listed in the parentheses of the
-# English Choices above, e.g. msgstr "nl" (NOT msgstr "Dutch (nl)").
-_Default: en[ default language]
+# You must NOT translate this string, but you can change its value.
+# You should put your language (if it is among the possible choices)
+# so that it becomes the default for users of that language
+_Default: English
 _Description: Blog default language:
- Please choose the default language of your blog, which will be used for the
+ Please choose the default language of this blog, which will be used for the
  public pages.
  .
  Registered blog contributors will be able to choose their language for the
@@ -64,7 +62,7 @@
 Type: string
 Default: PluXml
 _Description: Blog title:
- Please choose a title for your blog, which will be displayed in the top of each
+ Please choose a title for this blog. It will be displayed at the top of each
  page and in the browser window title.
 
 Template: pluxml/blog/description
@@ -75,8 +73,8 @@
 # (replace $LANG by your language code), under the name "L_SITE_DESCRIPTION".
 _Default: Blog or CMS, XML powered!
 _Description: Blog description or subtitle:
- Please choose a short description for your blog, which will be displayed as a
- subtitle in the top of each page and in the browser window title.
+ Please choose a short description for this blog. It will be displayed as a
+ subtitle at the top of each page and in the browser window title.
 
 Template: pluxml/blog/name
 Type: string
@@ -90,10 +88,10 @@
 Template: pluxml/blog/login
 Type: string
 Default: admin
-_Description: Administrator user name:
+_Description: Administrator username:
  Please enter a name for the administrator account, which will be used to manage
- PluXml's configuration, users and content. The username should be composed of
- lowercase ASCII letters only.
+ PluXml's configuration, users, and content. The username should only
+ contain lowercase ASCII letters.
 
 Template: pluxml/blog/password
 Type: password
@@ -103,10 +101,10 @@
 Template: pluxml/blog/confirm
 Type: password
 _Description: Confirm password:
- Please enter the same administrator password again to verify you have typed it
- correctly.
+ Please enter the same password again to verify that you have
+ typed it correctly.
 
 Template: pluxml/blog/failpass
 Type: error
-_Description: Password mismatch
- The two passwords you entered are not identical. Please try again.
+_Description: Password input error
+ The two passwords you entered were not the same. Please try again.
Template: pluxml/system/webservers
Type: multiselect
__Choices: apache2, lighttpd
Default: apache2
_Description: Web servers to configure:
 PluXml can run on any web server supporting PHP, but only listed web servers
 can be configured automatically by this package.
 .
 Please select the web servers that should be configured for PluXml.
 .
 Note that you will have to make sure a PHP interpreter is enabled for the
 web server.

Template: pluxml/system/reload-webserver
Type: boolean
Default: true
_Description: Should the web server(s) be reloaded?
 To activate the configuration for PluXml, the web server(s) have to be
 reloaded.
 .
 Accepting this option will reload the web server(s) when the installation is
 complete, otherwise you will have to do that yourself.

Template: pluxml/system/purgedata
Type: boolean
Default: false
_Description: Purge blog data on package removal?
 PluXml will store all blog data in /var/lib/pluxml.
 .
 Accepting this option will remove all blog data when this package is
 purged, which will leave you with a tidy system but may cause data loss if you
 purge an operational blog.

Template: pluxml/system/writeconf
Type: boolean
Default: false
_Description: Allow editing the configuration files from the web interface?
 PluXml includes a web-based configuration interface that allows the user to
 change blog settings, including the list of registered users. To be usable, it
 requires the web server to have write permission to the configuration files.
 .
 Accepting this option will give the web server write permissions to the
 configuration files. These files will still be readable and editable by hand
 regardless of whether or not you accept this option.

Template: pluxml/blog/lang
Type: select
__Choices: German, English, Spanish, French, Italian, Dutch, Polish, Portuguese, Romanian, Russian
Choices-C: de, en, es, fr, it, nl, pl, pt, ro, ru
# You must NOT translate this string, but you can change its value.
# You should put your language (if it is among the possible choices)
# so that it becomes the default for users of that language
_Default: English
_Description: Blog default language:
 Please choose the default language of this blog, which will be used for the
 public pages.
 .
 Registered blog contributors will be able to choose their language for the
 administration pages.

Template: pluxml/blog/title
Type: string
Default: PluXml
_Description: Blog title:
 Please choose a title for this blog. It will be displayed at the top of each
 page and in the browser window title.

Template: pluxml/blog/description
Type: string
# This is the default blog description (subtitle); official translations of
# this string are available at
# <https://github.com/pluxml/PluXml/tree/master/core/lang/$LANG/install.php>
# (replace $LANG by your language code), under the name "L_SITE_DESCRIPTION".
_Default: Blog or CMS, XML powered!
_Description: Blog description or subtitle:
 Please choose a short description for this blog. It will be displayed as a
 subtitle at the top of each page and in the browser window title.

Template: pluxml/blog/name
Type: string
Default: PluXml Administrator
_Description: Administrator real name:
 Please enter the real name associated with the blog administrator account.
 .
 This name will be displayed for articles written with the administrator
 account.

Template: pluxml/blog/login
Type: string
Default: admin
_Description: Administrator username:
 Please enter a name for the administrator account, which will be used to manage
 PluXml's configuration, users, and content. The username should only
 contain lowercase ASCII letters.

Template: pluxml/blog/password
Type: password
_Description: Administrator password:
 Please choose a password for the blog administrator account.

Template: pluxml/blog/confirm
Type: password
_Description: Confirm password:
 Please enter the same password again to verify that you have
 typed it correctly.

Template: pluxml/blog/failpass
Type: error
_Description: Password input error
 The two passwords you entered were not the same. Please try again.
Source: pluxml
Section: web
Priority: extra
Maintainer: Tanguy Ortolo <tanguy+debian@ortolo.eu>
Build-Depends: debhelper (>= 8.0.0), po-debconf (>= 0.8.0), slimit
Standards-Version: 3.9.4
Homepage: http://www.pluxml.org/
Vcs-Git: git://git.ortolo.org/pkg-pluxml.git
Vcs-Browser: http://git.ortolo.org/pkg-pluxml.git

Package: pluxml
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, php5
Recommends: php5-gd
Suggests: mail-transport-agent
Description: light blog/CMS engine powered by XML
 PluXml is a lightweight blogging and Content Management System that uses
 simple XML files to store its data and requires no database. It has all the
 usual features (static pages, comments, categories, tags, media managements,
 RSS feed, etc.) and supports multiple users, customizable themes, and
 plugins.

Reply to: