well I tried many ways and that way worked best. The point of a pixel font is to be good quality while small. As this was the problem with standard fonts. The font used in the header for the tutorial uses the same method and I can't see the line.....can you?
How do you do it?
If you follow the ultrashock tutorial it fills the holes in when dynamic or embeded or published. So the solution I found was to open the hole slightly....this stopped the fill.
yes sometimes when i use certain pixel fonts in my flash movies and i test it the fonts ilke "o" "d" or the other ones which are kinda hollow in the middle well the get filled with color.
what should i do?
i've made 4 fonts now and they work great!!
one thing though - you say open the "holes" by a "very small amount" -- when i zoomed right in and opened it the tiniest amount possible they still filled in. i now click the offending points and move them with one press of an arrow key. it looks like a lot on screen but you can't see the gap at all. works every time.
Flash already has anti-aliased text. That's what smooths the fonts and lines and everything onscreen. But for small fonts you want to get rid of that to make it clearer. It's what pixel fonts are avoiding. So what is MX4 adding?
Originally posted by bart otj Flash already has anti-aliased text. That's what smooths the fonts and lines and everything onscreen. But for small fonts you want to get rid of that to make it clearer. It's what pixel fonts are avoiding. So what is MX4 adding?
i think he just made a typo. i think he means anti-anti-aliased, or aliased.
you can only prevent the 'fill' by open a gap by 3 points.i tried opened 1&2 point but it still fill in.other way if you don't want to open a gap but want to have it unfilled is to make the font dynamic.it's filled if you put that font in static mode.
Originally posted by richblend i think he just made a typo. i think he means anti-anti-aliased, or aliased.
true. they're obviously not obsolete now though, like frets explained. i haven't atually tested the "don't antialias" feature on many regular fonts, but the picture you show of arial doesn't look so bad at all in my opinion.
in the fonts-for-flash manual it suggests using the "don't antialias" feature in mx2004 on pixel fonts, just so you don't have to worry about getting them bang on an exact pixel. i've used it a few times when i want such a font centred (and when i know i need the flash 7 player - otherwise i'll do it manually).
as for how much gap to have between joining parts of a character, i bought some fff fonts and took them into fontographer to have a look what they did. they seem to cut out a little corner rather than move a whole edge. i'll post a screenshot if anyone is interested. in some cases though i couldn't understand what was happening. i really don't know what i'm doing on fontographer though - i just follow the tutorial (mostly - explained in a sec) and it all seems to work.
the part of the tutorial i don't follow is the kerning instructions. if you follow the kerning instructions you will find that if you type two successive characters of the alphabet, for instance "hi", they will have no space between them. this is because following the tutorial lines up all the characters of the alphabet and puts no space between them, but leaves all other combinations. if you leave all kerning at 128 (minus a few others - for some fonts you want a letter after q to be a little closer than it would be in this case - things like that) everything should be fine. maybe i should just rtfm though, that might explain what i'm doing.