<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="FreeSerif">There was a <a moz-do-not-send="true"
href="https://github.com/crosswire/xiphos/issues/524">bug report</a>
about how fonts whose names end in digits don't work. I fixed the
underlying problem of the digits and closed the report, but as I
mentioned at the end, that font doesn't actually work.<br>
<br>
I was wondering whether there was something funky about handling
font names that consist of more than one space-separated word (the
original report regarded Goudy Bookletter 1911), but that's not
the problem, because I can set "Linux Libertine O" without any
problem.<br>
<br>
Then I wondered if it was because OTF fonts weren't recognized,
but then I noticed that Linux Libertine fonts are OTF rather than
TTF.<br>
<br>
Can anyone out there experiment a bit with different fonts and try
to find the pattern for why certain fonts are effectively NOPs
(displaying some generic, ugly sans serif font) but other fonts
work just fine? My normal go-to font for Xiphos texts is
FreeSerif with occasional use of Linux Libertine, both of </font><font
face="FreeSerif"><font face="FreeSerif">which</font> work fine,
with wide charset coverage.<br>
<br>
</font>
</body>
</html>