![]() That N means neutral: if the characters were used in an East-Asian context, an implementation could treat them as "full-width" (a misleading term for double-width). EastAsianWidth.txt (see TR11-38) has this information:ġD4A9.1D4AC N # Lu MATHEMATICAL SCRIPT CAPITAL N.MATHEMATICAL SCRIPT CAPITAL QġD49E.1D49F N # Lu MATHEMATICAL SCRIPT CAPITAL C.MATHEMATICAL SCRIPT CAPITAL D UnicodeData.txt gives this information:ġD4AB MATHEMATICAL SCRIPT CAPITAL P Lu 0 L 0050 N ġD49F MATHEMATICAL SCRIPT CAPITAL D Lu 0 L 0044 N īut refers you to the EastAsianWidth.txt file for the actual width. Uses U+1D4AB and U+1D49F, which xterm and the system agree should occupy one cell on the screen. In some cases, the system's wcwidth is not up-to-date to handle some special characters, and xterm will unnecessarily truncate the cell. ![]() ![]() Some fonts are worse than others fontconfig doesn't help in this area. For urxvt - it's probably simply ignoring the glyph, since it doesn't follow the font-metrics. fontconfig silently uses its default font for this. By the way, "fixed" is probably not an entry in fc-list output. xterm generally uses the system's wcwidth function to get a (more) correct estimate of individual character width, and when drawing characters clips, and the erroneous pixels are lost. With xterm, the problem is that the first/last characters go outside the bounding-box which xterm reads from the fontconfig metrics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |