RE: [pdf-devel] Any idea about solving CMap problem?

[Leonard Rosenthol]

As I can see from this discussion, there are three specific issues that
need to be addressed.  I've listed them below along with
responses/comments.

1) Distribution of the existing Adobe CMap files.

        It has always been Adobe's intention that these CMap files can
be distributed with both commercial and open-source solutions.  We
believe that the included license enables that to happen - just as a
similar license exists for ICC profiles such as AdobeRGB. If there is
something in the license that prevents the ability of the gnu-pdf
project from using our CMaps, we would like to know the details.


2) Modification of the Adobe CMap files.

        Because these CMaps are used by numerous pieces of PDF consuming
software (both from Adobe and elsewhere), and users have an expectation
of consistency among their toolsets - we do not allow these files to be
modified outside of Adobe.  It is our way of ensuring that users are
guaranteed to be working with the latest, correct, information.

3) Creation of your own equivalents

        Short answer - feel free.

        The CMap file format is publicly documented in an Adobe Technote
and the contents are simply based on published information from the
Unicode consortium and others.  There are no technical nor legal hurdles
to someone recreating these documents using their own "database" of
equivalent content - you just can't use our CMap files as a starting
point. 


Hopefully that clarifies Adobe's position on these questions.  If you
have others or wish more clarification, I will be glad to provide that.

Leonard Rosenthol
Adobe Systems