Are you saying that the font doesn't behave as expected when it is in /Library/Fonts/, but it works in /Library/Application Support/Adobe/Fonts? I'm a bit skeptical. Did you try it in /Library/Fonts/ after clearing system font caches?

yes. yes. yes.

I think there must be something about adding cyrillic support that does this. I'm actually thinking of two cases where I have seen this kind of behavior on Mac OSX with OT fonts containing cyrillic support. The only way I could get the features to show up when installed to the /Library/Fonts folder was to export the font as a dfont.

I've always assumed that Adobe applications activate fonts in a way that is similar to a font manager. What you're information implies is that InDesign is in some way bypassing ATS and using the font directly.
Is it possible that InDesign is overcoming a Mac OS deficiency of some kind?

am i the only one who has experienced this problem?

Paul,
My Leporello family has Cyrillic and Greek and it works fine in all apps (including Adobe) on a Mac OS-X loaded in the normal system fonts library. I have not tried it on a PC though. I developed it completely on a Mac and it is PS otf flavored but I don't know if that matters.

ChrisL

i found that i can get rid of this problem if i "hack" the font and uncheck everything but "Basic Latin" in the "Supported Unicode Ranges". However, I'm fairly sure that it's having the Cyrillic checked that is throwing everything off, as I haven't had this problem with fonts OT fonts (PS flavored) that just have CE support.
Can you tell me what settings you have for this page for your fonts, Chris?

Paul,
I will look it up tonight when I am at home. I assume you mean which code pages are selected in check boxes.

ChrisL

Paul,
Here is a screen shot of one of the Leporello Unicode ranges:

Looks like Cyrillic and Greek are checked.

ChrisL

thnx chris, but it's not the codepages, it's the "unicode ranges" that are the problem. can i have you check that data for me?

Here ya go Cowboy:

ChrisL

curiouser and curiouser... i'm baffled.

Me too Paul. Maybe Adam can shed some light?

ChrisL

...maybe you'll have to wait for OS X 10.5 (and pay for yet ANOTHER upgrade). Way to go, Steve...you da man!

Gee Nick, that was a great bit of quick diagnosis. You instantly figured out that Apple was the culprit without ever even seeing the files or examining the code. You are the man. What genius you've wasted doing type design.

ChrisL

this problem seems to be fixed when running the font through Adobe OpenType FileTyper.

Paul, what I'm about to say might not relate directly with your problem, but may lead you to another possible solution.

My specific problem was in Quark 6, with an .otf font that covered Western and Central European Latin (no Greek or Cyrillic). The supported codepages selected were Latin 1, Latin 2: Eastern Europe, Turkish and Windows Baltic.
As you probably know, Quark 6 only supports Western characters in OpenType PS (.otf) fonts, nonetheless I was getting CE characters when typing Western. After some fiddling, I found out that adding Greek to the supported codepages would fix the problem.

Here's Adam Twardoch's explanation:
There is a bizarre bug in the Adobe font driver (ATM or the one built into Mac OS X) with respect to the "Windows Greek codepage" flag. If a font is flagged as "Roman" + "CE", then ATM thinks that the primary codepage of the font is CE, if the font is flagged as "Roman" + "Cyrillic", then ATM thinks that the primary codepage is Cyrillic, but if the font is flagged as "Roman" + "CE" + "Greek" or "Roman" + "Cyrillic" + "Greek", then ATM thinks that the primary codepage of the font is Roman. QuarkXPress only likes fonts that the system says the primary codepage is Roman. So in short, it may be help to activate the "Windows Greek" codepage flag.

Oh, I have similar trouble!
I'm working with font which contains Roman+Cyrillic+Greek+CE+Turkish+Baltic+Vietnamese and all features works excellent in Windows Adobe CS/CS2 apps (font installed via ATM) including cyrillic ligature, please see example

--------------------------------------

feature liga { # Standard Ligatures

script latn; # Latin
lookup liga3 {
sub f f i by ffi;
sub f i by fi;
} liga3;
lookup liga4 {
sub f f l by ffl;
sub f f j by ffj;
sub f f by ff;
sub f j by fj;
sub f l by fl;
sub f t by ft;
sub T h by T_h;
sub Tcaron h by T_h.caron;
} liga4;

language AZE exclude_dflt; # Azeri
lookup liga4;
language TUR exclude_dflt; # Turkish
lookup liga4;
language CRT exclude_dflt; # Crimean Tatar
lookup liga4;

script cyrl;
language UKR;
lookup liga2 {
sub afii10104 afii10104 by _jiji.liga;
} liga2;
} liga;

--------------------------------------

but under MacOS-X 10.4 (font installed via SuitCase 11) works all the features... except cyrillic ligature!

In "font info" checked all really present codepages, MS Charset = Bitstream, MAC script & Fond ID = Roman.

Any ideas?

Can you test it under version 10.3? I've heard that some thing(s) got broken in the 10.4 build that affect .otf fonts. (Don't know exactly what, but I'll enquire about it)

BTW, this line
sub Tcaron h by T_h.caron;
in your feature almost got me confuse. It makes no difference, but
sub Tcaron h by Tcaron_h;
seems more intuitive to me :)

Good catch. Not just more intuitive, but correct. One wants it to decompose to have a Tcaron, not just a T.

OS X 10.4 breaks style-linking for OpenType CFF fonts, btw. We hope to see it fixed in 10.5 "Leopard."

T

> Can you test it under version 10.3?

Under the 10.3 font don't recognized by Siutcase 11 as font... Brrrr... :(

> sub Tcaron h by Tcaron_h; seems more intuitive to me :)

May be, but IT WORKS! :)))

> We hope to see it fixed in 10.5 “Leopard.”

Thanks

I can just hope that Leopard is the cat's meow for type :-)

ChrisL

> May be, but IT WORKS! :)))

Did you read what Thomas wrote?
One wants it to decompose to have a Tcaron, not just a T.

If you don't know what that means, try this:
(The example is based on a couple Adobe tools, but it applies to other things as well)

1. Create an InDesign document that uses the Ť h ligature
2. Export it as a PDF file
3. Open the PDF, select the text and copy it
4. Paste it in a text editor

What do you get? Is it what you were expecting?

> 3. Open the PDF, select the text and copy it
> 4. Paste it in a text editor

It's impossible because I'm not allow installable mode in this font, only printing and previewing :)))

> It’s impossible because I’m not allow installable mode in this font, only printing and previewing :)))

Fonts with embedding permission set to Preview & Print can be embedded in PDFs, so it's not impossible. Embedding Permissions

Embedding Permissions:
font ... may be embedded in an electronic document, the embedded font may not be used to further edit the document it is contained in or to edit or create other documents.

Look, although you can't edit the document, you can still select and copy the text content (with a font set to Preview & Print), so I stand right.

Could we be talking about two different things?

As I understand it, a font with the embedding permissions set to Print & Preview Only can still be copied from a PDF. However, a file exported to PDF can have the permission set to Print & Preview, but turn off the ability to copy text.

I'm talking about font embedding permissions within the font file (fsType), not PDF permissions.

I just tested this with a font whose embedding permissions are:

I could copy from the PDF where I didn't set any permissions within InDesign. However, when I changed the settings as shown above I could highlight, but not copy and paste.

Thanks, Miguel, but I will discover this case later because I still resolving another troubles with this my project :)