Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Korean localization resource looks broken for v1.11 #9761

Closed
2 of 7 tasks
iamseunghyun opened this issue Jan 14, 2020 · 19 comments
Closed
2 of 7 tasks

Korean localization resource looks broken for v1.11 #9761

iamseunghyun opened this issue Jan 14, 2020 · 19 comments

Comments

@iamseunghyun
Copy link

iamseunghyun commented Jan 14, 2020

  • Gitea version (or commit ref): v1.11
  • Git version: 1.8.3.1
  • Operating system: CentOS 7
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

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

Screenshots

image

image

@sapk
Copy link
Member

sapk commented Jan 14, 2020

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

@sapk sapk added the issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself label Jan 14, 2020
@sapk sapk added this to the 1.11.0 milestone Jan 14, 2020
@sapk sapk added topic/ui Change the appearance of the Gitea UI issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Jan 14, 2020
@iamseunghyun
Copy link
Author

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.

@iamseunghyun iamseunghyun changed the title Some Korean localization resources looks broken for v1.11 Some Korean localization resource looks broken for v1.11 Jan 15, 2020
@iamseunghyun iamseunghyun changed the title Some Korean localization resource looks broken for v1.11 Korean localization resource looks broken for v1.11 Jan 15, 2020
@sapk
Copy link
Member

sapk commented Jan 15, 2020

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 ...

@sapk sapk removed the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Jan 15, 2020
@iamseunghyun
Copy link
Author

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.

@sapk
Copy link
Member

sapk commented Jan 15, 2020

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

@iamseunghyun
Copy link
Author

iamseunghyun commented Jan 15, 2020

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

@sapk
Copy link
Member

sapk commented Jan 15, 2020

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.

@iamseunghyun
Copy link
Author

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.

@sapk
Copy link
Member

sapk commented Jan 15, 2020

Should be good at next PR now

@sapk
Copy link
Member

sapk commented Jan 15, 2020

@zeripath
Copy link
Contributor

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

6543 added a commit to 6543-forks/gitea that referenced this issue Jan 15, 2020
@6543
Copy link
Member

6543 commented Jan 15, 2020

created just a nother locales backport: #9780 😅

@sapk sapk added modifies/translation and removed issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself topic/ui Change the appearance of the Gitea UI labels Jan 15, 2020
techknowlogick pushed a commit that referenced this issue Jan 15, 2020
* backport korean 20-20-01-15 | fix #9761

* update state 14:43:10 UTC
@iamseunghyun
Copy link
Author

iamseunghyun commented Jan 16, 2020

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

@6543
Copy link
Member

6543 commented Jan 16, 2020

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 ...

@iamseunghyun
Copy link
Author

iamseunghyun commented Jan 16, 2020

@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.

@iamseunghyun
Copy link
Author

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

@iamseunghyun
Copy link
Author

Need approval : https://crowdin.com/translate/gitea/68/enus-ko#q=ssh_port

@sapk
Copy link
Member

sapk commented Jan 21, 2020

Done

@iamseunghyun
Copy link
Author

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

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants