On 23 Feb 2003 [EMAIL PROTECTED] wrote: > > Restart xfs in a mode suitable for both CJK and non-CJK environment > if it is possible. Also try to install some TrueType font. > For Korean, you can probably tell the URL where baekmuk font > is available. For Japanese, try > http://yozk.hp.infoseek.co.jp/another/YOzFont.ZIP
Does this mean that to use our i18n-patched xforms lib, those with non-CJK environment should do all those hassles of installing TrueType fonts, and so on? This seems a bit unfair to them, then. By the way, in my machine with the TrueType fonts installed, I still have the same slowness problem as Angus machine suffers when loading i18n-xforms lib with locale set to 'C'. To remove the slowness what should I do? > > You can store XFontSet a.k.a. XOC (X Output Context) and reuse > it globally. > Right! > Now the question is: > Do we really need XFontSet? OK, Input Method needs one. > And UI code in xforms source may need one, so your conversion > of XDrawString => XmbDrawString in xforms source is a good move. > But LyX may not need one. Admittedly, at present state, > of the xforms frontend, you have to loop on a wchar string to > be drawn and switch fonts if encountered with latin characters > and numbers and then switch back later. I.e., you have to > combine a CJK font and a ASCII font manually. But you are > already doing similar thing for small cap emulation, right? > And when LyX move to Unicode with XDrawString16 for XPainter, > or if you are intending to port CJK-LyX to the Qt frontend, > such kludge will no longer be necessary with ISO-10464 encoded > fonts. You can remove CJK specific text drawing code as well > as FontLoader code from your patch and the unification of > CJK support gets nearer. > My short knowledge prevents me from understanding fully what you are saying here, but do you mean we do not need XFontSet to port CJK-LyX to the Qt frontend? Regards, cghan
