Page MenuHomePhabricator

Evolving system message "Adminlinks documentation"
Closed, ResolvedPublic

Description

I am adding this bug as a service for the tw.n community. A suggestion to change the system message "Adminlinks documentation" was done [1]:

"Here we need GRAMMAR on $1. Since the message is only used twice - as far as I can see - once Semantic Mediawiki and once for Semantic Form - how about having 2 individual messages, possibly one optional falling back to the other?"

[1] http://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Adminlinks_documentation/ksh


Version: unspecified
Severity: normal

Details

Reference
bz51286

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:52 AM
bzimport set Reference to bz51286.

Sorry, I don't understand - what's wrong with the current setup ("$1 documentation")?

Things can get complicated with languages [1]. However, the documentation does not appear very explicit, so I am not sure about this one either. Probably something like [2] will have to be done. I am sure that adding the I18n tag will trigger some comments from the I18n-team. I guess they have seen it all when it comes to languages ... which is good, by the way.

[1] http://www.mediawiki.org/wiki/GRAMMAR#.E2.80.A6on_use_context_inside_sentences_via_GRAMMAR
[2] 'adminlinks documentation' => '{{GRAMMAR:elative|$1}} documentation',

Kghbln lowered the priority of this task from Medium to Lowest.Apr 2 2015, 3:12 PM
Kghbln unsubscribed.
Kghbln subscribed.

"Here we need GRAMMAR on $1

This may still need to be revisited. However changing this to a more realistic priority.

@Nikerabbit Isn't {{GRAMMAR}} something that can be added to the system message by the translators without the need of adding it to the source message, i.e. the English one (e.g. aboutsite)?

If it is documented. We recommend translators to not add it on their own because there are many messages where grammar just wont work (plain output, raw parameters, etc.).

Also {{GRAMMAR}} is used almost solely for wiki names. There are no guarantees that it works for uncontrolled input in most of the languages.

Kghbln claimed this task.

Thank you for your insight into this. Since the parameter holds just a "name" and the message is text one could actually use GRAMMAR here. Finally this task can now be closed after nearly three years since I have now extended and updated the respective message documentation.