@HLeithner @wilsonge any opinions here? else we can close here and just trash the translation.

We should have own language packages for these translation or shouldn't they be part of the german language pack?

Thoughts

1. Crowdin is not taking care of these when people use it to create core lang packs.
2. Looks like the module and plugins lang files are missing in this repo (if i do not mistake)
3. We have decided to include all fr-FR webkinks lang files in our general lang pack, but I have no idea about other TTs also doing so.
4. There is no process to install another language weblinks lang files from this repo in function of the site installed languages.
5. Starting to include them in the core of this repo could be considered as a solution, except if we advertise this and get many languages doing such. I doubt about it, but it could happen theoritically.

Conclusion: the separation of this component from core was done in amateur way... Was it really necessary? Should it had been kept still as a supported extension while no good solution was provided concerning languages ?

Sorry if this is considered as a rant.

So we should find a solution for this process, because it's possible that more components will be decoupled. May understanding was that the weblink decoupling was a test to learn how to it right... It seams there are improvements necessary to achieve this.

Any update on this topic? Is there anything against merging this into the repo and maybe remove it when there is a better solution?

Nothing new as far as I know.

Makes sense to me to setup up full crowdin integration here

based on downloads.joomla.org and the integration of j4 languages.

Makes sense to me to setup up full crowdin integration here

This would result into the current behavior that the TT's have to ship that with thier translation packages right? Why not ship it with the component like all other extensions handle translation, for sure an crowdin implementation could make sense but i would suggest to keep it out of the core translation packages and just ship it with the component.

Shipping ALL languages with the package (comp, mod, plugins) would be very heavy and independent on the installed languages.

Any progress made on that topic here or should that PR here just be closed? @infograf768 @HLeithner @wilsonge ?

Thanks :)