[Feature]: Translation on web

[MalteKiefer]

Feature detail

It would be good if you could customize the web interface with its texts so that you could add translations.

Platform

Web

[waclaw66]

This is highly anticipated feature.

[linguowei]

+1

[bt90]

It would make sense to translate the mobile app using a platform such as Weblate. This way, translations could be shared between mobile and web at a later stage.

[alextran1502]

We are actually looking into Weblate right now

[bt90]

The syncthing project moved its projects to weblate in 2023. We went with their hosted service which is free for open source projects.

Discussion: https://forum.syncthing.net/t/the-old-transifex-thread-was-translating-syncthing/550/76

[Havouza15]

I can help with Swedish when necessary

[hectorzin]

And myself in spanish.... any way to do it?

[wqtty]

I posted a feature #8139 and it was closed as duplicated with this one, so any progress?

[JW-CH]

You posted a feature request for a feature that has already been requested. That's why it was closed. See #1688 (reply in thread)

[justkowal]

I'd love to provide Polish translations

[MickLesk]

I can do the German translation 👍🏻

[maicss]

I can do the Simple Chinese translation.

[alexisjanvier]

I can handle French translations if needed.

[AngelaDMerkel]

I can do Dutch translation (lol)

[nutzlichsein]

I can do Indonesian translation... how can I contribute?

[Deedikjupijn]

We are actually looking into Weblate right now

For anyone wondering, this has not happened yet and so the only way to contribute with the web translations is if you were to implement weblate into the website (if there is any topic on this update I would love to hear it). Otherwise you would maybe be able to create a temporary button where people are able to change the languages and we just update every page manually (not using weblate).

Hope this helps and hope everyone has a nice day!

[dianso]

i can handle chinese translation

[Ador-able]

Is there any progress on this feature?

[MickLesk]

For the App, @alextran1502 uses localizley. I have no idea whether this is still planned for the web. I hope so :-)

[Manic-87]

Is the usage of Weblate now out of question? I actually wanted to try to look into it and try to bring translations to the web, but if Weblate is out of question I can obviously save me some time (and probably some headaches).

[bo0tzz]

Weblate is still planned, we just haven't gotten around to it. Same goes for translation support on the web.

[Manic-87]

Alright. Then I will invest some time looking into it, but absolutely no promises anything will come out of it.

[Manic-87]

So I did invest some time on this and I currently could display quite a few texts in different languages and also make use of weblate.
Disregarding the weblate portion, I want to make sure I'm on the right track about translatability of the web.

1. I added svelte-i18n as a dependency as it looked good to me (mind you, I don't have any experience with svelte, so I can't properly asses if this is actually good). This would be the first question: Is the usage of svelte-i18n ok or are there any concerns?
2. I started with the "page.svelte" files, took the hardcoded texts, moved them into a "en-EN.json" file and used the svelte-i18n functions to get the texts back. Regarding the structure of the file would be the next important question. For Android it's a flat list. For the web I thought about using a hierarchical structure as it, in my opinion at least, improves later readability/extendability.
   This means my file currently would look like this for example:

page: {
  admin: {
    library_management: {
      error_create: "Unable to create library"
      ...
      ...
    },
    system_settings: {
      auth_settings_title: "..."
      auth_settings_subtitle: "..."
      ...
      ...
    }
  }
}

For components the top level would be "component". For stuff which is used more often like "Video" or "User" there would be a top level "common" and so on. In the svelte files you'd then use
$t(page.admin.user_management.error_create)
for example. For stuff with placeholders you'd use
$t(page.admin.user_management.error_create, {values: {placeholdername: placeholdervalue}}).
With the placeholders you can also use plurals, so instead of having two rules strings for ""Matched 1 item" and "Matched 10 items" there would only be one "ICU plural messages" Matched {count, plural, one {# item} other {# items}}

If you want you can also take a look at the actual translation file I'm currently building here. There you also find how I currently replaced the texts in the svelte files. The branch itself was/is just a testing ground and all relevant changes would be moved to another clean branch.

What do you think? Is this the correct way for you or should I go at it some other way?

[bo0tzz]

Exciting! Can you start a draft PR with what you have right now? That provides a better place for discussing all the details. It doesn't matter if the branch is a mess/not ready.

[Manic-87]

Done #9854

[MickLesk]

Looks good. I'd have to do some translations and build the local, but it looks good so far. Would be worth a big release.

[saltfish13]

Hi there, I have been translating a Unity-based software, they use CSV files to store the lines and the corresponding keys so that the devs can refer to those translated lines using their keys in the UIs across different localizations. That said CSV files were posted on google docs so community translators can help out. But it's a bit complicated I kenw there are off the shelf solution to do community localization but this is a free approach lol, I am willing to help out with SC(simplify Chinese) and TC (Traditional Chinese) localizations.

[bo0tzz]

Weblate is now set up for web translations at https://hosted.weblate.org/projects/immich/immich/. Feel free to sign up and have your hand at some translations!

[MickLesk]

Perfect. I do it today for germany