Open abartov opened 3 years ago
what work is required to "make all the interface strings translatable by one of the existing frameworks"? @justinlittman @jermnelson has your team done this before, perhaps with DLME?
Will require investigation. We've never done this with a React app.
making this a research task for Work Cycle 4: assess what would be required to support interface localization
@michelleif In order to get started, we need every english phrase from the editor translated to at least one other language. Here's how search works does it: https://github.com/projectblacklight/blacklight/tree/master/config/locales
we have users willing to do translations. what has to happen from development side in order for Sinopia to be able to display the strings in the user's desired language?
We need to decide on what the interface for this would look like. Is this something the user can change in the UI? If so we need a control for that. Alternatively, we could make this something that is decided by the person that is deploying Sinopia (e.g. If I work at Bibliothèque nationale de France, then I might want to ensure the interface is always using French). I believe the other option is to use the current locale configured in the web browser (navigator.language
).
thanks this is helpful. changing title of ticket and putting it in backlog for consideration for future Work Cycle
It would be great to be able to interact with Sinopia in other languages. I imagine most early-adopters are able to work with it in English, but many other potential users would be de-facto barred from using this useful environment without local-language support in the interface.
A minimal level of L10N would be making all the interface strings translatable by one of the existing frameworks.
Deeper support would be to also adapt UI layout to right-to-left languages, but I understand that is a much larger undertaking, probably out of scope for the current budgeted iteration.