phblinn

There was a technical glitch involving the URL I gave, which caused much of the format misery, and by the time I noticed, it was too late for me edit the post to change that. So I got to sit all day Saturday as the complaints rolled in, helpless. Live and learn!

Pretty impressive, thanks! It is quite a challenge that I've been tinkering with for over ten years now, really giving Unicode a workout. Plus, often the pre-modified characters (say, for the sake of argument, "a" with an acute accent) often don't turn out well in some fonts and I would have to fix that by using the regular character plus the combining character — two Unicode entities — then manipulating the latter with inline CSS to position it pixel by pixel.

I also faced the challenge of combining Arabic and/or Hebrew (which read right-to-left) and Roman in the same line. It drove both my browser and text editor nuts. In at least one such case in the book, Mozarabic, where I needed all three, separated by slashes, I just went for the nuclear option of simply bitmapping them.

As the title implies, I was able to exploit Google's Noto series to the hilt for my book. The Cardo I'm using for the body copy (sorry that some don't care for the ligatures, which I deliberately sought) was originally a web display-only font, but that's been fixed. Also, its italics wouldn't respond to CSS; fixed, also.

Weird. Naturally it works beautifully on mine with two different browsers, though I'm not in the habit of using the page-down key. I'll have to investigate that one further, I guess.

Just fixed that. It now accommodates cell width.