|
Post by Spike on Sept 28, 2009 3:18:53 GMT 2
This is subtle and I surely won't blame you if you can't confirm it or don't want to try. When I use my Fony-created font in Mozilla (3.0.8), the spaces between words are extra wide. Tonight I changed Mozilla's userChrome file to specify the font I created with Fony. Now there is the same effect, especially noticeable, in the search bar and address bar.
I seem to recall reading about a field in the file that specifies the width of a space, but I can't find anything in my manuals, or in the program with which I patched font files before I ran into you. If a FON file has such a field, Fony should certainly set it; using the defined width of the space character would be fine.
No other application does this; programs like Notepad seem to do the obvious thing: spaces between words are achieved simply by rendering the space character. Likewise the message I'm typing to you right now. Any ideas?
|
|
|
Post by hukka on Oct 2, 2009 11:08:12 GMT 2
There really isn't such a field in FNT. I'm assuming other, non-Fony-created bitmap fonts render properly in Mozilla? If you can email me your font and name/send another bitmap font that doesn't have this extra space, I'll try and look into it.
|
|
|
Post by Spike on Oct 18, 2009 17:25:02 GMT 2
Thanks again for analyzing the font files I mailed and verifying that you see the problem with Spik2009. Further research--
* The problem still happens when I disable the local style sheet (Mozilla's userContent). (Predictable based on your work, as your PC doesn't have a style sheet calling for my fonts.) * The problem does not happen with Squarish.FON--This is another font, inspired by Eurostile/Microgramma, on which used Fony, among other things creating new type sizes.
Been rereading Dundera's bug report on Thread 19 here. I wonder if the fonts in Spik2009 have bad dfSize fields. (Spik2006 would not, as all I did in the bad old pre-Fony days is manually patch the pixel data inside MS Serif. I couldn't vary widths at all until I met you.)
My comment in the previous message, that the bug wasn't happening on the Fony Support Board, is irrelevant, as this dialog doesn't use my custom fonts. Cheers!
|
|
|
Post by Spike on Oct 30, 2009 5:53:36 GMT 2
I created a new Spik2010 whose space characters let me see the width of the space--and can now tell you that Mozilla separates words by rendering the space, then shifting further to the right before starting the next word. (6 pixels for 8pt, 10pt, and 12pt; 10 pixels for 14pt and 18pt; 14 pixels for 24pt).
A separate peculiarity: In this file, I selected "Windows 3.x format" for all six fonts. The file (formerly 57,808 bytes) gained about 2K. Since the Mozilla bug didn't go away, I reverted the fonts to 2.x format, and the new file size was smaller than I started with (now 57,696 bytes).
|
|
|
Post by Spike on Oct 31, 2009 15:32:27 GMT 2
Problem solved!
I varied the width of the space, but the resulting space between words didn't vary. So what Mozilla was doing was not inserting filler, but establishing a minimum space between words. For 12pt Spik2009, this was always 10 pixels. Hmm: One of the reasons I created Spik2009 etc. was to define glyphs not present in MS Serif. Had I created any of width 10 pixels? Only Euro, at character 0x80. Replacing Euro with the small vertical bar that indicates an undefined character, the problem went away.
So Mozilla seems to separate words (including nbsp) by rendering a space AND effecting a minimum escapement of the width of the glyph at 0x80. The fact that the bug occurred with Spik2009 and not other fonts INCLUDING one produced by Fony should have reinforced the notion that it could only be based on the specific glyphs in the font.
|
|
|
Post by Spike on Jan 8, 2010 2:28:49 GMT 2
Let me document a separate problem that turns out to be the same problem. My monospace "Vga2009" (before and since I placed it under control of Fony) was not resulting in typewriter-style output, either in a <TEXTAREA> in a web page under Mozilla, nor in Notepad, because spaces were too THIN. The solution again was to change "Euro" (0x80) to be the same width as the space character at 0x20.
|
|
|
Post by hukka on Jan 8, 2010 14:47:20 GMT 2
Thanks for the information. I should probably put that in a FAQ at some point.
|
|