On 11/20/19 4:46 AM, Antonis Tsolomitis wrote: > > OK then. You asked for suggestions, you have at least one :-) > > The Go fonts. >
Ahh... What I was asking for suggestions on was a good font.aliases file for CDE (bitmap) fonts, that are as complete as possible in terms of utf8 glyph coverage. :) XFT has "issues" in CDE that someone needs to investigate/fix before it can be really used by default. Until then, bitmaps it is... -jon > Antonis. > > > On 19/11/19 8:28 μ.μ., Jon Trulson wrote: >> On 11/19/19 8:55 AM, Antonis Tsolomitis wrote: >>> I did not understand... does it (or will it) support ttf fonts? >>> >>> If so, then I think that the go fonts from >>> https://blog.golang.org/go-fonts >>> >>> is a great choice. Because they are of high quality, from a >>> great font designer (Bigelow), and are related with the history of CDE >>> as it was using Lucida on Solaris. >>> >>> The go fonts support many-many codepages including Cyrillic and Greek. >>> >> Motif can support TTF via the XFT library, which means that CDE can too: >> >> https://sourceforge.net/p/cdesktopenv/wiki/FontsWithXFT/ >> >> -jon >> >> >>> Antonis. >>> >>> >>> On 19/11/19 2:51 π.μ., Jon Trulson wrote: >>>> Hi, >>>> >>>> I've just merged the utf8-conversion branch to master. This branch >>>> converts the languages from ISO8859-1 to UTF-8. This was done for the >>>> message catalogs, resources and other related files. >>>> >>>> However, documentation (help, manpages, and the dtinfo guides) are still >>>> always built using the ISO8859-1 locales. >>>> >>>> To support UTF-8 documentation, our docbook sources and text need to be >>>> updated to something from this century, and ideally from this decade. >>>> In addition, a conversion to XML would also be required as a result. >>>> So, until that happens, we still need ISO8859-1 for the docs. This also >>>> means viewing the docs while in a utf8 locale may show anomalies as >>>> non-utf8 8 bit sequences might not be rendered properly. >>>> >>>> I had tried to convert the docs blindly to utf-8, which worked fine >>>> initially, but the tools we are using crapped out all over the place, >>>> and especially instant (used to create the help text) crashed quite >>>> frequently. I hate instant. >>>> >>>> So, I decided not to 'hack' it - it needs to be done correctly. >>>> >>>> There are undoubtedly some issues with this conversion - for example >>>> dtterm does not handle UTF-8 sequences properly where 2 or more >>>> characters are supposed to be drawn in the same cell (overlay ed) for >>>> example. As always, patches welcome. >>>> >>>> A choice of good ISO10646 X11 fonts also needs to be selected. Ideally >>>> fonts that look decent and have a good coverage of the utf-8 character >>>> space and will work properly with CDE's rather awkward font configurator. >>>> >>>> It would be good to explore XFT on CDE too, as this can help - it can >>>> select glyphs from other fonts if a font you are using does not support >>>> a glyph, for example. Plus all that anti-aliasing goodness, and the >>>> generally better quality and completeness of TTF fonts. >>>> >>>> But, if anyone has suggestions for good fontsets we can configure CDE >>>> with (via cde's fonts.alias files), let us know. >>>> >>>> Since at least linux and the BSD's are using essentially the same X11 >>>> environment and software, we should be able to come up with something >>>> that will work for most users out of the box. >>>> >>>> > -- Jon Trulson "Entropy. It isn't what it used to be." -- Sheldon _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
