Context : DSpace 7.2 I'm sorry if this has been discussed before.
What is the best approach to producing localized/custom versions of languages keys ((1) additional keys (only for local purposes, not for developments submitted back to the main code) and (2) changes to the content of existing keys in the language files (e.g. original : "home.top-level-communities.head": "Communities in DSpace" versus local : "home.top-level-communities.head": "Communities in UofM Institutional Repository") while ensuring easy updating when the time comes (i.e. new Dspace releases)? It would be desirable to have a way to install a local file that would contain the additional keys as well as the localized keys so that these forms would add to or override the original forms (found in en.json5, fr.json5, etc.). If it's already the case could someone explain how this can be done properly? I haven't seen anything adressing this issue on the https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441 page. Thank you, Marie-Hélène Vézina (she/her) Bibliothécaire · Projets numériques | *Librarian · Digital Initiatives* Bibliothèques | soutien à la réussite, à la recherche et à l'enseignement *Libraries | Teaching, Learning and Research Support* *Université de Montréal* -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/c300b528-be5c-4640-9e9d-e9d4df8f2707n%40googlegroups.com.
