Changes between Version 34 and Version 35 of EnglishStyleGuide


Ignore:
Timestamp:
Jan 13, 2019, 8:00:46 PM (5 years ago)
Author:
Nescio
Comment:

unicode

Legend:

Unmodified
Added
Removed
Modified
  • EnglishStyleGuide

    v34 v35  
    128128For example:
    129129
    130 ||=Good=||=Bad=||
    131 ||…     ||...  ||
     130||=Good               =||=Bad                  =||=Usage =||
     131||… (U+2026, ellipsis) ||... (three full stops) ||intentional omission ||
     132||• (U+2022, bullet)   ||- (hyphen)             ||itemization ||
     133||– (U+2013, en-dash)  ||- (hyphen)             ||range of values (500–1 BC), oppositions (Greco–Persian wars) ||
     134||— (U+2014, em-dash)  ||- (hyphen)             ||source of a quote ||
     135||− (U+2212, minus)    ||- (hyphen)             ||substraction, negative values ||
     136||× (U+00D7, times)    ||x (X)                  ||multiplication ||
     137||“ (U+201C)           ||" (programmer's quote) ||start of a quotation ||
     138||” (U+201D)           ||" (programmer's quote) ||end of a quotation ||
     139||‘ (U+2018)           ||' (apostrophe)         ||start of a quotation inside a quote ||
     140||’ (U+2019)           ||' (apostrophe)         ||end of a quotation inside a quote ||
     141
    132142
    133143However, [[Atlas_Manual|Atlas]] [https://trac.wildfiregames.com/ticket/4936 does not support Unicode], so English strings of map files (e.g. anything under `binaries/data/mods/public/maps/`) should not contain Unicode characters for the time being. But you should avoid using combinations of ASCII characters to try and reproduce Unicode characters as well. Be creative, try to rephrase the content in question so that Unicode characters are not necessary.