It seems to me that there are two ways:

1. Offer the VideoJS to transfer translation to translatewiki.net
2. Fork the translation table, this can complicate development.

@Nikerabbit Hi! :) Can you help me how you think the VideoJS project (https://github.com/videojs/video.js) is suitable for translating on translatewiki.net?

1. Offer the VideoJS to transfer translation to translatewiki.net

I note that Wikimedia has upgraded to new VideoJS versions about once a year (or sometimes a bit more often). So for translators this would still mean quite different experience compared to these messages that are translated as part of the extension and are deployed weekly.

This way, if it wouldn't be too much trouble, it'd seem more desirable to fork the translation table (or its parts that Wikimedia actually uses). This is also how we previously handled messages for KalturaPlayer, right?

I do not recommend forking, at least not without discussing with the upstream developers first. It would benefit us, but not all the other people who might be using the software.

In my opinion the localisation process is not the appropriate place to take shortcuts. Does TimedMediaHandler have a maintainer that could manage the process, such as upgrading the library more often or collaborating with upstream about syncing translations?

Yes, this is also one of the reasons why I don't like the idea of forking the table.

I can start a discussion, but I need someone to help with the technical details later. I was thinking of suggesting the following:

1. The player creates a separate folder of translations, for example
   1. lang-stable - their standart translation
   2. lang-community - translation from translatewiki
2. The player adds a separate setting that switches the translation to lang-community
3. We publish translation updates to both their repository and ours in lang-community folder. Then we won't depend on their releases.
4. We switch our player to use lang-community folder

We publish translation updates to both their repository and ours in lang-community folder. Then we won't depend on their releases.

Not sure who is "we" here, but translatewiki.net doesn't support pushing the same translations to multiple repositories.

In T311343#8040507, @Nikerabbit wrote:

We publish translation updates to both their repository and ours in lang-community folder. Then we won't depend on their releases.

Not sure who is "we" here, but translatewiki.net doesn't support pushing the same translations to multiple repositories.

Oh, thanks for the clarification. Thought such functionality is possible.

@Nikerabbit, to be clear, what is this stalled on? Is there a decision on what i18n approach should be taken, and accordingly what step should be taken next?

@Pikne I was treating this as new project request for translatewiki.net. It's stalled in the sense that the project is not ready to be added currently.

If this task is only for consultation, then we can place it on a different column.

Upstream discussion: https://github.com/videojs/video.js/discussions/8004

Considering that there has been no movement for a year and a half, we need to translate it ourselves and create a 'fork'.