Iosevka not considered monospace by Freetype about iosevka HOT 10 CLOSED

Is is caused by the double-width characters and Latin ligatures in it? They are designed to provide CJK compatibility.
What's the result if you manually delete them?

from iosevka.

@gber I have checked the source of libfontconfig, and it is really caused by full-width characters included within it. In the next release I will separate Iosevka into three variants:

• Iosevka — Single-width only.
• Variant Iosevka CJK — Iosevka and full-width characters.
• IosevkaCC — Contains full-width characters and enwiden symbols.

from iosevka.

Yep, I tried with only the Latin Extended subset and that is indeed then recognized as monospace.

from iosevka.

@gber Could you please try to build the newest snapshot in master and checkout whether the ttf files in build are recognized as monospaced?

from iosevka.

This is the result from my friend's test.

from iosevka.

I can't get it to build and don't know enough about node (might be the outdated distro-provided fontforge version). Could you upload the built font somewhere?

from iosevka.

The above looks right, 100 means mono, so it should be OK.

from iosevka.

@gber http://pan.baidu.com/s/1i38SZ5r
You can download and test it.

from iosevka.

Thanks, fontconfig/Freetype indeed now considers it monospace and it is also rendered correctly via Xft. Awesome, thanks for the quick response!

from iosevka.

@gber Okay, the fix will be published in the next release. Closed.

from iosevka.