Hi there,
> So I was wondering - can you include support for CP1251 (as UnixFonts > hints this). > Usually our locale is bg_BG, when written in full it is bg_BG.CP1251 > Still the proper naming of the fonts is > -*-*-*-*-*-*-*-*-*-*-*-*-microsoft-cp1251 > (so the part after the dot in locale is not the same as the proper name > of the font encoding). > How are we going to solve that. I gather you need the ttftool to support cp1251, that is easy to do, I will get that done in next couple of days, I only need you to tell me what Unicode character represents character 0x98 in cp1251, for some reason it is missing in my i18n maps. If the only difference between the font encoding and the encoding part of LANG is capitalsation, it should not cause any problems, just use the version that is returned by LANG as a name for the font subdirectory. You should be able to use AW already if you have any pfa fonts encoded for cp1251 (they have to be genuinely encoded for cp1251 though, often these recoded fonts get the correct glyphs in them, but use the iso-8859-1 names for them, in which case AW cannot print with them as they are). Tomas
