Last modified: 2011-04-14 15:12:39 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 T21893, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19893 - GRAMMAR should build on wiki family names, not SITENAMEs
GRAMMAR should build on wiki family names, not SITENAMEs
Status: NEW
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
1.16.x
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-23 11:47 UTC by Purodha Blissenbach
Modified: 2011-04-14 15:12 UTC (History)
3 users (show)

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


Attachments

Description Purodha Blissenbach 2009-07-23 11:47:38 UTC
In http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/WikimediaMessages/WikimediaGrammarForms.php?view=markup ,
we see an array of grammar forms of wiki names of the WMF.
Almost all of them use the local sitename as an index, thus
{{GRAMMAR:form indicator|{{SITENAME}}}} works in two cases:
- the userlanguage and the wiki language are the same,
- the sitename of the wikilanguage coincides with that of
the user language.

In all other cases, you get the value of {{SITENAME}} instead
of correct grammar forms. I.e. potentially wrong, or unreadble texts.

There are minor exceptions - for the Check language, for
instance, there are the canonical English names of the wikis,
too, being used as indexes to the $wgGrammarForms array, thus
English wikis, and those having identically spelt local names,
get correct grammar forms in Check, with their wiki names
properly translated to Check.

Why do we not use this way all the time? 

If we were using (canonical) wiki family names to address
grammar forms, we would get correct grammar in the user
language in all instances, and we were using the correct
user language spelling (or a translated / transliterated form)
of the wiki name, which is most likely what users want, who
select a specific interface language.

Even non-WMF wikis, when they form families of several
languages, are likely to profit from this approach.

Caveat: few languages use programmed code for GRAMMAR which needs to be integrated with this kind of change.
Comment 1 Niklas Laxström 2009-07-28 14:21:01 UTC
Interesting idea, but I don't see many uses outside of Wikimedia. Would need {{SITEFAMILYNAME}}, which defaults to {{SITENAME}} and change all messages to use it instead... sound complicated. Or some hacky maps to convert local {{SITENAME}} to family name in convert grammar function.

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


Navigation
Links