On Thu, Jan 22, 2009 at 06:53:46PM +0000, corvid wrote:
Johannes wrote:
On Thu, Jan 22, 2009 at 05:57:42PM +0000, corvid wrote:
Johannes wrote:
BTW. now you can set vw_fontname in dillorc again. This font will then be used when CSS specifies "sans" as font, e.g: vw_fontname="VL Gothic"
If I put a serif font in vw_fontname and then use sans in style.css for some things, it'll use the serif font.
True. We need to make new config options
sans-serif_fontname serif_fontname cursive_fontname fantasy_fontname monospace_fontname
maybe even dropping the "_fontname" suffix.
But of course that would no longer be compatible with older versions of dillorc.
I would add the new options and remove the old options. CSS is big and certainly worth some incompatibility.
I agree with corvid. And, dillo should be able to pick some sane defaults when we figure how to deal with them right through FLTK.
Related to this, I've been wondering whether we should have a policy about the dillorc on the website -- whether it should follow tip, or follow the most recent release, or always add new options but never delete old options...
The current practice is to make it compatible with the last release, and to update the one in the source tree for those using the repository. -- Cheers Jorge.-