Recent Posts

Hello,

Here's a screen shot:



My question: Everywhere that there's not a character, should I fill that in with a null character?

Reason why I ask: In a previous dingbat font I created, when typing, the program would switch to a default font if I typed a character that did not contain a dingbat. This would be annoying because I would be constantly switching from the defautl font back to my FLS-created font.

Any tips?

Thanks a billion!

Cheers,
Micky

Here is the full list of folders and files to remove. But note that they also can be used by other Fontlab products if installed (e.g. Fontographer, TypeTool, TransType, BitFonter, ScanFont etc.)

Folders:
HD/Library/Application Support/FontLab/
Users/~/Library/Application Support/FontLab/

Files:
HD/Applications/FontLab Studio 5 or FontLab Studio 5 DEMO
HD/Library/Preferences/com.fontlab.fs5m.lic (if the full version was activated)
Users/~/Library/Preferences/com.fontlab.studio5.plist or com.fontlab.studio5.demo.plist

Mac OS X might also keep these files in the hidden folder /private/var/db/receipts/:
com.fontlab.studio5.demo.pkg.bom
com.fontlab.studio5.demo.pkg.plist
com.fontlab.studio5.pkg.bom
com.fontlab.studio5.pkg.plist

Hi Alex!

Thx for the Help!

Yes, you can.

Don't worry. Not a problem at all.

Thanks!

Suddenly, unable to type additional glyphs in classes window.  I can type them, but the approve button is greyed out and does not work.

I'm using ScanFont 5 with Snow Leopard successfully, but have not upgraded to lion because I value ScanFont more.  After upgrading to Snow Leopard, there are some issues with ScanFont (hence the fear of upgrading to lion).  They can be resolved or worked around with a little help.  You may have some icon problems, but who cares. Most notably, for me, you loose the ability to open files by dragging them onto the ScanFont icon (you have to use the "open" command in scanfont).  It's not a horrible glitch, just changed 1 step of my workflow.  Also, expect frequent crashes if your merging and deleting cells quickly.  Work slower, and you'll be fine.  Finally, unless you install/use "rosetta" (fontlab sent instructions about this prior to the SN release/upgrade) SF will be very crash-prone (exporting, selecting the 'scale tool', etc).

As mentioned, most of this is minor and after getting used to minor workflow changes I'm still using (and loving) SF just fine.  Wish I knew what would happen if I upgraded to Lion, but i'm not willing to take that risk until I know it can be done without major problems.

Scanfont is truely a one-of-a-kind app... my business (and family) depend on it (I would pay yearly to upgrade/use it).  I, too, hope that lion has not killed any further development. I'd rather have scanfont than lion, but as years and operating systems come and go I fear I'll need to find a replacement.

If so, is there anything else out there that will easily export several paths/glyphs to typetool or fontlab in a couple clicks (vs. cutting and pasting each path/glyph individually from illustrator)?

Miguel,

did you see this behavior in earlier builds?

A.

If I use this option of fontographer can I rename the glyph to (example) A.alt1 o a.alt2 ---- etc...




Thanks!!!

Thanks Alex
Yes, I got this info earlier. I does seem to have fixed the problem.
Best wishes
PF