Can we make the project home page more multilingual without excessive labor?

Feedback
,
1

Should we consider exploring Linguise (or similar service) to expand automatic multilingual translation in the Gramps-project to the Gramps promotional WordPress site?

These WordPress pages serve as the main landing pages for new visitors to the gramps-project.org domain, introducing the application. Yet, currently, the WordPress pages are one of the few parts of the project with absolutely no translation… nor even any indication that other languages exist.

Linguise offers the flexibility to limit translations to the approximately 35 languages currently supported by our project, helping avoid the unrealistic expectation that support already exists.

For the other (about 50 more) languages not yet supported, we could add a few (automatically translated) informational pages explaining their language was currently without a volunteer translator and invite community members to contribute GUI translations through Weblate. And details on how to get started.

This approach could help us broaden Gramps’ reach while promoting collaborative translation efforts.

Learn more about Linguise here: Linguise WordPress plugin with cloud AI automatic translation

Composed with the assistance of Perplexity.

1 Like
2

An advert really!

Why not just link to the main wordpress category for Language plugins.

* https://wordpress.com/plugins/browse/translation

3 Likes
3

Most of the options looked like they required a lot of manual translation work.

This tool promises 5 minute set up and a free month testflight. (It is marketing crap so I don’t believe the 5 minute claim either.)

But we cannot expect any of the translators to jump on signing up for a new Account on a different CMS so they can manually edit 6 additional pages.

We need to test an automated solution.

4

Maybe something that integrates with the existing Weblate site used by Gramps?

I’ll research wordpress plugins and test.

2 Likes
5

Integrating with Weblate would be ideal for the MediaWiki content… terminology needs to sync up between the GUI and the online reference manual.

However, the WordPress content is all in marketing-speak. If the translation tool prioritizes the Weblate glossary, it may force more “jargon” into the mix than desired.

It also ups the complexity of the solution. So administrative burden becomes more of a consideration too.