Method and system for embedding a device profile into a document and extracting a device profile from a document in a color management system

Abstract

A method and system for embedding a device profile into a document and extracting a device profile from a document in a color management system. A tagged-element device profile allows for selective access to the device profile. The method of embedding a device profile into a document include allocating memory for a buffer, sending a ready call, transferring the device profile or portions of the device profile into the buffer and writing the same in the document, and lastly, sending a completed call. The method of extracting a device profile from a document includes allocating memory for a buffer, sending a ready call, reading the device profile or portions of the device profile from the document into the buffer and transferring the same to a file, and finally, sending a completed call.

Claims

What is claimed is:

1. A method for flattening a device profile into a document in a system having at least one device profile and at least one color matching method that can flatten device profiles, comprising the steps of:

allocating a memory buffer;

reading a portion of the device profile into the memory buffer;

transferring the portion of the device profile in the memory buffer to the document; and

if necessary, repeating the steps of reading and transferring portions of the device profile until the desired portions of the device profile are embedded in the document.

2. In a color management system having a default color matching method, a client, and at least one device profile which may specify a preferred color matching method, wherein additional color matching methods other than the default color matching method may be added to or deleted from the color management system, a method for dispatching a color matching method to flatten a device profile, comprising the steps of:

determining whether or not a preferred color matching method is included within the color management system;

if the preferred color matching method is included in the color management system, determining whether or not the preferred color matching method can flatten the device profile;

if the preferred color matching method can flatten the device profile, dispatching the preferred color matching method to flatten the device profile; and

if the preferred color matching method is not included in the color management system, or the preferred color matching method can not flatten the device profile, dispatching the default color matching method to flatten the device profile.

3. A method for unflattening a device profile in a system having at least one device profile and at least one color matching method that can unflatten device profiles, comprising the steps of:

allocating a memory buffer;

creating a file in the memory buffer to store the device profile;

writing a portion of the device profile into the file; and

if necessary, repeating the step of writing a portion of the device profile into the file until the desired portions of the device profile have been transferred to the file.

4. In a color management system having a default color matching method, a client, and at least one device profile which may specify a preferred color matching method, wherein additional color matching methods other than the default color matching method may be added to or deleted from the color management system, a method for dispatching a color matching method to unflatten a device profile, comprising the steps of:

accessing the device profile to identify a preferred color matching method;

determining whether or not the preferred color matching method is included within the color management system;

if the preferred color matching method is included in the color management system, determining whether or not the preferred color matching method can unflatten the device profile;

if the preferred color matching method can unflatten the device profile, dispatching the preferred color matching method to unflatten the device profile; and

if the preferred color matching method is not included in the color management system, or the preferred color matching method can not unflatten the device profile, dispatching the default color matching method to unflatten the device profile.

5. A color management system for flattening a device profile, comprising:

a client to send a flatten profile command;

a dispatcher to receive the flatten profile command; and

a color matching method that supports flattening, wherein upon receipt of the flatten profile command the dispatcher dispatches the color matching method to flatten the device profile.

6. A color management system for unflattening a device profile, comprising:

a client to send an unflatten profile command;

a dispatcher to receive the unflatten profile command; and

a color matching method that supports unflattening, wherein upon receipt of the unflatten profile command the dispatcher dispatches the color matching method to unflatten the device profile.

7. The method of claim 1, further comprising the step of reducing the amount of memory buffer to be allocated by a certain amount when the step of allocating the memory buffer fails due to an insufficient amount of available buffer space.

8. The method of claim 7, wherein the certain amount is a half.

9. The method of claim 2, further comprising the step of returning an error message when the preferred color matching method is not available.

10. The method of claim 2, further comprising the step of returning an error message when the preferred color matching method is not able to flatten the device profile.

11. The method of claim 3, further comprising the step of reducing the amount of memory buffer to be allocated by a certain amount when the step of allocating the memory buffer fails due to an insufficient amount of available buffer space.

12. The method of claim 11, wherein the certain amount is a half.

13. The method of claim 4, further comprising the step of returning an error message when the preferred color matching method is not available.

14. The method of claim 4, further comprising the step of returning an error message when the preferred color matching method is not able to unflatten the device profile.

15. A method for flattening a device profile in a system having at least one device profile and at least one color matching method that can flatten device profiles, comprising the steps of:

allocating a buffer for storing at least a portion of the device profile during the flattening process;

creating a new device profile in the buffer;

copying a header from the device profile into the new device profile;

copying a portion of the elements from the device profile into the new device profile;

transferring the copied header and elements from the buffer into a document, wherein the transfer is performed in at least one step; and

if necessary, repeating the steps of copying and transferring until the desired elements of the device profile have been transferred to the new device profile, wherein the device profile is then embedded in the document.

16. The method of claim 15, further comprising the step of determining which elements to be copied before performing the step of copying at least a portion of the elements from the device profile to be flattened into the new device profile.

17. The method of claim 16, wherein the step of determining which elements to be copied comprises determining the state of a flag.

18. The method of claim 15, further comprising the step of reducing the amount of buffer to be allocated by a certain amount when the step of allocating the buffer fails due to an insufficient amount of available buffer space.

19. The method of claim 18, wherein the certain amount is a half.

20. A system for flattening a device profile, wherein at least one color matching method is associated with the system that can flatten device profiles, said system comprising:

at least one device profile;

a buffer for storing at least a portion of the device profile during the flattening process;

means for transferring a portion of the device profile into the buffer;

means for transferring the portion of the device profile in the buffer to a document; and

if necessary, means for repeating the transferring steps until all of the desired portions of the device profile have been transferred to the document, wherein the device profile is then embedded in the document.

21. The system of claim 20, further comprising a memory for storing all of the device profiles in a single location.

22. The system of claim 21, wherein the memory is a read only memory (ROM).

23. The system of claim 20, wherein the buffer is a random access memory (RAM).

24. A system for unflattening a device profile embedded in a document, wherein at least one color matching method is associated with the system that can unflatten device profiles, said system comprising:

a buffer for storing at least a portion of the device profile during the unflattening process;

means for transferring a portion of the device profile from the document into the buffer, wherein the transfer is performed in at least one step; and

if necessary, means for repeating the step of transferring a portion of the device profile until the desired portions of the device profile have been transferred to the buffer, wherein the device profile is extracted from the document and reconstructed in the buffer.

25. The system of claim 24, wherein the buffer is a random access memory (RAM).

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates in general to computer systems, and in particular to color management systems operating in computer systems. Still more particularly, the present invention relates to a method and system for embedding a device profile into a document and extracting a device profile from a document in a color management system.

2. Description of the Prior Art

Color management refers to a system that supports color information exchange, color matching, profile management, and device calibration. As color input, display and output devices for computer systems proliferate, the need for color management increases. This is due to several factors. First, differing device types operate in different color spaces. For example, color display monitors typically display colors as combinations of red, green, and blue, and are said to work in the RGB color space. Printers typically print images as combinations of cyan, magenta, yellow and black, and are said to work the CMYK color space.

Another factor is that different color devices have different color capabilities. Every color device, such as a scanner, printer, or monitor, has a range of colors that it can produce. This range of produceable colors is known as a gamut. Those skilled in the art will recognize that color display monitors can produce and display hundreds to thousands of colors. Color printers, however, have a smaller number of printable colors. Consequently, in most situations the gamut for a color display monitor exceeds the gamut for a color printer. As a result, some colors displayed on display monitor can not be produced by a color printer.

A third factor is that devices of the same type that are manufactured by different manufacturers may produce different colors, or intensities of the same colors, for the same color data. For example, color display monitors made by different manufacturers may display different colors, or intensities of the same colors, for the same RGB values. Print technologies vary drastically, and the gamut that an ink jet color printer can print may be quite different from a printer based on a different technology, such as a color laser printer. A single printer may have different gamuts depending on the paper or ink being used at the time of printing.

The way colors are sampled in different devices is another factor. Generally, the method used by monitors to display color follows the laws of additive color mixture. Additive color mixture adds the color together to yield the result. Additive color mixture moves a color toward white, and usually results in vivid images. Printers, however, typically follows the laws of subtractive color mixture. In subtractive color mixture, color data specifies how much of a certain color to remove from white to yield the result. Consequently, a subtractive color mixture moves colors toward black or dark gray.

A color management system offers the means of transmitting color images and documents across local and wide area networks while maintaining the fidelity of the colors of the original image or document as much as possible. In January, 1993, Apple Computer, Inc. introduced ColorSync.TM. 1.0, a color management system in the form of a suite of utilities. The ColorSync.TM. Utilities are a set of routines and data structures that enable a color processing system to match colors and communicate color information between various source and destination devices. Color information is transmitted between devices via a device profile. A device profile is a data structure that describes the basic color characteristics of the device. Color information described in a device profile includes data relating to the device's color space, gamut, tonal reproduction curves, and the preferred color matching method (CMM).

Color matching means converting colors between differing gamuts. A CMM implements algorithms to match colors. Because the ColorSync.TM. Utilities are designed to provide an "open system" for color management, developers can use an Apple-supplied default CMM, create their own CMM, or obtain them from companies or vendors who create CMMs.

The ColorSync.TM. Utilities provide applications or device drivers with several tools for matching colors between devices. The tools include a default system color profile that describes the gamut of the Apple.TM. RGB 13 inch monitor, a control panel interface by which users can set their system profile, a means of specifying and obtaining device profiles for other devices, a means of associating device profiles with images or documents, an Apple-supplied default CMM, a folder for storing device profiles, and an open architecture that allows developers to create or obtain a custom CMM and associate it with a device profile.

Device profiles in ColorSync.TM. 1.0 are memory resident, meaning a profile is read into random access memory (RAM) when information regarding data within the device profile is needed or when the device profile is being used by the ColorSync.TM. Utilities. In order to do this, computer systems must have a sufficient amount of RAM to hold the entire device profile while one or more application software programs are running in the computer system.

The requirement to load the entire device profile into RAM adversely affects the performance and resource requirements of the computer system. This is due to the fact that as the size of device profiles increase, more and more RAM is needed in order to access or use the device profile. Consequently, an undesirable amount of RAM is consumed by the device profile, or the device profile is not used because the computer system does not have sufficient RAM.

Additionally, a user may wish to embed a device profile into a document. Embedding a device profile is a means of associating a device profile with documents. The device profile travels with the document and is available for reference at a later time when the document is accessed. To obtain the device profile from the document, the device profile must first be extracted from the document. ColorSync 1.0, however, does not provide the functionality to embed or extract a device profile from a document. Furthermore, if it did, the issue of RAM usage could possibly limit the ability to perform these tasks.

SUMMARY OF THE INVENTION

A method and system for embedding a device profile into a document and extracting a device profile from a document in a color management system. A tagged-element device profile allows for selective access to the device profile. The method of embedding a device profile into a document includes allocating memory for a buffer, sending a ready call, transferring the device profile or portions of the device profile into the buffer and writing the same in the document, and lastly, sending a completed call. The method of extracting a device profile from a document includes allocating memory for a buffer, sending a ready call, reading the device profile or portions of the device profile from the document into the buffer and transferring the same to a file, and finally, sending a completed call.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, and further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 illustrates a computer system which may be used to implement the method and system for dynamically dispatching device profile data in a color management system according to the present invention;

FIG. 2 is a block diagram depicting the architecture of a color processing system according to the present invention;

FIG. 3 is a block diagram illustrating the modular architecture of a color management system according to the present invention;

FIG. 4 is a pictorial representation of a device profile according to the present invention;

FIG. 5 is a block diagram depicting a method and system for dispatching an element in a device profile according to the present invention;

FIG. 6 is a block diagram illustrating a method and system for dynamically dispatching device profile data in a color management system according to the present invention;

FIGS. 7a-b are flowcharts depicting a method for embedding a device profile into a document according to the present invention;

FIG. 8 is a flowchart illustrating an alternative method to the method depicted in FIG. 7b for embedding a device profile into a document according to the present invention; and

FIGS. 9a-b are flowcharts illustrating a method for extracting a device profile from a document according to the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to the figures and in particular with reference to FIG. 1, a computer system is illustrated which may be used to implement the method and system for dynamically dispatching device profile data in a color management system according to the present invention. Computer system 10 includes a computer 12, keyboard 14, a color display monitor 16 having a display screen 18, a cursor control device 20, shown here as a mouse, and a printer 22. Computer system 10 may be implemented using any suitable computer, such as a Macintosh Quadra.TM. computer, a product of Apple Computer, Incorporated, located in Cupertino, Calif. Printer 22 is a color printer, such as a Color Stylewriter Pro.TM. printer, also a product of Apple Computer, Incorporated.

One of the utilities available in computer system 10 is ColorSync.TM. 2.0, a product created by Apple Computer, Incorporated. ColorSync.TM. 2.0 is a color management tool that supports color information exchange, color matching, device profile management, and device calibration. Color matching is important when transferring color images and documents between color devices, such as monitors and printers. Color matching is necessary because color devices have different color capabilities, describe color in different terms and operate in different color spaces.

For example, a color display monitor 16 in computer system 10 creates and describes colors in terms of red, green and blue ("rgb") values, and is said to work in the RGB color space. The rgb values for display monitor 16 are device dependent, meaning the rgb values are particular for that monitor. Because the rgb values are device dependent, colors displayed on a different monitor will probably not match the colors displayed on display monitor 16 for the same rgb values.

Most printers create and describe colors in device dependent terms differing from monitors. Printers use cyan, magenta, yellow and black ("cmyk") values to describe colors, and are said to work in the CMYK color space. Again, because the cmyk values are device dependent, colors printed on printer 22 will probably not match colors printed on a different printer for the same cmyk values.

The need for color matching is further supported by the fact that different color devices have different color capabilities. Every color device, such as a scanner, printer, or monitor, has a range of colors that it can produce. This range of produceable colors is known as a gamut. Those skilled in the art will recognize that color display monitors can produce and display hundreds to thousands of colors. Color printers, however, have a smaller number of printable colors. Consequently, in most situations the gamut for a color display monitor exceeds the gamut for a color printer. As a result, some colors displayed on display monitor 16 can not be produced by printer 22.

Finally, the way colors are sampled in different devices also increases the need for color matching. Generally, the method used by monitors to display color follows the laws of additive color mixture. Additive color mixture adds the color together to yield the result. Additive color mixture moves a color toward white, and usually results in vivid images. Printers, however, typically follows the laws of subtractive color mixture. In subtractive color mixture, color data specifies how much of a certain color to remove from white to yield the result. Consequently, a subtractive color mixture moves colors toward black or dark gray.

FIG. 2 is a block diagram depicting the architecture of a color processing system according to the present invention. Color processing system 24 includes a source device 26. Source device 26 is a device used to input a document or image into color processing system 24. For example, source device 26 can be a color display monitor, a scanner or other real or virtual devices, such as a camera or color composition routines. Block 28 represents a device driver associated with source device 26 or an application software program being used by a user to access the input document or image.

Color processing system 24 further includes a destination device 30. Examples of destination devices include a printer, a color monitor, or other real or virtual devices such as a plotter or color composition routines. Device driver 32 is associated with destination device 30.

When a user wants color processing system 24 to perform color matching on an image or document, the application software program or the device driver shown in blocks 28 or 32 calls ColorSync.TM. Utilities 34. The ColorSync.TM. Utilities 34 are a set of routines and data structures that enable color processing system 24 to match colors and communicate color information between the various source and destination devices. Color information is transmitted between devices via a device profile. A device profile is a data structure that describes the basic color characteristics of the device. Color information described in a device profile includes data relating to the device's color space, gamut, tonal reproduction curves, and the preferred color matching method (CMM). The structure and contents of a device profile will be described in greater detail with reference to FIG. 4.

Still referring to FIG. 2, color processing system 24 preferably has at least two device profiles. Source profile 36 is associated with source device 26. If color processing system 24 has a plurality of source devices, each source device may have its own source profile. Destination profile 38 is associated with destination device 30. If color processing system 24 has a plurality of destination devices, each destination device may have its own destination profile. Profiles can reside in files, device drivers, applications, documents, and images. Although FIG. 2 depicts only one source profile and one destination profile, more than two profiles may reside in color processing system 24.

Finally, color processing system 24 includes a component manager 40 and at least one color matching method (CMM). Blocks 42, 44, 46 represent three different CMMs within color processing system 24. The Apple.TM. Color Matching Method included with ColorSync.TM. is one of the CMMs in color processing system 24. A CMM is where the conversion, or color matching, between differing color gamuts occurs.

Components are called through component manager 40. In this manner, applications and device drivers are considered "clients." A component is a piece of code that provides a defined set of services to one or more clients. A component typically provides a specific type of service to its clients. For example, a component might provide image compression or decompression. A client would call the component, provide the component with the image, and the component would then compress the image and return the compressed image to the application. Multiple components can provide the same type of service. For example, separate components may exist that can compress an image by 20 percent, 40 percent, or 50 percent, with varying degrees of fidelity.

Component Manager 40 provides access to and management of components. An example of management of components is the tracking of the available components and routing requests to the appropriate component. The component manager 40 classifies components by three main criteria: the type of service provided, the level of service provided, and the component manufacturer. Component manager 40 uses a component type, consisting of a sequence of four characters, to identify the type of service provided by a component. CMMs have a component type of `CMM.sub.-- `. The Apple-supplied CMM component has a subcomponent type of `appl`. Manufacturers and suppliers of other CMMs who register their CMM with Apple Computer, Inc. are assigned a subcomponent type.

Component Manager 40 provides services that allow clients to obtain run-time location of and access to functional objects by creating an interface between components and clients. A standard interface is used through which a client can communicate with all components of a given class, such as CMMs. Component Manager 40 is used to locate and communicate with components of that class. The components, in turn, provide the appropriate services to the client. A more detailed description of component manager 40 is found in Chapter 6 of Inside Macintosh: More Toolbox Utilities (1993) by Apple Computer, Inc.

Component manager 40 allows a single component to service multiple clients at the same time. Each client has a unique access path to the component. These access paths are called component connections. A component connection is identified by specifying a component instance. Component manager 40 provides the component instance to a client when it opens a connection to a component. The component maintains separately status information for each open connection.

Multiple clients may each open a connection to a component. Component manager 40 routes each client request to the component instance for that connection. Because a component can maintain separate storage for each connection, client requests do not interfere with each other and each client has full access to the services provided by the component.

With ColorSync.TM., color matching is the type of service provided to one or more clients. A separate ComponentInstance is opened for each matching session. The set of device profiles used in the matching session is unique for each session. The color matching component should allocate private storage to store the necessary information for the instance and use Component Manager functions to manage the storage. The color matching component should free the storage when the matching session is completed by making a ComponentClose function.

As stated above, CMMs have a component of the type `CMM.sub.-- ` provide color matching services. All components of type `CMM.sub.-- ` share a common interface, but each component may support a unique color matching technique or take advantage of a special hardware implementation. Individual components may support additions to the defined interface, as long as they support the common routines.

The color matching process will now be described by way of example. A color image is input into color processing system 24 by a scanner (source device) and is to printed on a color printer (destination device). The user wants the color in the image printed on the color printer to be matched as close a possible to the colors scanned by the scanner. The device driver shown in block 28 associated with the scanner calls the ColorSync.TM. Utilities 34. The ColorSync.TM. Utilities 34 examines the source profile 36 associated with the scanner and the destination profile 38 associated with the color printer to determine which CMMs should be used. The ColorSync.TM. Utilities 34 then calls Component Manager 40 to call one or more CMMs 42, 44, 46 to perform color matching. How many CMMs are called depends upon whether or not the source profile 36 and the destination profile 38 can use the same CMM for color matching. Once color matching is completed, the image is printed on the color printer.

Referring to FIG. 3, a block diagram illustrates the modular architecture of a color management system according to the present invention. The ColorSync.TM. Utilities 34 include at least five components, or modules. These modules are dispatcher 48, profile management 50, color space conversion 52, CMMs 42, 44, 46, and device profiles (not shown).

Dispatcher 48 provides the overall color management administrative framework and manages the interaction between the color management system, including calling device 54, component manager 40, profile management 50, color space conversion 52, device profiles (not shown), CMMs 42, 44, 46, and the actual color image or document (not shown). Dispatcher 48 is installed from the Extensions file at system startup in the preferred embodiment. On 680.times.0 Macintosh.TM. computers, dispatcher 48 is implemented using the Toolbox A-trap mechanism. The interface defines the value for register DO at the time a function is called. The A selector is in the low 16 bits and the parameter size is in the high 16 bits. The functions use PASCAL stack-based calling conventions. ColorSync.TM. 34 implements a 680.times.0 mainline function which internally dispatches individual calls on the selector.

The implementation of dispatcher 48 will vary for other computer systems. For example, dispatcher 48 is implemented on Power Macintosh.TM. computers by including a mechanism for internal dispatch of traps with a 68K register D0 selector. A function .sub.-- SetTrapAddress is called with a pointer to a block of routine descriptors and selectors.

Profile management 50 provides searching, retrieval, and indexing functions for the various profiles, along with the ability to get and set individual attributes within a profile. Profile management 50 is registered at system startup with the following parameters.

    ______________________________________
    componentType           `prof`
    componentSubType        `dflt`
    componentManufacturer   `appl`
    ______________________________________

    ______________________________________
    typedef
    pascal
    Boolean (*ProfileFilterProcPtr)(Profile prof, void *refCon);
    #if USESROUTINEDESCRIPTORS
    typedef UniversalProcPtr ProfileFilterUPP;
    #else
    typedef ProfileFilterProcPtr ProfileFilterUPP;
    #endif
    struct ProfileSearchRecord {
     OSType           CMMType;
     OSType           profileClass;
     OSType           deviceColorSpace;
     OSType           interchangeColorSpace;
     unsigned long    deviceManufacturer;
     unsigned long    deviceModel;
     unsigned long    deviceAttributes›2!;
     unsigned long    profileFlags;
     unsigned long    searchMask;
     ProfileFilterUPP filter;
    };
    typedef struct ProfileSearchRecord
                          ProfileSearchRecord;
    ______________________________________

    ______________________________________
    #define    kMatchProfileCMMType
                                 0x00000001
    #define    kMatchProfileClass
                                 0x00000002
    #define    kMatchDeviceSpace 0x00000004
    #define    kMatchInterchangeSpace
                                 0x00000008
    #define    kMatchManufacturer
                                 0x00000010
    #define    kMatchModel       0x00000020
    #define    kMatchAttributes  0x00000040
    #define    kMatchProfileFlags
                                 0x00000080
    ______________________________________

    ______________________________________
                            bytes
    ______________________________________
    struct CM2 Header {
    unsigned long  size;          0-3
    OSType         CMMType;       4-7
    NumVersion     profileVersion;
                                   8-11
    OSType         profileClass;  12-15
    OSType         dataColorSpace;
                                  16-19
    OSType         interchangeColorSpace
                                  20-23
    CMDateTime     dateTime;      24-35
    OSType         CS2profileSignature;
                                  36-39
    OSType         platform;      40-43
    unsigned long  flags;         44-47
    OSType         deviceManufacturer;
                                  48-51
    unsigned long  deviceModel;   52-55
    unsigned long  deviceAttributes›2!;
                                  56-63
    unsigned long  renderingIntent;
                                  64-67
    FixedXYZColor  white;         68-79
    char           reserved›36!;/*for future
                                   80-127
                   use*/};
    ______________________________________

    ______________________________________
    `scnr`    input devices such as scanners and digital cameras
    `mntr`    display devices such as CRTs and LCDs
    `prtr`    output devices such as printers
    ______________________________________

    ______________________________________
    `link`         device link profiles
    `spac`         color space conversion profiles
    `abst`         abstract profiles
    ______________________________________

    ______________________________________
    pascal
    CMError
    GetProfileElement (Profile prof, OSType tag, long *elementSize, void
     *elementData);
    ______________________________________

    ______________________________________
    pascal
    CMError
    ProfileElementExists(Profile prof, OSType tag, Boolean *found);
    ______________________________________

    ______________________________________
    pascal
    CMError
    GetPartialProfileElement (Profile prof, OSType tag, unsigned long
     offset, unsigned long byteCount, void *elementData);
    ______________________________________

    ______________________________________
    pascal
    CMError
    SetProfileElementSize(Profile Prof, OSType tag, unsigned long
     elementSize);
    ______________________________________

    ______________________________________
    pascal
    CMError
    SetPartialProfileElement(Profile prof, OSType tag, unsigned long
     offset, unsigned long byteCount, void *elementData);
    ______________________________________

    ______________________________________
    pascal
    CMError
    FlattenProfile(Profile prof, long flags, FlattenProcUPP proc,
     void *refCon)
    ______________________________________

    ______________________________________
    pascal
    CMError
    CMFlattenProfile(ComponentInstance CMSession, Profile prof,
     long flags, FlattenUPP proc, void *refCon)
    ______________________________________

    ______________________________________
    AtoBElements
              Include elements necessary for the source side of a
              matching session. Common case for a document
              profile tag
    BtoAElements
              Include elements necessary for the destination side
              of a matching session
    intent0   Include elements necessary for rendering intent 0
    intent1   Include elements necessary for rendering intent 1
    intent2   Include elements necessary for rendering intent 2
    qd32KLimit
              Flattened CMProfile may not exceed 32K, the limit
              for QuickDraw PicComments
    ______________________________________

    ______________________________________
    pascal
    CMError
    UnflattenProfile(FSSpec *resultFileSpec, FlattenProcUPP proc,
     void *refCon)
    ______________________________________

    ______________________________________
    pascal
    CMError
    CMUnflattenProfile(ComponentInstance CMSession, Profile *prof,
     FlattenUPP proc, void *refCon)
    ______________________________________

• Inventors
  Swen, Iue-Na Steve; Stokes, Michael D.; Mohr, Thomas E.;
• Assignee
  Apple Computer Inc. (Cupertino, CA)
• Published
  Sep-8-1998
• Current US Classes:
  345/22
  345/543
  345/549
  345/593
  358/515
  358/527
  715/528
• Application #
  604208
• International Classes
  G06F 003/14; H04N 001/46
• Field of Search
  382/209 382/276 395/429 395/431 707/528 345/431 345/150 345/199 345/22 345/186 358/515 358/527
• Examiner
  Black; Thomas G.
• Agent
  Simon; Nancy R.
• US Patent References:
  4839828
  4907071
  4985759
  5175628
  5208911
  5212546
  5243414
  5257097
  5271096
  5282026
  5309257
  5319473
  5339176
  5349452
  5367387
  5375193
  5379049
  5446543
  5497431
  5524069
  5557688