Comments on: CID Identity H Fonts are Back? http://indesignsecrets.com/cid-identity-h-fonts-are-back.php InDesignSecrets Blog and Podcast Thu, 04 Dec 2008 19:34:14 +0000 http://wordpress.org/?v=2.5.1 By: Bjarne Undertun http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-470331 Bjarne Undertun Tue, 18 Nov 2008 11:44:05 +0000 http://indesignsecrets.com/?p=1754#comment-470331 We have problems sometimes with CID-fonts in adds, on a new Harlequin RIP! The only thing that differ from all other adds in our workflow is the Identity-H issue, so I guess this is it. What bother me is that this problem maybe will come up regardless which method to use when creating PDF-files (according to Dov above). Or is there some way to do it safe from ID CS3? A strange thing: RIP-results will not be the same from time to time, even if we put the same file through the RIP. Three times will get three different results, with characters in a mess on some rows! Why do the chaos theory have to interfere here! :( We can't dream of beeing the only company having problem with this issue, on a widely spread RIP-type as Harlequin! I believe Sweden shouldn't be the only place in the world that uses a lot of Harlequins... And no, there is no icebears in Sweden... ;) We have problems sometimes with CID-fonts in adds, on a new Harlequin RIP! The only thing that differ from all other adds in our workflow is the Identity-H issue, so I guess this is it. What bother me is that this problem maybe will come up regardless which method to use when creating PDF-files (according to Dov above). Or is there some way to do it safe from ID CS3?
A strange thing: RIP-results will not be the same from time to time, even if we put the same file through the RIP. Three times will get three different results, with characters in a mess on some rows!
Why do the chaos theory have to interfere here! :(

We can’t dream of beeing the only company having problem with this issue, on a widely spread RIP-type as Harlequin! I believe Sweden shouldn’t be the only place in the world that uses a lot of Harlequins…

And no, there is no icebears in Sweden… ;)

]]> By: K.C. http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-468774 K.C. Fri, 26 Sep 2008 06:17:29 +0000 http://indesignsecrets.com/?p=1754#comment-468774 Just saw this, and decided to leave a comment. Virendra Bhalla: Adobe has solved that problem relating to Zapf Dingbats. In Adobe Font Folio 11, they included an OpenType version of the font. Just saw this, and decided to leave a comment.

Virendra Bhalla: Adobe has solved that problem relating to Zapf Dingbats. In Adobe Font Folio 11, they included an OpenType version of the font.

]]> By: Dov Isaacs http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466512 Dov Isaacs Mon, 14 Jul 2008 15:34:48 +0000 http://indesignsecrets.com/?p=1754#comment-466512 (1) InDesign 4 (=CS2) attempted to avoid CID encoding as much as reasonably possible, but there were no changes in this for InDesign 5. (2) Use of the Distiller to produce PDF either from InDesign or any other application does NOT guarantee that you won't get CID encoding. In fact, the Distiller uses CID encoding for optimization its conversion of PostScript to PDF. (3) CID encoding has been an integral part of both the PostScript specification since 1996 (although it is supported by most PostScript Level 2 devices) and the PDF specification since PDF 1.3 (Acrobat 4 - 1999). In reality, if a print service provider (or a content creator) is using software that is NOT CID-encoding compatible, it is saying that software is being used that is also most likely incompatible with ICC color management, transparency, layers, and JPEG2000 image compression. This is a recipe for disaster for print customers. If your print service provider has problems with CID encoding, you should seriously question whether your print service provider is competent to handle your 21st century print needs with 20th century workflows and tools! - Dov (1) InDesign 4 (=CS2) attempted to avoid CID encoding as much as reasonably possible, but there were no changes in this for InDesign 5.

(2) Use of the Distiller to produce PDF either from InDesign or any other application does NOT guarantee that you won’t get CID encoding. In fact, the Distiller uses CID encoding for optimization its conversion of PostScript to PDF.

(3) CID encoding has been an integral part of both the PostScript specification since 1996 (although it is supported by most PostScript Level 2 devices) and the PDF specification since PDF 1.3 (Acrobat 4 - 1999). In reality, if a print service provider (or a content creator) is using software that is NOT CID-encoding compatible, it is saying that software is being used that is also most likely incompatible with ICC color management, transparency, layers, and JPEG2000 image compression. This is a recipe for disaster for print customers. If your print service provider has problems with CID encoding, you should seriously question whether your print service provider is competent to handle your 21st century print needs with 20th century workflows and tools!

- Dov

]]> By: lauren http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466324 lauren Mon, 07 Jul 2008 13:47:21 +0000 http://indesignsecrets.com/?p=1754#comment-466324 Lets all just use the Ellipse tool and draw little circles where ever we need bullets! (Kidding of course, sorry I just had to!) Lets all just use the Ellipse tool and draw little circles where ever we need bullets!
(Kidding of course, sorry I just had to!)

]]> By: Bob Levine http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466290 Bob Levine Sat, 05 Jul 2008 22:16:38 +0000 http://indesignsecrets.com/?p=1754#comment-466290 LTM's point was that ornaments don't get encoded as CID. I tested that out and as I already said, it's true. I'm curious, though. You refer to this as a problem. Are you a service provider that runs into this with your equipment or are you designer that has service providers with problems? LTM’s point was that ornaments don’t get encoded as CID. I tested that out and as I already said, it’s true.

I’m curious, though. You refer to this as a problem. Are you a service provider that runs into this with your equipment or are you designer that has service providers with problems?

]]> By: Virendra Bhalla http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466282 Virendra Bhalla Sat, 05 Jul 2008 15:44:20 +0000 http://indesignsecrets.com/?p=1754#comment-466282 Bob, you must have tried playing with Adobe fonts only. The problem is more often with Truetype fonts. Try Zapf dingbat. Virendra Bob, you must have tried playing with Adobe fonts only. The problem is more often with Truetype fonts. Try Zapf dingbat.

Virendra

]]> By: Bob Levine http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466262 Bob Levine Fri, 04 Jul 2008 20:10:00 +0000 http://indesignsecrets.com/?p=1754#comment-466262 Interesting discovery which I can confirm. I played around with several fonts and no CID encoding. Interesting discovery which I can confirm. I played around with several fonts and no CID encoding.

]]> By: L. Thomas Martin http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466239 L. Thomas Martin Fri, 04 Jul 2008 01:53:37 +0000 http://indesignsecrets.com/?p=1754#comment-466239 A quick test to see why I hadn't been seeing this problem and it appears that using ornaments -- at least those in Warnock -- as bullets avoids the problem. LTM A quick test to see why I hadn’t been seeing this problem and it appears that using ornaments — at least those in Warnock — as bullets avoids the problem.

LTM

]]> By: Bob Levine http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466228 Bob Levine Thu, 03 Jul 2008 17:47:29 +0000 http://indesignsecrets.com/?p=1754#comment-466228 Well, I'd be banging my head against a wall a bit more if Adobe didn't have a technote on it already. I'm going to guess that any software or RIP that's going to have problems because of this is going to have problems with just about any advanced features of exported PDFs. And if that's the case, and your stuck with that workflow, distilling is probably your best bet. In fact, you may be even better off supplying EPS files which shouldn't present any problem for any workflow that doesn't involve a camera. Well, I’d be banging my head against a wall a bit more if Adobe didn’t have a technote on it already.

I’m going to guess that any software or RIP that’s going to have problems because of this is going to have problems with just about any advanced features of exported PDFs.

And if that’s the case, and your stuck with that workflow, distilling is probably your best bet. In fact, you may be even better off supplying EPS files which shouldn’t present any problem for any workflow that doesn’t involve a camera.

]]> By: David Blatner http://indesignsecrets.com/cid-identity-h-fonts-are-back.php#comment-466219 David Blatner Thu, 03 Jul 2008 15:19:34 +0000 http://indesignsecrets.com/?p=1754#comment-466219 Bob, when I wrote "use a character that does appear in the font," I meant, "use some other character that looks like a bullet, but isn't that character." The more I look at this, the weirder it is; in some cases, just adding a bullet character anywhere in a document will make the entire font change to CID encoding. Strange behavior. Also note that it's not just printer RIPs that may have this problem. Other PDF-processing software (apps that need to read the pdf and do something with it) may have troubles. But again, that would likely only be an issue with old software. Bob, when I wrote “use a character that does appear in the font,” I meant, “use some other character that looks like a bullet, but isn’t that character.”

The more I look at this, the weirder it is; in some cases, just adding a bullet character anywhere in a document will make the entire font change to CID encoding. Strange behavior.

Also note that it’s not just printer RIPs that may have this problem. Other PDF-processing software (apps that need to read the pdf and do something with it) may have troubles. But again, that would likely only be an issue with old software.

]]>