I suggest to move the language resource directories one level deeper in the file system under a locales/ or sg similarly named directory in the production build.
It is annoying that all those 50 pcs two-letter country-codes directories clutter the main folder each time when I manually do something on the server's file system.
It is annoying that all those 50 pcs two-letter country-codes directories clutter the main folder each time when I manually do something on the server's file system.
Your request is not somehow related to the original topic about translations and language packs.
It's technical question related to how ASP.NET Core is implemented. These folders are not related to language packs but to resources of some third-party libraries. Just ignore them