AFDKO 2.0 : Post your feedback here

Primary tabs

105 posts / 0 new
Last post
Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
AFDKO 2.0 : Post your feedback here
0

If you're using the new [[AFDKO]] (v2.0), we would like to hear your feedback. Please use this thread for your comments, wishes, concerns, bugs found, and/or anything related with the tools contained in the new AFDKO. Thanks!

Andreas has already started.

Andreas Seidel's picture
Offline
Joined: 8 Mar 2002 - 3:44am
0

Overall, it runs and I'm able to compile the projects from 1.6.

I like to know how to set up usWinAscent and usWinDescent.

table OS/2 {
TypoAscender 765;
TypoDescender -235;
TypoLineGap 250;
usWinAscent 900;
usWinDescent -350;
} OS/2;

This is not working, why?

1. the mystery of -nr

If I use a project file I got lots of the time: [FATAL] unrecognized option (-nr).
Now I found out it its related to the option:
ReleaseMode true
But if you set it to false, the -nr fatal error comes up. So better use
#ReleaseMode true (vs) ReleaseMode false

2. relative paths under windows only by using -fp option with *.fpr file.

3. This message seems to be a general one since it comes everytime. Can we turn it off since its not specific to the font?

makeotfexe.exe [NOTE] There are -12851 instances of the deprecated “except” syntax in the feature file. Though such statements are processed correctly by this parser for backward compatibility, please update them to the newer “i gnore substitute” syntax. For example, change “except a @LET sub a by a.end;” to “ignore sub a @LET; sub a’ by a.end;”. (Note that the second rule is now required to be marked to identify it as a Chain Contextual and not a Single Substituti
on rule.)

So far I tested the makeotf programm only.

The FontLab scripts installer seems not to work under python 2.2 win xp.

line 134 and 105
NameError: global name '__file__' is not defined

So I tryed to move the files manually. No script is running. Maybe this is related no path was added to the python site packages by the installer. So what path should we set manually?

Example, the Auto-Hint script

Traceback (most recent call last):
File "", line 70, in ?
ImportError: No module named string

win xp sp2, FL5, Python 2.2

--astype.de--

Chris Lozos's picture
Offline
Joined: 25 Feb 2004 - 11:00am
0

Bravo Miguel. I look forward to giving it a spin.

ChrisL

Karsten Luecke's picture
Offline
Joined: 6 Aug 2005 - 8:41am
0

> [...]
> usWinAscent 900;
> usWinDescent -350;
> ) OS/2;

The Feature File Syntax says:
winAscent
winDescent

Andreas Seidel's picture
Offline
Joined: 8 Mar 2002 - 3:44am
0

and makeotf says:
syntax error at "WinAscent" missing "}"

ok fixed, since "WinAscent" is not the same like "winAscent" :-)

I miss to give the makeotf the path and name of the fontinfo file. Is it no longer needed?

BTW. Its not commen this file is called "fontinfo" everytime and placed in the path of yourfont.pfa. For example I call it _fontinfo.txt. Other developers place it under other paths call it with an other name. So if the new FDK is looking "hard coded" for "fontinfo" it can't find it.

My first impression is, in points of usability, this fdk has some serious back steps compared to 1.6. Its bound the developers special workflow. :-(

--astype.de--

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

Hi Andreas,

As Miguel has noted, the correct feature file keywords are described in the file "FDK/Technical Documentation/OT Feature File Syntax.html"

The "fontinfo" file is no longer required, and when used, makeotf pays attention to only a few parameters. The way things work now is that makeotf will llook , in order, in three sources for parameters settings:
- the fontinfo file, if there is one
- the project file
- the command line
If the different sources specify different settings, the last one seen wins.

If you use a project file, you have no need to use a fontinfo file at all, and would do better to not have one, in order to avoid possible conflicting options. I agree that if you *do* use a fontinfo file, it would be better to be abel to specify a path - I will add this to makeotf with the next bug fix release.

I am pleased to hear that you do use the project files. I thought it would be useful to have this option, but no one at Adobe uses them, and your e-mail is the first evidence that I have seen that anyone else does, either. I wil llook into the '-nr' problem under Windows.

The easiest way to supress the complain about use of the 'except' clause in in the feature file is to change from using "except' to 'ignore".

- Read Roberts

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

i experienced the same problems with the scripts as andreas described; any solutions yet?
t.

Blank's picture
Offline
Joined: 25 Sep 2006 - 2:15pm
0

I’m a little behind the curve, but thought this might be useful to others. I was having horrible problems with my outlines getting mutilated by my laser printer. It turns out that the Fontlab’s autohinter was doing some really nasty stuff and the bad hinting was screwing up my laser printer output. Switching to the Adobe autohinter solved my problems.

Of course, not using a crappy printer would have prevented this from ever being a problem, but that’s another story…

Rachel Roberts's picture
Offline
Joined: 21 Feb 2007 - 12:23pm
0

I'm getting some outputs I never seen before when running the outline check

glyph U.
looking for coincidentpaths ...
removing any intersections...
inspecting/repairing paths...
checking path directions...
glyph V.
looking for coincidentpaths ...
removing any intersections...
inspecting/repairing paths...
checking path directions...
glyph W.
looking for coincidentpaths ...
removing any intersections...
inspecting/repairing paths...
checking path directions...

I'm getting the same results on most glyphs. Can anyone explain this and is it something I should be worried about

Rr

Uli Stiehl's picture
Offline
Joined: 1 Feb 2006 - 8:02am
0

Some remarks on the Autohint function of Adobe's FDK 2.0

Here are a few tech notes, which may (or may not) be useful for typophiles:

1) The first version, i.e. FDK v2.0 Aug 31 2006 build 21 (FDK2.0-WIN.zip, file size ca. 14.4 MB), was faulty. It did not work on my Windowx XP machine.

2) Yesterday, I installed the current version, i.e. FDK v2.0 May 5 2007 build 26 (FDK2.0-WIN.zip, file size only 9.8 MB).

3) The current versions runs in the DOS box of Windows XP (but not in the DOS box of Windows 98, which I also tested).

4) After unpacking the zip file FDK2.0-WIN.zip into the folder c:\fdk, I switch to the DOS box (i.e. cmd.exe) and select the FDK folder via cd c:\fdk and then set the FDK program folder via path=c:\fdk\tools\win.

5) After copying the font to be autohinted into the FDK folder under the name c:\fdk\font.pfa, I start autohint by autohint -a font.pfa, which results in the hinted font saved under the same name font.pfa.

Now a few remarks on the Autohint function:

Adobe's FDK autohint function is of very high quality, but it seems to be geared to Latin fonts only, for the autohinting quality heavily depends on the x-height, ascender etc. alignment zones (which do not exist in most non-Latin fonts, e.g. in Indic fonts, so that it is unclear, how such non-Latin fonts could be hinted with FDK).

I compared the autohint function of Fontlab 4.6 with the autohint function of Adobe's FDK. It is astonishing that exactly the same font with exactly the same alignment zones and exactly the same vertical and horizontal stem widths has entirely different autohinting results in Fontlab, as compared with Adobe's FDK. Especially, Fontlab 4.6 does not seem to handle vertical stem widths properly:

a) The screenshot http://www.sanskritweb.net/temporary/fdk.jpg shows that Fontlab makes some vertical stems too thick, wheareas Adobe's FDK autohint function streamlines all vertical stems. This screenshot was made without font smoothing.

b) The PDF http://www.sanskritweb.net/temporary/fdk.pdf can be used for testing font smoothing, which, if switched on e.g. in Adobe Acrobat Reader, alleviates the Type 1 autohint deficiencies of Fontlab 4.6, which may (or may not) have been remedied by a later release of Fontlab.

Chris Lozos's picture
Offline
Joined: 25 Feb 2004 - 11:00am
0

FontLab 5 hinting is an improvement over 4.6 as well.

ChrisL

Chris Lozos's picture
Offline
Joined: 25 Feb 2004 - 11:00am
0

James,
Your potential clients may also have "crappy printers" so it may be well that you went through the process.

ChrisL

Andreas Stötzner's picture
Joined: 12 Mar 2007 - 10:21am
0

Can anybody here recomend a viable how-to intro for building up OpenType features?
Perhaps I’m the idiot on this thread, but I’d like to manage it, as a type designer who is not a technician …
Thanks for any advice.

Jason Pagura's picture
Offline
Joined: 10 Sep 2006 - 6:19pm
0

Is it possible to use the AFDKO scripts through FontForge (through X11 on Mac OSX 10.4.9), rather than just FontLab?

If so, how, or which chapters of the manuals do I need to look at?

Or am I totally misunderstanding how this whole thing works?

Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
0

I'll take this opportunity to point out that the Autohint macro will not apply Flex hints, whereas the Autohint you can run from the command line does.

Tim Ahrens's picture
Offline
Joined: 28 Sep 2004 - 9:15am
0

[edit]

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

great, thanks adobe, thanks miguel and read!

Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
0

Andreas, the OT Feature File Specification is available here http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html

And on this page http://www.adobe.com/devnet/opentype/afdko/ you'll find a link to ExampleRomanFonts.zip which you may use as a guide.

William Berkson's picture
Offline
Joined: 26 Feb 2003 - 11:00am
0

Where do I put the "example font sources" folder on my PC so that I can see the Minion example in Font Lab?

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

I am implementing support for the mark attachment lookups in the "Adobe FDK for OpenType", specifically the makeotf program. An area of difficulty is representing the mark-attachment rules within a contextual string, as one or more mark glyphs may appear between the base glyph and the attaching mark class. In order to make it easier to read and write such rules, I propose the following syntax. This differs from the previously published feature file syntax in requiring a lookup-type keyword in each statement. This makes it easier to distinguish glyphs which are part of the mark attachment rule from glyphs that are only part of a context.

1) Mark class definitions.

mark <glyph class list> <anchor x1 y1> @<mark class name;

Example:

mark [acute grave] <anchor 300, 0> @TOP_MARKS;
mark [dieresis umlaut] <anchor 40, 0> @TOP_MARKS;
mark [cedilla hook] <anchor 200, -50> @BOTTOM_MARKS;

Note that each mark class definition statement can specify only one anchor point. However, you can additional glyphs with different anchor points to a mark class definition by adding additional statements for that class.

2) cursive attachment (GPOS Lookup Type 3)


position cursive <base glyph or class> <anchor x1 y1> <anchor x1 y1>;

Example:

position cursive [m.final n.final] <anchor 0 -50> <anchor NULL>;

This defines a glyph class containing the two glyphs, n.final and m.final, designed for use at the end of words. The second anchor is NULL, as there is no exit attachment point.

3) Base to mark attachment (GPOS Lookup Type 4)


position base <base glyph or class> <anchor x1 y1> mark <mark class name>;

Example:

position base [a e o u] <anchor 300 500> mark @TOP_MARKS;
position base [a e o u] <anchor 300 -50> mark @BOTTOM_MARKS;

Note that each statement specifies only one attachment point on the base glyph or glyph class; you must provide as many statements for the base glyph or glyph class as there are real attachment points.

4) ligature to mark attachment (GPOS Lookup Type 5)


position ligature <base glyph or class>
<anchor x1 y1> <anchor x2 y2>... <anchor xn yn>
mark <mark class name #1>
<mark class name #2>...<mark class name #n>;

Example:

position ligature [oe ue] <anchor 350 400> <anchor 650 400>
mark @TOP_MARKS @TOP_MARKS;
position ligature [oe ue] <anchor 350 -50> <anchor NULL>
mark @BOTTOM_MARKS;

There must be as many anchors specified as there are ligature components. There must be as many attaching mark classes provided as there are non-NULL anchors. Each statement specifies only one attachment position on each ligature component; you must provided as many statements as the maximum of the number of attachment points on any ligature component.

5) Base to mark attachment (GPOS Lookup Type 6)


position mark <base glyph or class> <anchor x1 y1> mark <mark class name>;

Works just like the base-mark statement.

6) Contextual forms.

For all these statements, the contextual form allows glyph context strings before the lookup-type keyword, before the 'mark' keyword, and after the mark class(es).

position A1 A2 ..An
<lookup-type> <base glyph or class> <anchor x1 y1>+ B1 B2...Bn
mark <mark class>+ C1 C2...Cn;

The glyph or glyph class immediately following the lookup-type keyword is taken as the base glyph, and this must be immediately followed by the anchor clause(s).

The glyph class(es) immediately following the 'mark' keyword is assumed to be the attaching mark class, and must be of a mark class type.

If no glyph or glyph class items are marked as part of the contextual input string, then the attaching mark class will be used as the single item in the input string.

Any glyphs marked as part of the input string must be consecutive, and must include the attaching mark class.

Example:

position T base [a e o u] <anchor 300 500>
mark @TOP_MARKS' @BOTTOM_MARKS;

This contextual statement will match the single-glyph sequence of "@TOP_MARKS" when preceded by the backtrack string "T [a e o u]" and followed by the lookahead string "@BOTTOM_MARKS". It will advance the current context by just one glyph; subsequent rules will be trying to match at @BOTTOM_MARKS.


position T base [a e o u]' <anchor 300 500>
mark @TOP_MARKS' @BOTTOM_MARKS';

This contextual statement matches in the same context as above. The difference is that a sequence of three glyph or glyph classes ("[a e o u] @BOTTOM_MARKS @BOTTOM_MARKS") are marked with a suffix of single-quote to indicate that they are the input sequence. This statement will advance the current context by three glyphs; subsequent rules will be trying to match whatever follows @BOTTOM_MARKS.

Tim Ahrens's picture
Offline
Joined: 28 Sep 2004 - 9:15am
0

Or am I totally misunderstanding how this whole thing works?

Not totally, only partly. You can use most of the FDK without FontLab.

The "main" FDK, the tools that build and analyse OTFs are command line tools that are independent of FL. However, there are some additional tools that run as macros in FL. I doubt you will get them to work in any other application.

Riccardo Sartori's picture
Joined: 13 Jul 2009 - 4:20am
0

And, if you can post, your account is active.

&quot; class='s picture
Offline
Joined: 10 Aug 2010 - 11:39am
0

Hi there, I dont know if I am writing in a proper board but I have got a problem with activation, link i receive in email is not working... http://typophile.com/?086ed9d92dbc6242a21d4a9e8b0,

Theunis de Jong's picture
Offline
Joined: 22 Apr 2008 - 5:06pm
0

Why are you posting this in a 2 year old thread?

Eric Olson's picture
Offline
Joined: 15 Feb 2002 - 12:06pm
0

Relative to this build, I'm not sure how new they are, but Check Outlines and AutoHint are lovely.

Karsten Luecke's picture
Offline
Joined: 6 Aug 2005 - 8:41am
0

It's not really meant to be studied in FontLab, but rather to indicate which folders and files AFDKO needs, their hierarchy, and how feature files interact in this hierarchy (e.g. the separate 'kern' feature). The feature files themselves have wonderful examples for writing features -- AFDKO feature file syntax in action. So these are best studied in a plain text editor.
(I'm a bit oldfashioned and have made printouts of the sample feature files to read them unplugged.)

William Berkson's picture
Offline
Joined: 26 Feb 2003 - 11:00am
0

Thanks, Karsten, I'll read them with a text editor and print them out.

John Hudson's picture
Offline
Joined: 21 Dec 2002 - 11:00am
0

Uli, what do the actual hints for the h and n look like in FontLab? Can you provide a screenshot of the glyph windows? This is a strange effect, and not what I would expect from the FL autohinter, unless it is trying to hint the serif widths as well as the stem widths and miscalculating the hint replacement point.

Uli Stiehl's picture
Offline
Joined: 1 Feb 2006 - 8:02am
0

Mr. Hudson:

I already deleted the test font faultily hinted by Fontlab 4.6.

But you can most easily repeat my experiment as follows:

1) Open Adobe's OpenType font SerifaStd-Roman.otf with Fontlab 4.6.

2) Remove all hints (e.g. by key shortcut shift F7) via Fontlab 4.6

3) Autohint all glyphs (e.g. by key shortcut F7) via Fontlab 4.6

4) Generate PostScript Type 1 font SerifaStd-Roman.pfb with Fontlab 4.6

5) Also generate the PFA version SerifaStd-Roman.pfa with Fontlab 4.6

This PS Type 1 font SerifaStd-Roman.pfb will contain the faulty vertical stem hints faultily hinted by Fontlab 4.6. I do not know, whether later versions of Fontlab have the same problem. Using Adobe's FDK autohint function on the PFA version SerifaStd-Roman.pfa will remedy the faulty stem hints.

Tim Ahrens's picture
Offline
Joined: 28 Sep 2004 - 9:15am
0

As far as I can remember, these instructions are not sufficient in order to exactly reproduce what you did. In addition, FL considers your settings for minimum and maximum stem widths. You would need to provide your settings for this, as well.

Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
0

Karsten is right. The correct parameter names are winAscent and winDescent, which are case-sensitive. For a complete list of the parameters that can be specified by the FDK, in regards to the OS/2 table, please refer to the file 'OT Feature File Syntax.html', section 9.f. OS/2 table.

As for the file fontinfo, please refer to the documentation file 'MakeOTFUserGuide.pdf', page 9.

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

i updated my python installation and now the install macros scripts works; nevertheless, most of the scripts don't.
for example 'autohint' gives me:

Traceback (most recent call last):
File "", line 798, in ?
ImportError: No module named win32api

the 'adobe-update scripts' script, however, seems to work.

i checked other non-FDK scripts and they also work fine.

winxp, FL 5.0.2, python 2.4.3

Karsten Luecke's picture
Offline
Joined: 6 Aug 2005 - 8:41am
0

Not using a PC for this, but my guess is win32api is an 'external' Python library which you have to grab somewhere and install in addition to python and fdk.

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

thanks karsten,

i downloaded the win32api.dll and placed it into various places that seemed appropriate: the windows system folder, the python dll folder, the fontlab modules folder.

eventually the error changed, but was not solved:

Traceback (most recent call last):
File "", line 798, in ?
ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.

in line 798 AutoHint.py tries to import the win32api.dll and the win32con.py; i also downloaded the latter and placed it into the fl modules folder - with no changes in behaviour.

if __name__ == '__main__':
dontShowDialog = 1
if haveAC:
result = 2
if os.name == "nt":
import win32api
import win32con

any ideas?

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

Hi,

My apologies - I see that the dependency on the win32api and win32com.py modules in the Windows version is not documented. I will fix this in the next release. Note that they have to be installed in one of the directories which is in the sys.path list of your Python. The only directory under FontLab's Macros directory which is in this list is in Macros/System/Modules. Did you put both these modules in one of the directories in sys.path?

Another limitation is that the AutoHint and CheckOutlines modules use C extension modules that are linked for use with Python 2.3 ( aka FontLab 5) and won't work with Python 2.2 ( aka FontLab 2.2).

- Read Roberts

Dr. Ken Lunde's picture
Offline
Joined: 17 Sep 2006 - 8:31pm
0

AFDKO Version 2.0 includes several new tools, and I recently authored a new Adobe Tech Note, #5900, to act as a tutorial for three of them, specifically for mergeFonts, rotateFont, and autohint. This Adobe Tech Note will be available at the following URL: http://partners.adobe.com/public/developer/font/index.html

And, it will be included in the next release of AFDKO. Until then, if anyone would like to receive this Adobe Tech Note, contact me by email.

Ken Lunde
Senior Computer Scientist, CJKV Type Development
Adobe Systems Incorporated
lunde@adobe.com

Chris Lozos's picture
Offline
Joined: 25 Feb 2004 - 11:00am
0

Thanks Ken! I'll take you up on that.

ChrisL

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

read,

Note that they have to be installed in one of the directories which is in the sys.path list of your Python. The only directory under FontLab’s Macros directory which is in this list is in Macros/System/Modules. Did you put both these modules in one of the directories in sys.path?

this is actually what i've done, yet, it doesn't work. i also added a path file to the site-packages folder (just like the one created by the FDK) - but it makes no difference. fontlab (or python) still reports that the library can't be found.

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

One current problem with Python extension modules is that they work only with the version of Python for which they were built. It is possible that your win32api module doesn't match your Python. Another possibility is that the win32api module may have dependencies on other modules. I will echo Adam Twardoch's good advice and recommend that you download the entire win32 package. However, I will add that you need to pick the right one that works with the version of Python that you have. I actually used "pywin32-205.win32-py2.3.exe" to install the win32 package for my co-workers at Adobe. This translates as "build 205 of the win32 package, built for Python 2.3". The newer builds of win32 ought to work, as long as they are built for the Python you are using. These can be found at:
http://sourceforge.net/project/showfiles.php?group_id=78018

Note that the AFDK0 FontLab scripts are built to work with Python 2.3. Autohint and CheckOutlines in particular use extension modules that are tied to specifically to Python 2.3; the others assume in some places support for operations that exist only in 2.3 and later.

- Read

Adam Twardoch's picture
Offline
Joined: 3 Dec 2002 - 7:36pm
0

Windows users should install the win32all package:
http://www.python.net/crew/mhammond/win32/Downloads.html

It includes the win32api etc. modules.

A.

Titus Nemeth's picture
Offline
Joined: 8 Mar 2004 - 9:58am
0

i was aware of the version interdependence and installed the extensions accordingly. which didn't solve it. right now i am trying to get it to work with python 2.3.5 - not successful yet. i'll check back for new developments.

Adam Twardoch's picture
Offline
Joined: 3 Dec 2002 - 7:36pm
0

Read,

any chance that Adobe could also release AFDKO 2.0 compiled for Python 2.4?

A.

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

Yes, I can build the Python 2.4 libs as well, for the next update in a few weeks. Note that this affects only the FDK Check Outlines and Auto Hint scripts - the command -line tools are entirely independent of any installed Python, and none of the other scripts for FontLab use a Python extension module.

carol roth's picture
Offline
Joined: 30 Jul 2006 - 5:58pm
0

Good soul mind to post screenshot(s) how to install AFDKO (v2.0)?

- C.

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

The file "FDK/Read_Me_First.html" explains how to install the AFDKO v2.0

Göran Söderström's picture
Joined: 15 Feb 2006 - 2:53am
0

I have tried the Autohinter for a couple of project, and it feels very nice. Sometimes when autohinting with FontLabs own hinter, I got a couple of red "H" that I didnt know how to fix.

Adobes autohinter creates all green H’s ;-) I also kind of like that the log shows exactly what the autohinter did do to the font.

Andreas Seidel's picture
Offline
Joined: 8 Mar 2002 - 3:44am
0

Maybe a bug or a bug in the documentation, since the example doc shows the winDescent value with a minus.

The winDescent value have to be written without minus. Otherwise the font will be currupted and crashes instandly my xp system.

example for correct compilation:


table hhea {
Ascender 900;
Descender -350; # not 350
LineGap 0;
} hhea


table OS/2 {
TypoAscender 765;
TypoDescender -235;
TypoLineGap 250;
winAscent 900;
winDescent 350; # not -350
Panose 2 2 5 2 6 5 6 2 4 3;
XHeight 455;
CapHeight 720;
FSType 4;
WeightClass 400;
WidthClass 5;
} OS/2;

--astype.de--

Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
0

> Adobes autohinter creates all green H’s ;-)

This reminds me of something.
What I'm going to say might be obvious to many of you, but just wanted to make clear that in order to get good/proper hinting results, Alignment Zones and Standard Stems need to be set beforehand.

Göran Söderström's picture
Joined: 15 Feb 2006 - 2:53am
0

Miguel, in your opinion; do you thinks it’s OK to do this with FontLab’s auto-stems and auto alignment zones? When it comes to these matters, I really like the word Auto :)

Goran, Autodidakt

Miguel Sousa's picture
Offline
Joined: 18 May 2003 - 8:30pm
0

Goran, I here you there ;^)

I'd follow Adam's tip, with a couple additional steps:
...
1.1. Check that the auto Alignment Zones are good, i.e. they should cover all the "overshoot nodes". Eventually, you might want to shift some of these points a few units up or down.
...
5. Run Adobe's Autohint

That's all :^)

Göran Söderström's picture
Joined: 15 Feb 2006 - 2:53am
0

Great advices! Thanks for that.