Translations #19
Replies: 3 comments
|
If I understand it correctly, git-updater supports language updates by a git(hub) reporistory. My idea would be to utilize GlotPress to set up a translation server, that is integrated with WordPress to update translations. Update:
This way translations would be handled like currently via |
|
There's two parts to this: translations for FAIR itself, and a replacement for dotorg's translations. For the former, we're going with committing those files to the repo for now, but might have GP set up later. For the latter, we actually have the work mostly complete for this, including a system to mirror all the translation data from dotorg - you can find a bunch of that at https://github.com/fairpm/server/tree/main/content/plugins/f-translate - We've got a few bits there to fix up before it fully goes live though, so support definitely welcome on that! We need to backfill some of the issues as well which didn't make their way over to the published repos when we launched. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey all 👋
Topic: Translations aka
translate.wordpress.orgSorry if this is already discussed somewhere else.
Does it make sense / is it wanted to also include this topic into FAIR?
If so, maybe I can find time to contribute to GlotPress or elsewhere, if changes are need (like supporting/utilizing the WP Rest API).
On my company project, I'm working a lot with GlotPress lately - the base for WordPress translations.
Currently I'm not fully aware of how WordPress (the software) gets its translations from translate.wordpress.org.
Maybe someone with more insights can give some background / informations here and what changes would be needed.
All reactions