JP2007328741A - Method for editing electronic document, program and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for editing electronic documents, which dose not require binary comparison for embedded fonts and reduces redundant font data by extracting only necessary glyphs to reduce the size of an electronic document. <P>SOLUTION: An apparatus for editing electronic documents removes and sorts a unified document that consists of a plurality of electronic documents for every page, and then extracts and concatenates only necessary pages from the unified electronic documents to create a booklet. Fonts embedded when each page of the extracted electronic documents is concatenated are temporarily registered into an OS, and information on fonts commonly used at each page of the concatenated electronic documents is collected from the OS. Only glyphs used in the collected font information are extracted from the collected font information to embed the extracted glyphs into each page of the concatenated electronic documents. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an electronic document editing method, a program, and a storage medium, and more particularly, to an electronic document editing method, a program, and a storage medium for embedding fonts in an electronic document management system.

  Currently, companies are introducing electronic document management systems to promote the reuse of electronic documents. Recently, it has become possible to extract arbitrary pages from a plurality of electronic documents created and registered by various applications and bind them like a binder to form one booklet (structured electronic document). ing. In this case, the PDF file format is used to bind an arbitrary page of the electronic document. The PDF file format can embed fonts in order to draw characters correctly in various environments (for example, Patent Document 1).

  In the booklet, the PDF file is divided into pages and managed within the format, and an electronic document in a form in which these pages are bound is created by combining the divided pages.

In the process of binding as a booklet like this binder, the embedded font used in the original electronic document needs to be temporarily provided on each page. When these pages are bound, in order to determine whether or not they are the same embedded font, font information is once extracted and then a binary comparison is performed.
JP 2003-15849 A

  However, conventionally, when selecting only necessary materials from a plurality of materials (application files and scan images) and making them into booklet (book) format, there was a problem when binding an electronic document to a structured electronic document. . Specifically, there is a problem that the fonts need to be compared and the performance is poor when the number of embedded fonts is large and the number of pages is large. Also, since embedded fonts are embedded as they are in the bound electronic document, if a page is deleted and the font used only on that page is in the embedded font, it cannot be deleted and the font data There was a redundant problem.

  An object of the present invention is to reduce the size of an electronic document. More specifically, the binary comparison of embedded fonts is not required, and redundant font data is reduced by extracting only the necessary glyphs.

  In order to achieve the above object, an electronic document editing method according to claim 1 includes an integration step of integrating a plurality of electronic documents in units of pages, and deleting and rearranging the integrated plurality of electronic documents in units of pages. And an editing step of extracting and combining only necessary pages from the plurality of integrated electronic documents to form a booklet, wherein the editing step includes the pages of the formed booklet A step of associating the pages of the plurality of electronic documents with each other, a registration step of temporarily registering an embedded font in the OS when combining the pages of the extracted electronic document, and the combined electronic document Collecting step to collect font information commonly used in each page from the OS, and among the collected font information And retrieval retrieving a glyph that is being used from the collected font information, characterized in that it comprises a buried steps embedding the retrieved glyph to each page of the combined electronic document.

  6. The electronic document editing program according to claim 5, wherein the integrated module integrates a plurality of electronic documents in units of pages, and the integrated electronic document is deleted and rearranged in units of pages. In an electronic document editing program that causes a computer to execute an editing module that extracts and combines only necessary pages from a plurality of electronic documents to form a booklet, the editing module includes the formed booklet page and the plurality of electronic documents. Common to the association module for associating the pages of the document, the registration module for temporarily registering the embedded font in the OS when combining the extracted pages of the electronic document, and the pages of the combined electronic document Collection module that collects font information used in the OS from the OS, and the collected An extraction module for extracting glyphs used in the font information from the collected font information, and an embedding module for embedding the extracted glyphs in each page of the combined electronic document. .

  A computer-readable storage medium according to a sixth aspect stores the electronic document editing program according to the fifth aspect.

  According to the present invention, the size of an electronic document can be reduced. More specifically, binary comparison of embedded fonts is unnecessary, and redundant font data can be reduced by extracting only necessary glyphs.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  In FIG. 1, an electronic document 101 created with different application software is converted into a booklet (structured electronic document) in units of pages by an electronic document bundling method (FIGS. 2 and 3) described later by E-Binder Builder 102 which is utility software of the present invention. ). This “bundling” is also called “joining”. The electronic document 101 is, for example, an electronic document created with Microsoft's Word, an electronic document created with the company's PowerPoint, an image document read with a scanner, or an HTML document used on the Internet.

  Hereinafter, the electronic document bundling method will be described.

  2A and 2B are diagrams showing a configuration of electronic documents to be bundled, where FIG. 2A is a block diagram and FIG. 2B is a specific description example. FIG. 3 is a diagram illustrating an example of a storage form of an electronic document.

  <? Xml version = "1.0" encoding = "Shift_JIS"?> In FIG. 2B is a description of a declaration (XML declaration) performed at the head.

  The description of the electronic document used in this embodiment is XML (Extentional Markup Language). The configuration of this electronic document is an electronic document having a single-file multiple-file configuration. As its basic configuration, for example, an XML document named E-Binder.xml is configured, a predetermined description is described therein, and related elements (contents) are indicated by links. The file indicated by the link must be in a location where its location is known. An example of the folder and file structure is shown in FIG. In this example, it is possible to know the location of holding those link elements relative to E-Binder.xml at the root position.

  Hereinafter, the configuration of the electronic document of FIGS. 2 and 3 will be described using XML description.

  In FIG. 2A, an EBINDER section 201 indicates the beginning of this document. In FIG. 2B, the part surrounded by <EBINDER> to </ EBINDER> is the main body of this document. The EBINDER_INFO unit 202 is a part that holds meta information (management information) of this document. The information is retained in the part enclosed between <EBINDER_INFO> and </ EBINDER_INFO>. <TITLE> to </ TITLE>, <CREATOR> to </ CREATOR>, and <DATE> to </ DATE> are portions that hold the management information. This representation of management information is not limited to this. For example, it is defined by W3C (World Wide Web Consortium) as shown in <EFILE_INFO> to </ EFILE_INFO> and <EBINDER_INFO> to </ EBINDER_INFO> in FIG. RDF (Resource Data Framework) and other mechanisms may be used.

The MATERIAL unit 203 is a part that holds information on the material electronic document. The information is retained in the part surrounded by <MATERIAL files = ”2”> ~ </ MATERIAL>. In files, the number of source documents is held, and in the example, two files are held. The EFILE unit 204 is a part that holds information of one-material electronic document, and a part that converts a material document into a document in page units and holds the information. In FIG. 2 (B)
<EFILE href = ”Material \ ef0001 \ Original \ F_c01.ppt”
composedpagefile = ”Material \ ef0001.pdf”
type = ”pdf” totalpage = ”2” id = ”ef0001”>
~ </ EFILE>
The information is held in the part surrounded by. href indicates storage information of the electronic document that is the material. composedpagefile indicates storage information of a file in which material electronic documents are grouped in units of pages. The next type indicates the file format. In this example, Adobe's PDF file format is shown. Other multi-page TIFF formats that can store multiple images are set. totalpage describes the number of pages of the material electronic document. id describes the management number.

  An EFILE_INFO section 205 inside <EFILE> holds management information of material documents. The information is held in a portion surrounded by <EFILE_INFO datatype = "PowerPoint2000"> to </ EFILE_INFO> in FIG. datatype indicates that the type of the material electronic document is PowerPoint 2000. <TITLE> to </ TITLE>, <CREATOR> to </ CREATOR>, etc. are portions that hold the management information.

The DOC_SUMMARY unit 206 holds summary information of the material electronic document. In this part, the text simplified by the summary engine is saved from the full text so that the outline of the contents of the material can be understood. In the example of FIG. 2B, this part is omitted. The EPAGES unit 207 stores a document that has been changed from a material document to page-by-page information. For example, in the MS Word material document, the page is determined only at the time of display or printing, but the determined page document is stored for each page. A document in units of pages is stored in a portion surrounded by <EPAGES> to </ EPAGES> in FIG. In fact, continue
<EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"/>
<EPAGE page = "2" thumbnail = "Material \ ef0001 \ thumb2.bmp"/>
The part surrounded by <EPAGE… /> like this is a part for storing the document of page unit. “page” describes information about the page number of the whole page. The thumbnail describes information that holds the thumbnail (reduced image) of the page. The following description is also page unit information. In this way, the page development information of the material electronic document is held. Further, a developed document of a page unit document, for example, an image developed in A4 size is also held here.

<EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"
pagefile = "Material \ ef0001 \ page0001.bmp" type = ”bmp” />
In this way, the pagefile holds an image of one page in this example. type indicates the type that is held. In this example, the page document is a bitmap image called bmp, but the PDF format or other compressed file format may be used. The necessary condition is one page unit. <EPAGE… /> is determined by the number of pages of the material document.

  FIG. 2 shows an example in which two material electronic documents are held, while FIG. 3 shows an example in which necessary pages are selected and held from the material electronic documents.

In FIG. 3, the PAGEINDEX section 301 holds information indicating the page development location of the material electronic document. This is a configuration in which a generated document becomes a continuous electronic document if page images are read in that order as long as the id and page number of the material electronic document are managed. In the description example of FIG. 2B, the portion surrounded by <PAGEINDEX> to </ PAGEINDEX> is a description for managing and storing the pages of the generated document. Inside,
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “2” />
It is described as follows. <INDEX ... /> indicates a generated document page. The page attribute describes the page of the generated document. The idref attribute describes the id of the material electronic document. The efilepage attribute describes the used page number of the document with the id attribute. The above example shows that pages designated separately from two material electronic documents are used. Specifically, the first page of the generated document is the three-page file ID “efile0002” in the structured electronic document, and the second page has the file ID “efile0001” in the structured electronic document. "2 pages. Here, the file ID means the id attribute of the EFILE tag in the EFILE portion.

The BOOKBINDING section 2201 in FIG. 25 extracts the necessary pages from each document by actually expanding the pages from the description section that manages the pages of the generated document, and arranges them in the order of the pages of the generated document in the order defined by the <INDEX> tag. The format is maintained. In the description example of FIG.
<BOOKBINDING href = ”Bookbinding \ bind.pdf” type = ”pdf”>
What is given by the href attribute of the part of is the above-mentioned generated documents combined into one. The type attribute indicates the format used to combine the generated documents into one. In this example, the format is PDF.

In <BPAGE> 2202 in <BOOKBINDING ...> to </ BOOKBINDING> in FIG. 25, for example, in FIG.
<BPAGE page = ”2” thumbnail = ”Bookbinding \ page2.png” />
The page attribute and the thumbnail attribute are taken, and the page attribute of the generated page is given to the page attribute, and the location of the thumbnail image of the page is given to the thumbnail attribute.

  The above is an explanation using the example of the XML description about the document structure.

  Next, how to hold an embedded font of a PDF file which is one form of the electronic document will be described with reference to FIG. This PDF header has a predetermined description “PDF-1.3...”, Which indicates that this description is a PDF file (2401). This PDF has three embedded fonts, which are Font001 (2402), Font002 (2403), and Font003 (2404), respectively.

  These embedded fonts are used in one page (2405), two pages (2406), and three pages (2407), and are stored together as one font information for one typeface.

  FIG. 5A illustrates a case where a page is deleted from the PDF of FIG.

  The original PDF is 3 pages, and the embedded phones used are Font001 (2402), Font002 (2403), and Font003 (2404). When this PDF is changed to the first page after editing, it is created by combining (deleting) the used fonts Font001 (2501), Font003 (2502), and one page drawing data (2503) as a PDF file. The

  FIG. 5B illustrates a case where a page is deleted from the PDF of FIG.

  Similarly, the original PDF is 3 pages, and the embedded phones used are Font001 (2402), Font002 (2403), and Font003 (2404). When this PDF is changed to a PDF of only the second page after editing, it is created by combining (deleting) the used font Font002 (2510) and two-page drawing data (2511) as a PDF file.

  FIG. 6 illustrates a case where a page is deleted from the PDF of FIG.

Similarly, the original PDF is 3 pages, and the embedded phone used is Font001 (2402),
, Font002 (2403), and Font003 (2404). When this PDF is changed to the third page after editing, the fonts used are Font003 (2601), Font001 (2602), and the drawing data (2603) of one page is combined (deleted) as a PDF file. The

  The document configuration described above is a configuration in which the material electronic document, the material page unit document, and the generated document can be stored at the same time. Therefore, when editing, it is possible to return to the original electronic document and replace the page again. Further, the page unit document may be an imaged document, a PDF document, or a document described in XML, and can be switched by a software environment that can be paged.

  FIG. 8 is a diagram for explaining an example of linking with a document management system and an example of linking with a file system, using a GUI example and a preview GUI example of E-Binder Builder application software.

  In FIG. 8, 501 is an example of document management software, 502 is an example of file management managed on the OS of a computer, and 503 is E-Binder Builder software for processing the matters of the present invention. It is an example. Reference numeral 504 denotes a collection window for managing material electronic documents, and reference numeral 505 denotes a composed window for managing product documents. Reference numeral 506 denotes display software for displaying the generated document.

  FIG. 9 is a flowchart showing the procedure of the electronic document creation process.

  In FIG. 9, first, a material electronic document is selected (step S601), and the material electronic document is moved to E-Binder Builder by Drag & Drop (step S602). This operation is an operation of moving a file with a mouse as depicted by an arrow in FIG. The moved file is displayed as a thumbnail on the Collection Window (step S603). In this operation, in the background, the creation software of the material file is opened and a pseudo print operation is performed to create a file that can be handled in units of pages. For example, if you use software called Image Driver, you can create page images. At the same time, thumbnail images can be created. This created thumbnail is displayed. When the file is actually made into a file, the location of the material electronic document is described in the <EFILE href =…> href surrounded by <MATERIAL> to </ MATERIAL> shown in the explanation of FIG. <EPAGE page = ”1” thumbnail = ”… \ thumb1.bmp” /> A thumbnail image is stored at the thumbnail. This operation is the same when other plural material files are brought.

  Next, a thumbnail on the Collection Window is selected and moved to the Composed Window by Drag & Drop (Step S604). The input method of the material is not limited to the above-described method using Drag & Drop, but can be input by specifying a file on the local or network from E-Binder Builder. Further, in the calling software (in this embodiment, the document management system), for example, the necessary files and data are selected in advance by the calling software, and a button for starting E-Binder Builder is pressed. It may be input by the operation of. In this operation, a thumbnail of a page necessary as a final generated document is selected, the thumbnail is moved to the generated document operation side, and the page is prepared.

  Further, the thumbnail of the generated electronic document is displayed on the Composed Window (step S605). This operation is an operation for displaying the thumbnail moved in step S604 at the specified position at which it was dropped. By completing this processing, it is possible to move a necessary page from the material electronic document to the generated electronic document.

  FIG. 10 shows a state in which thumbnails of the selected page are displayed on the generated electronic document side.

  In FIG. 10, the designated page of the material electronic document 701 is moved to the first page of the generated electronic document 702.

Here, this state will be described with reference to FIG. In FIG. 2 (B)
<EFILE…>
<EPAGES>
<EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"/>
………
</ EPAGES>
</ EFILE>
………
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “2” />
<INDEX page = ”3” idref = ”efile0002” efilepage = ”2” />
</ PAGEINDEX>
There is a description that holds thumbnail images in <EPAGE ...>. This is the thumbnail displayed on the Collection Window. The portion surrounded by <PAGEINDEX> to </ PAGEINDEX> is the page information of the thumbnail displayed on the Composed Window. This does not have a thumbnail entity, but refers to the file name and page in the material electronic document. For example, <INDEX page = ”1” idref = ”efile0002” efilepage = ”3” /> specifies the file id (efile0002) of the material electronic document as the first page of the generated electronic document, and 3 pages of the file It is a description such as using eyes. In this way, the generated electronic document has the instruction information.

  As described above, E-Binder Builder is software for selecting and re-editing the necessary page documents from different types of electronic documents. The features at the time of input are that the original document for generating the page can be traced with a link, and that the document can be operated on a page-by-page basis.

  Next, the operation of moving the material electronic document stored in the Collection Window to the Composed Window will be described.

  FIG. 11 shows a state in which two material electronic documents are input and the two documents are held in the Collection Window. In FIG. 11, a thumbnail 801 of the material electronic document 1 and a thumbnail 802 of the material electronic document 2 are selected. When these files are moved to the Composed Window, thumbnails are displayed in the order selected. In this case, thumbnails 803 and 804 are displayed as a result of page selection in the order of thumbnails 801 and 802.

  FIG. 12 shows an example (902) in which a page 901 having a different material electronic document is inserted between two pages by dragging and dropping between two thumbnails displayed in the Composed Window. By this operation, the total number of pages is incremented by one.

  FIG. 13 illustrates that the selection order of the material electronic document is the order of the pages of the generated electronic document. Reference numerals 1001 and 1002 denote pages on the material side (FIG. 13A), but when the selection order is changed, the generated electronic document side is arranged in the selected order. Reference numerals 1003 and 1004 are examples in a case where the selection is made at once (FIG. 13B). In the case of batch selection, the generated electronic document side is arranged in the order of the pages of the material electronic document. Reference numerals 1005 and 1006 are examples in which selection is made across a plurality of material electronic documents (FIG. 13C). In the case of a plurality, the generated electronic document is created in the order selected. In the case of a plurality of materials, batch selection is prohibited or prioritized in material management and arranged in the order of the generated electronic document in that order.

  FIG. 14 is a process showing from which material electronic document the thumbnails selected in sequence are created on the Composed Window side. When the thumbnails of the 1/3 and 2/3 pages are selected, the material pages shown in 1101 and 1102 can be displayed as a frame display or a translucent display.

This is shown in FIG.
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
………
This is because the document management number (ID) and page number of the material are described in the description, so that the page of the material electronic document can be traced.

FIG. 15 shows a page replacement process using thumbnails stored on the Composed Window side. An example in which a 2/4 thumbnail 1201 is moved to the next side is shown. At 1202, the neighbors are replaced. this is,
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0001” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “2” />
<INDEX page = ”3” idref = ”efile0002” efilepage = ”2” />
<INDEX page = ”4” idref = ”efile0001” efilepage = ”4” />
</ PAGEINDEX>
Is
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0001” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0002” efilepage = ”2” />
<INDEX page = ”3” idref = ”efile0001” efilepage = “2” />
<INDEX page = ”4” idref = ”efile0001” efilepage = ”4” />
</ PAGEINDEX>
Will be edited as shown in bold.

  FIG. 16 shows a place where a plurality of thumbnails stored on the Composed Window side are separately selected and page replacement processing is performed. Numbers are stored in the order of selection and moved to the designated location as they are. Reference numerals 1301 and 1302 indicate after the selected thumbnail has been moved. The page is stuffed after moving. Since this movement process is switched in the selected order, FIG. 16 shows the normal order. However, if the larger page is selected first, the page order is reversed after the replacement. In the example of FIG. 16, when the selection orders 1 and 2 are reversed, 1301 and 1302 are reversed.

  FIG. 17 is a processing GUI when the electronic document once used is re-edited and reused. FIG. 18 is a flowchart illustrating the procedure of the electronic document re-editing process.

  In FIG. 18, the thumbnail 1401 of the material electronic document in FIG. 17A is double-clicked (step S1501). As a result, the application software that created the material electronic document receives and activates the file (1402 in FIG. 17) (step S1502). The file is corrected on the application side (step S1503). After the correction, the application side overwrites the file (step S1504). As a result of the saving, the E-Binder Builder receives the change notification, prompts the user for instructions, and enters the update file thumbnail creation process (step S1505). ).

  Next, the user is inquired whether to update or delete the page currently used in the Composed Window (step S1506). This is because the content of the page of the material electronic document is shifted by updating the file, and the generated electronic document side needs to be changed. When a deletion instruction is given (YES in step S1507), first, the display of the old thumbnails arranged in the Composed Window is deleted (step S1508). Next, the display of the old thumbnail arranged in the Collection Window is replaced with a new thumbnail (step S1509), and this process ends. If the instruction is not to delete (replace) (NO in step S1507), the position of the old thumbnail arranged in the Composed Window is stored, and the thumbnail is deleted (step S1510). Then, the display of the old thumbnail arranged in the Collection Window is replaced (Step S1511), the page display of the new thumbnail replaced at the position stored in the Composed Window is replaced (Step S1512), and this processing is terminated. To do.

  Next, the rotation of the page held in the Composed Window will be described.

  In FIG. 19, when two thumbnails (2/4, 3/4) 1601 are selected, and then a rotation instruction of 90 degrees to the right is performed, the vertical placement of the page does not change as indicated by 1602, but the page The contents rotate 90 degrees to fit. Although illustration is omitted, the same processing is performed for the left 90 degrees.

  In FIG. 20, when two thumbnails (2/4, 3/4) 1701 are selected and then a rotation instruction of 180 degrees is given, the thumbnails are turned upside down as specified by 1702. Become.

  FIG. 21 shows the overall rotation operation described above.

The final electronic document to be saved is
(1) Format including all information including material electronic document and generated electronic document (2) Format for storing only generated electronic document (3) Format for storing only material electronic document

(1) Format including all information including material electronic document and generated electronic document This is a format described with reference to FIG. 2 in a format that can be traced from the generated electronic document to the information of the material electronic document. This state is the state of the following excerpt in the XML description.

<EBINDER>
<MATERIAL files = ”2”>
<EFILE…>
<EPAGES>
<EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"
pagefile = "Material \ ef0001 \ page1.tiff” type = ”tiff” />
………
</ EPAGES>
</ EFILE>
<EFILE…>
………
</ EFILE>
</ MATERIAL>
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “1” />
<INDEX page = ”3” idref = ”efile0002” efilepage = ”2” />
</ PAGEINDEX>
</ EBINDER>
This storage state has a thumbnail for each page of the material electronic document, a page unit document used in the generated electronic document, in this example as an image (TIFF) (however, an intermediate format that can be described in page units, for example, PDF or XML / SVG may be used). This is because the page is designated on the generated electronic document side, and thus there is an all information document that can reconstruct the page. On the other hand, the page document on the material electronic document side that is not specified on the generated electronic document side has a large file, and can be selected without having it. In this way, it is stored as a collection of a plurality of electronic documents on the material side and the product side.

(2) Format for Saving Only Generated Electronic Document This is a saving method when only the generated electronic document is required.

  The compound document in (1) is a form in which the material electronic document and the generated electronic document are integrated. However, if the BOOKBINDING unit 2201 in FIG. It is a form that is completely extracted and held. This state is the state of the following excerpt in the XML description. (FIG. 2 (B)).

<EBINDER>
<MATERIAL files = ”2”>
<EFILE…>
<EPAGES>
………
</ EPAGES>
</ EFILE>
<EFILE…>
………
</ EFILE>
</ MATERIAL>
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “1” />
<INDEX page = ”3” idref = ”efile0002” efilepage = ”2” />
</ PAGEINDEX>
<BOOKBINDING href = ”Bookbinding \ bind.tiff” type = ”tiff”>
<BPAGE page = ”1” thumbnail = ”Bookbinding \ page1.png” />
<BPAGE page = ”2” thumbnail = ”Bookbinding \ page2.png” />
<BPAGE page = ”3” thumbnail = ”Bookbinding \ page3.png” />
</ BOOKBINDING>
</ EBINDER>
This saved state is a format in which the part enclosed by <BOOKBINDING href = ”Bookbinding \ bind.tiff” type = ”tiff”> to </ BOOKBINDING> is added. Is in a state of being saved in one format. In the example, it is in a state where it is bundled as a multi-page image called bind.tiff (sometimes called bind.pdf or bind.xml). Also, the thumbnail of each page is
<BPAGE page = ”1” thumbnail = ”Bookbinding \ page1.png” />
It is described in the place. This is to copy the thumbnail image used in the material electronic document and bring it under your control. A state in which these are arranged is a complete state on the generated electronic document side, and information enclosed by <MATERIAL> and <EFILES> is not necessary at this point. So, the above example
<EBINDER>
<BOOKBINDING href = ”Bookbinding \ bind.tiff” type = ”tiff”>
<BPAGE page = ”1” thumbnail = ”Bookbinding \ page1.png” />
<BPAGE page = ”2” thumbnail = ”Bookbinding \ page2.png” />
<BPAGE page = ”3” thumbnail = ”Bookbinding \ page3.png” />
</ BOOKBINDING>
</ EBINDER>
It can be saved in a simple form.

  There is also a simpler form that saves only the bind.tiff file. In this case, it is used when only the bundled file is desired.

  Next, how to hold an embedded font of a PDF file which is one form of the electronic document will be described with reference to FIG.

  The PDF shown in FIG. 26 has 1 to 3 pages of drawing data 2703 and 2704, which use Font001 (2701) and Font003 (2702), respectively. As described above, when a common font is used for a plurality of pages, one font (Font001 and Font003) is embedded in the PDF for each typeface.

  Next, the flow of embedded font data will be described with reference to FIG.

  In FIG. 27, when the electronic document is PDF, a PDF (2801) before page division is first created. This PDF is composed of 5 pages. P1 (A), P2 (Yes), P3 (U), P4 (E), P5 (O). These FONTs are the same. Since it is a typeface, one is embedded as a common embedded font 2804. This font 2804 has a glyph of (A, I, U, E, O). This PDF is first divided into PDF (P1 to P5) for each page inside the software (2802). At that time, a common embedded font (2804) is embedded in the PDF of each page.

  In the process of combining PDF files into one within the software, the drawing data of all pages except P3 are combined (2803). At that time, if the common font (2801) is registered in the OS at the first P1, (2804) The embedded fonts of p2 to p5 only need to refer to the already registered fonts, so registration in the new OS is not performed. . Finally, the font information used from the OS is collected, information necessary for the PDF file is extracted from the font information, and embedded in the PDF file (2805).

  When extracting font information from the OS, it is necessary to change the operation depending on the OS. When the functions provided by the OS can retrieve each table constituting the font information separately, for example, Windows (registered trademark) can use the GetFontData API. Here, examples of the table constituting the font information include cmap: character and glyf mapping, glyf: glyph data (font drawing information), head: font header, and the like. Also, hhea: horizontal header, hmtx: horizontal metrics, loca: location index, maxp: maximum profile, name: naming table, post: PostScript information, OS / 2: OS / 2 and Windows (registered trademark) metrics specification As an example. If you do not have a function that can separately extract the tables that make up such font information, get the data including all font tables from the OS and follow the published font specifications (published specifications by MicroSoft) Analyze and extract necessary tables. Embed the font extracted by the above method in the PDF file according to the PDF specification.

  FIG. 28 is a flowchart showing the procedure of the page-by-page combination processing of the electronic document (PDF).

  In FIG. 28, when creation of a generated electronic document (PDF creation) is started (step S2901), page-by-page electronic documents (PDF) are collected (step S2902).

  Next, the PDF of the first page is opened (step S2903), the drawing data and the embedded font data are analyzed, and it is determined whether or not the embedded font is already registered in the OS (step S2904). If the result of determination in step S2904 is that it has not been registered, the embedded font is extracted to create a file and registered in the OS (step S2905). On the other hand, if it is registered, the next page ( The electronic document (PDF) of the page to be combined is opened (step S2906).

  Next, the drawing data and the embedded font data are analyzed to determine whether or not the embedded font is registered in the OS (step S2907). If the result of determination in step S2907 is that it has not been registered, the embedded font is extracted and a file is created and registered in the OS (step S2908). The electronic document (PDF) of the next page is combined (step S2909).

Next, it is determined whether or not the combination of all pages has been completed (step S2910), and if not completed, the processing of steps S2906 to S2909 is repeated. If completed, information on all embedded fonts used in all the combined PDF pages is collected from the OS (step S2911). If necessary, the font file collected from the OS is analyzed, information is extracted for each table, and a subset font is created with all the embedded fonts (step S2912). Among them, only the characters used are cut out from the glyf table, information is embedded in the PDF file (generated electronic document) to be combined according to the PDF specification (step S2913), and this processing is terminated.
(3) Format to save only the material electronic document This is a form to save only the material electronic document, and the material electronic document once brought to the E-Binder Builder side has a thumbnail for each page together with the original document. Will hold. It means saving in this state. For example
<EBINDER>
<EBINDER_INFO>
………
</ EBINDER_INFO>
<MATERIAL files = ”2”>
<EFILE href = "Material \ ef0001 \ Original \ F_c01.ppt“
composedpagefile = ”Material \ ef0001.pdf”
type = ”pdf” totalpage = ”2” id = ”ef0001”>
<EFILE_INFO datatype = "PowerPoint2000">
………
</ EFILE_INFO>
<EPAGES>
<EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"/>
<EPAGE page = "2" thumbnail = "Material \ ef0001 \ thumb2.bmp"/>
</ EPAGES>
</ EFILE>
<EFILE href = "Material \ ef0001 \ Original \ HTML.doc"
composedpagefile = ”Material \ efile0002.pdf”
type = ”pdf” totalpage = ”3” id = ”ef0002”>
<EFILE_INFO datatype = "Word2000">
………
</ EFILE_INFO>
</ EFILE>
</ MATERIAL>
</ EBINDER>
In this example, only the material electronic document is stored, and the generated electronic document is not stored. Such storage is a method often used when the construction of the generated electronic document is paused and stored. In addition, when the original electronic document is changed with E-Binder Builder and only the modified original electronic document is desired, in the above example, href = "Material \ ef0001 \ Original \
Only the electronic document at the location described in “F_c01.ppt” is extracted and saved.

  The three types of storage methods have been described above, but will be described using the GUI shown in FIG. Reference numeral 1901 denotes a state in which a generated electronic document has been created. If this state is stored as it is, the document management system attaches a binder mark as shown at 1902 to indicate the form of a compound document. The document management system side displays thumbnails of the generated electronic document, and the material electronic document is informed to the user by the presence of a binder mark. Further, in the case of saving on a normal OS, the binder structure is saved with a configuration of a plurality of files and a plurality of folders as shown in FIG. To check the generated electronic document on a normal OS, for example, an XML document with this structure (E-Binder.xml in this example) and a style sheet (CSS: Cascading Style Sheet, XSL (Extensible Stylesheet Language, etc.) 2 types of files can be checked with a browser. There is also a way to directly view the bundled generated electronic documents inside the Bookbinding folder. In any case, an associated file group can be obtained.

  According to the first embodiment, different electronic documents according to the present invention can be bundled and managed.

<Example 2>
Another embodiment of the present invention will be described. FIG. 23 shows a configuration having a plurality of generated electronic documents. FIG. 23A shows an example of the GUI. Reference numerals 2001 and 2002 are Composed Windows for working with the generated electronic document. FIG. 23B is a configuration example of the E-Binder shown in FIG.

  In this embodiment, a plurality of PageIndex are configured. As shown in FIG. 23A, a plurality of composed windows are arranged, and a plurality of generated electronic documents can be created. In FIG. 23B, reference numerals 2003 and 2004 denote description examples holding a plurality of pieces of information. For example, it is possible to change the cover so that classified items can be separated from written documents and non-confidential documents.

<Example 3>
In addition to the image described in the first embodiment, it is not necessary to have an image developed for each page in the EPAGE section. In other words, in addition to the three finally stored electronic document forms described in the first embodiment, there is another storage form.
(4) A format that includes material electronic documents and generated electronic documents and does not include images developed in page units in the EPAGE section. This is a pre-assembled generated document, but the original material document has been modified. This is a storage method in the case of creating a generated document that has been collected again. This storage method keeps the relationship between the generated document and the original material document that are combined into one, and does not have page-expanded images or unnecessary thumbnails, so the total file size can be reduced as a whole There are features.

  In the form of collecting information in page units (information on which page of which material document) using the PAGEINDEX part in the BOOKBINDING section 2201 of FIG. 25, extracting thumbnails in the document in page units from the material document and holding them. is there. This state is the state of the following excerpt in the XML description. (FIG. 2 (B)).

<EBINDER>
<MATERIAL files = ”2”>
<EFILE href = "Material \ ef0001 \ Original \ F_c01.ppt“
type = ”pdf” totalpage = ”2” id = ”ef0001”>
<EFILE_INFO datatype = "PowerPoint2000">
………
</ EFILE_INFO>
</ EFILE>
<EFILE…>
………
</ EFILE>
</ MATERIAL>
<PAGEINDEX>
<INDEX page = ”1” idref = ”efile0002” efilepage = ”3” />
<INDEX page = ”2” idref = ”efile0001” efilepage = “1” />
<INDEX page = ”3” idref = ”efile0002” efilepage = ”2” />
</ PAGEINDEX>
<BOOKBINDING href = ”Bookbinding \ bind.tiff” type = ”tiff”>
<BPAGE page = ”1” thumbnail = ”Bookbinding \ page1.png” />
<BPAGE page = ”2” thumbnail = ”Bookbinding \ page2.png” />
<BPAGE page = ”3” thumbnail = ”Bookbinding \ page3.png” />
</ BOOKBINDING>
</ EBINDER>
Here, there is no EPAGE tag below the EFILE tag, and there is no composedfile attribute as an attribute of EFILE. A thumbnail is given to the href attribute on the BOOKBINDING side, and the EPAGE tag is omitted to eliminate redundancy. However, if redundancy is recognized, an EPAGE tag may be prepared and an attribute for giving a thumbnail may be given thereto. Further, the composedfile is not set because it is created from the original material document when it becomes necessary, which is a feature of this storage form. Each tag and attribute is in accordance with the first embodiment.

  Note that the present invention can be applied to a system (for example, a copier, a facsimile machine, etc.) consisting of a single device even if it is applied to a system composed of a plurality of devices (eg, a host computer, interface device, reader, printer, etc.). You may apply. Another object of the present invention is to supply a recording medium recording a program code for realizing the functions of the above-described embodiments to a system or apparatus, and the system or apparatus computer reads out and executes the program code stored in the storage medium. Is also achieved. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.

  Further, according to the present invention, the operating system (OS) running on the computer performs part or all of the actual processing based on the instruction of the program code, and the functions of the above-described embodiments are realized by the processing. This is also included. Furthermore, the present invention is also applied to the case where the program code read from the storage medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer. In that case, based on the instruction of the written program code, the CPU of the function expansion card or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing. .

It is a figure explaining producing a structured electronic document from a different electronic document. (A) is a format block configuration diagram of E-Binder, and (B) is a diagram illustrating an XML description example of E-Binder. It is a figure which shows the example of description by which the structure of PAGEINDEX was added to the structure of E-Binder. It is a figure explaining the relationship between the drawing data of the page in a PDF file, and the embedded font referred to. It is a figure explaining the relationship between the drawing data of the page in a PDF file, and the embedded font referred to. It is a figure explaining the relationship between the drawing data of the page in a PDF file, and the embedded font referred to. It is a figure which shows the example of a folder structure on the file system of E-Binder. It is a figure explaining the example of interlocking with a document management system, and the example of interlocking with a file system using the example of E-Binder Builder application software GUI and the example of preview GUI. It is a flowchart which shows the procedure of an electronic document creation process. It is a figure which shows CollectionWindow and Composed Window of E-Binder Builder. It is a figure which shows the example from which multiple pages of the electronic document of Collection Window are selected. It is a figure which shows the example which has inserted the selection page currently displayed on Collection Window between the pages with the production | generation electronic document currently displayed on Composed Window. (A)-(C) is a figure explaining the selection order of the thumbnail of the material electronic document currently displayed by Collection Window. It is a figure explaining that the thumbnail selected in Composed Window shows the relationship in Collection Window. It is a figure explaining the edit of the page in Composed Window. It is a figure explaining the movement edit of the thumbnail selected by Composed Window. (A) And (B) is a figure explaining re-editing the raw material electronic document preserve | saved by Collection Window, and reflecting an update result in E-Binder Builder again. It is a flowchart which shows the procedure of the re-editing process of an electronic document. It is a figure explaining the case where the state of the used page currently displayed on Collection Window is rotated 90 degree | times. It is a figure explaining the case where it rotates 180 degree | times similarly to FIG. It is a figure which shows rotation operation | movement comprehensively. It is a figure explaining the example which preserve | saves the example which preserve | saves E-Binder in a document management system, and a file system. (A) is a figure which shows the example in the case of having several Composed Window, (B) is a figure which shows the example of description showing the structure of (A). It is a figure which shows the example of a description in case RDF is used as metadata. It is a figure which shows the example of description by which the structure of BOOKBINDING was added to the structure of E-Binder. It is a figure which shows the example explaining the relationship between the drawing data of the page in a PDF file, and the embedded font referred. It is a figure which shows the example of the flow from the time of page division of the data of an embedding font to after page combination. It is a flowchart which shows the procedure of the combining process for every page of an electronic document (PDF). It is a figure which shows the example which described the BOOKBINDING structure of FIG. 25 by XML.

Explanation of symbols

101 Application software document 102 E-Binder Builder
103 booklet

Claims (6)

An integration step for integrating a plurality of electronic documents in units of pages, and deleting and rearranging the integrated plurality of electronic documents in units of pages, and then extracting only necessary pages from the plurality of integrated electronic documents. And an electronic document editing method comprising an editing step of combining and forming a booklet,
The editing step includes associating the formed booklet page with the pages of the plurality of electronic documents, and the font embedded when combining the extracted pages of the electronic document to the OS. A registration step of registering, a collection step of collecting font information commonly used in each page of the combined electronic document from the OS, and a collection of glyphs used in the collected font information An electronic document editing method comprising: a step of extracting from the extracted font information; and an embedding step of embedding the extracted glyph in each page of the combined electronic document.   2. The electronic document editing method according to claim 1, wherein the collecting step switches the collecting method according to the type of the OS when collecting the font information.   In the extracting step, when the OS includes the entire font information, the header information required for the format of each page of the combined electronic document is extracted from the header information included in the font information. The electronic document editing method according to claim 2.   When the OS is configured so that the font information can be collected for each header, the fetching step requires the format of each page of the combined electronic document among the header information included in the font information. 3. The electronic document editing method according to claim 2, wherein header information is extracted. An integration module that integrates multiple electronic documents in units of pages, and deletes and rearranges the integrated electronic documents in units of pages, and then extracts only the necessary pages from the integrated electronic documents. And an electronic document editing program that causes a computer to execute an editing module that is combined to form a booklet.
The editing module temporarily associates the formed booklet page with the plurality of electronic document pages, and the font embedded when combining the extracted pages of the electronic document with the OS. A registration module for registering, a collection module for collecting font information used in common on each page of the combined electronic document from the OS, and a collection of glyphs used in the collected font information An electronic document editing program comprising: an extraction module for extracting from the extracted font information; and an embedding module for embedding the extracted glyph in each page of the combined electronic document.   A computer-readable storage medium storing the electronic document editing program according to claim 5.

Images