Typophile

node 1247

unknown

FlashMX 2004 was released yesterday. It has several new features that will be of interest to makers or users of "pixel" fonts, fonts designed to overcome Flash's text anti-aliasing.

The most obvious thing is that there is now a button to turn antialiasing off for selected text.

After playing around with the Mac version last night and this morning, I have discovered the following:

- Pixel fonts, such as those from Atomic Media, work just as well as before, if not better.

- It is no longer necessary to set horizontal and verticle text box coordinates to whole numbers to prevent "blurring." The same goes for centered or flush right text and tracking, which used to be no-no's.

- Pixel fonts may be embeded for use in "dynamic" or "input" text boxes with no ill effect. Earlier versions of Flash had a bug which caused such fonts to blur somewhat. The work-around was to set the quality level for the movie to "low," but this caused everything in the movie to be aliased--not usually the desired effect.

- In certain cases (I'm still testing this), Flash will use bitmap fonts when they exist. For example, my Anonymous font is a TrueType font with bitmaps embedded for 8, 9, 10, and 11 ppm. When these sizes are used, and antialiasing is turned off, the embedded bitmaps are used.

- Even more amazing, Flash now appears to support bitmap fonts which don't have corresponding outline fonts. Again, I'm still testing this. So far the results are encouraging, but inconsistent.

- Although not bearing directly on pixel fonts, Macromedia seems to have fixed the bug which caused high-ascii character encoding to become scrambled when using PostScript fonts with Flash.

All in all, it seems like the situation has improved drastically for people who want to use aliased text in Flash. It also appears that the situation has improved for font makers as well, giving us more flexibility in the way of format, and perhaps making some of the tricks that were necessary before obsolete.

I will continue to try things out and report anything else I find. If anyone else has been doing the same, post your findings here.

unknown

> In certain cases (I'm still testing this), Flash will use bitmap fonts

This is great news! But I do wonder what those "certain cases" are...
Whatever further you find out, definitely let me/us know!

Also: What version of Flash Player supports embedded and/or lone bitmaps?

hhp

unknown

You need the Flash 7 player. I've set up a demo here:

http://www.ms-studio.com/demo.html

If you don't want to install the new player yet (or at all), here are standalone versions:

http://www.ms-studio.com/demo.zip (for Windows)

http://www.ms-studio.com/demoProjector.hqx (for Mac)

unknown

Some more discussion about this here:

http://newsfeed.fatorcaos.com.br/000021.html

(via WhatDoIKnow.org.)

unknown

Hey, thanks for the demo!

Remaining questions:
1) When does aliasing not work?
2) What about embedded grayscale bitmaps?
3) What about fonts with only embedded bitmaps?

BTW, does all this really mean the death of pixelfont development?
Including that fancy FFF stuff? Is that why Bardram has disappeared? :-)

--

BTW, why can't I get the Windows Alt-zero method (of accessing upper-ASCII characters) to work any more? I guess I might have forgotten - how does it work again?

hhp

unknown

Just hold Alt while hitting the numeric code on your numeric keypad.
You'll have to activate NumLock, I think.
Where/when is it not working?

unknown

I just figured it out: I have to press Function along with Numlock to turn numlocking on. Darned laptop keyboard. This Compaq Presario one is particulary lousy, like it only has a Ctrl key on the left (which makes me use two hands where I could otherwise sometimes get away with one), and the space bar is tiny. Instead it has all these idiotic "special" keys, including two backslant/pipe keys! "But dude, look at all that cool fake chrome!" Puke.

hhp

unknown

The upper ascii characters won't work in my demo because only the basic stuff is embedded. Just as before, you have a choice of which characters to include. For the demo I only included the basic A-Z, a-z, numbers and puncuation--about 95 characters. If I get a chance, I'll do another one with more characters included.

About the remaining questions:
1. Aliasing always works. Apparently, Flash creates an internal bitmap font at the size requested, even if the source font has none.
2. It does not appear to support grayscale fonts :-( although they can be used as before with the antialiased setting.
3. As I said, I had some luck with fonts that only have bitmaps, but so far the results are inconsistent.

I don't think it means the death of pixel fonts, but it does offer a larger range of solutions. See Craig Kroger's message near the end of the page I linked to above.

unknown

> Aliasing always works.

Even for dynamic text? I guess like "normal" Flash font embedding, characters you haven't elected to embed simply don't show up if typed?

> It does not appear to support grayscale fonts

How did you test this? Did you make some with BitFonter? Assuming you did: So these fonts worked directly in the OS, but not Flash?

> grayscale fonts ... can be used as before with the antialiased setting.

But that's just stuff rendered from [de-hinted] outlines, right?

Sorry for the grilling! :-)

hhp

unknown

> Aliasing always works.

Even for dynamic text? I guess like "normal" Flash font embedding, characters you haven't elected to embed simply don't show up if typed?


Yes and yes.

> It does not appear to support grayscale fonts

How did you test this? Did you make some with BitFonter? Assuming you did: So these fonts worked directly in the OS, but not Flash?


I deduced this from the fact that the "grayscale" fonts being produced for use with Flash depend on its normal antialiasing in order to work. When you turn aliasing on, you are defeating this feature, therefore the trick won't work. I haven't actually tested this hypothesis or anything, which is why I included the words "appear to" in my statement. Still, I would be surprised if I am wrong about this.

I have not tried using grayscale bitmap fonts made in BitFonter. I don't know if those work with Flash, but I'm doubtful. In my demo, for example, the bitmap fonts only show up when aliasing is switched on. If you turn aliasing off, the bitmap fonts disappear. If there is an outline font, that's used. If not, the field goes blank. Flash simply ignores bitmap fonts unless aliasing is on, but that also forces the pixels to be only on or off. Also, from what I've read (see the link above again), it appears that Flash actually embeds bitmap objects rather than using the host OS's bitmap font facilities. Embedded outline fonts are handled similarly. They are not fonts so much as collections of outline objects like any other in the symbol library.

It might be worth a try, though. Just to be sure.

> grayscale fonts ... can be used as before with the antialiased setting.

But that's just stuff rendered from [de-hinted] outlines, right?


Exactly. So you would still have the same problems if you try to use them for dynamic text as before.

unknown

> that also forces the pixels to be only on or off.

How do you know, without testing it with embedded grayscale bitmaps? It's possible Flash simply uses whatever image-of-character the OS gives it, which could be a grayscale rendering.

> Flash actually embeds bitmap objects rather than using the host OS's bitmap font facilities.

Yes, but it sounds like it's initially getting the bitmap renderings from the OS (the way Pyrus FONMaker works).
This, in order to avoid:
1) Reinventing all the -patented, mind you- rendering code;
2) Maintaining all the hinting/embedding in the font within the movie for eventual real-time rendering, which would make filesizes much bigger.

I'm hopeful.

hhp

unknown

Okay, I tested it in FlashMX 2004 on OS X. Not surprisingly, since OS X doesn't support grayscale bitmap fonts, it didn't work. By that I mean the font does not display correctly at all, much less take advantage of the new aliasing feature.

(OS 9 does support grayscale bitmap fonts, but FlashMX 2004 doesn't run on OS 9. The grayscale bitmap font I tried does show up in FlashMX, but disappears when you close out the text box or the movie is published. No surprise there.)

If anyone out there is using the Windows version of FlashMX 2004, here's a Windows TTF grayscale font you can use to try it out:

http://www.ms-studio.com/FeltTipGray18.zip

unknown

:-(

But thanks for testing it, and for the font!

Hey, what about this: if somebody made a Flash movie on Windows using an embedded grayscale font, might the movie display OK on MacOS, since the OS only takes part during creation?

hhp

unknown

Mark, can you do me a big favor?

That FeltTip font works great in Word and CharacterMap, but not PhotoShop for example: you just get those boxes.

I noticed the font has small boxes in each character slot on the outline side. Maybe that's causing Photoshop to ignore the embedded bitmaps, and having the outline characters empty (or more like undefined) would fix it? So if you get a chance could you possibly make a version of FeltTip with only the bitmaps? No pressure though.

hhp

unknown

Well, yeah, that's why I posted the font. It's an empirical question. (Referring to your second most recent post.)

unknown

As for Photoshop, I don't know what's going on there. The Mac grayscale bitmap I made only sort of works in Photoshop 7 in OS 9 (it comes out somewhat distorted) and not at all in OS X. As far as I know, Photoshop uses its own rendering engine for type, not the host OS's. Hey, if you really want the grayscale font in Photoshop, just set it in Word, do a screen capture, and paste it in. ;-)

Grayscale bitmap fonts do offer some advantages, but support is a real mixed bag. I'm not planning to spend a lot of time on them myself.

Captured from web.archive.org on 16 May 2005. view this capture