Mixed raster content files

[0001] Aspects of the present invention are directed to generating and using files. More particularly, the present invention relates to generating and using mixed raster content files.

[0002] The use of non-modifiable files has increased with the growth of the internet. One standard file format for publishing documents is the Adobe Acrobat file format (generally associated with the extension .PDF). Other file formats include JPEG and bitmap files. A benefit of these files is that one can use these file formats to exchange information on the internet with minimal concern for modification of the documents.

[0003] Another file format that is commonly used is the MRC or mixed raster content file. This file format separates an image into three equally sized images and stores them at different resolutions and, in some cases, with different compression rates or technologies. FIG. 2 shows a typical process for generation of MRC files. An image generator 301 outputs a source image 302. Source image 302 has an image resolution of 300 dpi. The source image 302 is separated by a separation process 303 into three separate images 304–306. The three separate images include a black/white (B/W) mask image 304, a foreground image 305, and a background image 306. The three images 304–306 have the same dimensions (x,y) as the source image 302. As shown in FIG. 2, the resolutions of the three images 304–306 are shown as 300 dpi, 300 dpi, and 100 dpi, respectively. The three images may be selectively compressed by compression process 307 to various degrees by different compression technologies.

[0004] Despite the benefits of being able to decompose a source image 302 into various other files 304–306, MRC files suffer from a long decomposition process (separation process 303), as is known in the art. The separation process 303 attempts to analyze all components of an image and separate out aspects for inclusion in each of the files 304–306. A need exists to generate MRC files without the long delay.

[0005] Also, the composite files 304–306 may be large while having little content. FIG. 3 shows a sample conventional MRC file. The file includes three layers including background layer 401, selector layer or black/white or B/W mask layer 402, and foreground layer 403. For purposes of illustration, the composite image 411 is shown as the resultant image when the three layers (401–403) are combined. As is known in the art, background layer has a color depth per pixel of 24 bits per pixel (24 bpp), selector layer has a color depth per pixel of 1 bpp, and foreground layer has a color depth of 24 bpp.

[0006] Each layer comprises one image. Each image has the same dimensions (x,y) (as shown in FIGS. 2 and 3). For example, background layer 401 includes one image with content 404 in the center. Selector layer 402 includes one image with three sets of content 405–407. The content 405 is “Black Text,” which is intended to represent black text. Content 406 is “Color Text A,” which is text that has color A in composite image 411, yet is represented in selector layer 402 as black text. This is because selector layer 402 only has a 1 bpp color depth. Similarly, content 407 is “Color Text B,” which is text that has color B in composite image 411, yet is black text in selector layer 402. Foreground layer 403 includes three sets of color palettes including black 408, color A 409, and color B 410. A concern with the MRC file of FIG. 3 is the significant amount of unused space. The unused space increases the underlying image size of each layer. This unused space increases time needed for encoding, decoding, and composition stages. Also, the combination of unused space with content sometimes results in poor compression of the layers. Accordingly, a need exists to minimize unused space in the composite files 304–306.

[0007] Aspects of the present invention are directed to the generation and use of MRC files to address one or more of the needs described above. In some aspects, MRC files are generated by print drivers without having to be processed by a separation process. In other embodiments, each layer of MRC files may include one or more images (or sub-images) to permit compression that is more efficient than a single image that covers each layer. These various aspects may be used separately or in combination.

[0008] These and other features of the invention will be apparent upon consideration of the following detailed description of various embodiments.

[0025] The following description is directed to mixed raster content files. It is appreciated that the disclosed concepts and approaches may be applied to other file types. Also, various processes are disclosed. These processes are provided as examples that may be used and are not considered the only expressions of the various processes used to generate or use the improved mixed raster content files. Further, the pixel colors of the selector layer are generally referred to as black and white. It is appreciated that the selector layer may only have a 1 bit per pixel color depth and therefore may only have pixels as on or off (or color state 1 and color state 0). Black and white are used to simplify the nomenclature.

[0026] However, any colors could be used in their place (e.g., fuchsia and cyan) or “on and off” and the like.

[0027] FIG. 1 illustrates a schematic diagram of a conventional general-purpose digital computing environment that can be used to implement various aspects of the present invention. In FIG. 1, a computer 100 includes a processing unit 110, a system memory 120, and a system bus 130 that couples various system components including the system memory to the processing unit 110. The system bus 130 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory 120 includes read only memory (ROM) 140 and random access memory (RAM) 150.

[0028] A basic input/output system 160 (BIOS), containing the basic routines that help to transfer information between elements within the computer 100, such as during start-up, is stored in the ROM 140. The computer 100 also includes a hard disk drive 170 for reading from and writing to a hard disk (not shown), a magnetic disk drive 180 for reading from or writing to a removable magnetic disk 190, and an optical disk drive 191 for reading from or writing to a removable optical disk 192 such as a CD ROM or other optical media. The hard disk drive 170, magnetic disk drive 180, and optical disk drive 191 are connected to the system bus 130 by a hard disk drive interface 192, a magnetic disk drive interface 193, and an optical disk drive interface 194, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 100. It will be appreciated by those skilled in the art that other types of computer readable media that can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the example operating environment.

[0029] A number of program modules can be stored on the hard disk drive 170, magnetic disk 190, optical disk 192, ROM 140 or RAM 150, including an operating system 195, one or more application programs 196, other program modules 197, and program data 198. A user can enter commands and information into the computer 100 through input devices such as a keyboard 101 and pointing device 102. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner or the like. These and other input devices are often connected to the processing unit 110 through a serial port interface 106 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). Further still, these devices may be coupled directly to the system bus 130 via an appropriate interface (not shown). A monitor 107 or other type of display device is also connected to the system bus 130 via an interface, such as a video adapter 108. In addition to the monitor, personal computers typically include other peripheral output devices (not shown), such as speakers and printers. In some embodiments, a pen digitizer 165 and accompanying pen or stylus 166 are provided in order to digitally capture freehand input. Although a connection between the pen digitizer 165 and the serial interface port 106 is shown, in practice, the pen digitizer 165 may be coupled to the processing unit 110 directly, via a parallel port or other interface and the system bus 130 as known in the art. Furthermore, although the digitizer 165 is shown apart from the monitor 107, the usable input area of the digitizer 165 may be co-extensive with the display area of the monitor 107. Further still, the digitizer 165 may be integrated in the monitor 107, or may exist as a separate device overlaying or otherwise appended to the monitor 107.

[0030] The computer 100 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 109. The remote computer 109 can be a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 100, although only a memory storage device 111 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) 112 and a wide area network (WAN) 113. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

[0031] When used in a LAN networking environment, the computer 100 is connected to the local network 112 through a network interface or adapter 114. When used in a WAN networking environment, the personal computer 100 typically includes a modem 115 or other means for establishing a communications over the wide area network 113, such as the internet. The modem 115, which may be internal or external, is connected to the system bus 130 via the serial port interface 106. In a networked environment, program modules depicted relative to the personal computer 100, or portions thereof, may be stored in the remote memory storage device.

[0032] It will be appreciated that the network connections shown are exemplary and other techniques for establishing a communications link between the computers can be used. The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed, and the system can be operated in a client-server configuration to permit a user to retrieve web pages from a web-based server. Any of various conventional web browsers can be used to display and manipulate data on web pages.

[0033] FIG. 4 shows a process for creating a mixed raster content file in accordance with aspects of the invention. An image generator 500 (for example, a painting program, word processing program, a web publishing system, and the like) outputs the content of the MRC file (the three layers: selector layer 502, foreground layer 503, and background layer 504) without outputting a composite image that needs to be converted (i.e., separated) via process 303 of FIG. 2. This output may include calls to a graphics rendering engine 501 (for example, the GDI API available from Microsoft Corporation of Redmond, Wash.). Other graphics renderers 501 may be used as well. Alternatively, the rendering may take place completely within the image generator 500. Finally, the MRC file may optionally be compressed by the selective compression engine 505. The compression is optional as is shown by a broken box.

[0034] FIG. 5 shows an example of a mixed raster content file in accordance with aspects of the present invention. The MRC file includes three layers: background layer 601, selector layer 602, and foreground layer 603. Composite image 604 is shown for explanatory purposes. The background layer includes content 605. The background content 605 may be represented by an image the size of the composite image 604. Alternatively, the background content may be represented by an image having a bounding rectangle smaller than the size of the composite image 604. Selector layer 602 includes content 606 represented by “color text A,” which while represented by text having font color A, selector layer 602 represents the content 606 as black text. Also, selector layer 602 includes content 610 represented by “color text C” which while represented by text having font color C, selector layer 602 represents the content 610 as black text. The content 606 and 610 ma be represented as a single image. Alternatively, the content 606 and 610 may be represented by two images (or sub-images). Foreground layer 603 includes black text 607, a colored rectangle 608 in color A, and content 609 as “color text B” in font color B. The colored rectangle 608 may be eliminated in a number of instances, for example, if the text has a uniform color and may be represented by the combination of the selection and background layers. The content 607–609 may be represented as a single image the size of composite image 604 (similar to the identical size descriptions above). Alternatively, the content 607–609 may be represented by two or more images (or sub-images). The images may be defined by bounding areas (rectangles or other shapes as known in the art) as represented by the bounding areas surrounding each of content 607–609.

[0035] As shown in FIG. 5, the selection layer 602 is used when a foreground image overlaps a background image. Here, pushing content to the foreground layer from the selection layer makes the rendering task faster, as there is no need to check and perform selecting or alpha blending when there is no overlapping of foreground and background content. Another aspect is that uniform color text and certain line drawings may be stored as binary images in the foreground layer with an appropriate color palette, instead of being stored as a binary image in the selector layer plus a color image in the foreground layer. It is believed that pushing content out of the selector layer into the foreground layer will improve compression and rendering performance.

[0036] Another combination is shown in FIG. 5 in which the selection and background layers are present with no foreground layer. In this case, when there is a non-white pixel in the selection layer but no corresponding pixel in foreground layer, the color of the pixel on the composite image is that of the selection layer. This combination is common and can be more efficient in rendering performance and compression than the background, selection, and foreground layer combination.

[0037] A foreground layer may have a high color depth (for example, 24 bpp). In one embodiment, all images in the foreground layer have the same color depth. Alternatively, the images in the foreground layer may have one or more color depths. For example, content 607 may have a color depth of 1 bpp, while content 608 and 609 have a different color depth of 24 bpp. Situations exist where the actual color to be associated with a region may be definable based on less than a high color depth. So, in yet a further embodiment, content 608 may have a color depth of 8 bpp while content 609 may have a color depth of something other than 1 bpp and 8 bpp (including but not limited to 2 bpp, 4 bpp, 16 bpp, 24 bpp, 32 bpp, and the like). Using color depth to the extent necessary to define a color range (rather than preset for an entire layer) permits greater and/or more efficient compression by eliminating unneeded color specifying bits per pixel and/or faster compression and rendering performance.

[0038] The ability to define color depths based on each image or collection of images in a layer is applicable to the background layer as well.

[0039] FIG. 6 shows another representation of an MRC file. Here, background image 614 is combined with “color text C” 611 and “black text” 612 to form a composite image 613. Each image 614, 611, and 612 has a size smaller than the size of composite image. In this alternative example, the combined sum of images 610, 611, and 614 is smaller than the size of the composite image.

[0040] FIG. 7A shows an exemplary process for creating a mixed raster content file in accordance with aspects of the present invention. The process starts in step 701 from the image generating application. First, text and line drawings are processed in step 702. If text and/or line drawings are present, they are added to the selector layer in step 703. The color of the line or text is used to create a color area for the foreground layer in step 704. The color area may be rectangular or any other shapes as needed to define the area in the foreground layer to properly specify the color of the text and/or lines from step 702. Next, the pictures resident in the image file are processed in step 705 and added to the background layer in step 706.

[0041] The example of FIG. 7A shows the ability to process images directly from an application, as having been sent to a device driver, or from a spooled metafile. In contrast, the conventional approach to generating the MRC file is to take an intact composite image and separate it into various components via separation process 303. The separation process 303 is error prone and consumes significant resources to handle the image decomposition process. The example of FIG. 7A, however, provides the ability to generate MRC files without the separation process as the example of FIG. 7A handles the various components of an image while the various components are still separately addressable.

[0042] FIG. 7B shows an alternative process for creating an MRC file. Here, when a graphics renderer starts the MRC generation process in step 701, the graphics calls are listed with the relevant image areas in step 708. The list may include one or more of the following for each image area:

• • [0043] Bounding area;
  • [0044] Type of graphics output; and
  • [0045] Color used.

[0046] Next, in step 709, if the image area is text or line drawings, then the image area is added to the selector layer in step 703. Otherwise, in step 710, the image area is added to the foreground/background layer. Any type of image is added to the foreground/background layer, making the foreground/background layer a good representation of the document.

[0047] FIGS. 8A and 8B show various options for step 704 of FIG. 7A. In FIG. 8A, the font or brush color of text and lines, respectively, are noted in step 801 and passed to step 803. Also, in step 802, the bounding area or areas (which may be rectangles or other shapes that define the boundaries of the text and or lines) are determined and passed to step 803. Steps 801 and 802 may occur in any order or may be handled concurrently. It is further appreciated that the areas determined in step 802 do not have to be completely filled. For example, a line drawing of a circle may have a bounding area in the shape of a torus. In step 803, the area or areas determined by step 802 are painted as filled areas on the foreground layer.

[0048] FIG. 8B shows another alternative for step 704. First, each pixel in the selection layer 804 is scanned. If the pixel is black as determined in step 805, then the color of the background pixel is used to fill in the color of a corresponding foreground pixel in step 806. The scanning step 804 may cover each pixel of the entire selector layer.

[0049] Alternatively, as the selector layer may be broken into images that contain content, step 804 may only scan the images in the selector layer. As the area of the selector layer not consumed by images would not contain content, these areas would not be scanned by step 804.

[0050] In another aspect of the invention, the arrangement of the MRC file is modified. FIG. 9A shows an exemplary process of rendering a composite image from a mixed raster content file of FIG. 6. In step 901, the system begins to construct a composite image from the various MRC layers. For all pixels in the composite image, it is determined if a pixel is in a selector layer in step 902. If yes, then the system determines if the pixel in the selector layer is white in step 905. If the pixel is white, then the system checks whether there is a pixel in the background layer in step 906. If there is no pixel in the background layer, then the default background color is used in step 909, otherwise the color from the corresponding pixel from the background layer is used in step 910.

[0051] If the pixel in the selector layer is not white from step 905, then the system checks whether there is a pixel in the foreground layer in step 907. If there is no pixel in the foreground layer, then the color of the pixel in the selection layer is used in step 908. If there is a pixel in the foreground layer in step 907, then the color from the corresponding pixel in the foreground layer is used in step 904.

[0052] If there is no pixel in the selector layer from step 902, then the system determines whether there is a pixel in the foreground layer in step 903. If there is a pixel in the foreground layer, then the system uses the color from the corresponding pixel in the foreground layer in step 904. Otherwise, the system determines whether there is a pixel in the background layer in step 906 and proceeds as described above.

[0053] If there was no pixel in the selector layer as determined in step 902, then the system determines if there is a corresponding pixel in the foreground layer in step 903. If no, then the color from the corresponding pixel in the background layer is used (step 906). If there is no corresponding pixel in the background image, then a default pixel color may be used (for example, white or gray or even be designated as transparent). If the outcome of step 903 is yes, then the color from the corresponding pixel in the foreground layer is used (step 904).

[0054] FIG. 9B shows a process for combining the multiple layers into a composite image. From the start in 901, the system obtains the bounding rectangles or other shapes for the content of the layers. Next, the system calculates four lists. The first list (NOL_FGBG) represents areas in which the foreground does not overlap with the selection areas and areas where the background does not overlap with the foreground areas. The second list (SEL) represents areas where the selection does not overlap with the foreground areas. The third list (SELFG) represents areas where only the selection and foreground areas overlap. The fourth list (BGFGSEL) represents areas where the background, selection, and foreground layers all overlap.

[0055] Next, in step 913, the composite image is filled with a default background color. Each list is processed in steps 914–917. In step 914, each area in the first list (NOL_FGBG), when a foreground area is present, is filled with the foreground image. Otherwise, the area is filled with the background image.

[0056] In step 915, for each area in the second list (SEL), when the pixel in the selection layer is white, no modification of the composite image is made. Otherwise, the color value from the pixel in the selection layer is used.

[0057] In step 916, for each area in the third list (SELFG), when the pixel in the selection layer is white, no modification to the composite image is made. Otherwise, the color of the pixel in the foreground layer is used.

[0058] In step 917, for each area in the fourth list (BGFGSEL), if the pixel in the selection layer is white, the color of the background is used. Otherwise, the color of the pixel in the foreground is used.

[0059] FIG. 10 shows another exemplary process of creating a mixed raster content file. The process as shown in FIG. 10 produces the MRC file of FIG. 6. The process begins in step 1001 where the process is initiated. In one example, step 1000 may be the receipt of a command to print the MRC file. As step 1000 may be part of an application, part of a graphics toolbox as called by an application, or may be a host of other ways of initiating the creating of the MRC file, step 1000 is shown in a broken box.

[0060] For purposes of simplicity, the following is described in association with creating MRC files in a print driver. The following includes reference to the GDI API, available in the WINDOWS® operating system available from Microsoft Corporation, which exposes various calls for image manipulation. It is appreciated that operating systems including LINUX and Apple-based systems will have variations on the various calls. Accordingly, as all operating systems and print drivers are intended to be encompassed by the scope of this disclosure, the reference to GDI calls is intended to be non-limiting and is for explanatory purposes only.

[0061] To construct a print driver using GDI, a number of calls may be used. The following describes a number of calls that help separate content into various layers. The calls may be described generally as DrvXXX GDI APIs. Specifically, they include:

• • [0062] DrvCopyBits
  • [0063] DrvBitBlt
  • [0064] DrvStretchBlt
  • [0065] DrvStrokePath
  • [0066] DrvFillPath
  • [0067] DrvStrokeAndFillPath
  • [0068] DrvLineTo
  • [0069] DrvTextOut
  • [0070] DrvAlphaBlend
  • [0071] DrvGradientFill
  • [0072] DrvPlgBlt
  • [0073] DrvStretchBltROP
  • [0074] DrvTransparentBlt

[0075] These calls are separated into foreground-generating methods and background-generating methods as follows:

• • [0076] Foreground-generating methods
    • [0077] DrvStrokePath
    • [0078] DrvLineTo
    • [0079] DrvTextOut
    • [0080] DrvBitBlt
  • [0081] Background-generating methods
    • [0082] DrvCopyBits
    • [0083] DrvBitBlt
    • [0084] DrvStretchBlt
    • [0085] DrvAlphaBlend
    • [0086] DrvGradientFill
    • [0087] DrvPlgBlt
    • [0088] DrvStretchBltROP
    • [0089] DrvTransparentBlt
    • [0090] DrvFillPath
    • [0091] DrvStrokeAndFillPath

[0092] It is appreciated that graphics renders change over time. Accordingly, the above list is given by way of example. It is appreciated that other calls may be used or will become known to those of ordinary skill in the art and are considered within the scope of graphics calls set forth above.

[0093] The printing process may be separated into two stages for the purposes of explanation. These two stages are represented by the left and right halves of FIG. 10. During the first stage, two bitmap buffers are created in step 1001. The two bitmaps are the selection layer and a combination background/foreground layer. The combination layer may be referred to as BGFG_SURFACE and the selection layer referred to as SEL_SURFACE. Both bitmaps cover the entire page. In step 1002, the system determines if one of the calls received was a foreground-generating DrvXXX call. Alternatively, FillPath and StrokeandFillPath calls, as opposed to BitBlt calls, may be used when a brush is a solid color and using various raster operations. If yes, then in step 1004, it renders on both BGFG_SURFACE and SEL_SURFACE by using a corresponding EngXXX call (as part of the GDI API) on BGFG_SURFACE and SEL_SURFACE separately. If the call was a background-generating DrvXXX call, (represented as “no” from decision step 1002), it renders on BGFG_SURFACE using corresponding EngXXX call from the GDI toolbox in step 1006.

[0094] Also, for each DrvXXX call, a data node is created that contains at least some of the following information:

• • [0095] Bounding rectangle or area that may be affected by the DrvXXX call,
  • [0096] Color value of the text for DrvTextOut call and for line drawings.
  • [0097] ID to identify type of DrvXXX call.

[0098] In addition, each node is added to a background elements list (BGE_LIST) or a foreground elements list (FGE_LIST) for processing in the second stage. Process steps 1003 and 1005 show the node may be pushed into each list. However, as the locations of these steps may occur before or after steps 1004 and 1006, steps 1003 and 1005 are shown in broken boxes.

[0099] BGFG_SURFACE may be the same resolution as the highest resolution to be used for background and foreground images. Alternatively, the resolution of the BGFG_SURFACE may be set to the same resolution as the page resolution as in the final image.

[0100] The second stage starts after all DrvXXX calls are processed. At this stage, images for the three layers are generated. In step 1007, the process determines whether the images in the background/foreground list overlap. If yes, then the images are added to the images to be combined by the MRC process (or processes) in step 1008. If the images do not overlap, the process attempts to push the images to the selection list in step 1009. To determine where selection image is needed, an intersecting test is performed for each image in the BGE_LIST with every image in FGE_LIST. All areas (rectangular or otherwise) where foreground elements and background elements intersect are addressed by a selection image.

[0101] In one embodiment, the process attempts to place as much of the images in the selection layer as possible into the foreground layer. In another embodiment, the process attempts to keep the sum of areas of all images at a minimum to reduce compression size and increase performance at compress, decompress and rendering stages. In a further embodiment, the process attempts to try to have the fewest numbers of total images in all layers. These embodiments may be combined or used separately. They are described together for purposes of explanation.

[0102] In step 1010, the process attempts to reduce the number of items or images per layer. For example, two non-overlapping text images of the same color may be combined.

[0103] In step 1010, the process attempts to reduce the number of elements in the layers. Here, elements of the same layer are combined together to make larger elements into large ones. It should be noted this step might introduce new items in the lists. The following lists various approaches for combining the elements. One or more may be used to determine how to group elements of the layers:

• • [0104] The combined element should avoid creating new overlaps with elements in other layers, unless the doing so brings benefits in other aspects listed below;
  • [0105] The area of combined element should not be much bigger than the sum of individual elements. A threshold may be set (for example, 30%–40%) and compared against to determine when combined elements are getting too big; and
  • [0106] Rendering-specific calls may have qualifiers (for example, foreground elements created by DrvTextOut should not be combined with elements created by other DrvXXX calls because they have different BPP values. Also, within foreground elements created by DrvTextOut, only elements with the same color can be combined).

[0107] After determining how to decompose the page, three lists exist:

• • [0108] BGE_LIST;
  • [0109] SLE_LIST; and,
  • [0110] FGE_LIST.

[0111] Each list contains a list of nodes that describe the area (e.g., rectangle or other shape) to crop from the page. In a further embodiment, the lists may include a scale factor describing how the image in the list will be scaled on the final image. The scale factor permits the ability to store each element image at a different resolution, even within the same layer.

[0112] Finally, the various layers are rendered in step 1011. For each element in the background element list that does not intersect with selection images, an image may be formed by cropping an area from BGFG_SURFACE and placing t in the background layer. For each element in the foreground element list that does not intersect with selection images, an image may be formed by cropping an area from SEL_SURFACE and adding it to the foreground layer. For elements in background and foreground lists that intersect with selection images, images are created for each layer by using both SEL_SURFACE and BGFG_SURFACE.

[0113] For example, also referring to that intersection/pixel-by-pixel comparison option of FIG. 9B, for a background element that intersects with the selection image, the background image may be constructed by cropping an area from BGFG_SURFACE. Next, for each pixel in the background image, the process checks the corresponding pixel in SEL_SURFACE. If the pixel in SEL_SURFACE is black, the pixel value in the background image is replaced with a nearby background pixel whose corresponding pixel in SEL_SURFACE is white. For a foreground element that intersects with the selection image, the foreground image may be constructed by cropping an area from BGFG_SURFACE. Next, for each pixel in the foreground image, the process checks the corresponding pixel in SEL_SURFACE. If the pixel in SEL_SURFACE is white, the pixel value in the background image is replaced with a nearby foreground pixel whose corresponding pixel in SEL_SURFACE is black. One advantage to pushing images to the selector layer and/or reducing the number of images per layer is that the resulting layers may be compressed with higher efficiency.

[0114] As mentioned above, various compression techniques may be used to compress the various images. For example, for each image that is 1 bpp, one may compress it using G4 compression. For each image that is 24 bpp, one may compress it using JPEG compression as known in the art.

[0115] FIG. 11 shows a process for merging images. Images may be processed all together or may be separated into groups (referred to herein as “chunks”). The images in the chunks may be grouped by image type. Alternatively, the chunks may be grouped by the order in which they were created. The chunks may have a predetermined maximum number of images or may not.

[0116] In FIG. 11, chunk 1 has N images. The images are arranged in order of proximity to each other. Proximity is described below in relation to FIG. 13. Proximity may be viewed as the physical distance between the images or may be the closeness of the images to each other for merging purposes. If two images overlap, their proximity value is “0”, meaning they have the lowest proximity value and should be merged. Images that should not be merged may be set to have a proximity value of 1 or more. It is appreciated that any proximity scale may be used.

[0117] All images in chunk 1 are compared against each other and each pair of images is ranked in terms of proximity value. If N=5 in FIG. 11, the pairs of images would be as follows:

• • [0118] Image 1, Image 2
  • [0119] Image 1, Image 3
  • [0120] Image 1, Image 4
  • [0121] Image 1, Image 5
  • [0122] Image 2, Image 3
  • [0123] Image 2, Image 4
  • [0124] Image 2, Image 5
  • [0125] Image 3, Image 4
  • [0126] Image 3, Image 5
  • [0127] Image 4, Image 5

[0128] The proximity for each pair is determined and the pairs ordered as shown in FIG. 11 for chunk 1 on the left side of the Figure.

[0129] In step 1101, for the first pair of images, the process determines if the threshold is less than a predetermined threshold. If yes, then the images are merged in step 1102 and the proximity recalculated for the remaining images. If the proximity from step 1101 is higher than the threshold, then the merging may stop in step 1104. For example, the threshold may be set to any value between the low proximity value (meaning the images should be merged) and the high proximity value (meaning the images should not be merged). The range for the threshold may be 0.4–0.6. It is noted that the threshold value may be higher or lower than the above range depending on the types of images, the ratios of the types of images and other factors.

[0130] As set forth above, the process attempts to merge images together that are proximate to each other. Another advantage may be achieved in minimizing the number of resulting images the MRC operation needs to process. In this case, even though the images may not have a proximity below the threshold used in 1101, a desired number of images per chunk may be specified in order to minimize the number of images needing to be processed. Step 1103 represents a determination of whether the number of images in the chunk is less than the desired number of images in the chunk. For example, the desired number of images may be 4. So, even though the proximity value between any two of the images may be high, the images may still be merged (step 1102) to reduce the number of resultant images and the proximity of the resulting image pairs recalculated in step 1105.

[0131] FIG. 12 shows an example of the merging function stepping through pairs of images and the resulting images. The single images are represented by image areas 1-N 1201–1205 respectively. The merging process 1206 moves among the images 1201–1205. The merging of any two images may be a simple merge process (process 1207) in which the resulting image (image area A 1209, which is a single image and is treated as a background image) does not result in any MRC images. Alternatively, the resulting merge may be a complex merge with MRC as shown in process 1208. There are at least two types of merge results from the MRC merge 1208. The first 1211 is image area C in which background and selection layers are produced. The second 1212 is image area D in which background, selection, and foreground layers are produced. This ordering of single (background) image, MRC with background and selection, and MRC with background, selection, and foreground layers is also the preference for determining which merge to perform. That is, one would rather produce an MRC file with a single background layer than an MRC file with background, selection, and foreground layers.

[0132] FIG. 13 shows a process for determining proximity for any two image areas. Two image areas A 1301 and B 1302 are checked for overlap in step 1303. If the images overlap, then the proximity is set to 0 in step 1307. If not, the process determines if both images are currently MRC images in step 1304. If both images are MRC images, then the proximity of the images is set (step 1308) to a value between 0 and a high value (here, the high value being 1). This intermediate value may be a fixed value for all situations (e.g., 0.5). Alternatively, the value may be set as a ratio. In one example, the ratio may be the ratio of efficiency of combining the image areas. In other words, the ratio may be the unused space of the merged image divided by the total area of the combined images. This ratio is shown by equation in step 1308.

[0133] FIG. 14 shows an example of determining the unused space. In FIG. 14, text image A 1401 is being considered for combination with text image B 1402. In this example, the bounding areas of 1401 and 1402 are shown by rectangles. The combined image area of the two areas 1401 and 1402 results in unused space 1403 shown bounded by dotted lines. In an alternate embodiment, the unused space may be based on a rectangular grid, resulting in the total area including 1401, 1402, area enclosed by the dotted lines 1403 and outlying areas 1404 and 1405. In the first example, the unused space includes area 1403. In the second example the unused space includes the unused area 1403, 1404, and 1405.

[0134] Referring back to FIG. 13, if both images are not currently MRC images, then the process determines if both images are text/line images in step 1305. If yes, and the images are the same color (step 1306), the proximity is set in step 1308 as described above.

[0135] If the text/line images are not the same color, MRC needs to be used so the proximity is set high (e.g. 1) as shown in step 1309. Alternatively, the proximity may be set high as shown in step 1310 in which the proximity is set to a coefficient times the new MRC area generated by the merger of the two images divided by the total area of the combined images.

[0136] If the outcome of step 1305 is no, then the proximity is set in step 1310. Alternatively, one may set the proximity as in step 1309.

[0137] Once the merged files are created, the amount of space consumed by the original images in the combined images may be remembered. There are different ways of counting the space for merged images. FIG. 15A shows three images (1–3) in which each is three units in size. It is appreciated that any designation of space may be used including square centimeters, square millimeters, square inches, pixels and the like. Image 1 overlaps with image 3 and image 2 overlaps with image 3. In FIG. 15B, 1501 shows the combination of images 1 and 2. After the merger of the combined image 1+3 with image 2, the resultant combination is represented as 1502. In 1502, the number of actually used units is 7. However, this number may be approximated by taking the combination of images 1 and 3 (1503) and adding the size of image 2 1504 resulting in the approximate size of 8 units.

[0138] FIG. 15C shows yet another representation. Here, images 1 and 2 are combined first resulting in image 1505. Adding image 3 results in image 1506, again being 7 units in size as the center unit of image 2 and the bottom unit of image 3 are not counted separately but combined. Alternatively, this value of the size of the used space in the combined image may include 1507 of images 1 and 2 with image 3 1508, yielding a total of 9 units. In yet a further embodiment, the size of the merged image may be capped at the total size of the combined image.

[0139] While exemplary systems and methods embodying the present invention are shown by way of example, it will be understood, of course, that the invention is not limited to these embodiments. Modifications may be made by those skilled in the art, particularly in light of the foregoing teachings. For example, each of the elements of the aforementioned embodiments may be utilized alone or in combination with elements of the other embodiments. Although the invention has been defined using the appended claims, these claims are exemplary in that the invention is intended to include the elements and steps described herein in any combination or sub combination. Accordingly, there are any number of alternative combinations for defining the invention, which incorporate one or more elements from the specification, including the description, claims, and drawings, in various combinations or sub combinations. It will be apparent to those skilled in the relevant technology, in light of the present specification, that alternate combinations of aspects of the invention, either alone or in combination with one or more elements or steps defined herein, may be utilized as modifications or alterations of the invention or as part of the invention. It is intended that the written description of the invention contained herein covers all such modifications and alterations.