Hello! I couldn't fix this on the server (debian). I ran both commands in .../dspace-angular:
yarn run sync-i18n yarn merge-i18n -s src/themes/mytheme/assets/i18n And I keep seeing keys instead of translations. On the development team I can see them without problem. Is there a missing step to take into account? Thank you.- El jueves, 16 de noviembre de 2023 a las 14:01:49 UTC-3, Andrew K escribió: > Hi Tim! > > Thank you! > Looking deeper into this issue, I found this topic "Syncing existing > translations with changes to en.json5" > > https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Syncingexistingtranslationswithchangestoen.json5 > > I just run *yarn run sync-i18n* and magically received fully updated > localization file synced to the authoritative English file. > Moreover, all translated keys I had added before were kept! > So I highly recommend this tool. It completely solves the problem of > missing keys. > > Best regards, > Andrew > > > > четвер, 16 листопада 2023 р. о 00:56:22 UTC+2 DSpace Technical Support > пише: > >> 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/af8559b9-2f51-4a24-a5e3-e26d9a6059e7n%40googlegroups.com.
