Last modified: 2007-05-23 06:49:52 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 T12008, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10008 - Russian translation update
Russian translation update
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
1.11.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-22 18:53 UTC by Alexander Sigachov
Modified: 2007-05-23 06:49 UTC (History)
0 users

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


Attachments
checked by checkLanguage.php (24.98 KB, patch)
2007-05-22 18:53 UTC, Alexander Sigachov
Details

Description Alexander Sigachov 2007-05-22 18:53:29 UTC
Created attachment 3666 [details]
checked by checkLanguage.php

Next Russian translation update
Comment 1 Raimond Spekking 2007-05-22 21:52:41 UTC
Thanks for the patch, I have applied it with r22359.

For your information:

5 messages of 1645 in ru don't use some variables while en uses them:
* cascadeprotected
* cascadeprotectedwarning
* revdelete-selected
* logdelete-selected
* protect-cascadeon
Comment 2 Alexander Sigachov 2007-05-23 06:49:52 UTC
Thank you, but Russian plural form for words is not simple, so I can not use PLURAL in messages without numbers. Example:

"The page was visited $1 {{PLURAL:$1|time|times}}"
is OK

but

"The page was visited {{PLURAL:$1|one time|many times}}."
is untranslateable with current Russian plural function with 3 plural forms, so I did not use variables.

I think to change Russian plural function to 4 plural forms, but it is not common in  Russian software localization.


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


Navigation
Links