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

[Feature] Integrate internationalization plugin for multilingual support #451

Open
1 task done
Neilblaze opened this issue Feb 27, 2023 · 11 comments
Open
1 task done
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🔒 staff only Restricted to CC staff members 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Neilblaze
Copy link

Problem ❓

Since CC chooser has users from diverse linguistic backgrounds across the globe, it is important to have a feature that supports multiple languages to accommodate users from various regions and backgrounds. A good solution includes integrating an internationalization plugin like i18n.

Having an internationalization plugin in cc-chooser offers numerous advantages, including increased accessibility, improved user experience, compliance with legal requirements, and cost savings.

Implementation

  • I would be interested in implementing this feature.

cc: @possumbilities, @TimidRobot

@Neilblaze Neilblaze added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Feb 27, 2023
@possumbilities
Copy link
Contributor

@Neilblaze In general I agree with this and would love to see what you come up with in an integration as a PR!

@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 3, 2023
@Cronus1007
Copy link
Member

Cronus1007 commented Mar 3, 2023

@possumbilities I think that we have already integrated i18n into chooser web app since we are using vue-i18n. Please have a look over src/i18n.js.

@possumbilities
Copy link
Contributor

@Cronus1007 You're right, we just hadn't done any other languages yet, that's a fair point I missed it.

Perhaps we should close this, or consider any improvements to be made to that use in an additional Issue?

@Cronus1007
Copy link
Member

Cronus1007 commented Mar 3, 2023

@possumbilities I personally believe that english is sufficient however this calls for community discussion. Lets connect on slack huddle to have a brief discussion about this issue? Right now marking this as staff-only issue.

@Neilblaze Thanks for raising this issue. 😄
CC: @TimidRobot

@Cronus1007 Cronus1007 added the 🔒 staff only Restricted to CC staff members label Mar 3, 2023
@Cronus1007
Copy link
Member

@possumbilities If we were to consider the wp-plugin-creativecommons it also only provides the support for en language so I think both should be synced.

@TimidRobot
Copy link
Member

We use Transifex for localization: Creative Commons localization | Transifex.

Before any work is done on the Chooser code base, there needs to be a good understanding of how it will interact with Transifex. I suspect that Gettext Files (.mo & .po) are not the best solution for this project, but I'm not yet familiar with the other options available to us from Transifex.

@Cronus1007
Copy link
Member

Shall I start with creating a dummy project with Transifex. I have previously used it with PHP. And if I will be able to make some advancement in this approach. Then we can use Transifex for the complete chooser web app. Does that sound a good idea? @possumbilities @TimidRobot

@TimidRobot
Copy link
Member

@Cronus1007 I would start by looking at their documentation and describing what you think the two best options are here. You may want to wait until @possumbilities has a chance to provide input on Monday.

@Cronus1007
Copy link
Member

@TimidRobot Sure.

@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🏁 status: ready for work Ready for work labels Mar 4, 2023
@possumbilities
Copy link
Contributor

@Cronus1007 I've thought on this and my take is I'd like to see a strong set of research, proof of concept, and some data backing up approach strategies that utilize Transifex to accomplish this well before there's a PR initiated so the conversation here can guide the direction things take.

The aim is important, but there's still a lot of unknowns and I think sorting those in a sound way here first is the best way to begin.

That said, if you want to do that research with some proof of concept work I'd encourage it and look forward to your findings here.

@Cronus1007
Copy link
Member

@possumbilities Sure I would love to go ahead in this direction.

@Cronus1007 Cronus1007 self-assigned this Mar 8, 2023
@TimidRobot TimidRobot removed the 🧹 status: ticket work required Needs more details before it can be worked on label Jul 9, 2024
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Jul 9, 2024
@possumbilities possumbilities removed the 🏷 status: label work required Needs proper labelling before it can be worked on label Sep 18, 2024
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on 🚧 status: blocked Blocked & therefore, not ready for work and removed 🧹 status: ticket work required Needs more details before it can be worked on labels Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🔒 staff only Restricted to CC staff members 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

5 participants