<i>WARNING: PLEASE DO NOT RUN THIS CODE ON A HARD DRIVE, I'M NOT SURE HOW LONG IT WOULD TAKE. I USED A RAM DISK</i><p>I haven't looked at the implementation, but this seems to imply it is very I/O intensive and already takes a very long time in RAM. Yet, nothing about the problem statement suggests it would be such a task --- it sounds like something that could be very straightforwardly done completely in memory.
"This is stupid. Yeah probably, but for its very specific use case it's not terribly bad."<p>Don't put your work down like this. You created something useful for yourself, and likely useful for others. I'd be surprised if someone called it stupid.
That's great! When I first started trying to learn Chinese, I had a problem because I couldn't read the characters and sometimes couldn't copy-paste from some apps. I made a font that was similar, and then I could use the Unicode Hex Input keyboard. Your font looks so much better though!
re: license, the SIL Open Font License is common and well-accepted. <a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL" rel="nofollow">http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=...</a>
> WARNING: PLEASE DO NOT RUN THIS CODE ON A HARD DRIVE, I'M NOT SURE HOW LONG IT WOULD TAKE. I USED A RAM DISK<p>How much disk IO does this program generate? Why?<p>In any case, the OS should cache stuff and give similar performance to using a ramdisk, provided you have enough spare ram.
Might be interesting to compare SIL's "Unicode BMP Fallback Font",[1] which is significantly more compact (I believe it uses composite glyphs).<p>[1] <a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=UnicodeBMPFallbackFont" rel="nofollow">http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=...</a>
It is both reasonable and unfortunate that TrueType & OpenType fonts can have no more than 65,535 glyphs. That said, probably the logical font made of multiple physical fonts can be probably made to support all available planes.
We had a bug some weeks ago which was caused by a missing `trim` and an invisible chararcter. Our tester copied some text from a webpage which had such characters. This font is helpful in those cases.
Does anyone know the name of the app that's listing/displaying fonts? It looks pretty neat, and I haven't found anything good-looking like that for Linux/*nix.
very nice! this should be the default binary view on many, many things, especially debuggers/inspectors.<p>how does it handle combining characters? do they get everything in a single box or are going to be rendered as two boxes?