Re: What could be missing?
Jeremy <[email protected]> Thu, 17 Feb 2011 00:56:15 -0800
| Newsgroups | gmane.editors.nedit.user |
|---|---|
| Message-ID | <[email protected]> |
On 2/17/11, Emmanuel Florac <[email protected]> wrote: > You should try running mkfontdir and mkfontscale in your various fonts > directory, for a start. That's the very first thing I did when I installed the Luxi Mono fonts (which are the ones selected in NEdit): # fc-cache # mkfontscale # mkfontdir from the directory in which the fonts were found. The fonts properly showed in the fonts.scale and fonts.dir files in that directory. I have repeated that procedure (for all fonts installed) now, just in case. But it didn't change a yota in NEdit current behavior on the laptop. On 2/16/11, Jeremy <[email protected]> wrote: > On 2/16/11, Emmanuel Florac <[email protected]> wrote: > >> Does the output of these fonts look the same in xfontsel ? > > I don't have xfontsel in either installation. The fonts (I'm using Luxi > Mono) > look great in the working installation and terrible (microscopic in size > and partly black, partly red) in the non-working one. > Upon starting NEdit within an xterm, I get the error message: > > Cannot convert [FONT NAME] to type FontStruct > > for each of the four selected fonts in BOTH the working and > non-working instances, > with NEdit working great in the first case and very poorly in the second > one. -- NEdit Discuss mailing list - [email protected] http://www.nedit.org/mailman/listinfo/discuss