Mike FABIAN wrote:
>Pablo Saratxaga <[EMAIL PROTECTED]> さんは書きました:
>
>
>
>>Also, Xft allows to define "virtual fonts" created from a list of other
>>fonts; "Sans", "Serif" and "Monospace" come in standard.
>>
>>
>>
>~/.fonts.conf
>
>
I guess Pablo meant something like the following
but this doesn't work the way he (and
I) wrote it would if only Xft APIs are used(see below). For instance,
'monospace' is a 'virtual' font defined as
<alias>
<family>monospace</family>
<prefer>
<family>Luxi Mono</family>
<family>Nimbus Mono L</family>
<family>Kochi Gothic</family>
<family>ZYSong18030</family>
<family>AR PL SungtiL GB</family>
<family>AR PL Mingti2L Big5</family>
<family>Gulimche</family>
<family>Andale Mono</family>
<family>Courier New</family>
</prefer>
</alias>
>>and define some pseudo-fonts you want.
>>
>>
>How does that work? I didn't know that it is possible to define
>"virtual fonts" from a list of other fonts using fontconfig/Xft2.
>
>
>But I don't yet know a *simple* way to achieve that by using only Xft2.
>When using something like
>
> xft_font = XftFontOpenPattern(dpy, pattern);
>
>
I guess you have to call fontconfig APIs(e.g. FcFontSort) directly
and do manual break-up of your input text into mutilple pieces
to be rendered by one of fonts returned (by FcFontSort) depending
on their coverage. And, you know this *complex* way, don't you?
>I always got exactly one font. Are you saying that it is possible to use
>more than one font with a single call to XftFontOpenPattern()
>by doing some setup in ~/.fonts.conf?
>
>
I think Pablo mistook what fontconfig does for what Xft does unless
I'm missing something Pablo knows. I also plead guilty of making
a similar mistake when I wrote abuot working-around a hard-coded
font name in a Window manager and a theme (e.g. Courier)
Jungshik
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
