Localization

KeenSWH made significant changes to their Localization, removing the localization assemblies, and moving to using Resource files here:
steamapps\common\SpaceEngineers\Content\Data\Localization
I think this is paving the way to allow mods to have their own localized text resources.

I had a quick look at the localization, and tested a custom localization with Blueprints.sbc in a mod, and it doesn't work currently.
Hopefully some time soon it will be enabled.

There is a brief example of how I've used their Localization resources with an Extension here:
https://github.com/midspace/Space-Engineers-Admin-script-mod/blob/master/midspace%20admin%20helper/Data/Scripts/midspace.adminscripts/CommandSaveGame.cs

When the resources are enabled for use inside Mods, this will open the path to Localizing our mod.
In the mean time, we should make sure we are using string.Format() instead of concatenating strings.

We also need to look at modifying the Commands use of Regex, to embed custom command names into the Regex.
Regex.Escape() will make sure we don't embed anything silly into the command as a expression instead of a string.

There is currently no method for programmatically determining the Culture.

Start with the referenced CommandSaveGame.cs example and inspect the Commands code mentioned in the issue. Determine which localization, string formatting, Regex command-name, and culture-detection requirements are still applicable. Done would require an agreed scope and working localized mod resources without unsafe command-pattern interpolation.