I had a similar problem, and FontShop built a new version for me that removed the "s_t" ligature. Not sure why the "c_t" ligature would show up, as it is placed in the historical ligatures set, but they should be able to help you.

It seems that the version I have isn't an OpenType version of Nexus but a Type 1 version, yet InDesign still automatically replaces "ct" with a "c_t" ligature. I'm starting to suspect that it's actual InDesign bug. Very strange.

Stephen, that's odd, my original version of Nexus had the c_t ligature in the historical ligatures substitution set, while s_t was in the standard set. Could there already have been multiple versions floating about?

I'm confused... would a Type 1 version of Nexus still have standard and discretionary ligatures? I thought that only OpenType fonts had those features.

Yes, that's confusing indeed. However, as there is no way I know of to make either a ct or st ligature work automatically in InDesign without OpenType, I am wondering if you are mistaken as to the format you have?

T

I opened up the font in Font Book in Mac OS X, and the file format listed says it is a postscript type 1 font. I have read elsewhere that InDesign will automatically replace ligatures even in fonts that are not OpenType. I've attached an image to this message.

Also it looks like FontShop is offering a free downlof of Nexus Sans Bold on their site. I downloaded this and it is having the same issue with c_t ligatures in InDesign.

http://www.fontshop.com/index.cfm?fuseaction=virtual.content&area=fonts&content=fonts/free.htm

Weird! I just looked at the free Nexus Sans Bold in InDesign CS on Mac OS X. The strange behaviour appears for me as well.

FontAgent Pro loads it as a Type One. I opened the font in Fontlab, and couldn't see anything strange about it. It seems to be a Type One, with the c_t lig named "c_t".

The font functions as expected in Illustrator.

Strange indeed!
I am able to reproduce the problem described above with my fonts as well.

So... not a Nexus problem but rather a "Community Ligature Outreach Initiative"
brought to you by InDesign.

I have run accross this c_t s_t ligature problem with Type1 fonts as well.

Another problem I run across in InD is as follows: Type1 fonts with a standard character set. The figures in the font are named with standard names; zero, one, two etc. The design of these figures are of an oldstyle form. Also in the font are a set of Tabular Lining figures that are named zero.tab, one.tab, two.tab, etc.

The reason this second set of figures are in the font has to do with the production process I used several years ago. Anyway now in InDesign, the program ignores the correctly named figure glyphs (oldstyle in design) and substitutes the Lining Tabular figures. (Even though they use a non-standard name).

Charming huh.

I am certainly glad I'm not alone with this ligature problem! I thought I was just going crazy!

So then is the only way to correct this c_t ligature problem, with Type 1 versions of Nexus, is to delete the glyph completely from the font file? Or bitterly complain to Adobe and have them fix InDesign?

Chanpory

Interestingly, it doesn't seem to happen with the TrueType version. Very odd, all this. I am making some inquiries. Perhaps we can fix it in the future.

That being said, this phenomenon of having unencoded glyphs like this kicking around in a Type 1 font was pretty uncommon until recently. Now that people are making OpenType fonts, they may want to have a single source file from which they are generating multiple font formats. Thus the problem.

Cheers,

T

I just generated a new version of NexusSans Bold, with the "c_t" lig renamed "ct_lig" and the problem disappeared. No surprise there, I guess.

Are there comparible pieces of software written in the 80's
that not only still work on current machines, but remain
unchanged and in use like PostScript Type 1?

The Mac Calculator desk accessory?

>still work on current machines,

I still run a G-3 with system 8.6, as well as my current set-up. I find that there are some things that older software does more simply, and hence more efficiently. So I will do certain procedures in Illustrator 8 ('98), for instance, before moving the file to CS, or stuff in Fontographer ('94), before moving to FontLab. Potential for disaster, no doubt.

I would contact the folks from whom you licensed the font. If it
is FontShop, they will get back to you very promptly with assistance.

Talked to the boys here at FS today and they say the font's got
these two ligatures ("st" and "ct") set as Standard rather than
Discretionary. This is something we will fix for future font sales,
but in the meantime, contact FS and they will send you new font data.

Any update, Thomas? Behavior different in CS3?

As I don't have one of the problematic fonts to try with CS3, I can't tell you. It's been over two years now so I admit I've completely forgotten what became of the bug report....

Regards,

T

It seems to have been fixed (at least on my system).