Hi, At Wed, 29 Jun 2005 22:31:06 +0900, GOTO Masanori wrote:
> At Wed, 22 Jun 2005 18:03:55 +0100, > Martin Michlmayr wrote: > > * Fumitoshi UKAI <[EMAIL PROTECTED]> [2005-06-23 01:55]: > > > I hope so. Try "-x m17n" or "-x m17n -x xft". m17n rendering engine > > > is high priority but it may not show so good rendering result, so > > > you may need to disable it by -x option. > > > > Hmm, doesn't seem to make a difference. > > I tested mgp 1.11b-5 with my mgp file, and the result was: > > * "-x m17n -x xft" worked fine for me. > > * "-x m17n" worked: signle-byte characters were X11 helvetica (not > my specified %tfont), and Japanese characters were the default > TrueType font (not my specified %tmfont). Do you specify tfont with registry? If you specify just '%tfont "font.ttf"' then it is considered for "iso8859-1" registry. You should explicity specify registry, like "%tfont 'font.ttf' 'jisx0208.1983-0'". > * "-x xft" worked: signle-byte characters were my specified %tfont > TrueType font, and Japanese characters were the default TrueType > font (not my specified %tmfont). Same as above. > So, at least my problem was fixed with "-x m17n -x xft". Martin, how > about this analysis? > > BTW, I wonder why the useless "m17n" is enabled currently... Can we > drop it from the current Debian mgp, Ukai-san? I investigate this and it seems m17n-lib should be built with fontconfig. Currently, m17n-lib is built without fontconfig so that it failes to find any truetype fonts. Without fontconfig, m17n-lib only checks xfont and /usr/share/m17n/fonts, which doesn't exists. Regards, Fumitoshi UKAI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
