css and font specification [Re: Dillo2 + FLTK2 + NxLib running on mips linux]
----- Forwarded message from ?? ? -----
I have try current version dillo + fltk base on X11 in X86 PC (Ubuntu) with LC_LANG=zh_TW.UTF-8.
Using default font_xxxx I can see chinese text and write chinese characters to text editor also works.
But, I cannot see any chinese text after google search ??? The same URL works on dillo + fltk base on nxlib.
What I think is the FLTK already supports multi bytes characters well. The problem is caused by others (I mean fonts / X11 configuration etc.) Am I right ?
(This came with screenshots showing that www.google.com.tw doesn't work.) If dillo doesn't parse embedded css, it works for me. The "body,td,a,p,.h{font-family:arial,sans-serif}" in the page overrides my font_* prefs. So I tried to add a !important rule to set font-family in style.css, e.g. * {font-family: "Bitstream Cyberbit" !important} but either it's impossible or I was getting the syntax wrong somehow. (This is not necessarily the same problem he's having, but...)
On Fri, May 08, 2009 at 03:27:56PM +0000, corvid wrote:
----- Forwarded message from ?? ? -----
I have try current version dillo + fltk base on X11 in X86 PC (Ubuntu) with LC_LANG=zh_TW.UTF-8.
Using default font_xxxx I can see chinese text and write chinese characters to text editor also works.
But, I cannot see any chinese text after google search ??? The same URL works on dillo + fltk base on nxlib.
What I think is the FLTK already supports multi bytes characters well. The problem is caused by others (I mean fonts / X11 configuration etc.) Am I right ?
(This came with screenshots showing that www.google.com.tw doesn't work.)
If dillo doesn't parse embedded css, it works for me. The "body,td,a,p,.h{font-family:arial,sans-serif}" in the page overrides my font_* prefs. So I tried to add a !important rule to set font-family in style.css, e.g. * {font-family: "Bitstream Cyberbit" !important}
Hm, this seems to work fine for me. Maybe you have other stuff in your style.css that confuses the CSS parser?
but either it's impossible or I was getting the syntax wrong somehow.
Looks ok to me and works here. What does xlsfonts | grep -i cyberbit say? Cheers, Johannes
Johannes wrote:
Hm, this seems to work fine for me. Maybe you have other stuff in your style.css that confuses the CSS parser?
Yes, it turns out to have been an error in my style.css. The previous rule was commented out, but I used html comment delimiters instead of css comment delimiters. Sigh... Sorry about that. All is well now.
On Fri, May 08, 2009 at 07:59:43PM +0000, corvid wrote:
Johannes wrote:
Hm, this seems to work fine for me. Maybe you have other stuff in your style.css that confuses the CSS parser?
Yes, it turns out to have been an error in my style.css. The previous rule was commented out, but I used html comment delimiters instead of css comment delimiters. Sigh... Sorry about that. All is well now.
Not quite.... Html comment delimiters should be completely ignored by the CSS scanner/parser. With the re2c implementation that did work, but it is missing from the current scanner.
participants (2)
-
corvid＠lavabit.com -
Johannes.Hofmann＠gmx.de