Re: reducing equality tests in displaying text

[Kenichi Handa]

In article <address@hidden>, Jason Rumney <address@hidden> writes:

> Kenichi Handa wrote:
>>> Another (maybe cleaner) design would be to separate the current
>>> `has_char' function into that for font entities (font listing layer)
>>> and that for font objects (font driving layer).
>>> 
> >
> > Ah, it seems that is a good idea.  I put that in my todo list.
> >   
> Isn't encode_char sufficient for font_object use?  It will return 
> FONT_INVALID_CODE if the font does not have that char.

It depends.  For instance, Xft has two separate functions
XftCharExists and XftCharIndex, and it seems that the former
is faster.

---
Kenichi Handa
address@hidden