Last modified: 2011-03-13 18:04:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6492 - Localization of numbers should be done via {{FORMATNUM|$n}} when used with {{PLURAL}}
Localization of numbers should be done via {{FORMATNUM|$n}} when used with {{...
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Lowest normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://svn.wikimedia.org/viewvc/media...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-29 22:39 UTC by lɛʁi לערי ריינהארט
Modified: 2011-03-13 18:04 UTC (History)
1 user (show)

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


Attachments
Updates to English messages file (Messages.php) (17.75 KB, patch)
2006-06-29 23:12 UTC, Broken Arrow
Details

Description lɛʁi לערי ריינהארט 2006-06-29 22:39:09 UTC
Hallo!

Many of the messages mentioned at
bug 5805: {{plural:}} support for counters in some special pages
require also localization of numbers.

this should be done via the new magic word {{FORMATNUM|$n}}.

best regards reinhardt [[user:gangleri]]
Comment 1 Rob Church 2006-06-29 23:07:25 UTC
No. Most of the code that constructs these pages formats the numbers prior to
inserting them into the page output. This would introduce needless brace
substitution and is slower and less efficient.
Comment 2 Broken Arrow 2006-06-29 23:12:53 UTC
Created attachment 2029 [details]
Updates to English messages file (Messages.php)

At Gangleri's request:

* Wrapped in {{FORMATNUM|$n}} numeric parameters in undelete_short, viewcount,
imagelisttext, sitestatstext, nbytes, ncategories, nlinks, nmembers,
nrevisions, nviews, watchlistcount, watchdetails, subcategorycount,
categoryarticlecount.

* Moved to canonical namespace names (from {{ns:x}} syntax) newarticletext,
noarticletext, enotif_body, revertpage, exporttext, uploadtext

* Updated uploadtext for smoother rendering on RTL wikis

* Corrected capitalization in disambiguationspge for consistency with
Wiktionaries

* Exporttext will now work also at Wiktionaries

* Prefaced lines in Monobook.js with space for better presentation
Comment 3 Niklas Laxström 2006-06-30 07:31:29 UTC
(In reply to comment #1)
> No. Most of the code that constructs these pages formats the numbers prior to
> inserting them into the page output. This would introduce needless brace
> substitution and is slower and less efficient.

Most of them already have brace substitution as they use plural. If you have
better solution to make {{plural}} actually work, please go ahead. Otherwise
performance is not a sensible reason to block proper i18n support.
Comment 4 Rob Church 2006-06-30 08:05:14 UTC
Plural is a little different. We agree, I think, that pluralisation should be
handled in the message, since the alternative is one hell of a lot of mess in
the internationalisation files, and a confusing one at that.

The point is that where the parameter will always be a number, then the code
should be localising it before injecting it into the message; this is a little
cheaper, and it's the logical thing to do.

I'm not blocking proper i18n support, but I am blocking *needless* extra work.
Comment 5 Niklas Laxström 2006-06-30 08:25:03 UTC
Plural DOES NOT WORK with localized numbers. You didn't provide solution to that
yet.
Comment 6 Rob Church 2006-06-30 08:26:19 UTC
The penny drops.
Comment 7 Niklas Laxström 2007-01-01 03:17:32 UTC
{{PLURAL:}} should handle localized numbers now.

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


Navigation
Links