-
Notifications
You must be signed in to change notification settings - Fork 4
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
Allow database content translation #105
Comments
@jraddaoui There's no need to translate the database content, per CCA current practice. We have single-language finding aids based on the language of the collection -- this won't be changing for this project. The only things that need to be translated are all the field names and the FAQ page. So long as the FAQ can be updated in both languages, doing the string translations isn't even necessary for that. We'll let you know if we have any additional feedback after @mireilleN 's translations have been merged, but as of right now, I think we're satisfied with the level of translation. Thanks! |
Currently looking at other possibilities to allow translations of static content (added in #96):
|
We finally used This is ready for review in the test instance. Some notes about how translations work for now:
|
Looks great, thanks Radda! :) |
With the setup of Django i18n in #16, all the interface is translatable, but the database fields are not translatable yet.
Estimates:
The text was updated successfully, but these errors were encountered: