From: Jungshik Shin <[EMAIL PROTECTED]>
I'm sorry I forgot that I always had built Mozilla with a patch
that went into the trunk only a few days ago. That patch was made so
long time ago (and it's only necessary for Devanagari but not for Tamil)
that it was taken for granted by me, but it was not in the tree until
a few days ago. The patch to apply (you only need to apply the patch
if you download 1.6b release source instead of the CVS trunk source)
is available at http://bugzilla.mozilla.org/show_bug.cgi?id=203406
(the last patch uploaded there).
BTW, X11core build doesn't need this patch to work although with the
patch, it works better.
Aha. So Mozilla-1.6b fails but CVS should work.
First tried that patch, but it had some rejects, and after
hand-applying it things still failed. So, got a CVS checkout
and all worked as it should. Excellent.
(That is, the --enable-ctl --enable-xft works fine.
Have not tried the --enable-ctl version.)
Andries
[By the way, --enable-ctl is documented as
"Enable Thai Complex Script support". That should perhaps
be changed, as no Thai need be involved. I see
const char*
nsULE::GetDefaultFont(const PRUnichar aString)
{
if ((aString >= 0x0e01) && (aString <= 0x0e5b))
return "tis620-2";
if ((aString >= 0x0901) && (aString <= 0x0970))
return "sun.unicode.india-0";
return "iso8859-1";
}
so maybe Thai should be Thai/Devanagari.]
[The next step is vocalized Hebrew. Is the theory that it should
not work at all? What I get is a rendering with vowels in their
own space instead of on top / below the corresponding consonants.]
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
