Tracking problem with .otf OpenTypes generated by Fontographer 5


Can anyone suggest why the OpenTypes I'm generating in Fontographer 5 have sporadic spacing anomalies and the tracking occasionally goes way out. It looks like I've gone insane while kerning. This weirdness is only happening in .otf font files; the .ttf , Mac PostScript and Mac TrueTypes are all exactly as designed.

If I take my Fontographer-generated .ttf file into FontLab and generate .otf files, they have the correct spacing, the problem is only in Fontographer generated OpenTypes. Am I doing something stupid or has Fontographer 5 got a glitch?

Thanks in advance.

Any know what this error means? multiple glyphs macron overscore mapped to code


I am getting this error when i try to compile a simple opentype subs feature. i copied and pasted the code from another font i made and it works fine there.

cmap{plat=3,script=1,lang=0}: multiple glyphs macron overscore mapped to code

double checked the sub characters they all have the same naming conventions.

any ideas?

thanks you in advance,


Good Website Fonts

Hi there,
I wondered what website fonts might look good for an internet site. I tried Fakt (Opentype) on one website and I feel it looks better than Arial. ( in case you want to have a look: )

For 2 other websites I was thinking maybe I use another opentype font which can be included directly via the @font-face CSS rule. But I checked with Museo Sans or Calluna Sans and it does not look good at all.

Any idea which Font might work well? Verdana and Arial/Helvetica seem to be still the better choice. Also any example or link to a site which uses a well working font (being easy to read and also looking good) would be welcomed.

Tsukurimashou 0.1 - MetaFont meta-family for Japanese, first release


I've posted the first public version of the Tsukurimashou parametric font family on my Web site at

The main goal of this project is to support my own study of the Japanese language, so the finished product is less important than the process of getting there. However, you might still enjoy looking at it. To my knowledge, there's never been a native MetaFont family with glyph coverage for Japanese; there exist a couple that are conversions from other formats, and there was also the Quixote Oriental Fonts Project, announced more than two decades ago, apparently never usable, and now long abandoned.

Microsoft Word doesn't like my new OpenType font


I have a new OpenType font I'm working on and when I try to load it into Word X, it shows it in the menu, BUT when you click on it it switches to the font next to it in the list instead and refuses to make it work.

The font works perfectly in Adobe programs and in TextEdit (I'm using Mac OS X).

I have heard many people have problems with Microsoft programs loading various fonts, but I would like to sell this font sometime soon and don't want to have to tell anyone that it doesn't work in some Microsoft programs.

So far I have only heard people saying a font of theirs doesn't show up in the menu because they have the wrong printer drivers installed, but this is something different than that because it does show up in the menu - it just doesn't work!

Programming OpenType Font with FontLab 5 to have size restrictions


Does anyone know how to set some parameters that restrict a font to specific sizes? In my case, I need the character to be no smaller than 12pt and no bigger than 72pt. I would like the character to change to another character for sizes smaller than 12pt or bigger than 72pt.

Is this sort of thing possible in FontLab 5 with the OpenType programming panel?


Font Kerning-pair problem in Adobe CS software


I have quite 'weird' problem with my font. For some reason one kerning pair (as far as i know) is not working in Adobe CS3 software (indesign, photoshop etc.). Still its perfectly fine in numerous other softwares (MS Word, NeoOffice, Linotype fontexplorer etc.). The problem appears both in "class kerning" and "flat kerning mode".

The problematic kerning-pair is "Va" so it's too visible in display sizes to ignore.

I've attached detailed picture comparing the pair "Va" and "VA" in multiple softwares.

I hope someone knows something similar and can help me on this.


Language-specific OT ligatures


Good evening!

Some languages have problems with f-ligatures. One example is German, where ligatures across Wortfugen can be a source of confusion; another is Turkish, in which the dotless ı requires special treatment.

Have there been any efforts to identify (and compile a list of) such problems, and is it considered good practice to code those exceptions as language-specific OpenType alternates? Say, "ligatures for dflt, no ligatures for german"? Or would that go against users' expecations? How well are such features implemented in software at all?

Another solution, of course, is a Linotype ("Sabon") f, but you know, I do have a thing for nice fi and fl ligatures :)

Glyph names for the "case" feature


Hi crowd,

I've been designing a few caps features for one of my text typefaces. Think of the Van Krimpen hyphen, and of course height-adjusted parens, middots, endash and emdash (with hopes of making cap-specific tabular numerals too — one day!). Question is, how do I go about naming them? hyphen.alt is too vague and might clash at some point. hyphen.caps? I was looking for examples, but after ten minutes in the Adobe specification site, I threw in the towel. Is there a convention?

Edited title to reflect proper nomenclature; post left intact to keep the thread sensible.

OT Alternates not working in Adobe CS


I have a stylistic alternates in my opentype values, but for some reason the opentype panel in Photoshop/Illustrator will not toggle them. The interesting thing is, the glyph window in Illustrator reads them fine, but toggling the alternates in the opentype window does nothing. In order to select an alternate, it has to be done via the glyph window.

Has anyone ever experienced this, any ideas what is causing this?

Allumi Std: New cheaper version


Allumi Std was originally created by Jean François Porchez in 2009. This new variation “Std” is the basic version of the tailored Allumi PTF. Allumi is a sleek typeface designed with technology in mind. It’s a perfect font family of 27 series for any communication concerning design, robotics, or functionality.

6 weights pack: from € 140 / $ 145 for 2 users. Buy it!

One weight: from € 50 / $ 65 for 2 users. Buy it!

Dot font Opentype printing problems


I am trying to produce a scaleable dot-based font family in Fontlab as Mac flavoured Opentype. I’ve had a lot of trouble with getting small circles to be geometrically correct in Truetype (the beziers flatten the arcs) but Opentype keeps them geometrically consistent.

However, I have a bigger problem which I can't seem to fix.

OpenType / Alternates / InDesign / Please!


So I am starting a book project for which I am using a very complete and well designed typeface, the files are .otf. I thought .otf meant OpenType and that's it, I just discovered the different OpenType flavored types, which I don't quite understand yet, anyway, not the point...

So I checked and my typeface is an OpenType (Postscript Flavored).

Now... I am using the Book weight, which contains all the basic characters, but not the ligatures. For the ligatures, there is the Book Alt version, which contains all the nice ligatures that I would like to use in my text treatment...

From what I understand, OpenType would contain everything in one font file, these flavored things do not, because of the 256 glyphs limit, right?

script and language statements in OT features


Trying to learn more about features, focusing on the kerning feature at the moment.

In another post Jens Kutilek kindly offered the following feature as a suggestion to a problem I was trying to solve (

feature kern {
script grek;
language dflt;
pos space <50 0 100 0>;
} kern;

What I'm wondering about is the script and language statements. I've read about them a bit on Adobe's site but, admittedly, will have to back and revisit to better understand. One thing I didn't see is how these statements get used or activated.

InDesign CS5 and OpenType language and script tags


[Cross-posted with the UAFDKOML group]

I'm starting to receive some questions about features not working in InDesign CS5 when a non-Latin language or "No Language" is selected. And this is happening with fonts that worked fine in CS3 and CS4.

From the cases I've seen, the bugs were in the fonts. More specifically, the feature file code lacked languagesystem declarations. Regarding InDesign CS5, what I can tell you is that this version is more strict than CS3 and CS4 were in terms of dealing with language and script tags. So if the fonts don't have lookups for all the necessary languagesystems, ID CS5 will just stick to what's in the font rather than creating them on-the-fly, like CS3 and CS4 used to do.

Contextual Lookups for Ordinals


I have this lookup for ordinals. It works OK for 1st, 2nd, 3rd, 4th, etc., and for Caps, 1ST, 2ND, 3RD, etc., but not for ordinals in French or Spanish, which use one or three ordinals e.g. 2º or 1ème.

How can I change my code to cater for one or more alpha characters after the digits? One to three superscripts would be OK, but I think one or more would be more flexible.

feature Ordinals ordn {
lookup Ordinals;
group @Digits [zero-nine];
group @Alphas [A-Z a-z];

lookup Ordinals{
context (@Digits) @Alphas @Alphas;
sub 0 Super;
sub 1 Super;
} lookup Super {
sub [A-Z] -> [uniEAA1 - uniEABA];
sub [a-z] -> [uniEAC1 - uniEADA];

I am using OpenType Compiler.

Fully featured OT font into separate fonts


What would be the best/smart/easy way to transform an OT font that is fully featured and has several stylistic variants, into separate fonts for each feature, while still maintaining the kerning pairs etc.?

For example if an OT font has the standard latin characters + small caps + titling characters + alternates... to have the SC and Titling as standalone functional separate fonts.

What would be a good way to do do that?

LeFrancois : soon available !

LeFrançois is a typeface in OpenType format based on 3 series of capitals.
It seems to be classical but some glyphs show that it's not so conventional.
It's seems to be a typical French type, that's why its name is LeFrançois (with the accent please !)
With a particular work on kerning (about 5000 !) and ligatures, you'll be able to compose words as logotypes thanks to capitals and small caps.
It will be soon available at

OpenType features support in Linux software


Does anyone know of an application for Linux that lets me use OpenType features? I'm thinking alternate forms, swashes, dicretionary ligatures.

I would like to migrate from using windows to linux, all the things I do I can do in Inkscape and Scribus, but the OT features would be a nice touch. I'm open to learning TeX or any other piece of software as long as it's usable.


contextual multiple substitution in OT


I'm trying to set up a contextual multiple substitution (one-to-many), but FOG 5 keeps choking on the feature file and won't generate a font. The same substitution works in VOLT for TrueType OpenType fonts, although the substitution works only in Microsoft programs, and not in Adobe programs.

In VOLT, I was able to set up the substitution as:

    comma -> special_glyph comma -- when preceded by -- glyph_group

Now I'm trying to use it in a feature file (based on Adobe specs) for generating a CFF OpenType font in Fontographer 5.

Here's the basic syntax for an Adobe spec feature file:

    sub [ @Glyphclass ] comma' by specialglyph comma;

Better web typography with OpenType features

Now that webfonts are supported by all major browsers, more and more professional fonts are available for web linking. These fonts usually contain a large set of OpenType features, which are only accessible in OpenType-savvy applications like InDesign, Illustrator or QuarkXPress. Browsers have barely supported such advanced typographic features so far. But with the latest Beta of Firefox 4 this is about to change …

see also: