Sceneri title changes

[taggart]

Here is a collection of scenari related stuff, mostly title.gettext changes to make things more consistent. There are a couple changes that could be considered related to #362 where an authenticated version of a type didn't exist. In those cases the patch adds one, but maybe it would be better to add the authentication to the existing non-auth version?

Feel free to just cherry pick whatever makes sense and also let me know if you'd prefer that I break things up into multiple PRs.

[ikedas]

@taggart, I feel we would be better to divide works: Adding auth versions (suggested by #362), and correcting titles (currently proposed here).

One idea: Instead of submitting single PR, how about opening another issue page to discuss about titles?

[qosobrin]

Why don't you have #179 into account? In my institution we ended by renaming scenari files with numeral prefixes. For example, the add menu now shows these scenarios in this order:

add.auth            restricted to owner with authentication
add.authdkim        restricted to owner without authentication if DKIM signature is OK.
add.closed          add impossible
add.owner           add performed by list owner does not need authentication
add.owner_notify    add performed by owner does not need authentication (notification)
add.ownerdkim       add performed by list owner does not need authentication if DKIM signature OK

But if you rename the scenari files from public to restricted you will get something like:

add.1-owner         add performed by list owner does not need authentication
add.2-owner_notify  add performed by owner does not need authentication (notification)
add.3-ownerdkim     add performed by list owner does not need authentication if DKIM signature OK
add.4-authdkim      restricted to owner without authentication if DKIM signature is OK.
add.5-auth          restricted to owner with authentication
add.6-closed        add impossible

This makes life easier for users to select the correct scenario since now they know the scenarios proposed in the drop-down menus have a logical order. And furthermore, an exercise like this will allow you to identify scenarios that are useless or are equal (for example, add.authdkim is basically the same as add.ownerdkim and one of them could be removed).

Best regards,

[ikedas]

@qosobrin , I think @taggart does not propose about ordering of the scenarios.