<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">follow up from previous email.</div><div class=""><br class=""></div><div class="">example of mangled font on certain size. </div><div class="">This happens for several fonts/sizes.</div><div class=""><br class=""></div><div class="">bye</div><div class="">n.</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="7D5BBBCD-C7ED-48B6-B2CA-FF02B529D2B3" width="640" height="400" src="cid:24DEB2FD-DDB5-477E-959F-CB602021AEDC" class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 7, 2019, at 11:19 AM, tim Rowledge <<a href="mailto:tim@rowledge.org" class="">tim@rowledge.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class=""><blockquote type="cite" class="">On 2019-12-07, at 8:12 AM, Tobias Pape <<a href="mailto:Das.Linux@gmx.de" class="">Das.Linux@gmx.de</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 07.12.2019, at 14:36, Thiede, Christoph <<a href="mailto:Christoph.Thiede@student.hpi.uni-potsdam.de" class="">Christoph.Thiede@student.hpi.uni-potsdam.de</a>> wrote:<br class=""><br class="">It would be great if the Trunk image would contain more sizes of this font by default, perhaps 1 to: 72 by: 1<br class="">...<br class=""></blockquote><br class="">If only "that" wouldn't take up so much money<br class=""></blockquote><br class="">I suspect you intended to type 'memory' here, but perhaps you were indeed concerned about licensing; some fonts are certainly very license/cost encumbered.<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class=""><br class="">Or could you maybe provide a dense set of generated PNGs in the release section of your repo? For all the people who don't have a mac :-)<br class=""></blockquote><br class="">Err. I am unsure whether the licenses permit that and I have no time to check.<br class=""></blockquote><br class="">There are a good number of free outline fonts available. I mentioned one source a week or three ago - <a href="http://fonts.google.com" class="">fonts.google.com</a><br class=""><br class="">Probably the best trick would be to make it easier to locate/load/process/use such fonts in normal usage. We can read TTF files pretty well (not sure if we handle all the skeleton hinting etc) and produce font glyphs at specific sizes. Caching them efficiently shouldn't be beyond the skills of such an impressive bunch of programmers. We could save the glyph data out as image segments in much the same way that we cache local MC files. Waaaaaay back in the last millennium we (as in 'exobox') did that and loading the glyphs for maybe 50 fonts/sizes from image segments took a small fraction of a second on the cheapest x86 machines of the era. Even waaaaay-er (is that word? It is now) back in time Acorn did a related thing for high quality fonts for RISC OS; render the glyphs as needed on a per-character basis, and render them separately for sub-pixle positioning. We could easily manage quarter-pixel positioning that way - remember, the Acorn machines had at max 4mb ram. we have code in the image already to do sub-pixle rendering, or at least the preferences to select it!<br class=""><br class=""><br class="">tim<br class="">--<br class="">tim Rowledge; <a href="mailto:tim@rowledge.org" class="">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" class="">http://www.rowledge.org/tim</a><br class="">Artificial Intelligence: Making computers behave like they do in the movies.<br class=""><br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>