JP6602993B1 - Document creation support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document creation support system that facilitates translation work. A manual creation support server replicates node information of a document in a first language as node information of a document in a second language, and associates parts specified by the node information as parts in a second language. make a copy. In addition, when a part is updated, a notification regarding the update is made for parts in other languages corresponding to the part. Then, based on the parts of the parts management table 440 and the node information of the manual management table 420, XML data in which the parts are structured is generated, and a manual is generated based on the generated XML data and the layout template. [Selection] FIG.

Description

  The present invention relates to a system that supports document creation, and more particularly to a document creation support system that facilitates translation work.

Conventionally, as a technique for creating a document, for example, a technique described in Patent Document 1 is known.
The technique described in Patent Document 1 is composed of a whole structure of a document and a text element piece for embedding in the framework structure. When creating a document, a large number of documents prepared in advance according to required specifications are used. This is a document creation device in which a document is created by repeatedly selecting text element pieces and embedding them in a framework structure (the same document [0013] to [0031] and FIGS. 1 to 21).

JP 2001-331481 A

  However, in the technique described in Patent Document 1, when a document is translated into another language, the document is created by creating a document in another language and embedding sentence element pieces described in the other language. However, there is a problem that the translation work must be performed while confirming the correspondence with the document in the original language, and the translation work is not easy.

  Therefore, the present invention has been made paying attention to such an unsolved problem of the conventional technology, and an object thereof is to provide a document creation support system that facilitates translation work.

  [Invention 1] In order to achieve the above object, a document creation support system according to Invention 1 has a part storage means for storing parts composed of one or a plurality of elements, and the arrangement order or hierarchical relationship of the parts for each document. Node information storage means for storing specified node information, and structured data generation means for generating structured data in which the parts are structured based on the parts of the parts storage means and the node information of the node information storage means Template storage means for storing a layout template that defines the layout of the parts; document generation means for generating the document based on the structured data generated by the structured data generation means and the layout template of the template storage means; , No of the document in the first language With duplicate information as the node information of the document in the second language, and a multi-language development means to replicate in association with the part defined by the node information as part of the second language.

  If it is such a structure, structured data will be produced | generated by the structured data production | generation means based on the node information of a part memory | storage part and the node information storage means, and the structured data produced | generated by the document production | generation means and A document is generated based on the layout template of the template storage means. Further, the node information of the document in the first language is copied as the node information of the document in the second language by the multilingual expansion means, and the parts specified by the node information are associated as the parts in the second language. Duplicated.

  Here, the elements include, for example, letters, numbers, signs, symbols, terms and other text, images (including still images and moving images), mathematical formulas, tables, figures, graphs, footnotes, pillars, nombles, titles, Contains text or audio. The same applies to the document creation support system according to the seventh aspect.

  In addition, the parts storage means stores the parts by any means and at any time, and the parts may be stored in advance, or when the system is operated without storing the parts in advance. Parts may be stored by external input or the like. The same applies to storing information in the storage means.

  Further, the present system may be realized as a single device, terminal, or other device, or may be realized as a network system in which a plurality of devices, terminals, or other devices are communicably connected. In the latter case, each component may belong to any one of a plurality of devices and the like as long as they are connected so as to communicate with each other. The same applies to the document creation support system according to the seventh aspect.

  [Invention 2] Furthermore, in the document creation support system of Invention 2, when the part is updated in the document creation support system of Invention 1, a process of updating or prompting a part of another language corresponding to the part is performed. Update management means for performing

  With such a configuration, when a part is updated, the update management unit performs a process of updating or prompting another language part corresponding to the part.

  [Invention 3] Furthermore, in the document creation support system according to Invention 3, in the document creation support system according to Invention 2, the update management means performs a notification regarding the update of the parts in the other languages.

  With such a configuration, when a part is updated, the update management means notifies the update regarding the parts in other languages corresponding to the part.

  [Invention 4] Furthermore, the document creation support system of the invention 4 in the document creation support system according to any one of the inventions 1 to 3, stores variable information defining variable identification information and variable content information for each of the documents. Variable information storage means, wherein the element includes the variable identification information, and the document generation means includes the variable information stored in the variable information storage means based on the variable information of the document to be generated. The included variable identification information is converted into variable content information corresponding to the variable identification information.

  With such a configuration, the variable identification information included in the element corresponds to the variable identification information based on the variable information of the document to be generated among the variable information in the variable information storage unit. Converted to variable content information.

  Here, the variable identification information is information for identification, and can be configured as link information such as a name, a number, an ID, a code, and a URL, for example. The variable identification information can be configured as, for example, characters, numbers, figures, signs, symbols, images, and other information.

  The variable content information is information that replaces the variable identification information, and any information can be adopted. For example, the variable content information can be configured as link information such as a name, number, ID, code, and URL.

  [Invention 5] The document creation support system according to invention 5 is the document creation support system according to any one of inventions 1 to 4, further comprising element storage means for storing the element, wherein the part identifies the element. The document generation unit acquires the element from the element storage unit based on the replacement information included in the part, and generates the document based on the acquired element.

  With such a configuration, the document generation unit acquires an element from the element storage unit based on the replacement information included in the part, and the document is generated based on the acquired element.

  Here, the replacement information is information for identifying an element, and can be configured as link information such as a name, a number, an ID, a code, and a URL, for example. The replacement information can be configured as, for example, characters, numbers, figures, signs, symbols, images, and other information.

  [Invention 6] The document creation support system according to the invention 6 is the document creation support system according to any one of the inventions 1 to 5, wherein an update history generation for generating an update history for each language for parts corresponding to a plurality of languages. Means.

  If it is such a structure, the update log | history will be produced | generated by the update log | history production | generation means for every language about the part corresponding to a some language.

  [Invention 7] The document creation support system according to Invention 7 further includes a parts storage means for storing a first part composed of one or more elements and a second part composed of one or more elements in association with each other; The first node information defining the arrangement order or hierarchical relationship of the first parts for the language document, and the second node information corresponding to the arrangement order or hierarchical relationship specified by the first node information for the second language document. A node information storage means for storing second node information that defines the arrangement order or hierarchical relationship of parts, and a structured structure in which the parts are structured based on the parts in the parts storage means and the node information in the node information storage means Structured data generating means for generating data, and a template for storing a layout template defining the layout of the parts Comprising a chromatography preparative storage means, and a document generation means for generating the documents based on layout template structured data and the template storage unit generated in the structured data generation means.

  With such a configuration, since the parts used in the second language document correspond to the parts used in the first language document, each part used in the first language document is transferred to the second language. Can be translated. Then, structured data is generated by the structured data generation means based on the parts of the part storage means and the node information of the node information storage means, and the generated structured data and the layout template of the template storage means by the document generation means A document is generated based on

  As described above, according to the document creation support system of the invention 1 or 7, the translation into the second language can be performed for each part used in the document in the first language. Work becomes easy.

  Furthermore, according to the document creation support system of the second aspect, when a part is updated, a process of updating or prompting another language part corresponding to the part is performed. This can be done and the translation work becomes easier.

  Furthermore, according to the document creation support system of the invention 3, when a part is updated, a notification about the update is made for a part in another language corresponding to the part, so that the part to be updated can be grasped. .

  Furthermore, according to the document creation support system of aspect 4, variable content information corresponding to a document can be applied to a context common to a plurality of documents.

  Furthermore, according to the document creation support system of the fifth aspect, one element can be used at a plurality of locations and the element can be easily changed.

  Furthermore, according to the document creation support system of aspect 6, it is possible to grasp the update history for each language for parts corresponding to a plurality of languages.

It is a block diagram which shows the structure of the network system which concerns on this Embodiment. 2 is a diagram illustrating a hardware configuration of a manual creation support server 100. FIG. It is a figure which shows the relationship between a manual, node information, and parts. It is a figure which shows the data structure of the company information management table 400 and the category information management table 410. FIG. It is a figure which shows the data structure of the manual management table 420 and the parts management tables 430 and 440. FIG. FIG. 6 is a diagram showing data structures of an image management table 450, a mathematical expression management table 460, and a version management table 470. It is a figure for demonstrating the preparation point of a manual. It is a flowchart which shows a manual preparation process. It is a screen which shows operation which adds a part. It is a screen which shows operation which changes the content of parts. It is a screen which shows operation which deletes parts. It is a figure which shows the data structure in the case of expand | deploying from a Japanese manual to an English and German manual. It is a figure which shows the procedure in the case of expand | deploying from a Japanese manual to a German manual. It is a figure which shows the data structure in the case of performing partial translation. It is a figure which shows the procedure in the case of performing partial translation. It is a figure which shows the procedure in the case of reusing the existing translation. It is a figure which shows the data structure in the case of managing the update history about a Japanese, English, and German manual. It is a flowchart which shows a manual production | generation process. It is a figure for demonstrating implement | achieving various layouts with a layout template.

  Embodiments of the present invention will be described below. 1 to 19 are diagrams showing this embodiment.

First, the configuration of the present embodiment will be described.
FIG. 1 is a block diagram showing a configuration of a network system according to the present embodiment.

  As shown in FIG. 1, a manual creation support server 100 that supports manual creation and a user terminal 200 installed for each company are connected to the Internet 199.

Next, the configuration of the manual creation support server 100 will be described.
FIG. 2 is a diagram illustrating a hardware configuration of the manual creation support server 100.

  As shown in FIG. 2, the manual creation support server 100 includes a CPU (Central Processing Unit) 30 that controls operations and the entire system based on a control program, and a ROM that stores a control program of the CPU 30 in a predetermined area in advance. (Read Only Memory) 32, RAM (Random Access Memory) 34 for storing data read from the ROM 32 and the like and calculation results required in the calculation process of the CPU 30, and data input / output to an external device An I / F (InterFace) 38 is connected to each other via a bus 39 which is a signal line for transferring data so that data can be exchanged.

  The I / F 38 includes, as external devices, an input device 40 such as a keyboard and a mouse that can input data as a human interface, a storage device 42 that stores data, tables, and the like as files, and a screen based on image signals. Is connected to a signal line for connecting to the Internet 199.

Next, the data structure of the storage device 42 will be described.
FIG. 3 is a diagram illustrating a relationship between a manual, node information, and parts.

  In the manual creation support server 100, the manual can create terms, sentences, images, mathematical expressions and other elements in parts. For this reason, as shown in FIG. 3, the manual includes one or a plurality of parts and node information that defines the arrangement order or hierarchical relationship of the parts. In the example of FIG. 3, the manual for “Product A” is composed of parts 1, 2, 4, and 5, and the arrangement order or hierarchical relationship of these parts is defined by node information. The manual of “Product B” is composed of parts 5, 6, 8, and 9, and the arrangement order or hierarchical relationship of these parts is defined by node information. Here, the part 5 is shared by the manual of “Product A” and the manual of “Product B”.

  The manual is managed for each company and each category. A plurality of images are registered in the image library. A plurality of mathematical expressions are registered in the mathematical expression library. In the parts library, a plurality of parts consisting of one or a plurality of elements (terms, sentences, images, mathematical expressions and other elements) are registered. Attributes can be set for parts, and a plurality of attributes are registered in the attribute library.

  FIG. 4 is a diagram showing the data structures of the company information management table 400 and the category information management table 410.

  As shown in FIG. 4, the storage device 42 stores a company information management table 400 that manages company information and a category information management table 410 that manages category information.

  In the company information management table 400, one record is registered for each company as shown in FIG. In each record, main information including company number, company ID, and other information, and variable information including a list and other information registered in association with variable names and variable values are registered. Note that No is an internal number for system implementation. On the other hand, the ID is included in the data as an external specification. No is always a numerical value, but the ID includes characters other than numbers. Also, No is always unique in the system, but the same ID is in different languages.

  In the category information management table 410, as shown in FIG. 4B, one record is registered for each company and each category. In each record, main information including company No, category No, category ID, and other information, and variable information including a list and other information registered in association with variable names and variable values are registered.

  FIG. 5 is a diagram showing the data structure of the manual management table 420 and the part management tables 430 and 440.

  As shown in FIG. 5, the storage device 42 further stores a manual management table 420 for managing manuals and part management tables 430 and 440 for managing parts of the part library.

  In the manual management table 420, as shown in FIG. 5A, one record is registered for each manual. Each record includes main information including company number, category number, language number, manual ID, update ID, node information (node ID), part ID, creator ID, creation date / time, updater ID, update date / time and other information. , Version, language classification, book code, attribute, title, subtitle, version, number, and remarks, attribute information consisting of lists and other information registered by associating part attribute names and part attribute values, and variables Relationship between variable information consisting of lists and other information registered in association with names and variable values, reference information consisting of lists of parts ID and node ID and other information, original manual (category No, manual ID) and original Derived information consisting of sex is registered.

  The node information will be described. Elements constituting the manual are called nodes and have IDs uniquely identified in the manual. A part in which node data (for example, text) is stored is a part, and has an ID uniquely identified in a company. Making parts used in a plurality of manuals the same (same part ID) is called aggregation, and the aggregated parts are referenced from a plurality of nodes. On the other hand, making a part used in one manual unique (another part ID) is called separation, and the separated part is referenced from one node.

  A manual copy (duplication) will be described. There are three types of manual copies: separate copy, consolidated copy, and expanded copy. Separation copying is copying so as to use unique parts different from the manual of the copy source. Aggregated copy (also referred to as “reference copy”) is to copy so as to use the same parts as the copy source manual. The expanded copy is a consolidated copy accompanied by a change of language classification and an update ID (version).

  The variable information will be described. Since manuals have a context, simple text limits the reuse of parts. By describing the context dependent part with a variable name and converting the variable name to a variable value at the time of manual output, the dependency on the context is reduced. The variable value for the variable name is set for each context. For parts used in a plurality of manuals, variable values set for each manual for variable names are listed as selection candidates. The variable value corresponding to the variable name is converted by a combination of situations and item contents described later.

  The situation (context) will be described. In order to reuse parts, set the data to be output in association with the following situation. Part specific, node specific, manual specific, category specific, company specific, media specific, language specific, update (version) specific.

  The items (references and conditions) will be described. Depending on the situation in which parts are used, parts information, manual meta information, category information, and company information can be referred to. Conditions can be set by combining information to be referred to. The part information includes section number, section title, figure number, figure, table number, title, number, title number, title content, item number, item name, and other information. Manual meta information includes version, language classification, book code, attribute, title, subtitle, version, number, remarks, and part attributes.

  Partial translation and multilingual development will be described. Traditionally, manuals that have not been converted into parts have to be translated entirely for terminology and other reasons. On the other hand, as in the present embodiment, in a manual in parts, translation can be limited to only the updated portion by detecting the update in parts. By providing the parts with data for each language category, it is possible to limit translations to updated parts even in manuals that require support for multiple languages. For manuals composed of pre-translated parts, translation can be completed simply by expanding and copying the manual. If there is no translation of the corresponding language classification in the new part, the original of the new part is output by tracing the manual of the expanded copy source, and the appearance as a manual is maintained. The new part prompts translation of other language segments through the expanded and copied manual.

  In the parts management table 430, as shown in FIG. 5B, one record is registered for each part. Each record consists of company information, category number, part ID, part type, initial part attribute, creator ID, creation date / time, updater ID, update date / time, and other main information, variable name list, and other information. Variable information, and condition information including a list in which item names and item values (conditions) are registered in association with each other are registered.

  In the parts management table 440, as shown in FIG. 5C, one record is registered for each updated part. Each record includes main information including company No, category No, part ID, language No, update No, XML data, creator ID, creation date, updater ID, update date, and other information, update No, XML data, Update information including an updater ID, update date and time, and other information (pre-update information at the time of update) is registered. For manuals written in different languages, the parts used in the manual in the first language are managed in association with the parts used in the manual in the second language. The same part ID is set for the parts of the same node, and is distinguished by the language number. In the example of FIG. 3, for example, if there is a Japanese manual Mjp and an English manual Men for the product A manual, the parts with the part IDs “1” “2” “4” “5” are used for the manual Mjp. The manual Men has node information having the same structure as the manual Mjp, and parts corresponding to the parts of the manual Mjp are used. Each part of the manual Mjp and each part of the manual Men are associated by setting the same part ID to the parts of the same node. Therefore, the parts of parts ID “1” “2” “4” “5” are used in the manual Men. However, the language No. corresponding to Japanese is set for the parts used in the manual Mjp, and the language No. corresponding to English is set for the parts used in the manual Men.

  FIG. 6 is a diagram showing the data structure of the image management table 450, the mathematical expression management table 460, and the version management table 470.

  Further, as shown in FIG. 6, the storage device 42 includes an image management table 450 for managing images in the image library, a formula management table 460 for managing formulas in the formula library, and a version management table 470 for managing manual versions. Is remembered.

  As shown in FIG. 6A, one record is registered in the image management table 450 for each image. Each record includes main information including image No., company No., language No., update No., replacement character, classification category, and other information, and condition information including a list in which item names and item values (conditions) are registered in association with each other. Reference information including edit screen data and PDF data and derivative information including a list of update numbers being referenced are registered.

  The replacement character will be described. Image data such as figures and mathematical formulas needs to be replaced, and the same image data is used at a plurality of locations. By describing the image data portion with replacement characters and converting the replacement characters into image data at the time of manual output, it is possible to replace the image data at once and reduce the dependence of the parts on the image data. Unlike variables, replacement characters and image data are managed as a library for each company. Image data for each language segment can be registered with the same replacement character string, and a combination of conditions and items described below are converted into conditions.

  In the mathematical expression management table 460, as shown in FIG. 6B, one record is registered for each mathematical expression. Each record includes main information including a formula number, company number, language number, update number, replacement character, classification category, and other information, and condition information including a list in which item names and item values (conditions) are registered in association with each other. Reference information including edit screen data and PDF data and derivative information including a list of update numbers being referenced are registered.

  In the version management table 470, as shown in FIG. 6C, one record is registered for each version. In each record, main information including an update ID, an update No, a version, a creator ID, a creation date and time, an updater ID, an update date and other information is registered.

  The storage device 42 further stores a layout template that defines the layout of parts. When creating a manual, a layout template to which a layout is applied is specified.

Next, the operation of the present embodiment will be described.
First, the operation when creating a manual will be described.

FIG. 7 is a diagram for explaining a manual creation procedure.
The manual is created by arranging parts in the layout area as shown in FIG. The parts are arranged in the vertical direction or the horizontal direction of the layout area. First, add one part to the layout area. The next part can be added immediately before or after the existing part. The subsequent parts are the same, and can be added at an arbitrary position with respect to the existing parts. Terms, sentences, images, mathematical formulas and other elements can be described in the parts, and hierarchical relationships can be set for other parts. In addition, there are two-parts, which are parts that divide the area into two parts on the left and right sides, and place text, images, tables, items, etc., respectively. There are also two-part parts, which are divided into two areas on the left and right sides, and the text is arranged continuously from the left side to the right side. The contents of the part can be changed or deleted.

FIG. 8 is a flowchart showing the manual creation process.
The CPU 30 comprises an MPU (Micro-Processing Unit) or the like, starts a predetermined program stored in a predetermined area of the ROM 32, and executes a manual creation process shown in the flowchart of FIG. 8 according to the program.

  When the manual creation process is executed by the CPU 30, as shown in FIG. 8, first, the process proceeds to step S100.

  In step S100, it is determined whether a part addition request for adding a new part has been made from the user terminal 200. If it is determined that a part addition request has been made (YES), the process proceeds to step S102.

FIG. 9 is a screen showing an operation for adding a part.
In the user terminal 200, in the screen shown in FIG. 9, the right half of the layout area is assigned to the area where the parts are placed, and the left half is assigned to the area where the menus are placed. When a “part insertion” button is clicked, a part addition request is transmitted to the manual creation support server 100.

  In step S102, a new part is added to the layout area, a description related to the new part is incorporated into the node information related to the manual currently being created, and the process proceeds to step S104, where a new element is described in the added part. Then, the added part is registered in the parts management table 440, and a series of processes is terminated and the original process is restored.

  On the other hand, if it is determined in step S100 that no part addition request is made (NO), the process proceeds to step S106.

  In step S106, it is determined whether a registered parts addition request for adding a new part from the parts registered in the parts management table 440 is made from the user terminal 200, and it is determined that a registered parts addition request is made. If yes (YES), the process proceeds to step S108.

  In step S108, a list of parts registered in the parts management table 440 is presented to the user terminal 200. When a part is selected from the list of parts, the process proceeds to step S110, and the selected part is laid out. Add to the area, incorporate the description about the new part into the node information related to the manual currently being created, end the series of processes, and return to the original process.

  On the other hand, if it is determined in step S106 that a registered part addition request is not made (NO), the process proceeds to step S112.

  In step S112, it is determined whether or not a part change request for changing the content of the parts arranged in the layout area has been made from the user terminal 200. If it is determined that the part change request has been made (YES), The process proceeds to S114.

FIG. 10 is a screen showing an operation for changing the content of a part.
In the user terminal 200, as shown in FIG. 10, when the “edit” button on the right side of the part whose contents are to be changed is clicked, a part change request is transmitted to the manual creation support server 100.

  In step S114, history information indicating the contents of the parts before the change is created, and the created history information is stored in the storage device. As a result, the parts can be restored based on the history information even after the contents have been changed. Then, the process proceeds to step S116, the node information related to the part to be updated is searched from the manual management table 420, and the target manual in which the part to be updated is used based on the retrieved node information. Is displayed on the user terminal 200 to prompt the user to confirm whether or not the update is possible. As a result, when confirmation of the update is obtained, the process proceeds to step S118, the part to be updated is updated among the parts registered in the part management table 440, and the series of processes is terminated to return to the original process. Return. When the parts are updated, the updated contents are reflected in common to the parts to be updated in a plurality of manuals using the parts to be updated.

  On the other hand, if it is determined in step S112 that no part change request is made (NO), the process proceeds to step S120.

  In step S120, it is determined whether or not a part deletion request for deleting a part arranged in the layout area has been made from the user terminal 200. If it is determined that a part deletion request has been made (YES), the process proceeds to step S122. Transition.

FIG. 11 is a screen showing an operation for deleting a part.
In the user terminal 200, as shown in FIG. 11, when a “delete” button on the right side of the part to be deleted is clicked, a part deletion request is transmitted to the manual creation support server 100.

  In step S122, the part to be deleted is not deleted, the description about the part to be deleted is deleted in the node information related to the manual currently being created, the series of processes is terminated, and the original process is restored.

  On the other hand, if it is determined in step S120 that no parts deletion request is made (NO), the process proceeds to step S124.

  In step S124, it is determined whether a registered parts deletion request for deleting a part registered in the parts management table 440 has been made from the user terminal 200. If it is determined that a registered parts deletion request has been made (YES). The process proceeds to step S126.

  In step S126, history information indicating the contents of the parts before deletion is created, and the created history information is stored in the storage device. Thus, the parts can be restored based on the history information even after being deleted. Then, the process proceeds to step S128, where the parts to be deleted are deleted from the parts registered in the parts management table 440, the series of processes is terminated, and the original process is restored.

  On the other hand, if it is determined in step S124 that the registered parts deletion request is not made (NO), the series of processes is terminated and the process returns to the original process.

Next, the operation when the manual is developed in multiple languages will be described.
FIG. 12 is a diagram showing a data structure when expanding from a Japanese manual to English and German manuals.

  FIG. 13 is a diagram showing a procedure for expanding from a Japanese manual to a German manual.

  When a German manual is created from a Japanese manual, first, a German manual is created from the Japanese manual by an expanded copy, as shown in FIGS. Next, items unique to the German manual (for example, chapter numbers) are set. Next, finish by translating texts and registering images for German. Images registered for German with the same replacement character are used. The parts used in the Japanese and German manuals correspond to multiple languages.

The same procedure applies when creating an English manual from a Japanese manual.
Next, the operation when the manual is partially translated will be described.

FIG. 14 is a diagram illustrating a data structure when partial translation is performed.
FIG. 15 is a diagram illustrating a procedure for performing partial translation.

  When partial translation is performed after an English manual is created from a Japanese manual, the basic Japanese manual parts are first updated as shown in FIGS. For example, for a sentence of a certain part, “Open that door!” Is changed to “Close that door!”. Next, the parts associated with the updated parts in different languages are changed to a display that needs to be updated. Next, the relevant parts of the English manual are updated. For example, “Open the door!” Is changed to “Close the door!” For the text of the corresponding part. When the updated content is confirmed, the display is changed to a normal display.

FIG. 16 is a diagram illustrating a procedure for reusing an existing translation.
When an English manual is created from a Japanese manual and then another Japanese manual is created by referring to the Japanese manual, first, as shown in FIG. A Japanese manual 2 is created from the reference copy. The English manual 1 is created in the Japanese manual 1. Next, in order not to change the basic Japanese manual 1, parts that need to be updated in the Japanese manual 2 are separated. There is no part for English parts because it was separated. Also, a new block is added. Next, an English manual 2 is created from the Japanese manual 2 by an expanded copy. For the common part, the parts used in the English manual 1 are used. Next, for the English manual 2, items (for example, chapter number style) corresponding to the manual are set. For the English manual 2, the translation is input to the separated parts. As a result, a corresponding English part is created.

Next, the operation when managing the manual update history will be described.
FIG. 17 is a diagram showing a data structure in the case of managing update history for Japanese, English, and German manuals.

  For manuals and parts corresponding to a plurality of languages, as shown in FIG. 17, an update history for each language is generated.

Next, the operation when generating a manual will be described.
FIG. 18 is a flowchart showing the manual generation process.

  In the user terminal 200, when manual creation is completed, a manual generation request is made to the manual creation support server 100.

  When a manual generation request is made, the CPU 30 activates a predetermined program stored in a predetermined area of the ROM 32, and executes a manual generation process shown in the flowchart of FIG. 18 according to the program.

  When the manual generation process is executed in the CPU 30, first, the process proceeds to step S200 as shown in FIG.

  In step S200, the node information related to the manual to be generated is searched from the manual management table 420, the process proceeds to step S202, and the parts described in the node information are searched based on the searched node information. A search is made from the parts management table 440, and the process proceeds to step S204.

  In step S204, XML (eXtensible Markup Language) data in which the parts are structured is generated based on the retrieved node information and parts, and the process proceeds to step S206 to specify the layout template designated for the manual to be generated. Reading from the storage device 42, the process proceeds to step S208, a manual is generated as a PDF file, for example, based on the generated XML data and the read layout template, and a series of processing is terminated and the original processing is restored.

  FIG. 19 is a diagram for explaining that various layouts are realized by a layout template.

  As shown in FIG. 19, a manual can be generated with various layouts simply by specifying a layout template.

Next, the effect of this embodiment will be described.
In the present embodiment, the node information of the document in the first language is copied as the node information of the document in the second language, and the parts specified by the node information are copied in correspondence with the parts in the second language.

  Thereby, since it can translate into a 2nd language for every part used with the document of a 1st language, a translation operation becomes easy compared with the past.

  Furthermore, in the present embodiment, when a part is updated, a notification regarding the update is made for parts in other languages corresponding to the part.

  Thereby, when a part is updated, since the notification about update is performed about the part of the other language corresponding to the part, the part which should be updated can be grasped | ascertained. Therefore, the translation can be updated on a part basis, and the translation work is further facilitated.

  Further, in the present embodiment, based on the variable information of the document to be generated, the variable name included in the element is converted into a variable value corresponding to the variable name.

  Thereby, the variable value corresponding to a document can be applied to the context common to a plurality of documents.

  Furthermore, in the present embodiment, an image or mathematical expression is acquired from the library based on the replacement character included in the part, and a document is generated based on the acquired image or mathematical expression.

  Thereby, one element can be diverted at a plurality of locations and the element can be easily changed.

  Furthermore, in this embodiment, an update history for each language is generated for parts corresponding to a plurality of languages.

  Thereby, the update history for each language can be grasped about parts corresponding to a plurality of languages.

  Further, in the present embodiment, the parts and their arrangement order or hierarchical relationship are edited, XML data in which the edited parts are structured is generated, and a manual is generated based on the generated XML data and the layout template.

  This makes it easy to create a manual because the parts and their arrangement order or hierarchical relationship can be edited. In addition, since the manual is generated based on the XML data and the layout template, the manual can be edited without considering the layout, and a uniform quality manual can be created regardless of the ability of the creator.

  Furthermore, in this embodiment, a part is selected from the parts management table 440, the arrangement order or hierarchical relationship of the selected parts is incorporated into the node information of the manual management table 420, the parts in the parts management table 440 are updated, Based on the parts in the parts management table 440 and the node information in the manual management table 420, XML data in which the parts are structured is generated, and a manual is generated based on the generated XML data and the layout template.

  Thus, when a part is selected, the arrangement order or hierarchical relationship of the parts is incorporated in the node information, so that the parts can be diverted by a plurality of manuals, and the manual can be easily created. In addition, when the parts in the parts management table 440 are updated, the update contents are reflected in common on the update target parts in the multiple manuals using the update target parts. Consistent editing can be performed. Furthermore, since the manual is generated based on the XML data and the layout template, the manual can be edited without considering the layout, and a uniform quality manual can be created regardless of the ability of the creator.

  Furthermore, the present embodiment has a function of deleting parts in the parts management table 440 and a function of deleting descriptions related to parts in the node information of the manual management table 420 without deleting parts in the parts management table 440.

  Thereby, if a part of the parts management table 440 is deleted, the parts can be deleted at once in a plurality of manuals using a common part. Moreover, if the description about the part in node information is deleted, the part can be deleted individually in a specific manual among a plurality of manuals using a common part.

  Further, in the present embodiment, the node information related to the part to be updated is searched from the manual management table 420, and based on the retrieved node information, the target manual in which the part to be updated is used. Present a list.

  Thereby, when changing the contents of the parts, a list of target manuals is displayed, so that it is possible to grasp which manual is affected by the update of the parts.

  In the present embodiment, the storage device 42 is the parts storage means of the invention 1 or 7, the node information storage means of the invention 1 or 7, the template storage means of the invention 1 or 7, the variable information storage means of the invention 4, or the invention 5. Corresponds to the element storage means. Step S204 corresponds to the structured data generation means of the invention 1 or 7, step S208 corresponds to the document generation means of the invention 1, 4, 5 or 7, and the manual corresponds to the invention 1, 4, 5 or 7. The XML data corresponds to the structured data of Invention 1 or 7.

  In the present embodiment, the variable name corresponds to the variable identification information of the invention 4, the variable value corresponds to the variable content information of the invention 4, and the replacement character corresponds to the replacement information of the invention 5. .

[Modification]
In the above-described embodiment, when a part is updated, a notification regarding the update is given for parts in other languages corresponding to the part. However, the present invention is not limited to this. It is also possible to update parts in other languages.

  Moreover, in the said embodiment and its modification, although implement | achieved as a network system, it can implement | achieve not only as this but as a single apparatus or an application.

  In the above-described embodiment and its modification, the case where the present invention is applied to a network system including the Internet 199 has been described. However, the present invention is not limited to this. Also good. Of course, the present invention is not limited to a network that performs communication using the same method as the Internet 199, and can be applied to a network of any communication method.

  Further, in the above-described embodiment and its modifications, the case where the program stored in advance in the ROM 32 is executed in the processes shown in the flowcharts of FIGS. 8 and 18 has been described. However, the present invention is not limited to this. Instead, the program may be read from the storage medium storing the program showing these procedures into the RAM 34 and executed.

  In the above-described embodiment and its modifications, the present invention is applied to the case where a manual is created for each company. However, the present invention is not limited to this, and can be applied to other cases without departing from the gist of the present invention. It is. For example, the present invention can be applied to a case where a document other than a manual is created.

DESCRIPTION OF SYMBOLS 100 ... Manual creation assistance server 200 ... User terminal 30 ... CPU, 32 ... ROM, 34 ... RAM, 38 ... I / F, 39 ... Bus, 40 ... Input device, 42 ... Storage device, 44 ... Display device, 199 ... Internet 400 ... Corporate information management table 410 ... Category information management table 420 ... Manual management table 430 440 ... Parts management table 450 ... Image management table 460 ... Formula management table 470 ... Version management table

Claims (4)

Parts storage means for storing parts consisting of one or more elements including parts identification information, language classification information and variable identification information;
Node information storage means for storing node information defining the arrangement order or hierarchical relationship of the parts for each document;
Variable information storage means for storing variable information defining the variable identification information and variable content information for each document;
Structured data generation means for generating structured data in which the parts are structured based on the parts of the parts storage means and the node information of the node information storage means;
Template storage means for storing a layout template defining the layout of the parts;
Document generating means for generating the document based on the structured data generated by the structured data generating means and a layout template of the template storage means ;
Node information that defines the arrangement order or hierarchical relationship of the parts in correspondence with the arrangement order or hierarchical relationship specified by the node information of the document in the first language is copied as the node information of the document in the second language. And multilingual expansion means for replicating the part specified by the node information as a part of the second language including the part identification information included in the part and the language classification information to which the second language belongs. With
The document generation unit converts the variable identification information included in the element into variable content information corresponding to the variable identification information based on the variable information of the document to be generated among the variable information in the variable information storage unit. A document creation support system characterized by conversion. Oite to claim 1,
Comprising element storage means for storing the element;
The part includes replacement information for identifying the element,
The document creation support system, wherein the document generation unit acquires the element from the element storage unit based on the replacement information included in the part, and generates the document based on the acquired element. In any one of Claim 1 and 2 ,
A document creation support system comprising update history generation means for generating an update history for each language for parts corresponding to a plurality of languages. Parts storage means for storing parts comprising one or more elements including part identification information and language classification information;
  Node information storage means for storing node information defining the arrangement order or hierarchical relationship of the parts for each document;
  Structured data generation means for generating structured data in which the parts are structured based on the parts of the parts storage means and the node information of the node information storage means;
  Template storage means for storing a layout template defining the layout of the parts;
  Document generating means for generating the document based on the structured data generated by the structured data generating means and a layout template of the template storage means;
  The node information defining the arrangement order or hierarchical relationship of the parts in correspondence with the arrangement order or hierarchical relationship specified by the node information of the document in the first language is copied as the node information of the document in the second language. And multilingual expansion means for replicating the part specified by the node information as the part of the second language including the part identification information included in the part and the language classification information to which the second language belongs. A document creation support system characterized by comprising: