Uppercase F not rendering on screen properly
Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex
Re: Uppercase F not rendering on screen properly
On 2/21/06, Rex Eastbourne [EMAIL PROTECTED] wrote: Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex I had this too. Try going into Edit-Preferences-LookandFeel-ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student
Re: Uppercase F not rendering on screen properly
John McCabe-Dansted Mon, 20 Feb 2006 15:43:56 -0800 On 2/21/06, Rex Eastbourne [EMAIL PROTECTED] wrote: Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex I had this too. Try going into Edit-Preferences-LookandFeel-ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student I reported this a while ago and got the response that it was a known bug. Though I'm pretty sure it is not a priority for 1.4. Anders Ekberg
Uppercase F not rendering on screen properly
Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex
Re: Uppercase F not rendering on screen properly
On 2/21/06, Rex Eastbourne [EMAIL PROTECTED] wrote: Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex I had this too. Try going into Edit-Preferences-LookandFeel-ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student
Re: Uppercase F not rendering on screen properly
John McCabe-Dansted Mon, 20 Feb 2006 15:43:56 -0800 On 2/21/06, Rex Eastbourne [EMAIL PROTECTED] wrote: Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex I had this too. Try going into Edit-Preferences-LookandFeel-ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student I reported this a while ago and got the response that it was a known bug. Though I'm pretty sure it is not a priority for 1.4. Anders Ekberg
Uppercase "F" not rendering on screen properly
Within LyX, my uppercase F's look like black blobs. Does anyone know of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. Rex
Re: Uppercase "F" not rendering on screen properly
On 2/21/06, Rex Eastbourne <[EMAIL PROTECTED]> wrote: > Within LyX, my uppercase F's look like black blobs. Does anyone know > of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. > > Rex I had this too. Try going into Edit->Preferences->LookandFeel->ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student
Re: Uppercase "F" not rendering on screen properly
John McCabe-Dansted Mon, 20 Feb 2006 15:43:56 -0800 On 2/21/06, Rex Eastbourne <[EMAIL PROTECTED]> wrote: > Within LyX, my uppercase F's look like black blobs. Does anyone know > of the solution to this problem? I'm using LyX 1.3.6 on Ubuntu. > > Rex I had this too. Try going into Edit->Preferences->LookandFeel->ScreenFonts and change the Roman fonts from aakar to something else (I now use URW Bookman L, DejaVu Sans, FreeMono respectively). Perhaps someone should file a bug report? -- John C. McCabe-Dansted Master's Student I reported this a while ago and got the response that it was "a known bug". Though I'm pretty sure it is not a priority for 1.4. Anders Ekberg
