JP2007193655A - Electronic document data processor, electronic document data processing method and program for functioning computer as electronic document data processor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an electronic document data processor generating XML data having suppressed data size. <P>SOLUTION: The electronic document data processor 100 is provided with an electronic document file input part 110, a printing/drawing data generation part 120, an XML data generation part 130, and a control part 150. The XML data generation part 130 includes a printing/drawing instruction classification part 131 for classifying drawing instructions, an XML data optimizing part 132 for removing the redundancy of data to be drawn and an XML data conversion part 136 for generating XML data for output from an electronic document. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a technique for processing electronic document data. More specifically, the present invention relates to a technique for converting a file expressed in a binary data format expressing electronic document data obtained by executing a print execution function of an application program into a file format based on a data description language.

As an example of a conventional electronic document data processing apparatus and electronic document data processing method, Japanese Patent Laid-Open No. 2003-108331 (Patent Document 1) discloses an electronic document processing apparatus. According to this electronic document processing apparatus, a file expressed by a description based on the first language specification expressing the electronic document obtained as a result of the print execution function of the application program is based on the XML ((eXtensible Markup Language)) language specification. Conversion processing can be performed to a file format expressed by description.
JP 2003-108331 A

  Currently, the process of converting the first file according to the description based on the language specification expressing the electronic document data obtained as a result of the output of the print execution function of the application program into the second file according to the description based on the XML language specification is as follows. This is realized by converting each of the descriptions constituting the first file.

  According to the electronic document processing apparatus disclosed in Japanese Patent Laid-Open No. 2003-108331, the output file format is composed of a representation of description based on a specified XML language specification. At this time, a description expression that is originally handled as one image on the application program may be expressed as a set of a plurality of images in the first file. Similarly, what is expressed as one character string may be expressed as a set of a plurality of character strings.

  As a result, the description expression included in the second file obtained by the conversion is expressed by a description based on the language specification, but the redundant description expression included in the first file is inherited by the description expression. May be. The redundant descriptive expression may affect the size of a file obtained by conversion, or may affect the processing of an application program that uses the converted file.

  The present invention has been made to solve the above-described problems, and a first object of the present invention is to provide an electronic document data processing apparatus that generates a file capable of reducing the data size.

  A second object of the present invention is to provide an electronic document data processing apparatus capable of generating a file that can smoothly execute processing of an application program that uses a converted file.

  A third object of the present invention is to convert the electronic document data expressed based on the first language specification into a file format expressed by a description based on the second language specification. It is an object of the present invention to provide an electronic document data processing apparatus capable of generating a file with less redundant description expression.

  A fourth object of the present invention is to provide a program for causing a computer to function as an electronic document data processing apparatus for generating a file capable of reducing the data size.

  A fifth object of the present invention is to provide a program for causing a computer to function as an electronic document data processing apparatus capable of generating a file that can smoothly execute processing of an application program that uses the converted file. is there.

  A sixth object of the present invention is to convert the second file format when electronic document data expressed based on the first language specification is converted into a file format expressed by a description based on the second language specification. It is to provide a program for causing a computer to function as an electronic document data processing apparatus capable of generating a file with fewer redundant description expressions.

  In order to solve the above problems, an electronic document data processing device according to an aspect of the present invention provides a storage means for storing an electronic document file represented by a data format unique to an application program, and an instruction to output the electronic document file. Based on the input means to be received, the generating means for generating a plurality of drawing commands from the electronic document file based on the instruction, and on the basis of the mutual relationship between the drawing commands, each drawing command is divided into data attributes and data contents. Conversion means for converting into data represented by a data description language described in association with each other.

  Preferably, the data description language includes XML (eXtensible Markup Language) data.

Preferably, the data description language includes a vector image description language.
Preferably, the converting unit includes an analyzing unit that analyzes a data structure of each drawing command, an identifying unit that identifies a mutual relationship between the drawing commands based on a result of the analysis by the analyzing unit, and an identified mutual relationship. And a rendering command converting means for converting each rendering command into data represented by a data description language.

  Preferably, the drawing command includes a plurality of records classified according to any of a plurality of predefined classification criteria. Each record includes data attributes in the electronic document file. The analysis means extracts data attributes in the electronic document file for each record. The identification unit identifies the mutual relationship based on the attribute of each data extracted by the analysis unit.

  Preferably, the identification unit includes an extraction unit that extracts data having a common attribute from each of the plurality of drawing commands, and a grouping unit that groups the data extracted by the extraction unit for each attribute.

  Preferably, the identifying means extracts each text drawing data for displaying each adjacent text based on preset coordinates, and each text drawing extracted by the text extracting means. Combining means for combining the data into one data based on the coordinates.

  Preferably, the identification means extracts each image data for displaying each image adjacent to each other based on preset coordinates, and each image data extracted by the image extraction means. And combining means for combining the data into one data based on the coordinates.

  Preferably, the application program outputs a print command for printing the electronic document file based on the instruction. The generation unit generates a plurality of drawing commands based on the print command.

  Preferably, the electronic document data processing apparatus further includes output means for outputting data generated by conversion by the conversion means.

  Preferably, the output means includes display means for displaying the electronic document file based on the data generated by the conversion.

  Preferably, the output means includes a data output interface that outputs data generated by the conversion.

  Preferably, the drawing command includes a command indicating the start of the metafile, a command for drawing the object, and a command indicating the end of the metafile.

  Preferably, the command for drawing an object includes any one of a command for drawing a diagram, a command for coloring a drawn image, a command for drawing a character, and a command for specifying a color for drawing a character.

  According to another aspect of the present invention, there is provided an electronic document data processing method comprising: preparing an electronic document file represented by a data format specific to an application program; receiving an instruction to output the electronic document file; Based on the step of generating a plurality of drawing commands from the electronic document file and the mutual relationship between the drawing commands, each drawing command is represented by a data description language in which data attributes and data contents are described in association with each other. Converting to data.

  According to still another aspect of the present invention, a program for causing a computer to function as an electronic document data processing device is provided. The program includes a step of preparing an electronic document file represented by a data format specific to the application program in a computer, a step of receiving an instruction to output the electronic document file, and a plurality of drawing instructions from the electronic document file based on the instruction. And a step of converting each drawing command into data represented by a data description language in which the attribute of the data and the content of the data are described in association with each other based on the mutual relationship between the drawing commands. Let

  According to the electronic document data processing apparatus of the present invention, when generating XML format data from a drawing command for printing application data, the related drawing command is identified, redundant data is omitted, and the data is saved. Combined. As a result, the size of the converted XML data is reduced. In other aspects, highly reusable XML data can be generated.

  According to the electronic document data processing method of the present invention, when generating XML format data from a drawing command for printing application data, the related drawing command is identified, redundant data is omitted, and the data is saved. Combined. As a result, the size of the converted XML data is reduced. In other aspects, highly reusable XML data can be generated.

  According to the program according to the present invention, the computer can function as the electronic document data processing apparatus as described above. As a result, the computer can generate XML data in which the data size after conversion is reduced. In addition, the computer can generate highly reusable XML data in other aspects.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

  With reference to FIG. 1, an electronic document data processing apparatus 100 according to an embodiment of the present invention will be described. FIG. 1 is a block diagram showing a schematic configuration of functions realized by the electronic document data processing apparatus 100. The electronic document data processing apparatus 100 includes an instruction input unit 102, an electronic document file input unit 110, a print drawing data generation unit 120, an XML data generation unit 130, a control unit 150, a temporary storage unit 160, and a storage unit. 170 and an output unit 180.

  The XML data generation unit 130 includes a print drawing command classification unit 131, an XML data optimization unit 132, and an XML data conversion unit 136. The XML data optimization unit 132 includes a common attribute grouping management unit 133, a text drawing data optimization unit 134, and an image drawing data optimization unit 135. The XML data conversion unit 136 includes an XML header generation unit 137, an XML footer generation unit 138, a graphic drawing XML data generation unit 139, a text drawing XML data generation unit 140, an image drawing XML data generation unit 141, and attribute information. A management unit 142 and a current object management unit 143 are included.

  The instruction input unit 102 receives an instruction input from the outside of the electronic document data processing apparatus 100. The instructions include an electronic document display instruction, an electronic document output instruction, and the like.

  The electronic document file input unit 110 displays a user interface screen for selecting a file, and accepts an input by the user for selecting a name of the displayed file. The electronic document is realized as an electronic document generated by, for example, document creation software or spreadsheet software. Also, the electronic document file input unit 110 receives an input of an electronic document file from the outside. For example, the electronic document file input unit 110 functions as a data communication interface and accepts input of an electronic document file. When the electronic document data processing apparatus 100 itself has an electronic document creation function, it accepts an input for creating the electronic document. In this case, the electronic document file input unit 110 is realized as a touch panel, a keyboard, a mouse, or the like, for example.

  The print drawing data generation unit 120 generates a drawing command based on the print function of the application program associated with the electronic document file whose input is received by the electronic document file input unit 110. The drawing command is generated, for example, when an electronic document print instruction is input via the instruction input unit 102. Here, a file named “test.document” will be described as an example when document creation software is used. First, the extension “document” of the file name is associated with the document creation software. This software has a print function. When the user designates this file name and inputs a print instruction to the electronic document data processing apparatus 100, the print function of the document creation software causes the test. A document drawing command corresponding to the document is generated.

  The XML data generation unit 130 analyzes data representing the print drawing command generated by the print drawing data generation unit 120 and generates data conforming to the XML format (hereinafter simply referred to as XML data). The XML data generation unit 130 converts each drawing command into data represented by a data description language in which data attributes and data contents are associated with each other based on the mutual relationship between the print drawing commands. The format of the XML data is, for example, the SVG (Scalable Vector Graphics) format. Specifically, the print drawing command classification unit 131 classifies the print drawing commands. This classification is performed according to, for example, attribute data included in the drawing command.

  The XML data optimizing unit 132 examines the mutual relationship between the print drawing commands, and generates XML data corresponding to the print instruction without generating redundant XML data. Specifically, the common attribute grouping management unit 133 checks the attribute data of each print drawing command and groups the common attribute data. The text drawing data optimizing unit 134 extracts adjacent text drawing data according to predetermined coordinates, and combines a plurality of text drawing data into one according to the coordinates. The image drawing data optimizing unit 135 extracts adjacent image drawing data or overlapping image drawing data according to the coordinates, and synthesizes the extracted image drawing data into one.

  The XML data conversion unit 130 converts the print drawing command into XML data. Specifically, the XML header generation unit 137 generates an XML header from a header command included in the print drawing command. The XML footer generating unit 138 generates an XML footer from an end command included in the print drawing command. The graphic drawing XML data generation unit 139 generates XML graphic drawing data from a graphic drawing command included in the print drawing command. The text drawing XML data generation unit 140 generates XML text drawing data from a text drawing command included in the print drawing command. The image drawing XML data generation unit 141 generates XML image drawing data from an image drawing command included in the print drawing command. The attribute information management unit 142 manages the attribute information generated in the print drawing command. The current object management unit 143 manages attribute information, text color, and the like that are currently selected or specified in the conversion processing to XML data.

  The control unit 150 controls the data input operation, the output operation, and the execution of the arithmetic processing operation as described above in the electronic document data processing apparatus 100.

  The temporary storage unit 160 stores data input from the outside or data generated by the XML data generation unit 130 in a volatile manner.

  The storage unit 170 stores data input from the outside or data generated by the operation of the electronic document data processing apparatus 100 in a nonvolatile manner.

  The output unit 180 executes an output operation by the electronic document data processing apparatus 100. The output operation includes, for example, display of an image based on XML data, text, or output of XML data to the outside.

  The data structure of the electronic document data processing apparatus 100 will be described with reference to FIGS. FIG. 2 is a diagram conceptually showing one aspect of storage of the electronic document file in storage unit 170. As described above, the electronic document file is generated by executing document creation software or spreadsheet software. The electronic document file is represented by a data format unique to each software. The electronic document file 200 includes text areas 210 and 220, graphics 230 and 240 represented as rectangles, and two images 250 and 260.

  FIG. 3 is a diagram illustrating an aspect of print drawing data generated from electronic document file 200 shown in FIG. The print drawing data is stored in the temporary storage unit 160, for example. Specifically, the print drawing data generation unit 120 uses the print function of the application program associated with the electronic document file 200 based on the print instruction input via the instruction input unit 102 to print the electronic document data. Generate drawing instructions. The print drawing data generation unit 120 stores the generated data in an area secured in advance in the temporary storage unit 160. The file format of data to be stored is represented by EMF (Enhanced Meta File) in the Windows (registered trademark) environment, for example. The EMF is actually binary data, but as shown in FIG. 3, text and graphics drawing commands are expressed in units of records. EMF records are classified as follows.

(1) Header instruction The header instruction represents the start of EMF. In the example of the print drawing data file 300 shown in FIG. 3, the “EMR_HEADER” record shown in the first line corresponds to this.

(2) End command The end command represents the end of the EMF. In the print drawing data file 300, for example, “EMR_EOF” shown in the 56th line corresponds.

(3) Pen generation instruction The pen generation instruction represents generation of a pen. Specifically, the “EMR_CREATEPEN” record is applicable (for example, the second row).

  Here, the pen represents the attribute of “line”. The “EMR_CREATEPEN” record includes “pen1” as the handle name that is the pen identifier, “# 000000” (black) as the pen color, and “2” as the pen width. When the pen specified in this way is used, the line drawn by the pen generation command has the color “black” and the thickness “2”.

(4) Brush generation instruction The brush generation instruction represents generation of a brush. In the print drawing data file 300, an “EMR_CREATEBRUSHINDIRECT” record corresponds. The brush represents an attribute of “filling”. For example, the “EMR_CREATEBRUSHINDIRECT” record shown in the fourth line of the print drawing data file 300 includes “brush1” as the handle name that is the brush identifier and “# FF0000” (red) as the brush color. When the brush specified in this way is used, the graphic drawn based on the brush generation command is painted in “red”.

(5) Font generation instruction The font generation instruction represents generation of a font. In the print drawing data file 300, an “EMR_EXTCREATEFONTINDIRECTW” record corresponds. The font represents text attributes. For example, in the “EMR_EXTCREATEFONTINDIRECTW” record shown in the 10th line of the print drawing data file 300, “font1” is used as the handle name that is the font identifier, “MS Gothic” is used as the font family representing the font name, and the font size is “44”. ”And font weight“ 700 ”. The text drawn using the font specified in this way has a typeface of “MS Gothic”, a size of “44”, and a thickness of “700”.

(6) Text color designation command The text color designation command designates the text color. In the print drawing data file 300, “EMR_SETTEXTCOLOR” corresponds. For example, “EMR_SETTEXTCOLOR” in the 12th line designates the text color as “# 000000” (black). Therefore, the text drawn after that becomes black.

(7) Object selection instruction The object selection instruction represents selection of an object. Here, the object includes the above-described pen, brush, font, and the like. In the print drawing data file 300, an “EMR_SELECTOBJECT” record corresponds. The pen, brush, and font generated by the commands (3) to (5) are effective only when they are selected by the object selection command. For example, the “EMR_SELECTOBJECT” record in the third line in the print drawing data file 300 represents the selection of the pen with the handle name “pen1” generated in the second line. As a result, when a graphic drawing command to be described later is executed after the command, the color of the graphic line is “# 0000000” (black) and the thickness is “2”.

(8) Graphic Drawing Command The graphic drawing command represents drawing of a graphic. In the print drawing data file 300, the “EMR_RECTANGLE” record represents rectangular drawing. Specifically, the “EMR_RECTANGLE” record shown in the sixth line of the print drawing data file 300 represents a drawing of a rectangle whose upper left coordinates are (100, 100) and lower right coordinates are (1100, 600). . The rectangle drawn by this command has a line color of “# 000000” (black), a line width of “2”, and a fill color of “# FF0000” depending on the pen and brush selected at that time. (Red). Note that the graphic drawing command is not limited to a command for drawing a rectangle, and may include, for example, a command for drawing a line, circle, or other graphic.

(9) Text Drawing Command The text drawing command represents text drawing. In the print drawing data file 300, an “EMR_EXTTEXTOUTW” record corresponds. For example, the “EMR_EXTTEXTOUTW” record shown in the 13th line of the print drawing data file 300 indicates that the text “No.” is drawn at the coordinates (200, 200). The text drawn at this time is “MS Gothic” in the font type, “44” in size, “700” in thickness, and “# 000000” in color depending on the currently selected or designated font and text color. (Black).

(10) Image Drawing Command The image drawing command represents image drawing. In the print drawing data file 300, an “EMR_BITBLT” record corresponds. For example, the “EMR_BITBLT” record shown in the 52nd line in the print drawing data file 300 has the coordinates (300, 800), the width “1700”, the height “500”, and the data attribute “. "Represents that the image data specified by""is drawn.

  Note that the electronic document file 200 shown in FIG. 2 includes two images 250 and 260. In contrast, the print drawing data file 300 shown in FIG. 3 includes four image drawing command “EMR_BITBLT” records as shown in the 52nd to 55th lines. That is, one image of the electronic document file may be divided into a plurality of image drawing commands in the print drawing data generated corresponding to the file.

  Note that the print drawing data shown in FIG. 3 is expressed in such a manner that information of each record of the EMF can be understood by those skilled in the art for the sake of simplicity. In practice, each piece of information is represented by a data structure defined by the EMF.

  FIG. 4 is a diagram showing a state in which the records are converted into SVG format data on a one-to-one basis for each record without identifying the mutual relationship of the records included in the print drawing data file 300 shown in FIG. The SVG record file therefore contains redundant data as shown below. For example, in the RECT elements shown in the third and fourth lines of the file 400, both elements include “stroke =“ # 000000 ”stroke-width =“ 2 ”” as attribute data. This attribute is a common attribute included in all elements.

  In addition, the text elements shown in the 5th to 22nd lines in the file 400 all include “fill =“ # 000000 ”” as attribute data.

  Further, the data representing the drawing of the text of “first game” shown in the fifth to seventh lines is obtained by dividing the EMF record into “first”, “1”, and “match”. . Therefore, if the text of the “first game” can be expressed as one text element, XML data with high reusability can be generated by reducing the data amount.

  Further, as shown in the 24th and 25th lines in the file 400, the data representing the drawing of the image 250 shown in FIG. 2 is converted into one-to-one because the EMF record is divided into two. The divided SVG data is also divided into two. If these data can also be expressed as one image element, the amount of data for rendering an image can be reduced.

  FIG. 5 is a diagram showing the data structure of the SVG format generated by electronic document data processing apparatus 100 according to the present embodiment. As will be described later, the SVG file 500 is grouped for each instruction grouped by identifying the relationship between the records. A manner of generating the SVG file 500 will be described in detail with reference to FIGS.

  FIG. 6 is a diagram conceptually showing a table generated by the electronic document data processing apparatus 100. The table is generated, for example, in an area secured in the temporary storage unit 160, and the contents are updated according to the processing of each command. Specifically, the temporary storage unit 160 includes a pen attribute information management table 610, a brush attribute information management table 620, and a font attribute information management table 630. The pen attribute information management table 610 includes a handle name 611, a pen color 612, and a pen width 613. For example, the data record 615 includes “pen1” as the handle name, “# 000000” as the pen color, and “2” as the pen width.

  The brush attribute information management table 620 includes a handle name 621 and a brush color 622. For example, the data record 625 includes “brush1” as the handle name and “# FF0000” as the brush color. The data record 626 includes “brush2” as the handle name and “# FFFF00” as the brush color.

  The font attribute information management table 630 includes a handle name 631, a font family 632, a font size 633, and a font weight 634. For example, the data record 635 includes “font1” as the handle name, “MS Gothic” as the font family, “44” as the font size, and “700” as the font weight. The data record 636 includes contents with different handle names and font weights.

  FIG. 7 is a diagram showing how data changes in the current object management table 700. The current object management table 700 is managed by the current object management unit 143. The current object management unit 143 sequentially updates the records in the current object management table 700 in accordance with the instruction processing in the XML data generation unit 130.

  The current object management table 700 includes an area 701 for storing objects and an area 702 for storing handle names. For example, in the state (A), the data record 710 includes “pen” as an object and “pen1” as a handle name.

  The state (A) is generated immediately after the object selection command in the third line of the print drawing data file 300 shown in FIG. 3 is processed, for example.

  Thereafter, when the object selection command shown in the fifth line is processed, the current object management table 700 is updated to that shown in the state (B). That is, the current object management table 700 includes a data record 720 in addition to the data record 710. The data record 720 includes “brush” as an object and “brush1” as a handle name.

  Thereafter, when the object selection command shown in the eighth line is processed, the current object management unit 143 updates the current object management table 700. By the update, the table is changed to that shown in the state (C). That is, in the state (C), the data record 720 includes “brush2” instead of “brush1” in the state (B) as a handle name.

  Thereafter, when the object selection command in the eleventh line of the print drawing data file 300 is processed, the current object management table 700 is updated to that shown in the state (D). That is, the current object management table 700 includes a data record 730 in addition to the data records 710 and 720. The data record 730 includes “font” as an object and “font1” as a handle name.

  When the command is further processed and the object selection command shown in the 20th line is processed, the current object management unit 143 updates the current object management table 700. By this update, the current object management table 700 is switched to that shown in the state (E). That is, the current object management table 700 includes “font2” in the data record 730 in place of the handle name “font1” so far.

  In this way, the current object management table 700 is sequentially updated, and conversion from the print drawing data file 300 to SVG data is performed.

  FIG. 8 is a diagram showing the configuration of the text color management table 800. The text color management table 800 is generated in an area secured in the temporary storage unit 160. Text color management table 800 includes an area 810 for representing the current text color. In this area, data designated by the instruction shown in FIG. 3 is stored. The current object management unit 143 sequentially updates the contents of the text color management table 800 in accordance with the command processing shown in FIG.

  The control structure of the electronic document data processing apparatus 100 will be described below with reference to FIGS. FIGS. 9 to 26 are flowcharts showing the procedure of processing executed by each unit (FIG. 1) of the electronic document data processing apparatus 100.

  Referring to FIG. 9, in step S910, control unit 150 reads one EMF record stored in print drawing data generation unit 120. In step S920, the print drawing command classification unit 131 classifies the record according to the attribute included in the read record. If the read record is a header command, control is transferred to step S930. If the read record is a pen generation command, control is transferred to step S940. If the read record is a brush generation command, control is transferred to step S950. If the read record is a font generation command, control is transferred to step S960. If the read record is a text color designation command, control is transferred to step S970. If the read record is an object selection command, control is transferred to step S980. If the read record is a graphic drawing command, control is transferred to step S1000. If the read record is a text drawing command, control is transferred to step S1800. If the read record is an image drawing command, control is transferred to step S2500. If the read record is an end command, control is transferred to step S2600.

  In step S930, the XML header generation unit 137 executes processing for generating an XML header according to the header instruction. Specifically, the XML header generation unit 137 writes an xml declaration indicating the start of SVG data and a start tag of the svg element (first and second lines shown in FIG. 5).

  In step S940, the attribute information management unit 142 extracts pen attribute information based on the pen generation instruction, and registers the attribute information in the pen attribute information management table 610 (FIG. 6).

  Specifically, the attribute information management unit 142 extracts pen attribute information from the “EMR_CREATEPEN” record, and writes the extracted information in each area of the pen attribute information management table 610. In the example shown in FIG. 6, information “pen1” as the handle name, “# 000000” as the pen color, and “2” as the pen width are registered.

  In step S950, the attribute information management unit 142 extracts brush attribute information based on the brush generation command, and registers the extracted information in the brush attribute information management table 620 (FIG. 6). Specifically, the attribute information management unit 142 extracts brush attribute information from the “EMR_CREATEBRUSHINDIRECT” record, and stores information corresponding to each area of the attribute information management table 620. For example, in the example shown in FIG. 6, “brush1” is registered as the handle name and “# FF0000” is registered as the brush color as the data record 625, respectively.

  In step S960, the attribute information management unit 142 extracts font attribute information based on the font generation command, and registers the extracted information in the font attribute information management table 630.

  In step S970, current object management unit 143 extracts text color information based on the text color designation command, and registers the extracted information in text color management table 800 (FIG. 8).

  In step S980, current object management unit 143 updates current object management table 700 (FIG. 7) based on the object selection command.

  In step S1000, the common attribute grouping management unit 133 executes a “graphic drawing command common attribute grouping process” to be described later based on the graphic drawing command. When this process is executed, the common attribute grouping process state is classified, and each process based on the result of the classification is executed.

  In step S1800, common attribute grouping management section 133 executes a “text drawing command common attribute grouping process” to be described later based on the text drawing command. When this processing is executed, the processing is performed according to the processing state of the image drawing command.

  In step S2500, XML data generation unit 130 executes an XML rendering process for an image rendering command, which will be described later, based on the image rendering command. When this processing is executed, each processing based on the result of classification of the processing state of the image rendering command is realized.

  In step S2600, the XML data generation unit 130 executes an “XML generation end process” to be described later based on the end command. When this processing is executed, the common attribute grouping processing state is classified, and each processing based on the result of the classification is performed, and then an XML footer is generated.

  Referring to FIG. 10, in step S1010, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is the initial state, control is transferred to step S1020. If the processing state is before the start of text rendering command grouping, during font attribute grouping, or during text color attribute grouping, control is transferred to step S1200. If the processing state is before the grouping of the graphics drawing command, the grouping of pen attributes, or the grouping of text color attributes, control is transferred to step S1300.

  In step S1020, common attribute grouping management section 133 determines whether or not the processing state of the image rendering command is being processed. If common attribute grouping management section 133 determines that the processing state is being processed (YES in step S1020), the control moves to step S1100. Otherwise (NO in step S1020), control is transferred to step S1030.

  In step S1030, the common attribute grouping management unit 133 retains the currently selected pen and brush handle names and the graphic drawing command, and sets the common attribute grouping processing state to “graphic drawing command. "Before starting grouping". These pieces of information are stored, for example, in an area secured in advance in the temporary storage unit 160 before processing.

  In step S1100, the common attribute grouping management unit 133 executes an “image drawing command end process” to be described later. When this processing is executed, the processing state of the image drawing command is set to “initial state”.

  In step S1200, the common attribute grouping management unit 133 executes a “text drawing command grouping end process” to be described later. When this process is executed, a process corresponding to the result of the classification of the common attribute grouping process state is performed.

  In step S1300, common attribute grouping management section 133 executes a “graphic drawing command XML conversion process” to be described later. When this process is executed, a conversion process according to the matching status between the pen attribute and the brush attribute is realized.

  Referring to FIG. 11, in step S1110, common attribute grouping management unit 133 writes XML data corresponding to the temporarily stored image drawing command in an area reserved in advance in temporary storage unit 160. .

  In step S1120, common attribute grouping management section 133 sets the processing state of the image rendering command to “initial state”. This state of setting is realized by writing data representing the “initial state” in an area reserved for the processing in temporary storage unit 160, for example.

  Referring to FIG. 12, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before text rendering command grouping starts”, control is transferred to step S1220. If the processing state is “grouping text color attributes”, control is transferred to step S1230. If the processing status is “grouping font attributes”, control is transferred to step S1240.

  In step S1220, common attribute grouping management unit 133 writes XML data corresponding to the text drawing command stored in temporary storage unit 160. At this time, the common attribute grouping management unit 133 writes the data in a form including the text color and font attribute information stored in the temporary storage unit 160 in the same manner.

  In step S 1230, common attribute grouping management section 133 writes the grouping end element of the font attribute information that was being grouped into an area reserved in advance in temporary storage section 160. Further, the common attribute grouping management unit 133 similarly writes the grouping end element of the text color attribute information that was being grouped into another area of the temporary storage unit 160.

  In step S1240, common attribute grouping management section 133 writes the grouping end element of the text color attribute information that was being grouped into an area reserved in advance in temporary storage section 160. Further, the common attribute grouping management unit 133 similarly writes the grouping end element of the font attribute information that was being grouped into another area of the temporary storage unit 160.

  Referring to FIG. 13, in step S1310, common attribute grouping management section 133 displays pen and brush attribute information at the time of the previous graphic drawing command stored in temporary storage section 160, and the graphic drawing concerned. The attribute information of the pen and brush at the time of command is compared. If only the pen attributes match as a result of the comparison, the control moves to step S1400. If only the brush attributes match, control is transferred to step S1500. If both pen and brush attributes match, control is transferred to step S1600. If neither the pen attribute nor the brush attribute match, control is transferred to step S1700.

  In step S1400, the common attribute grouping management unit 133 executes a first conversion process to be described later. When this process is executed, processes defined in advance according to the result of the grouping process state classification of the common attribute are realized.

  In step S1500, the common attribute grouping management unit 133 executes a second conversion process to be described later. When this process is executed, processes defined in advance according to the result of the grouping process state classification of the common attribute are realized.

  In step S1600, the common attribute grouping management unit 133 executes a third conversion process to be described later. When this process is executed, processes defined in advance according to the result of the grouping process state classification of the common attribute are realized.

  In step S1700, the common attribute grouping management unit 133 executes a fourth conversion process to be described later. When this process is executed, processes defined in advance according to the result of the grouping process state classification of the common attribute are realized.

  Referring to FIG. 14, in step S1410, common attribute grouping management section 133 classifies the common attribute grouping processing state. This classification is performed according to an attribute associated with each instruction. If the processing state is “before the start of grouping of graphic drawing commands”, control is transferred to step S1420. If the processing state is “grouping of pen attributes”, control is transferred to step S1430. If the process state is “grouping of brush attributes”, control is transferred to step S1440.

  In step S1420, common attribute grouping management section 133 writes the grouping start element included in the pen attribute information in an area secured in advance in temporary storage section 160 as a first process. As a second process, the common attribute grouping management unit 133 writes the grouping start element of the brush attribute information stored in the temporary storage unit 160 at the previous graphic drawing command to another area. As a third process, the common attribute grouping management unit 133 writes the XML data corresponding to the previous graphic drawing command stored in the temporary storage unit 160 in an area reserved for the processing of the current command. . As the fourth process, the common attribute grouping management unit 133 writes the grouping end element for the brush attribute information used in the second process to the temporary storage unit 160. As a fifth process, the common attribute grouping management unit 133 writes a grouping start element of brush attribute information for the current graphic drawing command. The common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command as a sixth process. As a seventh process, the common attribute grouping management unit 133 writes the currently selected pen and brush handle names, and sets the common attribute grouping process state as “grouping of pen attributes”. Data representing the processing state is stored in an area secured in advance in temporary storage unit 160.

  In step S1430, common attribute grouping management section 133 stores the grouping end element of the brush attribute information for the previous graphic drawing command in the area secured in temporary storage section 160 as the first processing. As a second process, the common attribute grouping management unit 133 stores the grouping start element of the brush attribute information for the current graphic drawing command in an area secured in the temporary storage unit 160. As a third process, the common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command in an area secured in the temporary storage unit 160. As a fourth process, the common attribute grouping management unit 133 writes the currently selected pen and brush handle names in the temporary storage unit 160, and sets the common attribute grouping process state to “grouping pen attributes”. And Data representing the processing state is also stored in an area secured in temporary storage unit 160.

  In step S1440, common attribute grouping management section 133 writes the grouping end element of the pen attribute information for the previous graphic drawing command in the area secured in temporary storage section 160 as the first process. As a second process, the common attribute grouping management unit 133 writes the grouping end element of the brush attribute information for the current graphic drawing command in an area different from the above area. As a third process, the common attribute grouping management unit 133 stores each handle name of the currently selected pen and brush and the current graphic drawing command in an area secured in the temporary storage unit 160, and Assume that the attribute grouping processing state is “before grouping of graphics drawing commands”. Data representing the processing state is also stored in an area secured in temporary storage unit 160.

  Referring to FIG. 15, in step S1510, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before the start of grouping of graphic drawing commands”, control is transferred to step S1520. If the processing state is “grouping of pen attributes”, control is transferred to step S1530. If the processing status is “grouping of brush attributes”, control is transferred to step S1540.

  In step S1520, the common attribute grouping management unit 133 writes the grouping start element of the brush attribute information as the first process. As a second process, the common attribute grouping management unit 133 writes the grouping start element of the pen attribute information at the time of the previous graphic drawing command held in the temporary storage unit 160 to the work area. As a third process, the common attribute grouping management unit 133 writes XML data corresponding to the previous graphic drawing command held in the temporary storage unit 160 to the work area. As a fourth process, the common attribute grouping management unit 133 writes a grouping end element for the pen attribute information referred to in the second process in the work area. As a fifth process, the common attribute grouping management unit 133 writes the grouping start element of the pen attribute information for the current graphic drawing command in the work area. As a sixth process, the common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command to the work area. The common attribute grouping management unit 133 temporarily stores the handle names of pens and brushes that are currently selected as the seventh process, and sets the common attribute grouping processing state to “grouping brush attributes”. .

  In step S1530, the common attribute grouping management unit 133 writes the grouping end element of the brush attribute information for the previous graphic drawing command in the work area as the first process. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the pen attribute information for the previous graphic drawing command in the work area. As a third process, the common attribute grouping management unit 133 temporarily stores the currently selected pen and brush handle names and the current graphic drawing command, and sets the common attribute grouping process status to “ "Before starting drawing command".

  In step S1540, the common attribute grouping management unit 133 writes the grouping end element of the pen attribute information for the previous graphic drawing command in the work area as the first process. As a second process, the common attribute grouping management unit 133 writes a grouping start element of pen attribute information for the current graphic drawing command in the work area. The common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command as a third process. As a fourth process, the common attribute grouping management unit 133 temporarily stores the handle names of the currently selected pen and brush, and sets the common attribute grouping process state to “grouping brush attributes”. And

  Referring to FIG. 16, in step S1610, common attribute grouping management section 133 classifies common attribute grouping processing states. If the processing state is “before the start of grouping of graphic drawing commands”, control is transferred to step S1620. If the processing state is “grouping of pen attributes”, control is transferred to step S1630. If the processing status is “grouping brush attributes”, control is transferred to step S1640.

  In step S1620, common attribute grouping management section 133 writes the grouping start element of the pen attribute information in the work area as the first process. As a second process, the common attribute grouping management unit 133 writes the grouping start element of the brush attribute information at the time of the previous graphic drawing command held in the temporary storage unit 160 to the work area. As a third process, the common attribute grouping management unit 133 writes XML data corresponding to the previous graphic drawing command stored in the temporary storage unit 160 to the work area. The common attribute grouping management unit 133 writes the grouping end element for the brush attribute information referred to in the second process to the work area. As a fifth process, the common attribute grouping management unit 133 writes the grouping start element of the brush attribute information for the current graphic drawing command to the work area. As a sixth process, the common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command to the work area. As a seventh process, the common attribute grouping management unit 133 writes the handle names of the currently selected pen and brush in the temporary storage unit 160, and sets the common attribute grouping process state to “Pen attribute grouping in progress”. "

  In step S1630, as a first process, common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command to the work area. As the second process, the common attribute grouping management unit 133 temporarily stores the currently selected pen and brush handle names and the current graphics drawing command, and sets the common attribute grouping process state to “ "Pen attribute grouping".

  In step S1640, as a first process, common attribute grouping management unit 133 writes XML data corresponding to the current graphic drawing command to the work area. As the second process, the common attribute grouping management unit 133 temporarily stores the currently selected pen and brush handle names and the current graphics drawing command, and sets the common attribute grouping process status to “ “Brush attribute grouping”.

  Referring to FIG. 17, in step S1710, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before the start of grouping of graphic drawing commands”, control is transferred to step S1720. If the processing state is “grouping of pen attributes”, control is transferred to step S1730. If the processing status is “grouping of brush attributes”, control is transferred to step S1740.

  In step S1720, as a first process, common attribute grouping management unit 133 writes XML data corresponding to the previous graphic drawing command stored in temporary storage unit 160 in the work area. At this time, the common attribute grouping management unit 133 writes the data to the work area in a form including the pen and brush attribute information at the time of the previous graphic drawing command temporarily stored. As the second process, the common attribute grouping management unit 133 stores the handle name of the currently selected pen and brush and the current graphic drawing command in the temporary storage unit 160, and the common attribute grouping process state Is “before the start of the graphics drawing command”.

  In step S1730, as a first process, common attribute grouping management unit 133 writes the grouping end element of the brush attribute information for the previous graphic drawing command to the work area. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the pen attribute information for the previous graphic drawing command in the work area. As a third process, the common attribute grouping management unit 133 temporarily stores the handle name of the currently selected pen and brush and the current graphic drawing command, and sets the grouping process state of the common attribute to “ "Before starting drawing command".

  In step S1740, as a first process, common attribute grouping management unit 133 writes a grouping end element of pen attribute information for the previous graphic drawing command in the work area. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the brush attribute information for the previous graphic drawing command to the work area. As the third process, the common attribute grouping management unit 133 temporarily stores the currently selected pen and brush handle names and the current graphics drawing command, and sets the common attribute grouping process status to “ "Before starting drawing command".

  Referring to FIG. 18, in step S1810, common attribute grouping management section 133 classifies common attribute grouping processing states. If the processing state is the “initial state”, control is transferred to step S1820. If the processing state is any one of “Before grouping of graphic drawing commands”, “Pen attribute grouping”, and “Brush attribute grouping”, control is passed to step S1900. If the processing state is “before text rendering command grouping start”, “grouping font attributes”, and “grouping text to attributes”, control is passed to step S2000. .

  In step S1820, common attribute grouping management section 133 determines whether or not the processing state of the image rendering command is “processing”. If common attribute grouping management section 133 determines that the processing state is “processing” (YES in step S1820), the control moves to step S1100. If not (NO in step S1820), control is transferred to step S1830.

  In step S1830, common attribute grouping management section 133 stores the handle name, text color, and text rendering command of the currently selected or designated font in temporary storage section 160, and the common attribute grouping processing state Is “before the start of grouping of text drawing commands”.

  In step S1900, the common attribute grouping management unit 133 executes a grouping end process of a graphics drawing command to be described later. When this process is executed, a process defined in advance according to the grouping process state of the common attribute is realized.

  In step S2000, the common attribute grouping management unit 133 executes an XML conversion process of a text drawing command to be described later. When this process is executed, a process defined in advance according to the continuity included in the text rendering command is realized.

  Referring to FIG. 19, in step S1910, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before starting drawing command grouping”, control is passed to step S1920. If the processing state is “grouping of pen attributes”, control is transferred to step S1930. If the processing status is “grouping of brush attributes”, control is transferred to step S1940.

  In step S1920, common attribute grouping management unit 133 writes XML data corresponding to the previous graphic drawing command stored in temporary storage unit 160 in the work area. The common attribute grouping management unit 133 writes the data in a form including the pen and brush attribute information at the previous graphic drawing command stored in the same manner.

  In step S1930, as a first process, common attribute grouping management section 133 writes the grouping end element of the brush attribute information that was being grouped into the work area. As a second process, the common attribute grouping management unit 133 writes the grouping end element of the pen attribute information being grouped into the work area.

  In step S1940, the common attribute grouping management unit 133 writes the grouping end element of the pen attribute information being grouped in the work area as the first process. As a second process, the common attribute grouping management unit 133 writes the grouping end element of the attribute information of the brushes that were being grouped into the work area.

  Referring to FIG. 20, in step S2010, the common attribute grouping management unit 133 stores the handle name and text color of the font at the time of the previous text drawing command stored in the temporary storage unit 160, and the current The font handle name and text color included in the text rendering command are compared. If only the text colors match as a result of the comparison, the control moves to step S2100. If only the font handle names match, control is transferred to step S2200. If both the font handle name and the text color match, control is transferred to step S2300. If neither the font handle name nor the text color match, control is transferred to step S2400.

  In step S2100, the common attribute grouping management unit 133 executes a fifth conversion process to be described later. When this process is executed, each process defined in advance according to the result of classification of the common attribute grouping process state is realized.

  In step S2200, common attribute grouping management section 133 executes a sixth conversion process to be described later. When this process is executed, each process defined in advance according to the result of the classification of the common attribute grouping process state is realized.

  In step S2300, common attribute grouping management section 133 executes a seventh conversion process to be described later. When this process is executed, processes specified in advance according to the result of the grouping process state classification of the common attributes are respectively executed.

  In step S2400, common attribute grouping management section 133 executes an eighth conversion process to be described later. When this process is executed, processes specified in advance according to the result of the grouping process state classification of the common attributes are respectively executed.

  Referring to FIG. 21, in step S2110, common attribute grouping management section 133 classifies the common attribute grouping processing state. As a result of the classification, when the processing state is “before the start of grouping of text drawing commands”, the control is moved to step S2120. If the processing state is “grouping text color attributes”, control is transferred to step S2130. If the processing status is “grouping font attributes”, control is transferred to step S2140.

  In step S2120, common attribute grouping management section 133 writes the text color attribute grouping start element in the work area as the first process. As a second process, the common attribute grouping management unit 133 writes a font attribute grouping start element in another work area. As a third process, the common attribute grouping management unit 133 writes XML data corresponding to the text drawing command held in the temporary storage unit 160 to the work area. As the fourth process, the common attribute grouping management unit 133 writes the grouping end element for the font attribute referred to in the second process to the work area. As a fifth process, the common attribute grouping management unit 133 writes a font attribute grouping start element for the current text drawing command in the work area. As the sixth process, the common attribute grouping management unit 133 stores the handle name, text color, and current text drawing command of the currently selected or designated font in the area secured in the temporary storage unit 160, and the common processing is performed. The attribute grouping processing state is assumed to be “grouping text color attributes”.

  In step S2130, common attribute grouping management section 133 writes XML data corresponding to the text rendering command held in temporary storage section 160 in the work area as a first process. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the font attribute information whose processing state is “grouping” in the work area. As a third process, the common attribute grouping management unit 133 writes the grouping start element of the font attribute information for the current text drawing command in the work area. As a fourth process, the common attribute grouping management unit 133 holds the handle name, text color, and current text drawing command of the currently selected or designated font in the area secured in the temporary storage unit 160, and the common processing is performed. The attribute grouping processing state is assumed to be “grouping text color attributes”.

  In step S2140, common attribute grouping management section 133 writes XML data corresponding to the text rendering command held in temporary storage section 160 in the work area as a first process. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the text color attribute whose processing state is “grouping” in the work area. As the third process, the common attribute grouping management unit 133 writes the grouping end element of the attribute of the font attribute whose processing state is “grouping” in the work area. As a fourth process, the common attribute grouping management unit 133 stores the handle name, text color, and current text drawing command of the currently selected or designated font in an area secured in advance in the temporary storage unit 160, The common attribute grouping processing state is assumed to be “before text rendering command grouping starts”.

  Referring to FIG. 22, in step S2210, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before text rendering command grouping is started”, control is passed to step S2220. If the processing state is “grouping text color attributes”, control is transferred to step S2230. If the processing state is “grouping font attributes”, control is transferred to step S2240.

  In step S2220, as a first process, common attribute grouping management section 133 writes a font attribute grouping start element in the work area. As the second process, the common attribute grouping management unit 133 writes the text color attribute grouping start element to another work area. The common attribute grouping management unit 133 writes XML data corresponding to the text drawing command held in the temporary storage unit 160 as a third process in the work area. The common attribute grouping management unit 133 writes a grouping end element in the work area for the text color attribute referred to in the second process as the fourth process. As a fifth process, the common attribute grouping management unit 133 writes a text color attribute grouping start element for the current text drawing command in the work area. As the sixth process, the common attribute grouping management unit 133 stores the handle name, text color, and current text drawing command of the currently selected or designated font in the area secured in the temporary storage unit 160, and the common processing is performed. The attribute grouping processing state is set to “grouping font attributes”.

  In step S2230, common attribute grouping management section 133 writes XML data corresponding to the text rendering command held in temporary storage section 160 in the work area as the first process. The common attribute grouping management unit 133 writes out the grouping end element of the font attribute whose processing state is “grouping” as the second process. The common attribute grouping management unit 133 writes the grouping end element of the text color attribute whose processing state is “grouping” as the third process in the work area. As the fourth process, the common attribute grouping management unit 133 stores the handle name, text color, and current text drawing command of the currently selected or designated font in the area secured in the temporary storage unit 160, The common attribute grouping processing state is assumed to be “before text rendering command grouping starts”.

  In step S2140, common attribute grouping management section 133 writes XML data corresponding to the text rendering command held in temporary storage section 160 as the first process. As the second process, the common attribute grouping management unit 133 writes the grouping end element of the text color attribute information whose processing state is “grouping” in the work area. As a third process, the common attribute grouping management unit 133 writes the grouping start element of the text color attribute information for the current text drawing command in the work area. As a fourth process, the common attribute grouping management unit 133 writes the handle name, text color, and current text drawing command of the currently selected or designated font in the area secured in the temporary storage unit 160, and the common processing is performed. The attribute grouping processing state is set to “font attribute grouping”.

  Referring to FIG. 23, in step S2310, common attribute grouping management section 133 determines whether or not the common attribute grouping processing state is “before text rendering command grouping processing”. If common attribute grouping management section 133 determines that the processing state is “before text rendering command grouping processing” (YES in step S2310), the control moves to step S2320. If not (NO in step S2310), control is transferred to step S2330.

  In step S2320, common attribute grouping management section 133 writes the text color grouping start element in the work area as the first process. As a second process, the common attribute grouping management unit 133 writes a font attribute grouping start element in another work area.

  In step S2330, common attribute grouping management unit 133 determines whether or not the y coordinate included in the text drawing command held in temporary storage unit 160 matches the y coordinate included in the current text drawing command. to decide. If common attribute grouping management section 133 determines that these y coordinates match (YES in step S2330), the control moves to step S2340. If not (NO in step S2330), control is transferred to step S2350.

  In step S2340, common attribute grouping management unit 133 determines whether or not the last character of the text drawing command held in temporary storage unit 160 is adjacent to the first character of the current text drawing command. to decide. This determination is made, for example, by comparing the coordinate values of the characters. If common attribute grouping management section 133 determines that the last character and the first character are adjacent (YES in step S2340), the control moves to step S2370. If not (NO in step S2340), control is transferred to step S2350.

  In step S2350, common attribute grouping management unit 133 writes XML data corresponding to the text drawing command held in temporary storage unit 160 in the work area. In step S2360, common attribute grouping management section 133 holds the handle name, text color, and current text drawing command of the currently selected or designated font in an area reserved in advance in temporary storage section 160. .

  In step S 2370, common attribute grouping management unit 133 adds the current text drawing command to the text drawing command held in temporary storage unit 160. In step S2380, common attribute grouping management section 133 sets the common attribute grouping processing state to “text color attribute grouping processing in progress”.

  Referring to FIG. 24, in step 2410, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is “before text rendering command grouping is started”, control is passed to step S2420. If the processing state is “grouping text color attributes”, control is transferred to step S2430. If the processing status is “grouping font attributes”, control is transferred to step S2440.

  In step S2420, common attribute grouping management section 133 writes XML data data corresponding to the text rendering command held in temporary storage section 160 in the work area as the first process. At this time, the common attribute grouping management unit 133 writes the XML data in a form including the attribute information of the font and text color that are similarly held. As a second process, the common attribute grouping management unit 133 writes the handle name, text color, and current text drawing command of the currently selected or designated font to the temporary storage unit 160, and performs a common attribute grouping process. The state is assumed to be “before the start of grouping of text drawing commands”.

  In step S2430, as the first process, common attribute grouping management unit 133 writes a grouping end element in the work area for the font attribute whose processing state is “grouping”. As a second process, the common attribute grouping management unit 133 writes a grouping end element for the text color attribute whose processing state is “grouping”. As the third process, the common attribute grouping management unit 133 writes the handle name of the currently selected or designated font and the current text drawing command of the text color in the area secured in the temporary storage unit 160, and the common The attribute grouping processing state is set to “before text rendering command grouping starts”.

  In step S2440, as the first process, common attribute grouping management unit 133 writes the grouping end element for the text color attribute whose processing state is “grouping” in the work area. The common attribute grouping management unit 133 writes out a grouping end element for the font attribute whose processing state is “grouping” as the second process. As a third process, the common attribute grouping management unit 133 writes the handle name of the currently selected or designated font and the current text drawing command of the text color to the temporary storage unit 160, and performs a common attribute grouping process The state is assumed to be “before the start of grouping of text drawing commands”.

  Referring to FIG. 25, in step S2510, common attribute grouping management unit 133 classifies the processing state of the image drawing command. If the processing state is “processing”, control is transferred to step S2530. If the processing state is the “initial state”, control is transferred to step S2520.

  In step S2520, common attribute grouping management section 133 classifies the common attribute grouping processing state. If the processing state is any of “Before grouping of graphic drawing commands”, “Pen attribute grouping”, and “Text color attribute grouping”, control is passed to step S1900. . If the processing state is one of “Before starting text rendering command grouping”, “Grouping font attributes”, and “Grouping text color attributes”, control is passed to step S1200. . If the processing state is the “initial state”, control is transferred to step S2550.

  In step S2530, image drawing data optimizing unit 135 determines whether the image region drawn by the image drawing command stored in temporary storage unit 160 is in contact with the image region drawn based on the current image drawing command, or Determine if they overlap. If image drawing data optimizing unit 135 determines that these areas are in contact with each other or overlap (YES in step S2530), control is transferred to step S2560. If not (NO in step S2530), control is transferred to step S2540.

  In step S2540, image drawing data optimizing unit 135 writes XML data corresponding to the image drawing command stored in temporary storage unit 160 in the work area.

  In step S2550, image drawing data optimizing unit 135 stores the current image drawing command in the area secured in temporary storage unit 160, and sets the processing state of the image drawing command to “processing”.

  In step S2560, image drawing data optimizing unit 135 adds the current image drawing command to the image drawing command stored in temporary storage unit 160.

  Referring to FIG. 26, in step S2610, XML data generation unit 130 classifies the common attribute grouping processing state. If the processing state is any of “Before grouping of graphic drawing commands”, “Pen attribute grouping”, and “Text color attribute grouping”, control is passed to step S1900. If the processing state is one of “Before starting text rendering command grouping”, “Grouping font attributes”, and “Grouping text color attributes”, control is passed to step S1200. . If the processing state is the “initial state”, control is transferred to step S2620.

  In step S2620, XML data generation unit 130 determines whether or not the processing state of the image rendering command is “processing”. If XML data generation unit 130 determines that the processing state is “processing” (YES in step S2620), the control moves to step S1100. If not (NO in step S2620), control is transferred to step S2630.

In step S2630, the XML data generation unit 130 generates an XML footer.
The operation of the electronic document data processing apparatus 100 based on the above-described structure and flowchart will be described. Here, a case where the electronic document data processing apparatus uses the print drawing data file 300 shown in FIG. 3 will be described.

[First line]
The control unit 150 of the electronic document data processing apparatus reads the record in the first line of the EMF (“EMR_HEADER” in the print drawing data file 300) (step S910). Since the record is a header command (step S920), XML header generation processing is executed (step S930). As a result, the xml declaration and the start tag of the svg element as shown in FIG. 5 are written. Thereafter, the process of step S910 is executed again.

[Second line]
The control unit 150 reads the record in the second line of the EMF (“EMR_CREATEPEN” in the print drawing data file 300) (step S910). Since the record is a pen generation command (step S920), the process shown in step S940 is executed. As a result, as illustrated in FIG. 6, information on the handle name “pen1”, the pen color “# 000000”, and the pen width “2” is stored in the table 610. Thereafter, the process of step S910 is executed again.

[3rd line]
The control unit 150 reads the record in the third line of the EMF (“EMR_SELECTECTJECT” in the print drawing data file 300) (step S910). Since the record is an object selection command (step S920), the process shown in step S980 is executed. As a result, as shown in FIG. 7, information indicating that the currently selected pen is the pen identified as the handle name “pen1” is registered in the table 700 (state (A)). Thereafter, the process of step S910 is executed again.

[Line 4]
The control unit 150 reads the record in the fourth line of the EMF (“EMR_CREATEBRUSHINDIRECT” in the print drawing data file 300) (step S910). Since the record is a brush generation command (step S920), the process shown in step S950 is executed. As a result, as shown in FIG. 6, information on the handle name “brush1” and the brush color “# FF0000” is stored in the table 620. Thereafter, the process of step S910 is executed again.

[5th line]
The control unit 150 reads the record in the fifth line of EMF (“EMR_SELECTBJECT” in the print drawing data file 300) (step S910). Since the record is an object selection command (step S920), the process shown in step S980 is executed. As a result, as shown in FIG. 7, information indicating that the currently selected brush is the brush identified as the handle name “brush1” is added to the table 700 (state (B)). Thereafter, the process of step S910 is executed again.

[6th line]
The control unit 150 reads the record in the sixth line of the EMF (“EMR_RECTANGLE” in the print drawing data file 300) (step S910). Since the record is a graphic drawing command (step S920), the process shown in step S1000 is executed. At this point, the grouping processing state of the common attribute is the initial state, and the processing state of the image drawing command is also the “initial state” (NO in steps S1010 and S1020). Therefore, the pen handle name “pen1”, the brush handle name “brush1”, and the graphic drawing command “EMR_RECTANGLE left =“ 100 ”top =“ 100 ”right =“ 1100 ”bottom =“ 600 ”” are stored in the temporary storage unit 160. Stored (step S1030). In addition, the control unit 150 sets the grouping state of the common attribute to “before start of grouping of graphic drawing commands”. The control unit 150 ends the process without converting the graphic drawing command into XML, and the control returns to the process that read step S1000.

[7th line]
The control unit 150 reads the EMF record on the seventh line (“EMR_CREATEBRUSHINDIRECT” in the print drawing data file 300) (step S910). Processing similar to that performed on the record in the fourth row is executed. As a result, as shown in FIG. 6, each information of the handle name “brush2” and the brush color “# FFFF00” is added to the table 620 as a data record 625. Thereafter, the process of step S910 is executed again.

[8th line]
The control unit 150 reads the EMF line 8 record (“EMR_SELECTBJECT” in the print drawing data file 300) (step S910). A process similar to the process executed for the record in the fifth row is executed. As a result, as shown in FIG. 7, information indicating that the currently selected brush is the brush identified as the handle name “brush2” is written in the table 700, and the table 700 is updated (see FIG. 7). State (C)). Thereafter, the process of step S910 is executed again.

[9th line]
The control unit 150 reads the EMF 9th line record (“EMR_RECTANGLE” in the print drawing data file 300) (step S910). Since the record is a graphic drawing command (step S920), the process shown in step S1000 is executed. At this point, since the common attribute grouping processing state is “before the start of grouping of graphic drawing commands”, the XML conversion processing of the graphic drawing commands (step S1300) is executed.

  Specifically, the pen and brush handle names at the time of the previous graphic drawing command (see the record on the sixth line) are “pen1” and “brush1”, respectively, and the pen and brush at the time of the current graphic drawing command The handle names are “pen1” and “brush2”, respectively. Therefore, only the pen handle name matches. Therefore, the first conversion process (step S1400) is executed.

  Here, since the grouping state of the common attribute is set to “before the start of grouping of graphic drawing commands” when the process for the record on the sixth line has already been executed, the first conversion process includes the step The process defined as S1420 is executed.

  That is, as the first processing, from the attribute information of the pen handle name “pen1”, the XML grouping start element “<g stroke =“ # 000000 ”representing the line color“ # 000000 ”and the line width“ 2 ”is obtained. “Stroke-width =“ 2 ”>” is written in the area secured in the temporary storage unit 160 (third line of the SVG file 500 shown in FIG. 5).

  As a second process, from the attribute information of the brush handle name “brush1”, the XML grouping start element “<g file =“ # FF0000 ”>” representing the fill color “# FF0000” is stored in the temporary storage unit 160. Is written in the area secured in (4th line of the SVG file 500).

  As a third process, the graphic drawing command “EMR_RECTANGLE left =“ 100 ”top =“ 100 ”right =“ 1100 ”bottom =“ 600 ”” ”stored in another area of the temporary storage unit 160 is converted into XML data. Then, the converted data “<rect x =“ 100 ”y =“ 100 ”width =“ 1000 ”height =“ 500 ”/>” ”is written in the area secured in the temporary storage unit 160 (SVG 5th line of file 500).

  Here, the attribute of the brush is valid only for the previous graphic drawing command written in the third process. Therefore, as a fourth process, the grouping end element corresponding to the grouping start element of the brush attribute is written in the area (sixth line of the SVG file 500).

  As a fifth process, from the attribute information of the brush handle name “brush2”, an XML grouping start element “<g fill =“ # 0000FF ”>” representing the fill color “# 0000FF” is written in the area. (7th line of SVG file 500).

  As a sixth process, the current graphic drawing command “EMR_RECTANGLE left =“ 1200 ”top =“ 100 ”right =“ 2200 ”bottom =“ 600 ”” ”is converted into XML data, and is generated by the conversion. “<Rect x =“ 1200 ”y =“ 100 ”width =” 1000 ”height =” 500 ”/>” is written in the area (the 8th line of the SVG file 500).

  As a seventh process, the pen handle name “pen1” and the brush handle name “brush2” are stored in another area secured in the temporary storage unit 160. The grouping state of the common attribute is set to “grouping pen attributes”. When the above process is completed, the process of step S910 is then executed again.

[10th line]
The control unit 150 reads the record in the 10th line of the EMF (“EMR_EXTCREATEFONTDIRECTW” in the print drawing data file 300) (step S910). Since the record is a font generation command (step S920), the process defined as step S960 is executed. Specifically, as shown in FIG. 6, each data of handle name “font1”, font family “MS Gothic”, font size “44”, and font weight “700” is recorded as data record 635 in table 630. Is done.

[11th line]
The control unit 150 reads the EMF 11th line record (“EMR_SELECTBJECT” in the print drawing data file 300) (step S910). Since the record is an object selection command (step S920), the process shown in step S980 is executed. As a result, as shown in FIG. 7, information indicating that the currently selected font is the font with the handle name “font1” is registered in the current object management table 700 (state (D)). Thereafter, the process of step S910 is executed again.

[12th line]
The control unit 150 reads the record in the 12th line of the EMF (“EMR_SETTEXTCOLOR” in the print drawing data file 300) (step S910). Since the record is a text color designation command (step S920), the process shown in step S970 is executed. As a result, as shown in FIG. 8, data 810 indicating that the currently designated text color is “# 000000” is registered in the text color management table 800.

[13th line]
The control unit 150 reads the record in the 13th line of the EMF (“EMR_EXTTEXTOUTW” in the print drawing data file 300) (step S910). Since the record is a text drawing command (step S920), the process shown in step S1800 is executed.

  At this time, since the common attribute grouping process state is “grouping pen attributes”, the process defined as step S1900 is executed. Specifically, based on the fact that the common attribute grouping process state is classified as described above, the process defined as step S1930 is executed.

  Specifically, as the first process, the grouping end element of the brush attribute information that was being grouped is written to the temporary storage unit 160 (9th line of the SVG file 500 shown in FIG. 5). As a second process, the grouping end element of the pen attribute information that was being grouped is written to the temporary storage unit 160 (10th line in the SVG file 500).

  Thereafter, the handle name “font1” of the font, the text color “# 000000”, and the text drawing command “EMR_EXTTEXTOUTW x =“ 200 ”y =“ 200 ”data =“ first ”” are stored in the temporary storage unit 160 ( Step S1830). The common attribute grouping processing state is changed to “before text rendering command grouping is started”. The control unit 150 ends the process without converting the text drawing command into XML.

[14th line]
The control unit 150 reads the EMF 14th line record (“EMR_EXTTEXTOUTW” in the print drawing data file 300) (step S910). Since the record is a text drawing command (step S920), the process shown in step S1800 is executed.

  At this point, since the common attribute grouping process state is “before text rendering command grouping starts”, the process defined as step S2000 is executed (FIG. 20).

  Specifically, the handle name and text color of the font at the time of the previous text drawing command stored temporarily are compared with the handle name and text color of the font at the time of the current text drawing command. At the time when the record on the 14th line is processed, the handle name and text color of the font at the previous text drawing command are “font1” and “# 000000”, respectively. The handle name and text color of the font at the time of this text drawing command are also “font1” and “# 000000”, respectively. Therefore, the process defined as step S2300 is executed (FIG. 20).

  Specifically, as shown in FIG. 23, at this time, the grouping process state of the common attribute is “before text rendering command grouping process”. Therefore, the process specified in step S2320 is executed. That is, first, the XML grouping start element “<g file =“ # 000000 ”>” representing the text color “# 000000” common to the previous text drawing command and the current text drawing command is temporarily stored. Is written in the unit 160 (11th line of the SVG file 500 shown in FIG. 5). Second, from the attribute information of the font handle name “font1” common to the previous text drawing command and the current text drawing command, the font family “MS Gothic”, the font size “44”, and the font weight “700”. An XML grouping start element “<g font-family =“ MS Gothic ”font-weight =“ 700 ”font-size =“ 44 ”” is written in the temporary storage unit 160 (12 lines in the SVG file 500) Eye).

  Thereafter, text drawing data combining processing is performed. First, it is confirmed whether or not the y coordinate of the text drawing command temporarily stored matches the y coordinate of the current text drawing command (step S2330). At this time, the text drawing command temporarily held is “EMR_EXTTEXTOUTW x =“ 200 ”y =“ 200 ”data =“ second ””, and therefore the y coordinate is “200”. In addition, since the current text drawing command is “EMR_EXTTEXTOUTW x =“ 244 ”y =“ 200 ”data =“ 1 ”” ”, the y coordinate is“ 200 ”. Therefore, the y coordinates included in the two text drawing commands match (YES in step S2330), the last character of the text drawing command temporarily stored and the first character of the current text drawing command Whether or not the character is adjacent is checked based on the value of the x coordinate (step S2340).

  Here, the last x coordinate of the last character “text” of the text drawing command stored temporarily is “200”. In addition, the x coordinate of the first character “1” of the current text drawing command is “244”. This x coordinate is equal to a value obtained by adding the font size “44” to the x coordinate (200) of the last character of the text drawing command stored temporarily. Therefore, it is determined that the last character of the text drawing command temporarily stored is adjacent to the last character of the current text drawing command (YES in step S2340), and these data can be combined. It becomes. Therefore, the control unit 150 adds the current text drawing command to the temporarily stored text drawing command (step S2370). As a result, the text drawing command temporarily held becomes “EMR_EXTTEXTOUTW x =“ 200, 244 ”y =“ 200 ”data =“ first ””. The common attribute grouping processing state is set to “text color attribute grouping processing in progress” (S2380).

[Line 15]
The control unit 150 reads the EMF 15th line record (“EMR_EXTTEXTOUTW” in the print drawing data file 300) (step S910). Since the record is a text drawing command (step S920), the process shown in step S1800 is executed.

  At this time, the grouping process state of the common attribute is “in process of grouping the text color attribute” unlike the case of the record in the 14th line, and therefore the process defined as step S2000 is executed ( FIG. 20).

  That is, first, the handle name and text color of the font at the time of the previous text drawing command stored temporarily are compared with the handle name and text color of the font at the time of the current text drawing command (step S2010). ). At this time, since both the handle name and the text color match, the process defined as step S2300 is executed.

  Specifically, the common attribute grouping process state is “in process of text color attribute grouping” (NO in step S2310). Further, since the text drawing command temporarily held is “EMR_EXTTEXTOUTW x =“ 200, 244 ”y =“ 200 ”data =“ first ””, the y coordinate is “200”. Further, since the current text drawing command is “EMR_EXTTEXTOUTW x =“ 288, 332 ”y =“ 200 ”data =“ game ””, the y coordinate is “200”. Therefore, it is determined that the y-coordinates of the two text drawing commands match (YES in step S2330), and control unit 150 checks whether or not the characters are adjacent (step S2340).

  Specifically, at this time, the value of the x coordinate of the last character “1” of the text drawing command temporarily held is “244”. In addition, the value of the x coordinate of the first character “trial” of the current text drawing command is “288”. The x-coordinate corresponds to a value obtained by adding the font size “44” to the x-coordinate value of the last character of the text drawing command that is temporarily held. Therefore, control unit 150 determines that the last character of the text drawing command that is temporarily held is adjacent to the last character of the current text drawing command (YES in step S2340). Data can be combined. Therefore, the control unit 150 adds the current text drawing command to the text drawing command stored in the temporary storage unit 160 (step S2370). As a result, the text drawing command is “EMR_EXTTEXTOUTW x =“ 200, 244, 288, 332 ”y =“ 200 ”data =“ first game ””. The grouping process state of the common attribute is continuously set to “during text color attribute grouping process” (step S2380).

[16th line]
The control unit 150 reads the record of the 16th line of EMF (“EMR_EXTTEXTOUTW” in the print drawing data file 300) (step S910). Since the record is a text drawing command (step S920), the process shown in step S1800 is executed.

  At this point, the grouping process state of the common attribute is “during text color attribute grouping process” as in the case of the record in the 15th line, and therefore the process defined as step S2000 is executed ( FIG. 20).

  That is, first, the handle name and text color of the font at the time of the previous text drawing command stored temporarily are compared with the handle name and text color of the font at the time of the current text drawing command (step S2010). ). At this time, since both the handle name and the text color match, the process defined as step S2300 is executed.

  Specifically, the y-coordinates of any drawing command match (YES in step S2330). Therefore, the common attribute grouping management unit 133 temporarily stores the last text drawing command “EMR_EXTTEXTOUTW x =“ 200, 244, 288, 332 ”y =“ 200 ”data =“ first game ””. The value “332” of the x coordinate of the character “go” and the value “332” of the first character “first” of the current text drawing command “EMR_EXTTEXTOUTW x =“ 1300 ”y =“ 200 ”data =“ th ”” 1300 ". In this case, even if the font size “44” is added to the “coordinate” x-coordinate value “332”, it does not become the “first” x-coordinate value “1300”. It is determined that the character is not adjacent (NO in step S2340). Therefore, the common attribute grouping management unit 133 passes a temporarily stored text drawing command to the text drawing XML data generation unit 140 and instructs the writing of the corresponding XML data.

  Specifically, the text drawing XML data generation unit 140 stores the text drawing command “EMR_EXTTEXTOUTW x =“ 200, 244, 288, 332 ”y =“ 200 ”data =“ first game ”” temporarily stored. Is converted into XML data, and the data “<text x =“ 200,244,288,332 ”y =“ 200 ”> first game </ text>” generated by the conversion is written in the temporary storage unit 160 (FIG. 5th line 13 in the SVG file 500).

  The current object management unit 143 holds the handle name and text color of the currently selected / designated font, and the text drawing command (step S2360). Specifically, the current object management unit 143 sets the font handle name “font1”, the text color “# 000000”, and the text drawing command “EMR_EXTTEXTOUTW x =“ 1300 ”y =“ 200 ”data =“ second ””. Remember. The common attribute grouping processing state is continuously set to “text color attribute grouping processing in progress” (S2380).

[17th and 18th lines]
The control unit 150 also executes the above-described processing for the records on the 17th and 18th lines of the EMF (“EMR_EXTTEXTOUTW” in the print drawing data file 300). As a result of the processing, the text drawing command temporarily retained is “EMR_EXTTEXTOUTW x =“ 1300, 1344, 1388, 1432 ”y =“ 200 ”data =“ second game ””.

[Lines 19-21]
The control unit 150 performs the same processing as described above for each record in the 19th to 21st lines of the EMF. As a result, as shown in FIG. 6, the data record 636 is added to the font attribute information management table 630. Further, as shown in FIG. 7, the data record 730 is updated, and the current object management table 700 is in the state shown in the state (E). The text color management table 800 remains in the state shown in FIG.

[Line 22]
The control unit 150 reads the record on the 22nd line (“EMR_EXTTEXTOUTW” in the print drawing data file 300) (step S910). Since the record is a text drawing command (step S920), the process shown in step S1800 is executed.

  At this point, since the common attribute grouping process state is “in process of text color attribute grouping”, the process defined as step S2000 is executed.

  Specifically, the handle name and text color of the font at the time of the previous text drawing command stored temporarily are compared with the handle name and text color of the font at the time of the current text drawing command ( Step S2010). At this time, the handle name and text color of the font at the time of the previous text drawing command are “font1” and “# 000000”, respectively. The handle name and text color of the font at the time of this text drawing command are “font2” and “# 000000”, respectively. Therefore, only the text color matches. Therefore, the fifth conversion process defined in step S2100 is executed.

  Since the current common attribute grouping process state is “text color attribute grouping process in progress”, the common attribute grouping management unit 133 performs the process defined as step S2130. Specifically, as the first process, the common attribute grouping management unit 133 temporarily stores the text drawing command “EMR_EXTTEXTOUTW x =“ 1300, 1344, 1388, 1432 ”y =“ 200 ”data = “Second game” is converted into XML data, and data “<text x =“ 1300, 1344, 1388, 1432 ”y =“ 200 ”> second game </ text>” generated by the conversion is temporarily stored. Is written into the SVG file 500 of the section 160 (14th line in the SVG file 500 shown in FIG. 5). As a second process, the common attribute grouping management unit 133 writes the grouping end element of the font attribute information that was being grouped into the SVG file 500 (15th line in the SVG file 500).

  As a third process, the common attribute grouping management unit 133 obtains the font family “MS Gothic”, the font size “44”, and the font weight “400” from the attribute information of the font handle name “font2” of the current text drawing command. "<G font-family =" MS gothic "font-weight =" 400 "font-size =" 44 "" is written to the SVG file 500 (16th line in the SVG file 500) . As a fourth process, the common attribute grouping management unit 133 performs the font handle name “font2”, the text color “# 000000”, and the text drawing command “EMR_EXTTEXTOUTW x =“ 200,244,288,332 ”y =“ 300 ”. “Data =“ start time ”” is temporarily saved. The grouping process state of the common attribute is continuously set to “text color attribute grouping process in progress”.

[Lines 23 to 50]
The control unit 150 performs the same process as described above for each record in the 23rd to 50th lines of the EMF. As a result, the XML shown in the 17th to 45th lines is written to the SVG file 500 as shown in FIG.

[Line 52]
The control unit 150 reads the record on the 52nd line (“EMR_BITBLT” in the print drawing data file 300) (step S910). Since the record is an image drawing command, the XML conversion processing (FIG. 25) of the image drawing command defined as step S2500 is executed.

  Specifically, first, since the processing state of the image rendering command is “initial state”, the grouping processing state of the common attribute is confirmed in S2520, and then, in step S2550, the current image rendering command is temporarily stored. Remembered. Specifically, the image drawing command “EMR_BITBLT x =“ 300 ”y =“ 800 ”width =“ 1700 ”height =“ 500 ”data =“. . . “” Is stored in the temporary storage unit 160. The image drawing processing state is set to “processing”.

[Line 53]
The control unit 150 reads the record on the 53rd line (“EMR_BITBLT” in the print drawing data file 300) (step S910). Since the record is also an image drawing command, the XML conversion processing (step S2500) of the image drawing command is executed.

  Specifically, since the processing state of the image drawing command is “processing”, the image drawing data optimizing unit 135 performs image drawing data combining processing (step S2530). That is, it is confirmed whether the image area drawn by the temporarily stored image drawing command is in contact with or overlaps the image area drawn by the current image drawing command. In this case, the image drawing data optimizing unit 135 performs the temporarily stored image drawing instruction “EMR_BITBLT x =“ 300 ”y =“ 800 ”width =“ 1700 ”height =“ 500 ”data =“. . . “” And the current image drawing command “EMR_BITBLT x =“ 300 ”y =“ 1300 ”width =“ 1700 ”height =“ 500 ”data =“. . . Based on “”, the positional relationship of each image is examined. The image drawing data optimization unit 135 determines that the two images are in contact with each other by a line connecting the coordinates (300, 800) and (2000, 800), and determines that the two images can be combined (step S2530). YES)

  Therefore, the image drawing data optimizing unit 135 determines that “EMR_BITBLT x =“ 300 ”y =“ 800 ”width =“ 1700 ”height =“ 500 ”data =“. . . "" And "EMR_BITBLT x =" 300 "y =" 1300 "width =" 1700 "height =" 500 "data =". . . Two image drawing commands "" are stored (step S2560).

[Line 54]
The control unit 150 reads the record on line 54 (“EMR_BITBLT” in the print drawing data file 300) (step S910). Since the record is also an image drawing command, the XML conversion processing (step S2500) of the image drawing command is executed.

  Specifically, since the processing state of the image drawing command is “processing”, the image drawing data optimizing unit 135 performs image drawing data combining processing (step S2530). That is, it is confirmed whether the image area drawn by the temporarily stored image drawing command is in contact with or overlaps the image area drawn by the current image drawing command.

  In this case, the image drawing data optimizing unit 135 performs the temporarily stored image drawing instruction “EMR_BITBLT x =“ 300 ”y =“ 800 ”width =“ 1700 ”height =“ 500 ”data =“. . . "", "EMR_BITBLT x =" 300 "y =" 1300 "width =" 1700 "height =" 500 "data =". . . ”” And the current image drawing command “EMR_BITBLT x =“ 300 ”y =“ 2000 ”width =“ 1700 ”height =“ 500 ”data =“. . . Based on “”, it is determined that the image area drawn by the temporarily stored image drawing command and the image area drawn by the current image drawing command are not touching or overlapping.

  Therefore, the image drawing data optimization unit 135 instructs the image drawing XML data generation unit 141 to write out XML data corresponding to the temporarily stored image drawing command. In response to the instruction, if there are a plurality of image drawing commands, the image drawing XML data generation unit 141 combines these commands and represents them as one image. Here, the image drawing XML data generation unit 141 includes two image drawing commands “EMR_BITBLT x =“ 300 ”y =“ 800 ”width =“ 1700 ”height =“ 500 ”data =“. . . "" And "EMR_BITBLT x =" 300 "y =" 1300 "width =" 1700 "height =" 500 "data =". . . "" And XML data representing drawing of one combined image "<image x =" 300 "y =" 800 "width =" 1700 "height =" 1000 "xlink:" ref = ". . . “/>” Is written into the SVG file 500 of the temporary storage unit 160 (the 47th line of the SVG file 500 shown in FIG. 5). The image drawing XML data generation unit 141 executes the current image drawing command, that is, “EMR_BITBLT x =“ 300 ”y =“ 2000 ”width =“ 1700 ”height =“ 500 ”data =“. . . "" Is temporarily stored (step S2540). The processing state of the image drawing command is continuously maintained as “processing”.

[Line 55]
The control unit 150 reads the record on the 55th line (“EMR_BITBLT” in the print drawing data file 300) (step S910). Since the record is also an image drawing command, the XML conversion processing (step S2500) of the image drawing command is executed.

  Further, the image drawing data combining process is executed as described above. Specifically, two image rendering commands “EMR_BITBLT x =“ 300 ”y =“ 2000 ”width =“ 1700 ”height =“ 500 ”data =“. . . "" And "EMR_BITBLT x =" 300 "y =" 2500 "width =" 1700 "height =" 500 "data =". . . "" Is stored.

[Line 56]
Finally, the control unit 150 processes the record on line 56 (“EMR_EOF” in the print drawing data file 300. Since this record is an end command, an XML generation end process (step S2600) is executed.

  At this point, since the common attribute grouping processing state is “initial state”, the processing defined as step S2620 is executed, and the processing state of the image rendering command is confirmed. At this time, since the processing state is “processing” (YES in step S2620), an image drawing command end process (step S1100) is executed.

  Specifically, two temporarily stored image drawing commands “EMR_BITBLT x =“ 300 ”y =“ 2000 ”width =“ 1700 ”height =“ 500 ”data =“. . . "" And "EMR_BITBLT x =" 300 "y =" 2500 "width =" 1700 "height =" 500 "data =". . . "" And the XML data "<image x =" 300 "y =" 2000 "width =" 1700 "height =" 1000 "xlink: href =". . . “/>” Is written in the temporary storage unit 160 (the 48th line in the SVG file 500 of FIG. 5).

  The processing state of the image drawing command is set to “initial state”. The XML footer generation unit 138 writes the SVG end instruction “</ svg>” into the SVG file 500 as the footer of the XML data (line 49 in the SVG file 500).

  As described above, according to the electronic document data processing apparatus 100 according to the present embodiment, when generating XML format data based on a drawing command for printing application data, the related drawing command is identified. Then, redundant data such as attributes commonly used for a plurality of instructions is omitted, and data unique to each instruction is combined to generate XML data with a reduced size. Thereby, the capability calculated | required with respect to the arithmetic processing apparatus using the data of an application can be suppressed.

  The electronic document data processing apparatus 100 described in detail above can be realized as a combination of hardware by combining circuit elements that execute each process, for example. Further, as shown below, it can also be realized by causing a computer system to read software for realizing each processing.

  Therefore, with reference to FIG. 27, an aspect of a specific configuration of electronic document data processing apparatus 100 according to the present embodiment will be described. FIG. 27 is a block diagram illustrating a hardware configuration of a computer system 2700 that functions as the electronic document data processing apparatus 100.

  The computer system 2700 includes, as hardware, a CPU 2710, a mouse 2720 and a keyboard 2730 that receive input of instructions from a user of the computer system 2700, data generated by execution of a program by the CPU 2710, or a mouse 2720 or a keyboard 2730. RAM 2740 for storing the input data in a volatile manner, hard disk 2750 for storing the data in a nonvolatile manner, CD-ROM (Compact Disk-Read Only Memory) driving device 2760, monitor 2780, communication IF (Interface) 2790. Each hardware is mutually connected by a data bus. A CD-ROM 2762 is attached to the CD-ROM drive 2760.

  Processing in computer system 2700 is implemented by hardware and software executed by CPU 2710. Such software may be stored in the hard disk 2750 in advance. The software may be stored in a CD-ROM 2762 or other storage medium and distributed as a program product. Alternatively, the software may be provided as a program product that can be downloaded by an information provider connected to the so-called Internet. Such software is read from the storage medium by the CD-ROM drive 2760 or other reading device, or downloaded via the communication IF 2790 and then temporarily stored in the hard disk 2750. The software is read from the hard disk 2750 by the CPU 2710 and stored in the RAM 2740 in the form of an executable program. CPU 2710 executes the program.

  Each hardware constituting the computer system 2700 shown in FIG. 27 is general. Therefore, it can be said that the essential part of the present invention is software stored in the RAM 2740, the hard disk 2750, the CD-ROM 2762 or other storage media, or software downloadable via a network. Since the operation of each hardware of computer system 2700 is well known, detailed description will not be repeated.

  The recording media are not limited to CD-ROM, FD, and hard disk, but are magnetic tape, cassette tape, optical disk (MO (Magnetic Optical Disc) / MD (Mini Disc) / DVD (Digital Versatile Disc)), IC (Integrated). Circuits (including memory cards), optical cards, mask ROMs, EPROMs, EEPROMs, flash ROMs, and other semiconductor memories may be used as mediums that carry a fixed program.

  The program here includes not only a program directly executable by the CPU but also a program in a source program format, a compressed program, an encrypted program, and the like.

  When the XML format data thus generated by the computer system 2700 is transferred to a PDA (Personal Digital Assistant), a mobile phone or other information processing terminal, the information processing terminal is based on the XML format data. Text, diagrams, and other electronic documents. The data size of the XML format does not have a redundant expression as described above, and is smaller than the size of data generated by normal processing. Therefore, when the information processing terminal performs display based on the data, it is not necessary to execute processing based on redundant data, so that a display operation can be realized smoothly. Specifically, since the number of objects in the XML format data generated by the electronic document data processing apparatus 100 is smaller than the number of objects in the data generated by normal processing, the time required for drawing is reduced. Shorter. Thereby, the user of the information processing terminal can view the electronic document without stress.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

2 is a block diagram showing a schematic configuration of functions implemented by electronic document data processing apparatus 100. FIG. FIG. 3 is a diagram conceptually illustrating one aspect of storage of an electronic document file in a storage unit. FIG. 4 is a diagram illustrating an aspect of print drawing data generated from an electronic document file 200. FIG. 6 is a diagram illustrating a mode in which records included in a print drawing data file 300 are converted into SVG format data on a one-to-one basis. 3 is a diagram illustrating a data structure of an SVG format generated by the electronic document data processing apparatus 100. FIG. 3 is a diagram conceptually showing a table generated by the electronic document data processing apparatus 100. FIG. It is a figure showing the mode of change of the data in the current object management table 700. FIG. FIG. 4 is a diagram showing the configuration of a text color management table 800. 4 is a flowchart (part 1) showing a procedure of processing executed by the electronic document data processing apparatus 100. 6 is a flowchart (No. 2) showing a procedure of processing executed by the electronic document data processing apparatus. 10 is a flowchart (part 3) illustrating a procedure of processing executed by the electronic document data processing apparatus 100. 6 is a flowchart (part 4) illustrating a procedure of processes executed by the electronic document data processing apparatus. 10 is a flowchart (No. 5) showing a procedure of processing executed by the electronic document data processing apparatus. 10 is a flowchart (No. 6) showing a procedure of processes executed by the electronic document data processing apparatus 100. 10 is a flowchart (No. 7) showing a procedure of processing executed by the electronic document data processing apparatus 100. 12 is a flowchart (No. 8) showing a procedure of processes executed by electronic document data processing apparatus 100. 12 is a flowchart (No. 9) showing a procedure of processes executed by the electronic document data processing apparatus 100. 10 is a flowchart (No. 10) showing a procedure of processes executed by electronic document data processing apparatus 100. 10 is a flowchart (No. 11) showing a procedure of processes executed by the electronic document data processing apparatus 100. 14 is a flowchart (No. 12) showing a procedure of processes executed by the electronic document data processing apparatus 100. 14 is a flowchart (No. 13) showing a procedure of processes executed by electronic document data processing apparatus 100. FIG. 14 is a flowchart (No. 14) showing a procedure of processes executed by electronic document data processing apparatus 100. FIG. 18 is a flowchart (No. 15) showing a procedure of processes executed by electronic document data processing apparatus 100. FIG. 18 is a flowchart (No. 16) showing a procedure of processes executed by electronic document data processing apparatus 100. FIG. 18 is a flowchart (No. 17) showing a procedure of processing executed by the electronic document data processing apparatus 100. FIG. 18 is a flowchart (No. 18) showing a procedure of processes executed by electronic document data processing apparatus 100. FIG. 2 is a block diagram illustrating a hardware configuration of a computer system 2700 that functions as the electronic document data processing apparatus 100. FIG.

Explanation of symbols

  100 electronic document data processing apparatus, 200 electronic document file, 300 print drawing data, 2700 computer system, 2710 CPU, 2720 mouse, 2730 keyboard, 2740 RAM, 2750 hard disk, 2760 CD-ROM drive, 2762 CD-ROM.

Claims (16)

Storage means for storing an electronic document file represented in a data format specific to the application program;
Input means for receiving an instruction to output the electronic document file;
Generating means for generating a plurality of drawing commands from the electronic document file based on the instructions;
An electronic document comprising: conversion means for converting each drawing command into data represented by a data description language in which data attributes and data contents are described in association with each other based on a mutual relationship between the drawing commands. Data processing device.   The electronic document data processing apparatus according to claim 1, wherein the data description language includes XML (eXtensible Markup Language) data.   The electronic document data processing apparatus according to claim 1, wherein the data description language includes a vector image description language. The converting means includes
Analyzing means for analyzing the data structure of each drawing command;
Identification means for identifying a mutual relationship between the drawing commands based on the result of analysis by the analysis means;
The electronic document data processing apparatus according to claim 1, further comprising: a drawing command conversion unit that converts each drawing command into data represented by the data description language based on the identified correlation. The drawing command includes a plurality of records classified according to any of a plurality of predefined classification criteria, each record including an attribute of data in the electronic document file,
The analysis means extracts data attributes in the electronic document file for each of the records,
The electronic document data processing apparatus according to claim 4, wherein the identification unit identifies the mutual relationship based on an attribute of each of the data extracted by the analysis unit. The identification means includes
Extraction means for extracting data having a common attribute from each of the plurality of drawing commands;
The electronic document data processing apparatus according to claim 4, further comprising: a grouping unit that groups the data extracted by the extraction unit for each attribute. The identification means includes
Text extraction means for extracting each text drawing data for displaying each text adjacent to each other based on preset coordinates;
The electronic document data processing apparatus according to claim 4, further comprising: a combining unit that combines the text drawing data extracted by the text extracting unit into one data based on the coordinates. The identification means includes
Image extracting means for extracting each image data for displaying each image adjacent to each other based on preset coordinates;
The electronic document data processing apparatus according to claim 4, further comprising: combining means for combining each image data extracted by the image extracting means into one data based on the coordinates. The application program outputs a print command for printing the electronic document file based on the instruction,
The electronic document data processing apparatus according to claim 1, wherein the generation unit generates the plurality of drawing commands based on the print command.   The electronic document data processing apparatus according to claim 1, further comprising output means for outputting data generated by the conversion by the conversion means.   The electronic document data processing apparatus according to claim 10, wherein the output unit includes a display unit that displays the electronic document file based on the data generated by the conversion.   The electronic document data processing apparatus according to claim 10, wherein the output unit includes a data output interface that outputs data generated by the conversion.   The electronic document data processing apparatus according to claim 1, wherein the drawing command includes a command that indicates the start of a metafile, a command that draws an object, and a command that indicates the end of the metafile.   The instruction for drawing the object includes any of an instruction for drawing a diagram, an instruction for coloring an image to be drawn, an instruction for drawing a character, and an instruction for designating a color for drawing the character. Item 14. The electronic document data processing device according to Item 13. Preparing an electronic document file represented in a data format specific to the application program;
Receiving an instruction to output the electronic document file;
Generating a plurality of drawing commands from the electronic document file based on the instructions;
Transforming each rendering command into data represented by a data description language in which data attributes and data contents are described in association with each other based on the interrelationship between the rendering commands. Processing method. A program for causing a computer to function as an electronic document data processing device, wherein the program causes the computer to
Preparing an electronic document file represented in a data format specific to the application program;
Receiving an instruction to output the electronic document file;
Generating a plurality of drawing commands from the electronic document file based on the instructions;
A program for executing the step of converting each drawing command into data represented by a data description language in which data attributes and data contents are described in association with each other based on a mutual relationship between the drawing commands.

Images