anchor.diff:  Even though the built-in fonts require the content to be encoded in WINANSI, _you still type your AsciiDoc document in UTF-8_.
   Asciidoctor PDF encodes the content into WINANSI when building the PDF.
   
  +CAUTION: Built-in fonts do not fallback to <<fallback-fonts,fallback fonts>>, you must use TrueType font for that.
  +
   .WINANSI Encoding Behavior
   ****
   When using the built-in PDF (AFM) fonts on a block of content in your AsciiDoc document, any character that cannot be encoded to WINANSI is replaced with a logic "`not`" glyph (`&#172;`) and you'll see the following warning in your console:
  
positive.code: All the available keys are documented in <<Keys>>.
  The converter uses the information from the theme map to help construct the PDF.
  
  [TIP]
  ====
  Instead of creating a theme from scratch, another option is to download the https://github.com/asciidoctor/asciidoctor-pdf/blob/master/data/themes/default-theme.yml[default-theme.yml] file from the source repository.
  
negative.code: But we recognize that can be a major obstacle when you're starting out.
  Therefore, your other option is to simply redeclare the fonts from the https://github.com/asciidoctor/asciidoctor-pdf/blob/master/data/themes/default-theme.yml[default theme] in the <<Custom Fonts,font catalog>>.
  Asciidoctor PDF will then resolve the fonts that are bundled with the gem.
  
  WARNING: If you don't declare your own fonts, the built-In (AFM) Fonts declared in https://github.com/asciidoctor/asciidoctor-pdf/blob/master/data/themes/base-theme.yml[base theme] will be used instead.
  However, since AFM fonts only support WINANSI characters (which is similar to Basic Latin), using them will result in missing functionality and warnings. See <<built-in-afm-fonts,Built-In (AFM) Fonts>> section to know more about limitations.
  
  toc::[]
  
  