Hi, On Mon, Nov 21, 2016 at 6:34 PM, Anton Zinoviev <an...@lml.bas.bg> wrote: > On Sun, Nov 20, 2016 at 12:14:33AM +0100, Cyril Brulebois wrote: >> >> I'm not sure what's involved to add support for those. Maybe it's >> sufficient to add two lines with the codepoint to the file you >> mentioned? > > Yes, it is sufficient, provided there is enough space in the font (only 256 > glyphs can be included).
Perfect! > On Mon, Nov 21, 2016 at 10:32:46AM +0500, Baurzhan Muftakhidinov wrote: >> >> >> Recently I loaded CyrAsia font in console, and have noticed >> >> that it misses one Kazakh letter: >> >> >> >> Ұ U+04B0 Cyrillic Capital Letter Straight U with Stroke >> >> ұ U+04B1 Cyrillic Small Letter Straight U with Stroke >> >> Also I see that currency symbols of some countries are added, >> so I would like to add Kazakh tenge as well, its code is >> >> ₸ - Unicode Character 'TENGE SIGN' (U+20B8) > > This is how you can check that there haven't been problems with space in > the fonts (after you compile the package): > > grep 'no space in the font' Fonts/*.log > > If you see no such warnings, then everything is ok. I've tried this myself > and it seems there is enough space in the fonts for these three additional > symbols. So, go ahead and add them! Should I prepare a patch for it? It is only 3 lines change. >> While we are at it, I wonder where these glyphs are taken from? >> Because in build log I see that № symbol is missing from the resulting font. >> In log file it says >> >> WARNING: U+2116: no glyph defined > > The glyphs come from the fonts in the directory Fonts/bdf. This particular > warning means that no suitable source font includes this glyph, so it has > been impossible to support it in the generated console font. > > Anton Zinoviev So how to actually add that numero sign to CyrAsia Font? Thanks,
