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

Re: [RFR] templates://kstars-data-extra-tycho2/{templates}



Sorry, no patch yet - I'm running late for once and haven't been
keeping up with revisions.

Noel David Torres Taño wrote:
>>  Template: kstars-data-extra/kstarsrc-title
>>  Type: title
>> -_Description: kstars global config file
>> +_Description: Handling of kstars configuration file
>> 
>> I have to mention that I'm not entirely fond of the overuse of
>> db_title. I think that the default title ("Configuration of <foo>")
>> fits its needs.
>> 
>> Anyway, I'w rewording to avoid the leading lowercase.
>> 
> I think the word 'global' here is important for two reasons:
> a) the file will affect the behaviour of the kstars program, and it is the 
> same file I will use in other kstars-data-extra-* packages
> b) the file is the system-wide configuration of kstars, there are other 
> configurations per-user

So
 _Description: Handling of kstars global configuration file

> [...]
(Reinstating a bit that needs fixing:)

>>  Template: kstars-data-extra/kstarsrc-exists
>>  __Choices: backup and create new, delete and create new, keep actual file
>> Default: keep

Hang on; for a start "actual" is a false friend (you mean "current")
and one-word "backup" isn't a verb.  And I don't follow how this
Default will work given that "keep" isn't one of the options.  Could
this perhaps become:

   __Choices: keep, replace (preserving backup), overwrite
  Default: keep

>> +_Description: Action for the /etc/kde4/kstarsrc file:
>>   A kstars global config file has been detected as /etc/kde4/kstarsrc .

No need to say that you've detected it (and no need to keep specifying
the path):

    A kstars global configuration file already exists.

>>   .
>> + The package installation process can't modify it, but you can
>> + backup it up now and create a new one. You will be prompted for
>> + options in this file.

If I could find a way of drawing less attention to the mechanics of
"the package installation process" I would, but nothing occurs to me.
Except that it's "you can back it up".

>>  Template: kstars-data-extra/kstarsrc-does-not-exist
>>  Type: boolean
>>  Default: true
>>  _Description: Create /etc/kde4/kstarsrc file?
>> + There is no kstars global config file.
                                    ^uration
>>   .
>> + In order to optionnally disable the user download feature, one
>> + is needed. If you choose to create one, you will be prompted for
>> + options in this file.

"Optionally", but I don't much like the phrasing anyway... how about:

    A configuration file will be needed if user downloads should be
    disabled, but if not then it is still safe to create one. You will
    be prompted for options in this file.

>>  Template: kstars-data-extra/disable-downloads

Oops, hang on, I'm taking too long (busy for once!) - this version's
been obsoleted by:
| Template: kstars-data-extra/disable-downloads
| Type: select
| __Choices: keep enabled, disable, lock
| Default: lock

Given that there's no guarantee that its previous state is "enabled",
I think this should be:

  __Choices: enable, disable, lock

| _Description: Choice for downloads of new data by kstars users:

Could we make that something like

  _Description: User data downloads for kstars:

| By default, unless the feature is locked or disabled, each user will be able
| to enable data downloads.
| .
| If you choose "keep enabled", users will be able to download data
| files. If you choose "disable", each user can re-enable data download
| (for instance to download data from other catalogs than Tycho2). If
| you choose "lock", no user can enable data downloads.

Well, the "by default" part is true if there's no config, but the
default *here* is "lock".  Perhaps start from describing it as a
feature of KStars:

   KStars has a download feature allowing users to download extra data
   files for their own use. Since packaged catalogs can be handled more
   efficiently by installing a single central copy, you may wish to
   restrict the use of this feature.
   .
    * enable - users will be able to download data files;
    * disable - individual users can re-enable data downloads (for
      instance to download data from other catalogs);
    * lock - users cannot enable data downloads.

(Oh, handily I've anticipated the s/Tycho2//.)

>>  Template: kstars-data-extra/kstarsrc-saved-title
>>  Type: title
>> -_Description: old kstarsrc saved
>> +_Description: Backup of old kstarsrc file
       
Well, "item modified" isn't strictly a sentence, and it makes a
shorter and snappier title... but if the rule is "it must be a noun
phrase" then this does make sense.

Then the package description:

 -Description: Tycho2 star catalogue for centralized install of KStars

It isn't a "centralized install of KStars"; in fact I can't find an
accurate explanation that fits in the synopsis, so save it for the
long description.  Oh, and google tells me "Tycho-2" with a hyphen.

 +Description: Tycho-2 star catalog for KStars

 - This package contains the data of the Tycho 2 star catalogue for KStars, the
 - graphical desktop planetarium for KDE. Without this package, KStars would offer
 - each user to download it. Installing this package avoids the need for each user
 - to individually download the whole catalog. It is configurable if you want the
 - users to be unable to do those downloads.

en_US "catalog" (to match "centralized").

Saying that a desktop planetarium for KDE is graphical seems redundant.

The "download it" is inaccurate, since KStars wouldn't offer to
download this .deb file.

If this package can configure whether I want something, I don't want
it anywhere near me.

How about:

 + This package contains the data of the Tycho-2 star catalog for KStars, the
 + desktop planetarium for KDE. It allows users to use a central shared catalog
 + instead of each needing to download their own personal copy of the whole
 + catalog. It can also configure KStars to disable these user downloads.

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: