If you want to help translate Typora into other languages, we would very appreciate that.
- Just fork this project, change text resources and make a pull request
- Check our issue list to see if there are already someone else translating the text recourse to your language. If not, open an issue to tell others that you doing the translation, in order to avoid duplicate work.
- Fork this repo.
- Create a folder named
{locale}.lproj
,local
code should be picked from locale-identifiers.csv. - Copy
*.strings
files fromBase.lproj
to{locale}.lproj
. - Open
*.strings
with any text/code editor, do the translation. Please also check the translation rules. - Make a pull request to us.
- We could also appreciate if you leave any contact method, like email, in issues or in
*.strings
file after your translation, so we can reach you and, at least, give free license as rewards after we come out of beta. You could also email us directly if you do not want your email address go public in Github.
- Translations in
Menu.strings
should follow https://github.com/martnst/localize-mainmenu. - If translation in https://github.com/martnst/localize-mainmenu is not proper on Windows/Linux, add the proper one in
Menu-electron.strings
. (see zh-Hans.lproj as one example).- To search the translation of terms for Windows machines you can use Microsoft's Terminology Search at https://www.microsoft.com/en-us/language. Other useful resources can be found at the Microsoft Language Toolbox at https://www.microsoft.com/en-us/language/Toolbox.
- Comment style
/* some words */
is supported,// comment
is NOT supported.
Can I test my translations?
Sorry… We do not support that. If you are not sure about the context of the some original English text resource or have doubts about your translation, please feel free to contact us.
Feel free to contact us via [email protected]
- Menu items on macOS → https://github.com/martnst/localize-mainmenu
- Terminology for Windows → https://www.microsoft.com/en-us/language/