There are several resource files (5, I believe) that would need to be translated to change the full UI into English. There is also a separate mechanism for providing alternate verbalization. Neither of these should require C# code.
Modifying the verbalizer (either into alternate English forms or a different language) is designed to be an XML exercise, and setting an option.
Here are the steps for alternate verbalization:
1) In the C:\Program Files\Neumont\ORM Architect for Visual Studio\XML\Verbalization\Core directory, copy the _default.xml file to another file with the .xml extension.
2) Near the top of the file, change either Language/@xml:lang or Snippets/@name. If your choosing a language other than en-US (sv-SE for example) you can keep the "_default" name. Otherwise, change it (TestOverride, for example).
3) Any change you make to the Snippet text in this file will override the default verbalization. Note that you cannot change the default by modifying _default.xml. The defaults are compiled in: _default.xml is provided as the authoritative reference on what we're currently using (the default code is generated from this file).
4) You can pick and choose the snippet values to override. Any snippet not changed can be deleted and will fallback on the default.
5) To use your new verbalization in VS, go to the ORM Designer page of the Tools/Options dialog. In the Verbalization section, change the 'Alternate Verbalization Text' to 'Neumont.Tools.ORM.ObjectModel.CoreVerbalizationSnippetType,LANGUAGE,SNIPPETSNAME'. The default is 'Neumont.Tools.ORM.ObjectModel.CoreVerbalizationSnippetType,en-US,_default' (Obviously, we'll have a UI for this in the future).
6) If you have an ORM designer open, you can force a reload by changing this property, closing the options dialog, forcing something to reverbalize, then reapplying your option.
The goal of this approach is to enable verbalization modification at the snippet level in XML without reprogramming how the snippets are combined. You can refer to ORMModel\ObjectModel\VerbalizationGenerator.xml to see how these snippets are combined. Obviously, we'll have more verbalization snippets added to the default set as we fill in verbalization for more constraints. Extensions to the ORM tool can also use this same mechanism (each extension gets their own directory corresponding to their own enum type, the options uses a semi-colon to separate options for different snippet sets). We should have UI for this option by our next major drop.
-Matt