Gitea: Korean localization resource looks broken for v1.11

Created on 14 Jan 2020  路  19Comments  路  Source: go-gitea/gitea

  • Gitea version (or commit ref): v1.11
  • Git version: 1.8.3.1
  • Operating system: CentOS 7
  • Database (use [x]):

    • [ ] PostgreSQL

    • [ ] MySQL

    • [ ] MSSQL

    • [x] SQLite

  • Can you reproduce the bug at https://try.gitea.io:

    • [x] Yes (provide example URL)

    • [ ] No

    • [ ] Not relevant

  • Log gist:

Description

Korean resource looks broken. I guess localization files for Korean defiled.
...

Screenshots

image

image

kintranslation

All 19 comments

Hi, can you have a look at crowdin where the translation are managed.
If the translation are good please come back and indicate it since it may be related to font.

For more details on translations: https://github.com/go-gitea/gitea/blob/master/CONTRIBUTING.md#translation

Thank you @sapk . I signed in crowdin to find misinterpreted string but few strings were shown. It is hard to find original English term before translation. It would be helpful if there is revision history for Korean translation.

Crowdin should make propositions based on previous values and translations on others projects.
If you see string with %s it means that this part will be replaced by a word and should be kept (but can be moved if needed).
If it can help you, the result of translation is stored in this file https://github.com/go-gitea/gitea/blame/master/options/locale/locale_ko-KR.ini and you can access the history of the file https://github.com/go-gitea/gitea/commits/master/options/locale/locale_ko-KR.ini
You should also be able to copy and edit this file under custom/options/locale/locale_ko-KR.ini of your setup (need a reboot for changes to apply) if you want to see the change in-situ. But all translation should be submitted via crowdin.

I can't really help you more on the process as I don't even see the letters with my setup and don't know korean ...

Thank @sapk for your great explanations about Crowdin and language resources. I found more than 40 strings on Crowdin which have no meaning in Korean and voted them as abuses.
image

Also, I translated them to Korean with right meaning.
image

I want to review my suggestions and apply to Gitea as soon as possible.

Translation should have landed on master by now. We should maybe backport thoses change to v1.11 branch.

Is migration on the way now? Still bad translations are on master.
image

They are updated each time a PR is validated. If they are not here they should come soon.
If it isn't here in few hours please indicate missing key like sign_in_with, we may have missed them on crowdin.

I understand it takes time but translation like user_profile_and_more is not yet approved in Crowdin. I am afraid that next release would be shipped without correct translation.

Should be good at next PR now

We'll need another backport of translations before 1.11rc2 I guess.

created just a nother locales backport: #9780 :sweat_smile:

My suggestions almost have been updated on master except ssh_port. Would you approve it?

backport is already merged :/
I think for release candidate 2 we wont backport ...

@jeremy3825 but if you translate more stings ... it will be worth backporting for final release ...

@6543 I know just a string is too much for backport. I hope that ssh_port would be approved quickly and see it fixed on next version. Thanks a lot.

Correct translation for ssh_port remains unapproved on Clowdin. I'd rather close this issue with merging the last one.

Done

@sapk I appreciate your great help for Korean users. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

thehowl picture thehowl  路  3Comments

flozz picture flozz  路  3Comments

jorise7 picture jorise7  路  3Comments

ghost picture ghost  路  3Comments

thehowl picture thehowl  路  3Comments