| commit | e32bec11e6dadde05e1316f489454091ab2a5b8c | |
| author | Ben Pfaff <blp@cs.stanford.edu> | |
| Sat, 24 Jun 2023 17:04:48 +0000 (24 10:04 -0700) | ||
| committer | Ben Pfaff <blp@cs.stanford.edu> | |
| Sat, 24 Jun 2023 17:06:36 +0000 (24 10:06 -0700) | ||
| tree | 4639174fd42e6c353d08503d7e46877e9f59a4a6 | treesnapshot (tar.gz zip) |
| parent | 04401e9f1707b7b3c4ede08eaa3b18ffe754ee4e | commitdiff |
html: Include generic font-family name "sans-serif" as a fallback.
https://developer.mozilla.org/en-US/docs/Web/CSS/font-family recommends
that a font-family specification should always include one of the generic
font-family names to serve as a fallback. For PSPP, sans-serif is a
reasonable fixed fallback.
This addresses bug #63020, which asks for "Sans Serif" to mean sans-serif.
It obviously doesn't generalize to other font name translations, but it
does address the case that the bug filer complained about. If we need a
more general mechanism, we can invent it later.
Thanks to Frans Houweling for reporting this issue.
https://developer.mozilla.org/en-US/docs/Web/CSS/font-family recommends
that a font-family specification should always include one of the generic
font-family names to serve as a fallback. For PSPP, sans-serif is a
reasonable fixed fallback.
This addresses bug #63020, which asks for "Sans Serif" to mean sans-serif.
It obviously doesn't generalize to other font name translations, but it
does address the case that the bug filer complained about. If we need a
more general mechanism, we can invent it later.
Thanks to Frans Houweling for reporting this issue.
| src/output/html.c | diffblobblamehistory |