> From: [email protected] > Sent: Tuesday, 22 June 2010 11:17 > > MN> In JHS, the output of < i. 2 3 has misaligned box characters. > > RS> Altering the current JHS CSS font-family setting to add another > RS> alternative font before "monospace" might be worthwhile if this > affects > RS> enough users and there is a common font on these systems that does > work > RS> ok. > > That's why I'm reporting this.
No, problem. I was just explaining that we need to know what alternative font to put in there and you're in a position to help with that. > Unfortunately, I have little clue about font issues (I'm usually a > console guy) or on CSS. If somebody can explain to me how I can > check how the sequence '"Courier new", "Courier", "monospaced"' > gets resolved into font file, we could say if the misalignment is > from a standard system font or some locally added font. > But one never knows and I'll happily research this further. Your browser will look for fonts on your system that match entries in the font-family setting, starting from the left. It will use the first one it finds. "monospace" is a generic name that refers to the font set in your browser that should be used when a monospaced font is required. You should be able to look in your browser's settings to see what font is set to be the default monospace font. In Firefox on Windows this is "Tools|Options|Content|Advanced..." , on Linux it is probably "Edit|Preferences|Content|Advanced..." You could try to substitute the font currently defined with other monospaced fonts on your system to see if one works. If it does (and is commonly installed on other similar systems) then it could be added to the font-family tag for JHS. However from what Eric is saying there may not be such a font on your system? > When the betas are done, the released version should certainly > get this font right. Two reasons: If possible I agree. However if some systems don't come with fonts that work then it may not be. Even then we can't be certain that a user hasn't altered their settings to use a font that doesn't work. As you suggest, defaulting to use ASCII box chars would be the safest option. However IMO the decision to default to ASCII should depend on how widespread this problem is likely to be, and what the target minimum system requirements for the j701 are. There has to be a cut-off somewhere, the trick as always is to find the right one! It will be interesting to see if there are any others out there with font problems? Meantime however we can still hope that there is a suitable font on your system! In the future it should be possible to solve this problem using WOFF. http://en.wikipedia.org/wiki/Web_Open_Font_Format ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
