Should we split Translation.All in two such that Core can reference core module translations, and .All include Cms modules too?

@sebastienros That would be even better.

Translation.Core.All
Translation.CMS.All

Though, the thing is that currently the OrchardCore.Application.Cms.Targets is only there for including OC themes to the OrchardCore.Cms.Web project.

We would need to split translations for CMS modules vs Core Modules. Then have 3 or 4 .targets projects to included them all separately. I'm not sure if we have everything splitted up with Core and Modules. That may cause some issues of missing translations in the beginning.

Here, I remember that we set the Translations.All in the Cms.Target because we wanted to make the main one to be lightweight but that doesn't make sense to have modules that can be translated without having translations. We end up adding the reference to our web project. And it doesn't follow the same version as the current one which can lead to forgetting upgrading it along with the OC version.

I think the main issue here is that we include all the translations even if we didn't use them, what if we include them on demand?

I saw some CMS load the translations on the fly, but while we don't have this capability we could install them using dotnet CLI