#11323 closed (fixed)
Updated Korean translation
| Reported by: | daybreaker | Owned by: | anonymous |
|---|---|---|---|
| Component: | Translations | Version: | dev |
| Severity: | Keywords: | i18n translation korean | |
| Cc: | me@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Updates to Korean translation for Django 1.1 release.
Attachments (3)
Change History (17)
comment:1 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
About 50% complete. Short comment: A lot of local flavors, and Korean local flavor should be added soon. :P
comment:3 by , 16 years ago
Please don't do a Korean local flavor as a part of this translation patch, they should be separate because, if nothing else a translation is in scope for 1.1 but a local flavor isn't. Plus they're 2 totally separate things.
comment:4 by , 16 years ago
Ok, then I will separate them and only post the other parts of translations, and keep those for later uses. (Maybe part of 1.2?)
comment:5 by , 16 years ago
And the Korean local flavor module should be implemented with a different ticket, of course. I meant, I will separate Korean translations for currently existing local flavors from translations for other functional parts and post only the later.
comment:6 by , 16 years ago
To clarify more (sorry for interrupting the timeline), currently I won't implement the Korean local flavor module, but translate only. Which did you mean between that implementation of Korean local flavor module and Korean translation should be separated or that Korean translations for local flavors and functional parts should be separated?
comment:7 by , 16 years ago
I just meant that they live in totally seperate parts of the code base, so neither part relies on the other.
comment:8 by , 16 years ago
Um... so I'm asking your meaning of "they". I first thought they meant translations for functional parts and translation for local flavor, but after a while, I began to think that they meant translations and Korean local flavor module. Was the later your intention?
comment:9 by , 16 years ago
I've finished the first draft translation. A check is needed by other Korean translators if any.
I could not find any transcription method for Slovakian geographical names, so just let it same. (I think very very few Korean people would notice that.) Others are from Wikipedia and local encyclopedia sources.
comment:10 by , 16 years ago
Updated 3rd draft. Added missing translation for "Hindi" and fixed some other language names also according to Korean Wikipedia.
by , 15 years ago
| Attachment: | django-i18n-ko-r11129.patch added |
|---|
Updated Korean translation, in Django's i18n contribution format
comment:11 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
by , 15 years ago
| Attachment: | django-i18n-ko-r11268.patch added |
|---|
comment:12 by , 15 years ago
| Has patch: | set |
|---|---|
| Summary: | Updating Korean translation → Updated Korean translation |
I've updated a new version.
Another Korean reviewer suggested minor improvements in timesince.py.
comment:13 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I'm going to work on this ticket. Any support or help is appreciated, and please notify me if someone is already working on this.