After my last post I was pretty clear on how evas font searching worked and how it could benefit from FontConfig. So, I knuckled down and put the fontconfig code into evas.
After initial testing in E17 I was disappointed to find that edje text classes were broken. The problem was that whenever a reference to an edje would be given up (when removing a border) all of the text classes would be wiped out. I found a problem with this and seem to have fixed it. The latest changes are in CVS.
Now, E17 does not have to install anyfont. This is good because now we don't have to install and package CJK fonts, which was an issue we have been working on for a long time. Of course, the old methods of font loading are still working as always.
My Font Setup
[shorne@Asus themes]$ enlightenment_remote -font-default-list REPLY <- BEGIN REPLY: DEFAULT TEXT_CLASS="menu_item" NAME="Sans" SIZE=9 REPLY: DEFAULT TEXT_CLASS="move_text" NAME="monospace" SIZE=12 REPLY: DEFAULT TEXT_CLASS="resize_text" NAME="monospace" SIZE=12 REPLY: DEFAULT TEXT_CLASS="title_bar" NAME="Serif" SIZE=12 REPLY: DEFAULT TEXT_CLASS="default" NAME="Serif" SIZE=12 REPLY <- END [shorne@Asus themes]$ enlightenment_remote -font-fallback-list REPLY <- BEGIN REPLY <- END
Screenshot