Ideas for resources

[Jay-o-Way]

Description of the new feature / enhancement

• The Settings file is huge. We can split off the OOBE and Flyout strings to a new file.
  • https://learn.microsoft.com/windows/uwp/app-resources/localize-strings-ui-manifest#factoring-strings-into-multiple-resources-files
  • Maybe OOBE and Flyout should be a separate project?
• There are a few cases where a module's name is set in a few redundant strings. We could remove the duplicates and re-use the remaining ones. (think of Settings > ModuleTitle versus OOBE and Navigation strings)
  • This also prevents different translations
• We can "squash" all the "Enable <module>" into one general "Enable". Same for all the "Learn more about ..." HyperLinks.
  1. use "Enable {0}" where the name is filled in (or...)
  2. is <Hyperlink><Run x:UID="LearnMore"><Run x:UID="ModuleName"></HyperLink> possible?
• Every data name="<modulename>.SecondaryLinksHeader" is identical and thus redundant.
• Check for unused data.
  • src/modules/fancyzones/FancyZonesLib/Resources.resx
  • src/runner (e.g. STARTUP_DISABLED_BY_USER)
• Should we be using resX or resW?

[niels9001]

I wonder if there's an automated way to filter out all unused strings from the Resources file. I think, due to UI changes and other things, we might have a lot of dead strings that can be removed.

[Jay-o-Way]

I wonder if there's an automated way to filter out all unused strings from the Resources file. I think, due to UI changes and other things, we might have a lot of dead strings that can be removed.

I can't think of anything. Maybe somebody can write a AutoIt script that takes the data-names from the res, crawls through all the files and makes a list of all the ones that it can't find 😅

(edit)

I actually made a script that does this! At the moment, on a per-folder basis. Not perfect, but still... 😆

[Jay-o-Way]

ping