-
Notifications
You must be signed in to change notification settings - Fork 68
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
Adding i18n Support #99
Comments
This feature should be implemented using transifex. Related documentation:
Please write a proposal before submitting a PR (🧹 status: ticket work required). I expect some coordination will be required to setup Transifex. |
I would like to work on this issue and can draft a proposal for implementing i18n support. However, I have some concern regarding the translation process. Since legal content is highly specialized, translating it accurately can be challenging. Would it be acceptable to rely on voluntary translators for this task? While this could improve accessibility for non-English speakers, the translations may not be certified or legally accurate, serving more as a reference. I'd appreciate feedback on whether this approach aligns with the project's goals. |
@rypptc I share your concerns about legal text (indeed Creative Commons uses separate translation processes for non-legal-text). However, the LegalDB website doesn't, itself, contain any legal text (just summaries). I'll raise the concern with the legal team and see where they would like to draw the line. At a minimum, we can implement a translation workflow for the website UI. |
@rypptc the legal team agrees, all of the text in this project may be translated. |
Ok, great, I'm working on it |
Problem
Currently to support different languages there is nothing present thus only the person who understands English will be able to use our application
Description
The goal of this issue is to add i18n support with which we will be able to handle different languages and this our reach to people will highly increase
Implementation
The text was updated successfully, but these errors were encountered: