Hi Andrew, We're aware that these i18n files can get "out of sync" easily and are working on ways to improve that. See this ticket: https://github.com/DSpace/dspace-angular/issues/2340
There's no exact solution yet, but many developers agree it's a frustration. So, if you have more ideas to share, feel free to add to that ticket. Regarding the display of missing keys, the current behavior is the same as it was in DSpace 6.x (where the key was displayed if missing). I'm not aware of a way to change that to be English by default, but you are welcome to create a ticket regarding that and I can ask other developers to look into it. I agree that it might be better to show English instead of a (cryptic) i18n key. Tim On Tuesday, November 7, 2023 at 8:18:21 AM UTC-6 Andrew K wrote: > Hello! > > I noticed that the localization files lag behind. And this is perfectly > normal. > The documentation says: "*When new keys are introduced, TODO messages are > automatically added to the catalogs of other languages*" > > https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Translations(forexample,nl.json5) > But that does not happen, new keys are missing, at least for uk.json5. Is > there a way to correct that? > > And the next problem is that missing keys in the .json5 file are displayed > as key names. It would be much much better if the English names were shown > instead. > Is that possible? > > Best regards, > Andrew > > P.S.: > -- 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/58dfe0ca-b208-4b4b-8d3d-94138c3c50b7n%40googlegroups.com.
