- Capitalization: Use sentence style capitalization by default.
Q: Is this the default already?
A: Default is Title Capitalization on most buttons and UI with some instances in Sentence capitalization (such as items in dropdown menus). I inquired a bunch of people in IRC and most seemed to prefer sentence capitalization.

Examples:
Orig:
STR_INTRO_NEW_GAME                                              :{BLACK}New Game
STR_INTRO_LOAD_GAME                                             :{BLACK}Load Game
STR_INTRO_PLAY_SCENARIO                                         :{BLACK}Play Scenario
change:
STR_INTRO_NEW_GAME                                              :{BLACK}New game
STR_INTRO_LOAD_GAME                                             :{BLACK}Load game
STR_INTRO_PLAY_SCENARIO                                         :{BLACK}Play scenario

- Capitalization: Use title capitalization on vehicle names, resource names, currencies, locations, buildings, given names & ranks, applications, and keyboard shortcuts.
Q: Is this the default already?
A: IIRC all except for resources which are currently sentence capitalized.

Examples:
Orig:
STR_QUANTITY_GRAIN                                              :{WEIGHT_LONG} of grain
STR_QUANTITY_WOOD                                               :{WEIGHT_LONG} of wood
STR_QUANTITY_IRON_ORE                                           :{WEIGHT_LONG} of iron ore
STR_QUANTITY_STEEL                                              :{WEIGHT_LONG} of steel
change:
STR_QUANTITY_GRAIN                                              :{WEIGHT_LONG} of Grain
STR_QUANTITY_WOOD                                               :{WEIGHT_LONG} of Wood
STR_QUANTITY_IRON_ORE                                           :{WEIGHT_LONG} of Iron Ore
STR_QUANTITY_STEEL                                              :{WEIGHT_LONG} of Steel

- Tooltips: always leave a paragraph break between a tooltip title and description, and put a colon at the end of the title. If a tooltip only has a title, put no punctuation at the end.
Q: Is this the default already?
A: No. It's present in some strings, such as the tooltips for the signals menu. The reason why I propose this is made a default is because it makes tooltips much easier to read. The break is added by {}.

Examples:
Orig:
STR_BUILD_SIGNAL_SEMAPHORE_PBS_TOOLTIP                          :{BLACK}Path Signal (semaphore){}A path signal allows more than one train to enter a signal block at the same time, if the train can reserve a path to a safe stopping point. Standard path signals can be passed from the back side
change:
STR_BUILD_SIGNAL_SEMAPHORE_PBS_TOOLTIP                          :{BLACK}Path signal (semaphore):{}Allows more than one train to enter a signal block at the same time, if the train can reserve a path to a safe stopping point. Standard path signals can be passed from the back side

== Summary ==
Tooltips: tile/no title
Q: Can this be reviewed from the text files alone or does this need the game client? Is this a lot of churn or are the strings mostly consistent?
A: Has to be reviewed in-game. Title conditions mostly hinge on whether a button is graphic or text-based. Most of these strings aren't particularly hard to find with the game open however, and reviewing is faster than it seems.

Examples:
Orig:
STR_RAIL_TOOLBAR_TOOLTIP_BUILD_RAILROAD_STATION                 :{BLACK}Build railway station. Ctrl enables joining stations. Shift toggles building/showing cost estimate
change:
STR_RAIL_TOOLBAR_TOOLTIP_BUILD_RAILROAD_STATION                 :{BLACK}Build railway station:{}For loading and unloading cargo or passengers. Ctrl+Click enables merging stations. Shift+Click shows estimated cost without purchase

Q: How could translators follow this rule?
A: We are deciding a priori which tooltips have or don't have a title based on the button. Translators simply have to obey tag placement (the {} tags) in the english text. Nothing else to it.

== Language style ==
- Jargon and slang will not be used at all.
Q: Are we using this anywhere? Can you provide good/bad examples in the manual of style itself?
A: This is mainly future proofing, but take the previous discussing of bridgehead vs anchorage, the latter being an obscure technical term. Technically bridgehead is preferable because its easier to understand.

== Bias-free communication ==
Q: I agree with this section, but especially the "Use gender-neutral alternatives" section might be some churn and could be reviewed separately. I think that wording to make existing strings adhere to this might turn up some discussion around the right new text. As such this should not be forced through in a very large commit with many other smaller / more obvious changes.
A: AFAIK there's barely any of it. I only found "Chairman", in the ranks, and nothing referring to disabilities. No he or she pronouns either, so again, this is mainly future proofing.

Examples:
Orig:
STR_COMPANY_LEAGUE_PERFORMANCE_TITLE_CHAIRMAN                   :Chairman
change:
STR_COMPANY_LEAGUE_PERFORMANCE_TITLE_CHAIRMAN                   :Chair

== Descriptive texts and UI labels ==
Q: This is not useful when you're done, but at this point in time a few examples of tooltips/labels you want to change would be helpful in assessing the before/after state of these rules.
A: This section is more of a categorization to setup up further rules and to tell what is what.

== Acronyms ==
Q: Looks fine. Hope the changes to follow this should be minor.
A: I don't think tere's any at the moment.

== Capitalization ==
Q: Looks fine. Might be large churn, but easy changes.
A: This is probably the largest amount of churn, but it's pretty much just following the guide IIRC.

Examples:
Orig:
STR_FINANCES_SECTION_CONSTRUCTION                               :{GOLD}Construction
STR_FINANCES_SECTION_NEW_VEHICLES                               :{GOLD}New Vehicles
STR_FINANCES_SECTION_TRAIN_RUNNING_COSTS                        :{GOLD}Train Running Costs
STR_FINANCES_SECTION_ROAD_VEHICLE_RUNNING_COSTS                 :{GOLD}Road Vehicle Running Costs
STR_FINANCES_SECTION_AIRCRAFT_RUNNING_COSTS                     :{GOLD}Aircraft Running Costs
change:
STR_FINANCES_SECTION_CONSTRUCTION                               :{GOLD}Construction
STR_FINANCES_SECTION_NEW_VEHICLES                               :{GOLD}New vehicles
STR_FINANCES_SECTION_TRAIN_RUNNING_COSTS                        :{GOLD}Train running costs
STR_FINANCES_SECTION_ROAD_VEHICLE_RUNNING_COSTS                 :{GOLD}Road vehicle running costs
STR_FINANCES_SECTION_AIRCRAFT_RUNNING_COSTS                     :{GOLD}Aircraft running costs

== Formatting ==
Q: Can the "General descriptive text formatting" section be merged into "Descriptive texts and UI labels"/"Descriptive texts" (or the other way around)?
A: Again the previous section is more of an introduction telling what is what. I don't think merging would make much sense.