Code

Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#11323 closed (fixed)

Updated Korean translation

Reported by: daybreaker Owned by: anonymous
Component: Translations Version: master
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: UI/UX:

Description

Updates to Korean translation for Django 1.1 release.

Attachments (3)

django.po (113.4 KB) - added by daybreaker 5 years ago.
third draft
django-i18n-ko-r11129.patch (187.1 KB) - added by daybreaker 5 years ago.
Updated Korean translation, in Django's i18n contribution format
django-i18n-ko-r11268.patch (187.5 KB) - added by daybreaker 5 years ago.

Download all attachments as: .zip

Change History (17)

comment:1 Changed 5 years ago by daybreaker

  • Needs documentation unset
  • Needs tests unset
  • Owner changed from nobody to daybreaker
  • Patch needs improvement unset
  • Status changed from new to assigned

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.

comment:2 Changed 5 years ago by daybreaker

About 50% complete. Short comment: A lot of local flavors, and Korean local flavor should be added soon. :P

comment:3 Changed 5 years ago by Alex

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 Changed 5 years ago by daybreaker

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 Changed 5 years ago by daybreaker

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 Changed 5 years ago by daybreaker

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 Changed 5 years ago by Alex

I just meant that they live in totally seperate parts of the code base, so neither part relies on the other.

comment:8 Changed 5 years ago by daybreaker

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 Changed 5 years ago by daybreaker

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.

Changed 5 years ago by daybreaker

third draft

comment:10 Changed 5 years ago by daybreaker

Updated 3rd draft. Added missing translation for "Hindi" and fixed some other language names also according to Korean Wikipedia.

Changed 5 years ago by daybreaker

Updated Korean translation, in Django's i18n contribution format

comment:11 Changed 5 years ago by daybreaker

  • Owner changed from daybreaker to anonymous
  • Status changed from assigned to new

Changed 5 years ago by daybreaker

comment:12 Changed 5 years ago by daybreaker

  • Has patch set
  • Summary changed from Updating Korean translation to Updated Korean translation

I've updated a new version.

Another Korean reviewer suggested minor improvements in timesince.py.

comment:13 Changed 5 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [11304]) Fixed #11323 -- Updated Korean translation. Thanks to Hyun Mi Ae and Joongi Kim.

comment:14 Changed 3 years ago by jacob

  • milestone 1.1 deleted

Milestone 1.1 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.