Changes between Version 46 and Version 47 of EnglishStyleGuide
- Timestamp:
- Apr 4, 2019, 1:31:44 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
EnglishStyleGuide
v46 v47 6 6 == Orthography 7 7 === English spelling 8 Use American English spelling. For example:8 Use American English spelling. 9 9 10 10 ||='''US''' =||='''UK''' =|| … … 12 12 ||armor ||armour || 13 13 ||artifact ||artefact || 14 ||center ||centre || 14 15 ||defense ||defence || 15 16 ||dialog ||dialogue || … … 24 25 === Calender years 25 26 The name of the game is '''0 A.D.''', which includes dots, for stylistic reasons. 26 However, dots are not used when writing down years. E.g. Augustus was emperor of Rome from 27 BC until his death in 14 AD.27 However, dots are not used when writing down years. E.g. Augustus was emperor of Rome from 27 BC until AD 14. 27 28 28 29 ||='''Good''' =||='''Bad''' =|| … … 79 80 Always be precise. E.g., if a technology multiplies the melee attack damage of cavalry by 1.2, the tooltip should be “cavalry +20% melee attack damage”, not “melee cavalry +20% attack damage”. 80 81 81 Furthermore, there should be a bijection between descriptions and classes. E.g. if a technology affects the `Citizen` class, write “ Citizens”; if it affects the `Soldier` class, write “Soldiers”; if it affects only units that have both the `Citizen` and the `Soldier` class, write “Citizen Soldiers”; however, if it affects the `CitizenSoldier` class instead, then write “Citizen-Soldiers”. (However, this should typically not occur: `Citizen` and `Soldier` are visible classes, `CitizenSoldier` is a non-visible class.)82 Furthermore, there should be a bijection between descriptions and classes. E.g. if a technology affects the `Citizen` class, write “citizens”; if it affects the `Soldier` class, write “soldiers”; if it affects only units that have both the `Citizen` and the `Soldier` class, write “citizen soldiers”; however, if it affects the `CitizenSoldier` class instead, then write “citizen-soldiers”. 82 83 83 84 For specific words that you should use or avoid in 0 A.D. gameplay texts, see the tables below. … … 87 88 88 89 ||='''Good''' =||='''Bad''' =|| 89 || Build (structures) ||Construct, make ||90 || Collect (treasures) ||Gather ||91 || Construct (ships, siege weapons) ||Build, produce, train ||92 || Gather (resources) ||Collect, get ||93 || Research (technologies) || ||94 || Train (human units) ||Build, construct, recruit, produce ||90 ||build (structures) ||construct, make || 91 ||collect (treasures) ||gather || 92 ||construct (ships, siege weapons) ||build, produce, train || 93 ||gather (resources) ||collect, get || 94 ||research (technologies) || || 95 ||train (human units) ||build, construct, recruit, produce || 95 96 96 97 … … 102 103 103 104 ||='''Good''' =||='''Bad''' =|| 104 || Icon ||Image, Picture, Portrait, Sprite, Thumbnail ||105 ||icon ||image, picture, portrait, sprite, thumbnail || 105 106 106 107 … … 108 109 109 110 ||='''Good''' =||='''Bad''' =|| 110 || Food || ||111 || Metal ||Gold, Iron ||112 || Stone ||Brick, Rock ||113 || Wood ||Lumber ||111 ||food || || 112 ||metal ||gold, iron || 113 ||stone ||brick, rock || 114 ||wood ||lumber || 114 115 115 116 … … 117 118 118 119 ||='''Good''' =||='''Bad''' =|| 119 || Crush attack damage ||Crush, Crush attack, Crush damage ||120 || Health ||Hitpoints, HP||121 || Melee attack range ||Attack range, Melee range, Range ||120 ||crush attack damage ||crush, crush attack, crush damage || 121 ||health ||health points, hitpoints, HP || 122 ||melee attack range ||attack range, melee range, range || 122 123 123 124 … … 163 164 === Capitalization 164 165 Use [https://en.wikipedia.org/wiki/Letter_case#Title_case title case] for: 165 * Button captions166 * Entity names (including generic names of phases, structures, technologies, and units)167 * Key names168 * Proper names166 * button captions 167 * entity names (including generic names of phases, structures, technologies, and units) 168 * key names 169 * proper names 169 170 170 171 Never use full capitalization.
