#8495 closed (fixed)
Updated Hebrew translations
| Reported by: | Meir Kriheli | Owned by: | nobody |
|---|---|---|---|
| Component: | Translations | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Attached updated Hebrew translations (for django domain, djangojs is up to date).
Attachments (3)
Change History (8)
by , 16 years ago
by , 16 years ago
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 16 years ago
I wish there was some policy regarding translations. When I've posted the diff to po files in the past, the complete file was requested (po are different in a way, since only native speakers can read them and diffs don't mean much).
Attached the diff.
by , 16 years ago
| Attachment: | django_heb_po.diff added |
|---|
comment:3 by , 16 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
I understand, I'm a speaker so it's helpful for me so I don't have to see the entire file, just the changes.
That said I've gone through about 1/5 of this and it looks fine, so I'm going to promote to RFC, if another speaker has an issue feel free to push it back to accepted.
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Can you just upload the .po in the form of a diff(that way we can still apply this in the event other changes are made to the file, and it makes it easier for others to review).