Translation to Korean

[GoogleCodeExporter]

I have translated message.pot to message_ko.po
Please Check this.
It has not yet 100%, I'll update remaining soon.
And, this requires some code changes
in the gitinspector.py, I added

    reload(sys)
    sys.setdefaultencoding('utf-8') 

for Python 2 to treat unicode correctly.
So at the first, please review the modified code, too.

Original issue reported on code.google.com by [email protected] on 15 Dec 2014 at 5:26

Attachments:

• messages_ko.po
• gitinspector.py

[GoogleCodeExporter]

Great! It's a good start.

Concerning the code change - it shouldn't be needed and is mostly considered 
bad practice. If you need to set the encoding because of a misconfigured 
terminal or similar, using the PYTHONIOENCODING env variable should work.

However, I did find a bug (related to unicode) in the localization.get_date() 
function when testing your Korean translation. Maybe that was triggering your 
problems? It has been fixed with revision eed6d0debf43.

I added you to the project as the translator for the Korean locale.

/Adam Waldenberg

Original comment by [email protected] on 18 Dec 2014 at 3:10

• Changed state: Started
• Added labels: Milestone-Release0.4.0

[GoogleCodeExporter]

Thank you for adding me as the translator.
Your patch(revision eed6d0debf43) is working correctly. 
Without any other env. setting. it worked.
I'll delete my patch and will complete current translation upto this week.

And Question.
If I complete my translation, Should I commit with my hand?(I don't know 
permission)
Or you will add?

Original comment by [email protected] on 18 Dec 2014 at 3:32

[GoogleCodeExporter]

Good to hear that it's working.

Just add the translation to this issue and I will commit it to the repository 
under your name.

Also, gitinspector now properly supports languages with multi-column characters 
when using the terminal output. See revision 568a5e5e8b31 for the fix. I 
thought it might be a good idea now that both Chinese and Korean are part of 
the supported translations.

/Adam Waldenberg

Original comment by [email protected] on 19 Dec 2014 at 2:08

[adam-waldenberg]

Hi. A new messages.pot has been added with commit 47b11ad, so an update is needed to the translation file. Refer to the commit diff to see all changes.

Has any more work been done to this translation? If finished, it can be included in the upcoming 0.4.2 release.

[adam-waldenberg]

Pushing this to a later milestone, considering I haven't heard anything from the author for a while.

[adam-waldenberg]

If anyone is willing to take over maintaining this translation, or at the very least complete it; please drop a note here.

[moseskim]

Hi, I'd like to maintain Korean translation work from now. Which out be nice maintaining this pull request or making new pull request?

I have been leading translation work for SonarQube Korean Pack now. https://github.com/SonarQubeCommunity/sonar-l10n-ko

[adam-waldenberg]

Hi. Thank you. Welcome to the team :)

Just make a new pull requests and reference this issue from there. If I see a problem, I'll let you know of any changes needed in the new pull request. Don't forget to add your full name to the translation header.

When changes are needed to the translation I will notify you in this issue. This doesn't happen very often, but from time to time some modifications are required.

[moseskim]

@adam-waldenberg

Good. I will reference this issue on my new pull request for Korean translation :) You comment would be so much appreciated for my further work.

See you on my new pull requset.