Oh yes, that's a great idea for a future improvement that doesn't obliterate the default stock text. Similar to config file precedence. In the meantime, I'll edit by hand and also be sure to keep my own backups of the stock text. Thanks Mark! ~Amy
On Wednesday, July 12, 2023 at 5:36:20 AM UTC-7 Mark H. Wood wrote: > On Tue, Jul 11, 2023 at 04:46:49PM -0700, Amy Ball Wicklund wrote: > > Using the theme override approach, if I remove some of my custom text > from > > my theme's en.json5 file and run the yarn merge-i18n command, the > deletion > > doesn't propagate to the dist directory. New or changed custom text gets > > merged, but it seems the only way to undo custom text and revert back to > > the default text is to make the change manually in my theme AND in the > > production/dist file. > > > > Is this behavior intentional, by design? > > I think it's an unfortunate limitation of the current approach to > customizing message texts. Where would the merge script get the > original text, once it's been replaced in the stock catalog? > > I would like to replace the current approach with this: both the > *unaltered* stock catalogs and the custom catalogs are built into the > frontend, and localization code would consult an ordered list of > catalogs until the key is found. I haven't yet had time to work out > how to do this using the available facilities. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 <(317)%20274-0749> > www.ulib.iupui.edu > -- 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/49c8b7e2-3a01-4efb-a708-3b159afdff71n%40googlegroups.com.
