[Feature] Integrate internationalization plugin for multilingual support
Neilblaze opened this issue · 11 comments
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.
@Neilblaze In general I agree with this and would love to see what you come up with in an integration as a PR!
@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.
@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?
@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
@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.
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.
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
@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.
@TimidRobot Sure.
@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.
@possumbilities Sure I would love to go ahead in this direction.