#732 closed enhancement (fixed)
slightly update de-translation
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Translations | Version: | |
| Severity: | minor | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
A slightly modified de-translation:
changed all occurences of "Passwort" to "Kennwort" (we should decide which of one to use, and then use it throughout django :) and fixed a few typos.
Should we really open a new Ticket for each and every translation update?
Attachments (1)
Change History (7)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Just thinking about it, maybe Jacob could add "Translations" as a component to trac, so that translation tickets can be easily filtered on.
comment:4 by , 19 years ago
| Component: | Admin interface → Translations |
|---|
comment:5 by , 19 years ago
And I added a report that only lists active tickets for translations. Now you guys could just decide wether you would like to give some people commit rights to /django/conf/locale/ in the repository and you wouldn't have to care about translation updates any more ;-)
by , 19 years ago
Revised some strings, streamlined a bit so that it matches (I think) common translations in other programs ("Hinzufügen" instead of "Zufügen" f.e.)
comment:6 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Yeah, I am all for consistency, I am just not the right one to do it, as I am not that consistent myself ;-)
wrt. ticket: at the moment I would say it's the only way. And it's the best way to make sure that no updates are lost. Especially since we now have two targets for translation updates - trunk and new_admin (I will add all new translation targets in new_admin because it wouldn't be of much use to now update trunk just to do the same work again when new_admin hits trunk).