Any plans for translation?

[Bamowen]

EDIT 06.09: This is now discussed in #446. Closing this discussion.

Hi!
I don't have much programming skill, but I'd love to contribute more.
I can clearly help with translation if needed. Maybe we can setup something like Crowdin, which is what Mastodon is using for instance and would streamline all languages.

Any thoughts?

[CyanVoxel]

Hello! Translation is definitely planned, but nothing's been started with it as of yet. Now that 9.4 is out this would probably be a great time to get that ball rolling! There's an issue open for it (#83) but not specific implementations have been discussed there yet.

[Nginearing]

I'd definitely be willing to help if needed, I'm not exactly "fluent" in the languages I've been studying for the last few years but my knowledge can definitely help, since there's only so many strings to be localised.

[Bamowen]

Alright!
Is there any existing list of every string in the app, possibly with their keys?
We can put that in a json to start if it doesn't exist :)

[Tyrannicodin]

I'm going to try doing crowdin integration, I plan on using json files located at /tagstudio/resources/translations/

[Bamowen]

Do we need to exclude them from releases?
I'm looking over at Mastodon repo and they have it directly at app/javascript/mastodon/locales/en.json

[Nginearing]

@CyanVoxel What do you think about using Crowdin? Tyrannicodin is getting to grips with it, would you want to have full control over the translation on Crowdin or just create the actual Crowdin project and then just add someone like tyrannicodin or Bamowen as a maintainer (I think they are called managers on Crowdin) Crowdin honestly seems like a smooth way to localise (translate) the UI, there is progress management also on Crowdin to make it easier for managers to keep track of the localisation process.

[CyanVoxel]

@CyanVoxel What do you think about using Crowdin? Tyrannicodin is getting to grips with it, would you want to have full control over the translation on Crowdin or just create the actual Crowdin project and then just add someone like tyrannicodin or Bamowen as a maintainer (I think they are called managers on Crowdin) Crowdin honestly seems like a smooth way to localise (translate) the UI, there is progress management also on Crowdin to make it easier for managers to keep track of the localisation process.

I'm currently looking into Crowdin now

[Nginearing]

I'm currently looking into Crowdin now

I've already got a feature request written up, specifically detailing what it entails for the program, as the other translation feature request is not properly written out nicely. I'll post the feature request when you get back to us (and if you're up for it of course).

[Nginearing]

You can now join the discussion in #446.
Please no longer discuss on this page.

[Tyrannicodin]

Looks like Qt uses custom translation files translated using Qt Linguist so we'll have to use that I think

[Bamowen]

For completeness' sake, this is being discussed in #446

[Nginearing]

For completeness' sake, this is being discussed in #446

Sorry, I forgot to put this, Mentioned that I was going to create one, but didn't link it.

[Nginearing]

I'd recommend changing the first post of this discussion to link directly to it, so people don't get confused, Please close this discussion too.

[Nginearing]

Hi all,

You are now able to translate the TagStudio user interface into your language of choice by clicking here.

How the translation process is going so far.... ⬇️⬇️⬇️ - as of the 24th of September 2024

If you are still referring to this discussion for correspondence about translation support, please do not respond in this discussion, instead you should look at #446 for all future correspondence about this feature, where you can also ask any questions you may have.

And of course, make sure to join our Discord server, where we have a thread just for communicating about the Weblate translations!