Translations #783

Open
opened 2025-10-09 19:01:25 +03:00 by OVERLORD · 25 comments
Owner

Originally created by @pkrolkgp on GitHub.

It would be nice if we can help and translate planka to different languages.

Originally created by @pkrolkgp on GitHub. It would be nice if we can help and translate planka to different languages.
Author
Owner

@pkrolkgp commented on GitHub:

Thanks for creating image, but how i can change the language?

@pkrolkgp commented on GitHub: Thanks for creating image, but how i can change the language?
Author
Owner

@meltyshev commented on GitHub:

Ah, sorry. Currently, we haven't implemented a language change in the user settings. But you can open DevTools (F12) -> Application -> expand Local Storage menu and choose your domain, then you need to change the i18nextLng value.

@meltyshev commented on GitHub: Ah, sorry. Currently, we haven't implemented a language change in the user settings. But you can open DevTools (F12) -> Application -> expand Local Storage menu and choose your domain, then you need to change the `i18nextLng` value.
Author
Owner

@meltyshev commented on GitHub:

Yes, it would be more convenient. I will try to do it after releasing the first version. Thanks!

@meltyshev commented on GitHub: Yes, it would be more convenient. I will try to do it after releasing the first version. Thanks!
Author
Owner

@meltyshev commented on GitHub:

Hi! Sorry that we don't have some documentation about that, still focused on releasing a new version. I'll leave simple documentation here and pin this issue.

Translation files located in the client/src/locales folder.

  1. Make a copy of the en folder as de folder (for example for the German language)
  2. Change translations inside the copied folder
  3. Make a pull request

Or you can send translations here. I'll add them.

@meltyshev commented on GitHub: Hi! Sorry that we don't have some documentation about that, still focused on releasing a new version. I'll leave simple documentation here and pin this issue. Translation files located in the `client/src/locales` folder. 1. Make a copy of the `en` folder as `de` folder (for example for the German language) 2. Change translations inside the copied folder 2. Make a pull request Or you can send translations here. I'll add them.
Author
Owner

@pkrolkgp commented on GitHub:

Maybe for the future translations you can use some service like Weblate

@pkrolkgp commented on GitHub: Maybe for the future translations you can use some service like [Weblate](https://weblate.org)
Author
Owner

@michal-volf commented on GitHub:

Czech language, much appreciate
czech_language.zip

@michal-volf commented on GitHub: Czech language, much appreciate [czech_language.zip](https://github.com/plankanban/planka/files/6207743/czech_language.zip)
Author
Owner

@zicka commented on GitHub:

hello,
im using docker and im asking is it possible to translate files iside docker image?

BR Rok

@zicka commented on GitHub: hello, im using docker and im asking is it possible to translate files iside docker image? BR Rok
Author
Owner

@meltyshev commented on GitHub:

@michal-volf, thanks for the translations! Docker image with new language will be available in 1 hour.

@meltyshev commented on GitHub: @michal-volf, thanks for the translations! Docker image with new language will be available in 1 hour.
Author
Owner

@almereyda commented on GitHub:

If you wanted, there is an independent Weblate instance at https://weblate.allmende.io/ you could use for your FLOSS.

@almereyda commented on GitHub: If you wanted, there is an independent Weblate instance at https://weblate.allmende.io/ you could use for your FLOSS.
Author
Owner

@wucherpfennig commented on GitHub:

how do I simply change locale in a Docker installation?

@wucherpfennig commented on GitHub: how do I simply change locale in a Docker installation?
Author
Owner

@WofWca commented on GitHub:

There is a similar project, with a lot of similar strings, and the same license:
https://kolaente.dev/vikunja/frontend/src/branch/main/src/i18n/lang/en.json
Maybe it makes sense to unite the efforts somehow, cross-use the strings.

@WofWca commented on GitHub: There is a similar project, with a lot of similar strings, and the same license: https://kolaente.dev/vikunja/frontend/src/branch/main/src/i18n/lang/en.json Maybe it makes sense to unite the efforts somehow, cross-use the strings.
Author
Owner

@leonardobarrosdev commented on GitHub:

I got translate to PT-BR, but in the moment I'm receive a problem how this:

error: Malformed hook! (session)
[server] error: Hooks should be a function with one argument (sails)
[server] error: But instead, got: true
[server] [nodemon] app crashed - waiting for file changes before starting...

Someone help me? If that be complex, call me on Discord, please: LB#3121

@leonardobarrosdev commented on GitHub: I got translate to PT-BR, but in the moment I'm receive a problem how this: error: Malformed hook! (session) [server] error: Hooks should be a function with one argument (`sails`) [server] error: But instead, got: true [server] [nodemon] app crashed - waiting for file changes before starting... Someone help me? If that be complex, call me on Discord, please: LB#3121
Author
Owner

@xtay573269555 commented on GitHub:

I find a translation mistake in the app, but it is not related with the language package. Whatever, i post it here, maybe you can help to correct it.

The file is /app/public/static/js/683.e8a7c172.chunk.js in the docker container. The strings need to change from \u5b9e\u8df5 to \u65f6\u95f4.

@xtay573269555 commented on GitHub: I find a translation mistake in the app, but it is not related with the language package. Whatever, i post it here, maybe you can help to correct it. The file is `/app/public/static/js/683.e8a7c172.chunk.js` in the docker container. The strings need to change from `\u5b9e\u8df5` to `\u65f6\u95f4`.
Author
Owner

@pkrolkgp commented on GitHub:

I just got into https://crowdin.com/ and i think it's something you should consider instead translating by hand.

@pkrolkgp commented on GitHub: I just got into https://crowdin.com/ and i think it's something you should consider instead translating by hand.
Author
Owner

@chooya commented on GitHub:

hello,
I send the korean language file, please add it.

korean_language.zip

@chooya commented on GitHub: hello, I send the korean language file, please add it. [korean_language.zip](https://github.com/plankanban/planka/files/9247017/korean_language.zip)
Author
Owner

@KBCACheia commented on GitHub:

I got translate to PT-BR, but in the moment I'm receive a problem how this:

error: Malformed hook! (session) [server] error: Hooks should be a function with one argument (sails) [server] error: But instead, got: true [server] [nodemon] app crashed - waiting for file changes before starting...

Someone help me? If that be complex, call me on Discord, please: LB#3121

HI, have you finish it? Want any help?

@KBCACheia commented on GitHub: > I got translate to PT-BR, but in the moment I'm receive a problem how this: > > error: Malformed hook! (session) [server] error: Hooks should be a function with one argument (`sails`) [server] error: But instead, got: true [server] [nodemon] app crashed - waiting for file changes before starting... > > Someone help me? If that be complex, call me on Discord, please: LB#3121 HI, have you finish it? Want any help?
Author
Owner

@Istria1704 commented on GitHub:

@WofWca ,
So, I fork the repo. Then create a new branch called 'Translation Dutch'. I commit all the changes to that new branch. And when I'm done, I make a pull request. Correct?

@Istria1704 commented on GitHub: @WofWca , So, I fork the repo. Then create a new branch called 'Translation Dutch'. I commit all the changes to that new branch. And when I'm done, I make a pull request. Correct?
Author
Owner

@WofWca commented on GitHub:

@Istria1704 You commit changes to a different branch in your fork, you probably don't have write access in this repo.

@WofWca commented on GitHub: @Istria1704 You commit changes to a different branch in your fork, you probably don't have write access in this repo.
Author
Owner

@WofWca commented on GitHub:

@Istria1704 yes
Although you can't have spaces in a branch name

@WofWca commented on GitHub: @Istria1704 yes Although you can't have spaces in a branch name
Author
Owner

@Istria1704 commented on GitHub:

I just started a Dutch translation. Will be done soon (tomorrow probably).

But it's been a couple years since I used github and made a pull request. Should I make a new branch and commit the changes there? Or should I commit the changes to the master branch when I'm done translating and double-checking?

I know I could just place the .zip here. But I'd like to take this opportunity to refresh my github skills.

Thanks!

@Istria1704 commented on GitHub: I just started a Dutch translation. Will be done soon (tomorrow probably). But it's been a couple years since I used github and made a pull request. Should I make a new branch and commit the changes there? Or should I commit the changes to the master branch when I'm done translating and double-checking? I know I could just place the .zip here. But I'd like to take this opportunity to refresh my github skills. Thanks!
Author
Owner

@meltyshev commented on GitHub:

Hello Team, I have forked the main Planka project & translated into Bulgarian. Shall I open a PR or attach it as zip package here? Thank you.

Hi and thanks for translating! PR will be easier to accept and you'll also be listed as a contributor :)

@meltyshev commented on GitHub: > Hello Team, I have forked the main Planka project & translated into Bulgarian. Shall I open a PR or attach it as zip package here? Thank you. Hi and thanks for translating! PR will be easier to accept and you'll also be listed as a contributor :)
Author
Owner

@nimdassdev commented on GitHub:

Hello Team,
I have forked the main Planka project & translated into Bulgarian. Shall I open a PR or attach it as zip package here? Thank you.

@nimdassdev commented on GitHub: Hello Team, I have forked the main Planka project & translated into Bulgarian. Shall I open a PR or attach it as zip package here? Thank you.
Author
Owner

@meltyshev commented on GitHub:

Hello , first thanks for this lovely project that you provide, i have a question, i installed the project on my debian server through this document docs.planka.cloud/docs/installation/manual_installation/debian_ubuntu in directory of the project i dont have access to languges , for example fa-ir file is not in directory of my files, i can't change or custom the farsi languge and it's funny cause i don't know how it translate the site to Farsi when i dont't have the farsi file :D

Hi! This installation uses the prebuilt version of the frontend, meaning all translations are already included in the built files. To change or add a language, you need to clone the entire repository, add the new language to client/src/locales (or modify an existing one), and then build the frontend using npm run client:build. Afterward, instead of the step "Download the prebuilt version of Planka" (in the docs), use the resulting files from the client/build folder.

@meltyshev commented on GitHub: > Hello , first thanks for this lovely project that you provide, i have a question, i installed the project on my debian server through this document [docs.planka.cloud/docs/installation/manual_installation/debian_ubuntu](https://docs.planka.cloud/docs/installation/manual_installation/debian_ubuntu/) in directory of the project i dont have access to languges , for example fa-ir file is not in directory of my files, i can't change or custom the farsi languge and it's funny cause i don't know how it translate the site to Farsi when i dont't have the farsi file :D Hi! This installation uses the prebuilt version of the frontend, meaning all translations are already included in the built files. To change or add a language, you need to clone the entire repository, add the new language to `client/src/locales` (or modify an existing one), and then build the frontend using `npm run client:build`. Afterward, instead of the step "Download the prebuilt version of Planka" (in the docs), use the resulting files from the `client/build` folder.
Author
Owner

@tohidshabanloo commented on GitHub:

Hello , first thanks for this lovely project that you provide, i have a question, i installed the project on my debian server through this document
https://docs.planka.cloud/docs/installation/manual_installation/debian_ubuntu/
in directory of the project i dont have access to languges , for example fa-ir file is not in directory of my files, i can't change or custom the farsi languge and it's funny cause i don't know how it translate the site to Farsi when i dont't have the farsi file :D

@tohidshabanloo commented on GitHub: Hello , first thanks for this lovely project that you provide, i have a question, i installed the project on my debian server through this document https://docs.planka.cloud/docs/installation/manual_installation/debian_ubuntu/ in directory of the project i dont have access to languges , for example fa-ir file is not in directory of my files, i can't change or custom the farsi languge and it's funny cause i don't know how it translate the site to Farsi when i dont't have the farsi file :D
Author
Owner

@covaliandrei commented on GitHub:

Hi !
I've made a pull request with romanian language .

https://github.com/plankanban/planka/pull/555/commits

It is my first pull request, so correct me, if I do something wrong.
Thank you !

@covaliandrei commented on GitHub: Hi ! I've made a pull request with romanian language . https://github.com/plankanban/planka/pull/555/commits It is my first pull request, so correct me, if I do something wrong. Thank you !
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#783