Learn Test TranslatePress

Front-end requirements:

Language selector does not show as country flags. (Many countries speak multiple languages, so describing a language with a flag should be avoided.)
Languages can be changed without needing to log in to one's WordPress.org account.
Once a language is selected, it is applied globally.
Content of the selected language is shown above non-translated content.
English content is still shown where translations don't exist.

Back-end requirements:

Translators do not have permission to create or publish new content.
Translators have permission to both translate any content, and review content translated by others.
A flow can be implemented where translations must be approved (reviewed) before published.
Sensei content types can be translated in the same way as native post types.
Taxonomies can be translated.
Translated content is indexed and searchable by Jetpack Search.

Mar 14 '24 07:03 jonathanbossenger

Hi Jonathan,

Cristian Antohe, co-founder of TranslatePress here :)

If you have questions or want a paid version to test out (the free version doesn't allow for more then 1 language) I would be happy to help. (we can create a perpetual license, so you get updates moving forward to the paid version). The paid version is just an addon.

Some notes right of the bat regarding what doesn't work:

the one thing that we don't have is "A flow where translations must be approved (reviewed) before published"
translated search is indexed and searchable by Jetpack Search might not work. Normal WordPress search works, because we're hooking into the WP_Query and we have an index with translated content we serve from.
you'll probably want to limit translation to the post content. For that you just need to add the CSS id's or classes of the other elements like header, sidebar, footer on the exclude selectors list in the Advanced settings.

Best Regards!

Mar 20 '24 11:03 sareiodata

Hi @sareiodata thanks for the feedback. I'll take this into account during our testing.

Mar 22 '24 20:03 jonathanbossenger

@sareiodata what would be really helpful here is a summary of which requirements (listed in the issue description above) TranslatePress offers in either the free or the paid version.

If it's added to this issue as a check list (in a similar way as has been done for WPML, that would help me create a comparison table of the three options we're currently looking at.

Mar 26 '24 12:03 jonathanbossenger

Sure thing.

Front-end:

[x] Language selector does not show as country flags. (Many countries speak multiple languages, so describing a language with a flag should be avoided.)
[x] Languages can be changed without needing to log in to one's WordPress.org account.
[x] Once a language is selected, it is applied globally.
[ ] Content of the selected language is shown above non-translated content. - I don't understand the requirement.
[x] English content is still shown where translations don't exist.

Back-end:

[x] Translators do not have permission to create or publish new content - yes, available in the paid version.
[x] Translators have permission to both translate any content, and review content translated by others. Yes, a translator has access to all secondary languages, but there are no logs as to who translated what.
[x] Translators do not have permission to create or publish new content.
[ ] A flow can be implemented where translations must be approved (reviewed) before published. - This feature does not exist.
[x] Sensei content types can be translated in the same way as native post types.
[x] Taxonomies can be translated.
[ ] Translated content is indexed and searchable by Jetpack Search. - I haven't tested this myself. If it's a external index like the Google search that's found on other parts of wordpress.org, it might work. If it relies on WordPress internally for querying content and sending it to Jetpack servers, it might not as TranslatePress doesn't duplicate pages.

Notes:

maybe you can move the review of translated content internally like a process to be followed (Translator A finishes translation on an article then manually pings Editor B for review; while waiting for review, please note the translation will be live)
the main advantage for TranslatePress is how Translators interact with the website. Mainly point towards a paragraph, click, translate, save. They never have to see or work with the Editor. This might, or might not be a good thing depending on the flow you're looking for.

If there are questions, please let me know!

Mar 26 '24 14:03 sareiodata

@sareiodata thank you so much. I'll feed this back to the team at the next meeting, and also get some answers to your questions.

Mar 26 '24 14:03 jonathanbossenger