From: Araki K. <ara...@us...> - 2018-11-18 13:46:19
|
Hi, From: "Yuri D'Elia" <wa...@th...> Subject: [Mlterm-dev-en] Requesting "regular" font style Date: Fri, 09 Nov 2018 12:23:32 +0100 Message-ID: <87a...@wa...> > My aafont file right now contains: > > ISO10646_UCS4_1=PragmataPro Mono > > where "PragmataPro Mono" is the family of the font. > Unfortunately, the Bold weight doesn't contain some UTF8 symbols. > As such, I'd like to do the following: > > U+2219-2219_BOLD=PragmataPro Mono Regular > > to explicitly select the regular variant as a fallback. > However, it doesn't work. I guess due to the space in the family name. > > The fontconfig spec PragmataPro Mono:style=Regular is not > accepted either as far I understood the config syntax, since ":" is > interpreted in a different way. https://bitbucket.org/arakiken/mlterm/commits/a2f8558d621ed6a9d32844996f2f17632bdedbf7 commit supports the fontconfig spec. mlterm 3.8.8 will support it. > How can I force the regular variant then? > Also, is there a better way to specify fallback fonts, like "urxvt" > does? For instance, I'd like to specify the "regular" variant if a > glypth is missing in the bold face as opposed to listing unicode ranges. Do you specify "xft" as the value of "type_engine" option? Doesn't "type_engine = cairo" improve it? If "type_engine = cairo", mlterm falls back other fonts (according to the fontconfig settings) when a glyph is missing. Regards, --- Araki Ken ara...@us... |