Last modified: 2014-11-06 13:09:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43803, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41803 - Wikibase-item-summary-special-create-* messages are hard to translate
Wikibase-item-summary-special-create-* messages are hard to translate
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Wikidata bugs
u=dev c=frontend p=0 papercut
: i18n, need-volunteer, testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-06 06:11 UTC by Amir E. Aharoni
Modified: 2014-11-06 13:09 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Amir E. Aharoni 2012-11-06 06:11:56 UTC
There are three new messages:

* Wikibase-item-summary-special-create-item
* Wikibase-item-summary-special-create-property
* Wikibase-item-summary-special-create-query

The qqq documentation for all of them must be updated. Most importantly, these points must be addressed:

0. A message like "Created a [en] query" is not so great in English to begin with. I would expect "Created an [en] query".
1. Why is the language code in square brackets?
2. The number ($1) is only used in the {{PLURAL}} clause. Is it correct? This creates messages like "Created a [he] query with value" / "Created a [he] query with values". This is quite weird.
Comment 1 Lucie Kaffee 2014-11-06 12:51:29 UTC
I couldn't find the last two messages (Wikibase-item-summary-special-create-property, Wikibase-item-summary-special-create-query) and the first one is just in the same way all the other messages are. So is this still a problem or can we close this bug?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links