Translating talk:MediaWiki
- [View source↑]
- [History↑]
Contents
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
There are hundreds of identical messages of this kind. Can we please have one parameterized message, or one per project, if need be?
There was a big discussion on the topic, see phabricator:T112349. For sure, they must be marked optional.
I am working on an extended version of GRAMMAR for Colognian (ksh
) which is going to catch all of them, and I believe that would be possible with other languages as well. Amire80 is treating the same for Russian, if I am not mistaken.
See https://dpaste.de/Phsg#L801,807,808. The variable reason is assigned the error, and it is passed as a parameter in the message.
Can someone confirm that $1 actually corresponds to a working parameter? I had seen this message while proofreading as it is with "$1" shown in the button label. --Basetalkcontributions 14:50, 9 October 2015 (UTC)
There is, in the message before this one, Templatedata-modal-table-param-importoption ("Add $1 suggested parameters"). That suffices. So PLURAL support on the list length is not really needed here once more.
Needs PLURAL support on the number of item referred to.
Since 'status (s)' should not be translated, should not it be enclosed with <code> tags? See ksh translation.
What is meant with "excluding IPs" ?
Please remove the first sentence from this message. It is superfluous, euphemistic or subjective, and unnecessarily verbose.
The last sentence makes very little sense and should be clarified.
This refers to the fact that the dbname (like "commonswiki" or "svwiki") is made by the language code + project name for content projects and by subdomain + main domain for all the others.
I think your description is a lot clearer than the current message:
- "The code is either the unique identifier for specials or, for languages, the project code."
Alternatively a combo such as:
- "The code is either the language code + project code for content projects or the subdomain + main domain for all the others.
Are you sure you got this right? My understanding was that "code" refers to code field in the output. Now I'm confused. New wording says that "code" is "technically dbname/wikiid", but "dbname" is a separate field in the output, and field or parameter name "wikiid" doesn't seem to be present. Seems that now it's more like the description of "dbname" not "code". My advice is that we make it clear in the original message that "code" is an output field.
There are two different "code"s listed in the API: the first refers to the ISO 639 code of the project. The second refers to the project suffix ("wiki", "wikiquote" and so forth). It's definitely confusing (I created T100459) -- I'm not sure what this is supposed to really say, as the "language code + project code" it describes is actually the "dbname" field.
I think that for a start, to have less confusion, we could revert gerrit:212925.
Or we could improve the original sentence like this:
- "The code is either the unique identifier for specials or, for languages, the project code." →
- "The code for information about a site to return is either the unique identifier for specials or, for languages, the project code"
So it should be more clear that it's intended to describe the code in output for for "smsiteprop" parameter and not for "smlangprop" (see w:Special:ApiSandbox#action=sitematrix).
Whether API field(s) should be renamed (phab:T100459) would be a separate issue then.
What is "link" - imperative or noun?
What is a/the "score node" ?
What is a/the "override_midi attribute"?
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
- Open support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Open support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Open support requests for MediaWiki
- Open support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki
- Open support requests for MediaWiki
- Closed support requests for MediaWiki
- Closed support requests for MediaWiki