Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Polylang #2284

Open
Tracked by #2231
jonathanbossenger opened this issue Mar 5, 2024 · 11 comments
Open
Tracked by #2231

Test Polylang #2284

jonathanbossenger opened this issue Mar 5, 2024 · 11 comments
Assignees

Comments

@jonathanbossenger
Copy link
Collaborator

jonathanbossenger commented Mar 5, 2024

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.
@jonathanbossenger
Copy link
Collaborator Author

@cynthianorman feel free to leave your testing feedback here.

@jonathanbossenger jonathanbossenger changed the title Test Polylang for translation Test Polylang Mar 5, 2024
@cynthianorman
Copy link
Contributor

Successfully installed on Learn WordPress local dev env
https://drive.google.com/file/d/1FhK_aov9Ut8Plex77k8LbDFTWdIGs90A/view?usp=drive_link

@cynthianorman
Copy link
Contributor

@cynthianorman
Copy link
Contributor

We can select the languages we want to translate pages and posts to
https://drive.google.com/file/d/1npTZ3t9k9rWnaFMiVKHordb8YcKumMhF/view?usp=drive_link

Note that showing the flag in the front end is optional

@cynthianorman
Copy link
Contributor

@cynthianorman
Copy link
Contributor

cynthianorman commented Mar 16, 2024

It's important to know that we essentially build a separate set of pages/posts/taxonomies and corresponding menu for each language.

For this reason, we would need to create the copied English page/post and designate it as French (for example) otherwise I don't believe this will work out for us. In other words, the copied English page/post would act as a placeholder until a translator would contribute the translation.

https://drive.google.com/file/d/1ZLAMfGTc4nOa6Cl9Wdgo5BFpZEiBf4KR/view?usp=sharing

@jonathanbossenger
Copy link
Collaborator Author

jonathanbossenger commented Mar 26, 2024

@cynthianorman do you think you'd be able to update this issue with a summary of your findings, in a similar way as the WPML test?

Edit, I've prepared the list in the comment below, so you just need to mark off the relevant items.

This will allow me to prepare a summary comparison table of our test findings for the training team meeting on Thursday.

@jonathanbossenger
Copy link
Collaborator Author

jonathanbossenger commented Mar 26, 2024

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.

@cynthianorman
Copy link
Contributor

@cynthianorman do you think you'd be able to update this issue with a summary of your findings, in a similar way as the WPML test?

Edit, I've prepared the list in the comment below, so you just need to mark off the relevant items.

This will allow me to prepare a summary comparison table of our test findings for the training team meeting on Thursday.

ok @jonathanbossenger done

@jonathanbossenger
Copy link
Collaborator Author

Perfect, thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants