/**
   The fonts imported by the morbad-card-tools library. These are in a
   separate CSS file primarily so that we can load them from
   JavaScript because that allows us to consolidate certain code for
   use in both browser-based JavaScript and embedded WebView in a
   particular Android app.
*/

/*
  Reminders to self:

  - this "dominican" font is relatively small, which is why the font
  sizes uses by the morbad-card-tools library may seem to be specified
  as "too large."

  - How to add multiple entries for the same font-family:

  https://stackoverflow.com/questions/2436749/how-to-add-multiple-font-files-for-the-same-font

  - The url()s here are relative to the morbad-card-tools JS library,
  which is not necessarily the same path as the app. When morbad
  loads this script, it uses a path relative to its own code location,
  so this "should" be a non-issue in practice, but it merits being
  aware of in case something goes awry.

  - According to the article above, the order of the fonts must be
  reversed, such that the standard font comes last.
*/
/*Is a 'bolder' entry needed to get the 'bolder' effect?*/
/* doesn't seem to make a difference
@font-face {
    font-family: "dominican";
    src: url("fonts/caslon_antique_bold.ttf");
    font-weight: bolder;
}*/

@font-face {
    font-family: "dominican";
    src: url("../fonts/caslon_antique_bold.ttf");
    font-weight: bold;
}
@font-face {
    font-family: "dominican";
    src: url("../fonts/caslon_antique_regular.ttf");
}
@font-face {
    /* The Goblinko-official DD icon font. */
    font-family: "dd-icons1";
    src: url("../fonts/dd-icons.otf");
}
@font-face {
    /* Custom-made font holding DD icons which are not included in
       dd-icons.otf or which are unique to this app. */
    font-family: "dd-icons2";
    src: url("../fonts/dd-icons2.otf");
}
.dd-font {
    /* Historically, the toolkit has used a single font, so only needed
       one CSS class to model that.  All of the CSS and card font
       sizes are finely tunes for the Caslon Antique font, so we
       unfortantely can't just go swap out fonts willy-nilly.

       The game's physical cards *apparently* use the Libre
       Baskerville font for the main body and something wich Caslon
       approximates for the card name header. By the time i realized
       this, the framework was already neck-deep in Caslon-based
       tuning. "Someday" i'd like to explore making card bodies and
       footers Baskerville, but initial experimentation shows that not
       only font sizes, but also line heights, have to be minutely
       tweaked in order to get the card text to fit, and even then
       it's not clear that Baskerville will produce text large enough
       to read on certain cards. (The Call Fire skill card is a good
       test case, as it contains a slightly-too-much amount of
       text.)

       Someday. Maybe.
   */
    font-family: "dominican";
}
.dd-font-dominican {
    font-family: "dominican";
}
.dd-font-icon {
    line-height: 1.15em /* this is needed for the lair boxes, at a mininum */;
}
.dd-font-icon {
    font-size: 75% /* when used together with caslon, a.k.a. dominican,
                      we need to shrink these for size compatibility.
                      Curiously, set1 and set2 require approximately the same
                      scaling, despite having separate sources. */;
    vertical-align: baseline/*whethere baseline or bottom is better actually depends on the
                              element-local font size :(*/;
    font-weight: 100 /* keep bolding from distoring these */;
}
.dd-font-icon.set1 {
    font-family: "dd-icons1";
}
.dd-font-icon.set2 {
    font-family: "dd-icons2";
}