Opened 16 years ago

Closed 16 years ago

Last modified 13 years ago

#10778 closed (fixed)

Updated Russian translation

Reported by: dc Owned by: nobody
Component: Translations Version: dev
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Updated Russian translation for the trunk.

Attachments (2)

ru-trunk.patch (112.9 KB ) - added by dc 16 years ago.
Patch
django.po (125.6 KB ) - added by dc 16 years ago.
Full file

Download all attachments as: .zip

Change History (7)

by dc, 16 years ago

Attachment: ru-trunk.patch added

Patch

by dc, 16 years ago

Attachment: django.po added

Full file

comment:1 by Alex Gaynor, 16 years ago

milestone: 1.21.1
Triage Stage: UnreviewedAccepted

No need to post the full file, I assume this is different from the translation update that went in last night.

comment:2 by dc, 16 years ago

I assume this is different from the translation update that went in last night

Yes. This version adds translation for the recent commits (e.g. admin actions).

comment:3 by Malcolm Tredinnick, 16 years ago

Resolution: fixed
Status: newclosed

(In [10507]) Fixed #10778 -- Updated Russian translation from Andrew Fedorov.

comment:4 by Malcolm Tredinnick, 16 years ago

Probably worth waiting until string freeze at the release candidate for the next update. There's going to be a few little string changes between now and then.

Also, after running makemessages each time, you have to fix the Plural header line to put it back on one line. It keeps getting chopped in half and that will break things (I've fixed it the last couple of times because I've noticed, but one day I'm going to forget). Eventually we'll add an option to "makemessages" to allow unbroken lines, but that will have drawbacks in other ways (no lines will break), so just remember to check it manually for now.

comment:5 by Jacob, 13 years ago

milestone: 1.1

Milestone 1.1 deleted

Note: See TracTickets for help on using tickets.
Back to Top