LucidaTypewriter is one of the standard X fonts. With a 0524 build I can select it in the font pref dialog and Mozilla writes this line: user_pref("font.name.monospace.x-western", "b&h-lucidatypewriter-iso8859-1"); into prefs.js but Mozilla never uses it. A little tracing shows that Mozilla does this: ............REQUEST: ListFonts sequence number: 04fe request length: 000c max-names: ffff length of pattern: 0025 pattern: "-*-*-*-*-*-*-*-*-*-*-lucidatypewriter" which is clearly wrong. I'm guessing the ampersand in the foundry name is confusing Mozilla. Eric, maybe?
odd, i had no problems changing to it. Same entry got entered in prefs.js and it displays fine as well. (I have it aliases in fonts.alias in /usr/X11R6/lib/X11/fonts/100dpi - i assume you have too however..)
I have the standard X aliases and they just map non-xlfd names to the xlfd equivalents. You have to be careful about "appears to work" and "works." I been bitten before. You really need a tool like xmon to see exactly what's happening.
well i was just judging from which font it changed to after i changed prefs, and it was lucidiatypewriter. I kept using it and had no problems. Perhaps i misunderstand this bug.
Win a few, lose most of them! I had a user.js file in the profile with some old font prefs. Renaming it fixed the problem. There's at least one bug here but I have no idea what it is. Marking this one as invalid.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.