-
Notifications
You must be signed in to change notification settings - Fork 12
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 (ko-KR) translation #29
Comments
Hi can I do this?? |
Is it okay for me to just translate the English in Excel in No. 1 into Korean?? |
Hi @youjinup! Sure your translation is welcome. If Excel is your preference, then go ahead and create a PR where you update this Excel book with the strings translated into Korean. Please, take into account that line breaks and special characters should be respected (there are some & charecters that represent the underscore, in English, for the menu and button texts). If you need context, screenshots to understand the context of the strings or any kind help, please don't hesiste to let me know. |
This application is currently available in 15 languages, although some extra help is needed (#21) to translate the newly added strings.
There are a total of 198 strings that need to be translated into Korean (ko-KR).
Instructions
There are several ways to contribute the translation. However, all of them should be done via PR along with one of the following three options:
strings.ko-KR.resx
. The new file should contain all the string resources from the base strings.resx translated into Korean.Some of the string resources include string formatters and other characters (ampersands, line breaks, et cetera) that should be respected in order for the PR to be accepted.
If you use VS along with the extension ResX Manager you can translate the strings without manually editing the resx file, since the this extension automatically updates the corresponding
strings.xx-YY.resx
files.Please, don't hesitate to ask in case some strings need contextualization for their translation.
The text was updated successfully, but these errors were encountered: