Created attachment 82590 [details] facebook languages selection [freetype backend] In Windows freetype can display CJK properly when Pango fail. But in return Freetype fails on Hindi and Arabic when Pango thrive. Arrgh.. Is this happened to Linux? if not what can I do?
Created attachment 82591 [details] facebook languages selection [pango backend]
version: webkitgtk+ 1.2.7 with glib unicode backend
I think it is just font selection matter as not all arabic pages failed. This one works: ayaspell.sourceforge.net
google.co.jp which failed to render on Pango can be fixed if in the font-family css prepended by japanese font "MS PGothic" How this achieved from inside webkitgtk?
My guess is fontconfig or webkitgtk in Windows didn't match the meta lang id with system's fonts. For ex. it would pick Verdana which don't have lang=ar over Arial which have when rendering arabic pages (clearly defined lang=ar). I thought that what fontconfig have to deal with? or not? Why would I even need to override the preference from fonts.conf? Is there another good browser with fontconfig/freetype backend on Windows? I have Mplayer that use fontconfig to pick which font to render subtitle but also come with fairly standard fonts.conf so I doubt this is fontconfig fault... In other hand, how to make pango works without doing my previous comment#4? Pango lack of CJK (Korean is displayed but with wrong hint) in Windows.
Setting alias override in fonts.conf like this solve arabic and some indics: <alias> <family>sans-serif</family> <prefer> <family>Tahoma</family> </prefer> </alias> remaining failed fonts are: Kannada Gujarati Telugu Bengali Sinhala Myanmar Laos probably more those still failed even when Windows XP has the fonts (showing numbered matrices rectangle). Any idea is this fontconfig or webkitgtk issue?
apparently the mismatch is because pango's builtin_aliases in pango-utils.c use obsolete unicode fontlist. Here is my pango.aliases to display all supported indic languages (with freetype as backend): tahoma = "arabic typesetting,arabic transparent,tahoma,lucida sans unicode,browallia new,dokchampa,daunpenh,mingliu,simhei,gulimche,ms gothic,mongolian baiti,microsoft phagspa,microsoft tai le,kalinga,iskoola pota,vrinda,raavi,mv boli,gautami,tunga,shruti,kartika,latha,mangal,nyala,plantagenet cherokee" tohoma here refer to tahoma override in fonts.conf file previously new in XP SP3: indic: vrinda,raavi,mv boli,gautami,tunga,shruti new in Win7/Vista indic: iskoola pota (sinhala) and kalinga (oriya) america: plantagenet cherokee ethiopian : nyala SE asia: dokchampa (Laos), daunpenh (Cambodia) arabic: arabic typesetting central asia: mongolian baiti,microsoft phagspa,microsoft tai le my question now: which used by webkitgtk actually? pango, fontconfig or both? also if I add additional font search path (for other missing unicode fonts) in fonts.conf, pango didn't respect this like they were work independently and clashed each other. To prove this: I add other search path (which contain only sinhala font) in fonts.conf and remove WINDOWSFONTDIR. I can see wikipedia page still display arabic which prove pango used here. However if I remove all search path webkitgtk refuse to run.
Created attachment 86292 [details] freetype backend with tahoma override in fonts.conf and updated pango.aliases
It's the obsolete pango.aliases issue