Re: Pixel-based display functions

[Lars Ingebrigtsen]

Eli Zaretskii <address@hidden> writes:

> Not really the same, but how about using
>
>   (aref char-script-table (char-after POS))
>
> to find where in the text you have characters from a different script?
> If this is fast enough, it should give you a conservative estimation
> of where to call font-at again.  (It's conservative because the same
> font can, and usually does, cover more than a single script.)

That's a very good idea; thanks.  I'll try using that as a segmenting
function and see whether this thing ends up being fast enough...

> One more issue that I think needs to be handled are characters for
> which there's no font installed on the user's system.  We display them
> as defined by glyphless-char-display-control.  Or maybe you should
> allow the text to overflow in this case: after all, it's not really
> legible, is it?

I stumbled upon this issue a couple of days ago, I think.  It was a
utf-8-encoded web page that had one iso-8859-1 character in it, and
`font-get-glyphs' returned nil for that "character" (which was displayed
as \241 or something).  But these should have a pretty predictable
width, probably.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/