anchor.diff:  
   NOTE: See <<LayoutTargetWindows>> in the reference section below.
   
  -.Example of the layout-level targets section for Chrome
  +.Example of the layout-level targets section for Windows
   [source,yaml]
   ----
   targets:
  
positive.code: == Mappings between modes in layout files and Windows keyboards
  
  .Mappings from kbdgen modes to Windows keyboards
  iso-default:: Base keyboard
  iso-shift:: Shift pressed
  iso-alt:: AltGr (or Ctrl+Alt if keyboard missing AltGr) pressed
  iso-alt+shift:: AltGr plus shift
  iso-caps+alt:: AltGr plus caps lock
  iso-ctrl:: Ctrl pressed (mostly will not work due to OS-level key combinations overriding this layer)
  
  .Special cased mappings
  
  iso-caps:: Caps lock enabled
  iso-caps+shift:: Caps lock and shift pressed
  
  If both of the above modes are found, the limitation regarding single codepoints described in the Limitations section applies.
  
  
negative.code: 
  * Windows does not support Unicode glyphbombs ("grapheme clusters") in deadkeys,
    but does support them as ordinary keys.
  * Using `caps` and `caps+shift` with Windows is limited to single
    codepoints, as the glyphbomb limitation also applies here.
  * Windows keyboard identifiers must be unique, are 8 characters long and
    begin with `kbd`. The next 5 characters are generated from the next 5
  