Description
Headline
CourtListener Now Available in Spanish
What is the Feature?
It's l10n! If we are doing a big design update, that's the best time to add l10n to CL and enable it to go multi-lingual.
Even if the underlying documents are only in English, having the interface be in a user's native language is a big help. This ties in with #75 because we can localize labels applied by classifiers, which would help non-native speakers find relevant parts of a docket much more easily.
Doing Spanish first is a no-brainer.
What Problem Might it Solve?
This is an A2J issue. Users whose first language isn't English have a hard enough time with understanding the legal system. If we can give them a tool that's in their language, that's at least some help.
Describe a Scenario in Which the Feature Might be Used
It's not hard to imagine a pro se litigant whose first language is not English trying to use CL and having a hard time. If the interface was in their language, they'll have an easier time.
Technical Requirements
- Our frontend framework would need to support l10n
- We'd have to put all the existing English language strings into that l10n system
- Then we'd have to create Spanish or other strings and put them in
- Language detection from browser locale
- User setting for preferred language?
- I don't know how long this would take. Depends on our frontend framework and how many people we can put on it. Might be able to get volunteers for translations.
Existing Systems or Alternatives?
Lots of websites allow you to pick your language.
Any Additional Information?
Nope