Skip navigation
Currently Being Moderated

Ligature issue in PS - PDF

Nov 25, 2011 8:08 AM

Any one help me on this,

 

We are creating PS to PDF from IndesignCS3, with Ligatures ON,

 

In PDF copy the word "Pacific" and placed into search option,

 

 

 

1. There was a space between character "fi[space]c in PDF search,

2. Alfo not able to find the word "pacific" type in search.#

 

Font Times (Type1)

 

Pacific

Pacifi c

 
Replies
  • Currently Being Moderated
    Nov 25, 2011 8:30 AM   in reply to Sen.Soft

    What happens if you create the PDF through recommended method of export?

     

     

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:05 AM   in reply to Sen.Soft

    Sen.Soft wrote:

     

    No, our official method is Print ps to PDF, When we do so, we get this kind of error.

    We understand that. Adobe recommends EXPORTING to PDF fom ID, rather than distilling. Is there a sound reason why you think you need to make Postscript?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:23 AM   in reply to Sen.Soft

    That is a horribly archaic and troublesome method of PDF creation. I asked you to at least try to export and let us know what happens.

     

     

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:24 AM   in reply to Sen.Soft

    There are a number of reasons why creating PDF via distillation of PostScript from InDesign is a very bad idea.

     

    You've just stumbled upon one such reason! The PostScipt generated from InDesign is optimized for printing and not for generation of PDF. When you use ligatures, you lose the ability to search for most content using ligatures in Acrobat or Reader. When creating PDF via direct export, PDF alternate text information is inserted in the PDF such that ligatures, small caps, alternate characters, etc. that you typically find in fine typography don't interfere with the ability to search PDF files.

     

    Quite frankly, the only rational reason that we know of for creating PDF from distillation of PostScript from InDesign is to create smaller PDF files in some instances. However, improvements in direct creation of PDF from InDesign have been narrowing that sometimes-advantage over the releases and some fixes in the next full version of InDesign should eliminate much of the remaining bloat (which is primarily metadata).

     

    CS3 is also quite frankly a fairly old version of the software.

     

              - Dov

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:09 PM   in reply to Bob Levine

    Bob Levine wrote:

     

    That is a horribly archaic and troublesome method of PDF creation. I asked you to at least try to export and let us know what happens.

     

    Bob

     

    This is not an agreeable answer Bob, what Dov Isaacs said above is not right. It is a major issue from Indesign, while we go through PostScript to InDesign. Not exactly on all files but it happens. We are now at the end process and next stage is the printer still we didnt find a right solution for this.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:19 PM   in reply to Jaswin

    Why other software's like (Arbor Text and LaTeX) postscipt->pdf using Distiller server don't have this issue with ligatures on. Is this a bug in InDesign postscript creation?

     

    PS->PDF creation is one of the best optimized way to create pdf and do you think its a bad idea? If we export InDesign->PDF, Device N color appears in images and this is not acceptable in our customer printer preflight settings.

     

    There are a number of reasons why creating PDF via distillation of PostScript from InDesign is a very bad idea.

     

    You've just stumbled upon one such reason! The PostScipt generated from InDesign is optimized for printing and not for generation of PDF. When you use ligatures, you lose the ability to search for most content using ligatures in Acrobat or Reader. When creating PDF via direct export, PDFalternate text information is inserted in the PDF such that ligatures, small caps, alternate characters, etc. that you typically find in fine typography don't interfere with the ability to search PDF files.

     

    Quite frankly, the only rational reason that we know of for creating PDF from distillation of PostScript from InDesign is to create smaller PDF files in some instances. However, improvements in direct creation of PDF from InDesign have been narrowing that sometimes-advantage over the releases and some fixes in the next full version of InDesign should eliminate much of the remaining bloat (which is primarily metadata).

     

    CS3 is also quite frankly a fairly old version of the software.

     

              - Dov

     

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 10:20 PM   in reply to Jaswin

    I totally agree with Bob and Dov. Using the PostScript method may work in a limited fashion for some old workflows, but it has severe limitations. It will never be changed. It is a dead end. You may not like it, but that's just the way it is.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 11:23 PM   in reply to SASEKUMAR

    (1)     It is irrelevant what Arbor Text and LaTeX do in terms of PostScript generation or PDF creation via PostScript. As I indicated, the PostScript from InDesign, Illustrator, and Photoshop is not optimized for PDF creation, but rather what PostScript is best at, printing. You cannot optimize for both simultaneously.

     

    (2)     Creation of PDF via PostScript hardly optimal in any way. You lose color management, live transparency, the ability to search and/or touchup text in many situations, etc. How is that optimal?

     

    (3)     Yes, DeviceN does show up in PDF exported from InDesign, specifically when you place grayscale imagery into InDesign. Such grayscale images are exported using DeviceN Separation Black which is logically equivalent to DeviceCMYK=(0,0,0,K). There is nothing wrong with that. Unless you have a RIP that doesn't conform to the PostScript Language 3 or PDF 1.3 specification (depending on whether the RIP consumes PostScript or PDF respectively). If you have customer printer preflight settings that reject DeviceN Separation Black or don't understand that it is equivalent to and will render as DeviceCMYK (0,0,0,K), the problem is not with InDesign, but with the customer printer preflight settings or the knowledge of whoever setup such settings.

     

         - Dov

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 11:31 PM   in reply to Sen.Soft

    You have been given a direct (and from myself an official Adobe) response. There is no fix for the issue you describe since PDF generation from InDesign is officially supported via the export function with which this issue does not occur.

     

              - Dov

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2011 11:41 PM   in reply to Dov Isaacs

    Thanks for your direct response Dov

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points