JP2001290802A - Method and device for document processing and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document processor which can properly process a structured document, a document processing method which can be used by the document processor, and a computer-readable recording medium where a program making a computer implement the method is recorded. SOLUTION: This is a method for processing a structured document which has its internal data classified into constitution elements having a hierarchical structure and includes a stage for obtaining hash values corresponding to the constitution elements and a stage for obtaining display properties to be applied to the constitution elements by referring to a hash table wherein the hash values and display properties to be applied to the constitution elements are made to correspond to each other. A retrieving process for display properties can be made fast.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing apparatus, a document processing method, and a computer-readable recording medium storing a program for causing a computer to execute the method. In particular, the present invention provides a method for processing a structured document in which data in the document is classified into a plurality of elements having a hierarchical structure, a document processing apparatus capable of using the method, and a method for causing a computer to execute the method. The present invention relates to a computer-readable recording medium on which a program is recorded.

[0002]

2. Description of the Related Art With the spread of the Internet, an enormous amount of documents have been distributed. WWW (World Wide W
Most of the documents published on eb) are HTML (Hype
r-TextMarkup Language). H
It has been pointed out that a document described by TML can use only tags indicating elements predetermined by specifications, and is not suitable for efficiently processing a huge amount of documents. Was.

[0003] In order to effectively utilize a large number of documents, X
Markup languages such as ML (eXtensible Markup Language) have been proposed. Accordingly, a method and an apparatus for easily and efficiently processing a structured document in which data in the document described in a markup language such as XML is classified into a plurality of elements having a hierarchical structure have been developed. It has been demanded.

[0004]

SUMMARY OF THE INVENTION Accordingly, the present invention provides a document processing method, a document processing apparatus, and a computer-readable recording medium storing a program for causing a computer to execute the method, which can solve the above-mentioned problems. The purpose is to provide. This object is achieved by a combination of features described in the independent claims. The dependent claims define further advantageous embodiments of the present invention.

[0005]

That is, a document processing method according to a first embodiment of the present invention is a method for processing a structured document in which data in the document is classified into a plurality of components having a hierarchical structure. Acquiring a hash value corresponding to a component to be edited when the document is edited, and associating the hash value with a display attribute to be applied to the component. Acquiring a display attribute to be applied to the component with reference to the hash table, and applying the display attribute to data belonging to the component.

[0006] The hash value may be calculated based on the element names of the constituent elements. The hash value may be calculated based on the element name of the lowest hierarchy among the element names of the constituent elements. The hash table is a second table that associates a hash value with a display attribute to be applied to a class attribute value of a component.
May be further provided. Structured documents are SGML, XML, MHEG, HTML, XHTM
L, and any of extended or limited forms. The display attribute may be described in any of CSS, XSL, and an extended or limited format.

[0007] The recording medium according to the first embodiment of the present invention includes:
A computer-readable recording medium that records a program for causing a computer to execute any one of the methods described above.

[0008] A server device according to a first embodiment of the present invention is a recording medium for storing a program for causing a computer to execute any of the above methods, and a communication device for reading the program from the recording medium and delivering the program to the computer. And

A document processing device according to a first embodiment of the present invention is a document processing device for processing a structured document in which data in the document is classified into a plurality of components having a hierarchical structure, A hash value obtaining unit that obtains a hash value corresponding to, and a display that obtains a display attribute to be applied to a component by referring to a hash table in which the hash value is associated with a display attribute to be applied to the component Attribute acquisition unit.

The above summary of the present invention does not list all of the necessary features of the present invention, and a sub-combination of these features may also be an invention.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described through embodiments of the present invention. However, the following embodiments do not limit the claimed invention and have the features described in the embodiments. Not all combinations are essential to the solution of the invention.

FIG. 1 is a view showing a state where a program for causing a computer to execute the document processing method of the present embodiment is distributed via a network. The program is stored in a storage medium such as a hard disk provided in the download server 20. That is, the hard disk of the download server 20 is one form of the storage medium of the present invention. Users can access the Internet 10
The program stored in the hard disk of the download server 20 is downloaded via the
0 can be stored in a storage medium such as a hard disk provided in the storage device. Thus, the user terminal 30 can realize the document processing method according to the present embodiment. At this time, the act of reading the program from the hard disk provided in the download server 20 in order to distribute the program to the user terminal 30 corresponds to the use of a storage medium. Note that the program stored in the hard disk provided in the download server 20 may be provided as encoded or compressed data. A program for causing a computer to execute the document processing method according to the present embodiment can be provided in a form stored in a storage medium such as a CD-ROM, a floppy (registered trademark) disk, or a memory card.

The document processing apparatus according to the present embodiment may include a document server 40 and a plurality of editing terminals 50 connected via a network such as a LAN. The document server 40 includes at least an editing unit of the program according to the present embodiment. The editing terminal 50 includes at least a user interface and a display unit of the program of the present embodiment. With this configuration, one user stored in the document server 40 can be edited by a plurality of users using the editing terminal 50.
The editing terminal 50 may access the document server 40 via the Internet 10. Since the program for realizing the document processing method of the present embodiment is described in a highly versatile language such as the Java language, for example, even if the user terminal 30 does not have the program of the present embodiment, The document stored in the document server 40 can be edited by using a program provided in the document server 40.

FIG. 2 shows a configuration of a computer such as the download server 20, the user terminal 30, the document server 40, and the editing terminal 50. The computer mainly includes an input device 60, a display device 62, a communication device 64, a CPU 6
6, memory 68, hard disk 70, external storage device 7
2 and a bus 74. The input device 60 includes a device for transmitting information from a user to a computer, such as a keyboard, a mouse, a voice input device, and a touch panel. The display device 62 includes a device for displaying information such as a document being edited and a menu, such as a liquid crystal monitor. The communication device 64 includes a device for transmitting and receiving predetermined information via communication means such as the Internet 10 and a LAN. The CPU 66 loads and executes the program of the present embodiment. The memory 68 includes a storage device such as a ROM and a RAM.

The functional blocks of the document processing apparatus according to the present embodiment, which will be described in detail with reference to FIG. This program is downloaded from the download server 20 via the communication device 64 or the external storage device 72.
Provided from a portable storage medium such as a floppy disk or a CD-ROM mounted on the hard disk 70 and stored in the hard disk 70. The program may be read into the memory 68 from the download server 20 via the communication device 64 or from a portable storage medium such as a floppy disk or a CD-ROM mounted on the external storage device 72.

As a recording medium, a floppy disk,
In addition to CD-ROM, optical recording media such as DVD, MD
, A magneto-optical recording medium such as a PD, a tape medium, a magnetic recording medium, and a semiconductor memory such as an IC card or a miniature card. Such a recording medium is used only for manufacturing a document processing device, and it is not possible that the manufacture and sale of such a recording medium as a business constitute infringement of a patent right based on the present application. it is obvious.

FIG. 3 is a schematic functional block diagram of the document processing apparatus according to the present embodiment. The document processing device 90 mainly includes a user interface 100, an editing unit 200, a display unit 300, and a cancel / re-execution processing control unit 40.
0, and a plug-in unit 500.

The user interface 100 receives an instruction from the user input from the input device 60,
It performs necessary processing and transmits instructions to the editing unit 200, the display unit 300, the cancellation / re-execution processing control unit 400, and the plug-in unit 500. The editing unit 200 performs an editing process on the document in response to the instruction transmitted from the user interface 100,
The display request is transmitted to the display unit 300. Also, it transmits necessary instructions to the cancellation re-execution processing control unit 400.
The display unit 300 includes the user interface 10
0, editing unit 200, or plug-in unit 5
In response to the display request transmitted from 00, processing for displaying necessary information on the display device 62 is performed. The cancellation re-execution processing control unit 400 includes the user interface 1
00, control for canceling or re-executing the processing performed by the editing unit 200 or the plug-in unit 500.

The plug-in unit 500 includes a module for adding an additional function to the document processing apparatus 90.
Examples of the additional functions include, for example, a printing function, a document format conversion function, an editing function for a specific tag set, and a rendering function. Plug-in unit 500
Receives an instruction transmitted from the input device 60 via the user interface 100. Then, a process according to the instruction is performed, and if necessary, the user interface 100, the editing unit 200, the display unit 30
0, an instruction is transmitted to the cancellation re-execution processing control unit 400.

The document processing apparatus 90 of the present embodiment mainly includes
An apparatus for processing a structured document in which data in the document is classified into a plurality of elements having a hierarchical structure. Such structured documents include SGML, XML, MHEG, HT
Various formats such as ML have been proposed, and it is also possible to extend or limit them to create new formats. In the present embodiment, among these formats, a structured document described in XML will be described as an example. Information on XML is, for example, http:
// www. w3. org / TR /, etc., and will be described only as necessary in this specification.

The document processing apparatus 90 according to the present embodiment
The structured document is processed according to a DOM (Document Object Model) defined to provide an access method when a document is treated as data. In addition, in order to specify a method for displaying a structured document described in XML, CS
S (Cascading Style Sheets) or XSL (XML Styl
e Language). D
Information on OM, CSS and XSL is also available, for example, http
p: // www. w3. org / TR /, etc., and will be described only as necessary in this specification.

FIG. 4 shows the user interface 100.
2 shows detailed functional blocks of. The user interface 100 includes an event analysis unit 110, an event map 1
20, a UI command execution unit 130, and a menu control unit 140.

The event analysis unit 110 receives an event transmitted from the input device 60 and generates an event map 120
To analyze the contents of the event, referring to the UI command execution unit 130, the menu control unit 140, the editing unit 200
Communicate necessary instructions to Event map 120
Includes the type of event transmitted from the input device 60,
The type of the process activated by the event is stored in association with the event. The UI command execution unit 130 mainly executes processes related to the user interface 100, such as scrolling of a screen and switching display / non-display of a toolbar, which do not involve a document editing process. When the menu display request is transmitted from the event analysis unit 110, the menu control unit 140 generates a menu for executing various commands and performs a process for displaying the menu on the display device 62.

FIG. 5 shows detailed functional blocks of the editing unit 200. The editing unit 200 includes an editing command execution unit 210, a DOM engine 220, and a document holding unit 23.
0, a position information holding unit 240, an editing suitability judging unit 250, and a document correcting unit 260.

The edit command execution unit 210 executes various edit commands for editing a structured document. DOM
The engine 220 converts a DOM defined to provide an access method when an XML document is treated as data,
It is implemented in a programming language such as the Java language, and accesses a target document held in the document holding unit 230 to execute a designated process. The position information holding unit 240 holds position information such as the cursor position, the start point of the selection range, the end point of the selection range, and the bookmark position in the target document. The editing suitability determining unit 250 determines whether the editing process executed by the editing command executing unit 210 is appropriate. The document correction unit 260 executes a correction process when a document edited by the edit process executed by the edit command execution unit 210 requires further correction.

FIG. 6 shows detailed functional blocks of the display unit 300. The display unit 300 includes a rendering unit selection unit 310, a rendering unit 320, a tree display processing unit 330, and a display unit 340. The rendering unit 320 includes a style setting unit 322 and a layout processing unit 324.

The rendering unit selection section 310 selects a rendering unit for rendering data belonging to each element of the structured document, and requests the rendering unit to perform a rendering process. The rendering unit 320 mainly uses XHTML (eXtended Hyper-Tex
t Rendering data described in Markup Language). The style setting unit 322 determines the color, size,
Set styles such as fonts. The layout processing unit 324 performs layout processing of text data and floating blocks. The tree display processing unit 330 performs processing for displaying data that cannot be rendered by an appropriate rendering unit in a tree display. The display unit 340 performs a process for displaying the created display screen data on the display device 62.

The outline of the operation of the document processing apparatus 90 according to the present embodiment will be described with reference to FIGS.

FIG. 7 shows an example of a structured document that can be processed by the document processing apparatus 90 of the present embodiment. 7, a structured document 600 is a document described in XHTML. The first line is an XML declaration, and the document 600
Conforms to version 1.0 of the XML specification and shifts JIS
Indicates that it is encoded in the format. The second line indicates that this document is described in XHTML and is described in Japanese. The fourth to ninth lines are header information of the document.

Lines 10 to 20 are data constituting the main body of the document 600 and belong to the element "body". The element “body” has three elements “di” as elements at a level immediately below (hereinafter simply referred to as “child elements”).
v ". “Div” is an element corresponding to a paragraph of the document. The first element “div” includes the text data “aiueo”. The second element “div” includes a child element “hr”. The element “hr” is an empty element having no end tag, and is an element for displaying a horizontal line. The third element "div" includes text data "Kakikukeko". In the third element “div”, a display attribute indicating that the left indent has eight columns is specified. The style of the element "div" can be specified by the "paragraph properties" menu.

FIG. 8 shows a case where the document processing apparatus 90 has the structured document 6.
00 is read and displayed on the display device 62 by the display unit 300. The screen 700 displayed on the display device 62 includes a menu bar 702, a toolbar 70,
4, a horizontal ruler 706, a vertical ruler 708, a document display unit 710, and a cursor 712.

The menu bar 702 displays the structured document 600
Displays a menu of commands necessary to process.
For example, when "file" on the menu bar 702 is clicked with a mouse as an example of the input device 60, "file"
A menu is displayed. The toolbar 704 displays icons of frequently used commands as icons. Since a command can be activated by clicking the icon with a mouse, a desired command can be activated more easily than via a menu. Horizontal ruler 706
Indicates mainly the position of the cursor 712 in the horizontal direction. The vertical ruler 708 mainly indicates the position of the cursor 712 in the vertical direction. The document display unit 710 displays a result of rendering the structured document 600 by the rendering unit 320.

The document processing device 90 reads the structured document 600 to be processed and holds it in the document holding unit 230. Subsequently, the rendering unit selection unit 310 determines an appropriate rendering unit with reference to the namespace of the data of the structured document 600. All structured documents 600 are X
Since the rendering unit is described in HTML, the rendering unit selection unit 310 selects the rendering unit 320 as an appropriate rendering unit.

First, the style setting section 322 sets the display attribute (style) of each element. The display attribute of each element of XHTML is set in the order of the default style sheet and the user style sheet, and is sequentially overwritten.
If there is an author style sheet described in the document, the display attribute described in the author style sheet is further set. If a display attribute is specified for each element, a display attribute is further set for each element.
Here, since the display attribute that the left indent is 8 columns is specified in the third element “div”,
This is set as the third "div" display attribute.
The detailed operation of the style setting unit 322 is described in FIG.
Will be described in detail.

Subsequently, the layout processing section 324 lays out the text data and the floating block data. Since the document 600 has no floating block, only the text data is laid out.
The text data is subjected to layout processing line by line. For the detailed operation of the layout processing unit 324, see FIG.
Will be described in detail. The display data rendered by the rendering unit 320 is displayed on the display device 62 by the display unit 340.

As can be seen from the above description, the document processing device 90 of the present embodiment has a function as a browser for displaying a structured document described in XML or the like. If the program is started without specifying a document to be processed, a new document may be created as a target document. At this time, a document having no body part data is created as a target document. Nothing is displayed on the document display section 710 of the display screen 700.

Next, at the position of the cursor 712, a character string "1234" is input from a keyboard as an example of the input device 60.
The operation of the document processing apparatus 90 when the user inputs "." First, the event analysis unit 110 receives a character string input event from the keyboard. Event map 120
Is associated with a character string input event. The event analysis unit 110 refers to the event map 120 and instructs the editing unit 200 to activate a character string insertion command.

The edit command execution unit 210 receives the character string insertion command execution request from the event analysis unit 110 and executes the character string insertion command. The edit command execution unit 210 instructs the DOM engine 220 to insert the character string “1234” at the position after the second character in the text data of the first element “div”.
The DOM engine 220 accesses the document held in the document holding unit 230 according to the specification of the DOM, and executes the specified processing. At this time, as will be described in detail later, the position information held in the position information holding unit 240 is automatically updated. Subsequently, the DOM engine 220 issues a mutation event for notifying that the text data of the first element “div” has been changed, and transmits the mutation event to the display unit 300.

The display unit 300 receives the mutation event and re-renders the required part,
The screen of the display device 62 is updated. First, the rendering unit selection unit 310 selects an appropriate rendering unit. In this case, a rendering unit suitable for rendering the first element “div” is the rendering unit 320. The style setting unit 322 of the rendering unit 320 sets the style of the first element “div”. In this case, since the style has not been changed, there is no need to reset it. The layout processing unit 324
Re-layout the first element "div". In this case, a character string “Ai 1234 Ueo” is laid out in order from the left. It is clear that the second and third elements "div" are not affected by the floating block, so there is no need for a relayout.

In the above cycle, the processing specified by the user is executed. FIG. 9 shows the document 600 after the above processing has been performed. The text data on line 12 is
It has been changed from "aiueo" to "ai 1234ueo". FIG. 10 shows the screen 7 after the above processing has been executed.
00 is shown. The first paragraph changes from “Ai-ueo” to “Ai 1
234 ", and the cursor position has moved to the position after" 4 ".

FIG. 11 is a flowchart showing the operation of the menu control unit 140. First, the menu control unit 14
0 acquires a menu display request transmitted via the input device 60 (S100). When the menu display request is obtained, the cursor position or the editing range position is detected, and the current editing position is obtained (S102). Subsequently, the name space to which the data including the editing position belongs is acquired (S10).
4). When there are a plurality of editing positions, each name space is obtained. Subsequently, a document type definition (DTD: Document Type Definition) corresponding to the acquired namespace is acquired (S106). The document type definition is XML Schema
a, RELAX, and the like. Next, if necessary, a style sheet describing the display rules of the elements of the target document is obtained (S108). The style sheet may be described in a format such as CSS or XSL. Subsequently, a menu is generated with reference to the DTD and, if necessary, the style sheet (S110). Subsequently, the display unit 300 is instructed to display a menu (S112).

FIG. 12 shows an example of a structured document described in XML. In the structured document 610 shown in FIG. 12, the document type identified by the namespace "http://www.sample.com/" is called a document type "sample". Since there is no method for expressing a namespace in the XML DTD, FIG. 12 shows a modularized DT of the document type XHTML.
Assuming D, composite DTD with document type "sample"
Is described. That is, a document type definition is generated by converting all the element type names belonging to the document type "sample" to names to which a prefix "s:" is added, and synthesizes it with the modularized DTD of XHTML. Since CSS style sheets do not have a way to represent namespaces,
The style definition for the element type belonging to "le" is described as a style definition for an element with a name with a prefix "s:" added. Due to the above restrictions, the namespace prefix applied to the document type “sample” in the document 610 is limited to “s”. For convenience of explanation, FIG.
Although D and CSS are used, a document type description language or a style sheet language having a capability of expressing a name space may be used. In that case, there is no such restriction.

The document 610 includes a document type definition 612 of the document type “sample”, a style sheet 614 defining display attributes of each element of the document type “sample”, and a portion 616 belonging to the document “sample”.

The document type definition 612 includes an element type declaration and an attribute list declaration. Lines 3 to 8 are element type declarations. For example, the element type declaration on the third line is the element "sam
ple ", and specifies that the element" sample "includes the element" sect "or the element" parag "at least once. The element type declaration on the fourth line defines an element “sect”, and the element “sect” is
Text data, element "sect", element "para"
g ", element" sub ", element" bold ", or element" image "is specified to be contained 0 or more times.
The element type declaration in the eighth line defines the element "image", and specifies that the element "image" is an empty element tag having no content. The ninth line is an attribute list declaration. This means that the element "image"
stipulates that it has an attribute of "ze".

The style sheet 614 has a document type “sam
The display attribute of each element of “ple” is defined. Line 18
This indicates that the style sheet 614 is described in the CSS format. Line 22 specifies that the element “sub” is displayed in subscript. The 23rd line contains the element “b
"old" is displayed in bold.

FIG. 13 shows the structured document 61 shown in FIG.
0, a portion 616 belonging to the document type “sample”
FIG. 2 is a schematic diagram showing the hierarchical structure of FIG. “Sample” which is an element of the highest hierarchy includes “sect” and “parag” as child elements. The element “sect” includes text data “aiueo”, child element “sub”, and text data “kakikukeko”. The element “sub” includes text data “123”.
4 ", child element" bold ", and text data" 9 "
0 ”. The element “bold” includes the text data “5”.
678 ". The element “parag” includes text data “sashisusesoso” and child elements “image”.
The element "image" is an empty element. The above hierarchical structure complies with the document type definition 612 shown in FIG. That is, the document 610 is a valid XML document. Reference numbers (1) to (11) are used to explain the operation of the menu control unit 140 in FIG.

FIG. 14 shows a state where the menu is displayed when the cursor 712 is at the position (4) in FIG. When the cursor 712 is at the position (4) in FIG.
Clicking on with a mouse displays an “Insert” menu 720. Here, when the mouse position is further adjusted to the item “tag”, a display request of the “tag” menu 722 is transmitted to the menu control unit 140.

At this time, the menu control section 140 acquires the editing position. In this case, the editing position is the cursor 71
2 position. Subsequently, the menu control unit 140 acquires the name space of the editing position and acquires the corresponding document type. In this case, the position of the cursor 712 is the document type "sa
mple ”. Subsequently, the menu control unit 140
Obtains the document type definition corresponding to the document type. In this case, the document type definition corresponding to “sample” is as shown in FIG.
Is the document type definition 612 shown in FIG. Subsequently, the menu control unit 140 acquires a style sheet. in this case,
The style sheet of the document 610 is the style sheet 614 shown in FIG. Subsequently, the menu control unit 140
Generates a menu. The menu to be generated here is the “tag” menu 722. Menu control unit 1
40, first, refers to the document type definition 612 and extracts a tag that does not violate the document type definition 612 even if a tag is inserted at the position of the cursor 712.

FIG. 15 shows the relationship between the editing position in the document 610 and tags that can be inserted at that position. Now, since the cursor 712 is at the position (4), a tag that can be inserted at the position (4) is extracted. The position (4) corresponds to the element “su
b). According to the document type definition 612, the elements that the element “sub” can have as child elements are the element “sub”, the element “bold”, and the element “ima”.
ge ”. Therefore, these three tags are tags that can be inserted at position (4). In FIG. 15, such insertable tags are indicated by “で”. The element “sect” and the element “parag” correspond to the element “su”
Since it cannot be a child element of "b", it cannot be inserted at position (4). In FIG. 15, such non-insertable tags are indicated by “x” or “△”. The tag indicated by “△” is a tag that can be corrected to a format that conforms to the document type definition 612 by the correction processing by the document correction unit 260. The tag indicated by “x” is also stored in the document type definition 612
The tag cannot be modified to a format that conforms to. The operation of the document correction unit 260 will be described in detail with reference to FIG.

The menu control unit 140 includes the element "su
b ", the element" bold ", and the element" image "can be selected, and the element" sect "and the element" para "
The tag menu 722 is generated so that “g” cannot be selected. In FIG. 14, the unselectable element “se
“ct” and the element “parag” display a strike-through line. Items that can be selected from the menu may be displayed in black, and items that cannot be selected may be displayed in gray. At this time, when the mouse is moved to an item, selectable items are highlighted, but non-selectable items are not highlighted. Accordingly, the user can correctly recognize the tag that can be inserted at the position of the cursor 712 and the tag that cannot be inserted without knowing the contents of the document type definition 612. Further, an appropriate XML document can be created without being aware of the document type definition 612.

Here, the item “im” of the tag menu 722
“...” is displayed on the right side of “age”. This indicates that when the item "image" is selected, a dialog is displayed. According to the attribute list declaration of the document type definition 612, the element "image" always has the attribute "size". Therefore, a dialog for designating the attribute “size” is displayed, and the user is prompted to specify the attribute “size”. This allows users to
An appropriate XML document can be created without being aware of the document type definition 612.

The menu control section 140 may generate the tag menu 722 by further referring to the style sheet 614. According to the style sheet 614, the element “sec”
t "and the element" parag "have a display attribute as a paragraph type, and include the element" sub "and the element" bol ".
"d" has a display attribute as a character type. Therefore, the element “sect” and the element “parag” are displayed collectively, and the element “sub” and the element “bol” are displayed.
"d" may be displayed collectively. In this way, by classifying and displaying according to the display attributes, it is possible to make the menu easier to understand and operate.

In FIG. 14, the elements "sect" and "parag" which are indicated by "@" are not selectable, but these elements may be selectable. At this time, the hierarchical structure of the document 610 may be modified so as to conform to the document type definition 612. The user may be inquired whether or not the hierarchical structure should be modified. The correction method will be described in detail with reference to FIG.

FIG. 16 shows a state in which the menu is displayed while the range 724 is selected. The user selects the range 724 and then selects “Format” in the menu bar 702.
When is clicked with a mouse, a "Format" menu 726 is displayed. Here, when the mouse position is further moved to the item “Tag range”, the “Tag range” menu 7 is displayed.
The display request of 28 is transmitted to the menu control unit 140.

At this time, the menu control section 140 acquires the editing position. In this case, the editing position is the range 724. Next, the menu control unit 140 acquires the name space of the editing position. In this case, the namespace of the range 724 is “sample”. Subsequently, the menu control unit 140 acquires a document type definition corresponding to the name space.
In this case, the document type definition corresponding to "sample" is
This is the document type definition 612 shown in FIG. Subsequently, the menu control unit 140 acquires the CSS. In this case, the CSS of the document 610 is the style sheet 6 shown in FIG.
14. Subsequently, the menu control unit 140 generates a menu. The menu to be generated here is the “tagging range” menu 728. Menu control unit 140
First, with reference to the document type definition 612, a tag that does not violate the document type definition 612 even if the range 724 is tagged is extracted.

FIG. 17 shows the relationship between the editing range in the document 610 and tags whose range can be tagged. now,
Since the range 724 from the position (11) to the position (12) is selected, a tag is extracted that does not violate the document type definition 612 even if the text data in this range is converted into a new child element. The range 724 is included in the element “parag”. According to the document type definition 612, the element "par
The elements that “ag” can have as child elements are the element “sub”, the element “bold”, and the element “imag”.
e ”. Therefore, these three tags are in range 7
24 is a tag that can be tagged. Element “sect” and element “parag” cannot be child elements of element “parag”, so range 724 cannot be tagged to these tags.

The menu control unit 140 sets the element “su
b ", the element" bold ", and the element" image "can be selected, and the element" sect "and the element" para "
“Tag range” menu 728 is generated so that “g” cannot be selected. In FIG. 16, strike-through lines are displayed for the non-selectable elements “sect” and “parag”. Items that can be selected from the menu may be displayed in black, and items that cannot be selected may be displayed in gray. At this time, when the mouse is moved to an item, selectable items are highlighted, but non-selectable items are not highlighted. This allows the user to correctly recognize tags that can tag the range 724 and tags that cannot be tagged without knowing the contents of the document type definition 612. Also, without being aware of the document type definition 612,
A valid XML document can be created.

FIG. 18 shows a state in which the menu is displayed by right-clicking the mouse in the document display section 710 when the cursor 712 is at the position (4) in FIG. When the user issues a menu display request by an operation such as right-clicking the mouse while the cursor 712 is at the position (4) in FIG. 13, a “document edit” menu 730 is displayed. Here, furthermore, the item "insert"
When the mouse position is adjusted to “”, an “insert” menu 720 is displayed. Further, when the mouse position is adjusted to the item “tag”, a display request for the “tag” menu 722 is transmitted to the menu control unit 140. Menu control unit 1 at this time
The operation of 40 is the same as the operation described in FIG.

As described above, when an editing process is performed to change the hierarchical structure of elements in a document, there is a possibility that a document that is contrary to the document type definition may be generated. For this reason, the menu control unit 140 refers to the document type definition and generates a menu in which the editing process for generating a hierarchical structure that does not conform to the document type definition cannot be selected. When an editing process that generates a hierarchical structure that does not conform to the document type definition is selected,
A configuration that calls attention to the user may be used.
When an editing process that generates a hierarchical structure that does not conform to the document type definition is selected, the hierarchical structure may be modified to conform to the document type definition.

The document processing device 90 may have a plug-in unit 500 for processing data in a specific name space. When the menu display request is transmitted, if there is a plug-in unit 500 for processing the data in the namespace corresponding to the editing position at that time, even if the plug-in unit 500 displays the menu, good. According to this, the user can display the menu of the plug-in unit 500 suitable for processing each data in the document without being aware of the name space.

FIG. 19 is a flowchart showing the operation of the editing suitability judging section 250. The editing suitability determination unit 250
The editing command executed by the editing command execution unit 210 is
Determine whether it is appropriate. The aforementioned menu control unit 140
Has determined the suitability of the edit command when the menu is displayed, but the edit suitability determining unit 250 determines whether the edit command is appropriate when the execution request of the edit command is transmitted.

When the execution request of the editing command is transmitted, the editing suitability judging section 250 judges whether or not the editing command involves a change in the hierarchical structure (S202). If the editing process does not involve a change in the hierarchical structure, such as insertion, deletion, or change of only text data, the process proceeds to N and execution of the editing command is permitted (S214). When an editing process that involves a change in the hierarchical structure, such as a new element being added or an element being deleted, is requested, the process proceeds to Y, and it is determined whether a document type definition can be acquired (S20).
4). If the document type definition cannot be obtained, the process proceeds to N, performs alarm processing, and calls the user's attention (S21).
0), the execution of the editing command is prohibited (S21).
2). This is because a document that does not conform to the document type definition may be generated. If it is not necessary to generate a valid XML document, the execution of the edit command may be permitted regardless of whether the document type definition can be acquired. In this case, a step of determining whether or not the XML document generated as a result of editing is in a proper format may be provided.

If the document type definition can be obtained in S204, the process proceeds to Y, and it is determined whether or not the document generated as a result of executing the requested editing command conforms to the document type definition (S206). . If the document generated as a result of executing the edit command conforms to the document type definition,
Proceed to Y to permit execution of the edit command (S21)
4). If the document generated as a result of executing the edit command does not conform to the document type definition, the process proceeds to N and inquires of the user whether to execute the edit (S208).
When the user recognizes that a document that does not conform to the document type definition is generated and requests to execute the edit command, the execution of the edit command is permitted (S21).
4). At this time, the hierarchical structure may be modified to conform to the document type definition. The user may be inquired whether to correct the hierarchical structure. In S208, if the user determines not to execute the editing, the process proceeds to N, an alarm process is performed (S210), and execution of the editing command is prohibited (S212).

In S208, the editing may be prohibited without asking the user whether to execute the editing.
The editing may be permitted after performing the alarm processing without inquiring of the user whether or not to execute the editing.

When an editing process is performed to generate a document which is not a valid XML document by the above operation, the user is alerted and the editing process is properly prohibited. Therefore, an appropriate XML document can be created without the user being aware of the document type definition.

The timing of judging the suitability of editing is not limited to the execution of an editing command. For example, when the editing position is changed to a data position in a different name space, it may be determined whether or not the document generated by the previous editing process conforms to the document type definition. Further, when the processing for the document is completed and stored in the recording medium, it may be determined whether or not the document generated by the previous editing processing conforms to the document type definition. Also in this case, FIG.
The appropriateness of editing can be determined by the method shown in FIG. As described above, according to the method in which the determination is not made for each execution of the editing command but is performed collectively at the stage when the editing process is completed, a document that does not conform to the document type definition while editing the document is temporarily In this case, the editing process can be continued without performing the alarm process.

FIG. 20 is a flowchart showing the operation of the document correction section 260. The document correction unit 260 determines whether or not the document generated by executing the edit command needs to be corrected, and if so, makes an appropriate correction.

First, the document correcting section 260 determines whether or not the document generated by the editing process needs to correct the hierarchical structure (S252). If no correction is required, the process proceeds to N, and the process in the document correction unit 260 ends. If the correction is necessary, the process proceeds to Y and inquires of the user whether to execute the correction process (S25).
4). If the user determines not to execute the correction, the process proceeds to N and the processing in the document correction unit 260 ends. If the user decides to make the correction, Y
Then, a correction process is executed (S256). The correction process may be executed without asking the user.

FIGS. 21A and 21B show the document correction unit 260
FIG. 9 is a diagram for explaining an example of the operation of FIG. FIG. 21 (a)
13 shows a state where the tag “sect” is inserted at the position (4) in FIG. Document type definition 612 shown in FIG.
According to this, the element “sub” cannot have the element “sect” as a child element.
0 is not a valid XML document.

FIG. 21B shows an example in which the document 610 shown in FIG. 21A is modified so as to conform to the document type definition 612. Since the element “sect” cannot be a child element of the element “sub”, the element “sect” is traced up the hierarchy to search for an element that can have the element “sect” as a child element. In this case, the element “s” which is an element (hereinafter, simply referred to as “parent element”) in the hierarchy immediately above the element “sub”
“ect” can have an element “sect” as a child element. Therefore, instead of inserting the element “sect” as a child element of the element “sub”, the element “sect” is inserted as a child element of the element “sect”. That is, the element “sub” is divided into two, and the element “sect” is inserted between the divisions. As a result, the element “sect” can be inserted at the same position as the position requested by the user in a manner conforming to the document type definition. The above is the details of the correction processing S256 in FIG.

In FIG. 15, when a tag with a triangle mark is inserted, the document can be modified to conform to the document type definition by the same method as described above. For example, a case where a new tag is inserted at the position (6) will be described. The position (6) is included in the element “bold”. According to the document type definition 612, the element "bol
"d" can have an element "image" as a child element. When inserting another element, the document correction unit 26
Correction by 0 is required. When inserting the element “sub” and the element “bold”, the element “sub” can be inserted as a child element of the element “sub” which is a layer immediately above the element “bold”. The element "sect" and the element "par
When "ag" is inserted, it can be inserted as a child element of element "sect" which is a layer two levels above element "bold".

Referring to FIG. 15, a case where a new tag is inserted at position (1) will be described. The element "sampl
Since the elements that "e" can have are limited to the element "sect" and the element "parag", the element "su"
"b", element "bold", and element "image" cannot be inserted at position (1). In this case, the menu control unit 140 cannot select the element “sub”, the element “bold”, and the element “image” because the modification cannot conform to the document type definition 612.

Similarly, in the case where the range marked with a triangle in FIG. 17 is tagged, the document can be modified to conform to the document type definition by the same method as described above. For example, a case where the ranges (4) to (5) are tagged will be described. The ranges (4) to (5) are included in the element “sub”. According to the document type definition 612, the element “sub” has the elements “sub”,
It can have an element “bold” and an element “image”. When tagging another element, the document must be corrected by the document correction unit 260. When tagging the element “sect” and the element “parag”, the element “s
By inserting a new element “sect” or element “parag” having text data “3” so as to be a child element of the parent element “sect” of “ub”, it is possible to conform to the document type definition 612. .

FIGS. 22A and 22B show the document correcting section 260.
FIG. 10 is a diagram for explaining another example of the operation of FIG. FIG.
10A illustrates a hierarchical structure of a document 620 as an example of a structured document that can be processed by the document processing device 90. The document 620 has three elements “ul” in the main body. 1
The element "ul" has a child element "li", the element "li" has a child element "div", and the element "div"
Has text data “ABC”. The second element “ul” has a child element “li”, and the element “li”
It has a child element “div”, and the element “div” has text data “123”. The third element "ul" is
It has a child element “li”, and the element “li” has a child element “di”.
v ", and the element" div "has text data" ab ".
c ".

FIG. 22B shows a case where the document 620 is displayed on the display device 6.
2 shows the state displayed. Screen 70 of display device 620
The result of rendering the document 620 is displayed in the document display unit 710 of the “0”. Since the display attribute is set so that the element “ul” is displayed as an itemized list, the contents of the three elements “ul” are displayed with “•” added thereto. Now, the user has selected the range 730 using the input device 60 such as a mouse.

FIGS. 23A and 23B are diagrams for explaining the operation of the document correcting section 260 when an edit command for deleting the selected range is executed in FIG. 22B. . In FIG. 22B, when an edit command for deleting the range 730 is executed, the range from the position (x1) to the position (x2) in FIG. 23A is deleted. Performing such a DOM operation is not appropriate as processing for a structured document. Therefore,
In the present embodiment, the document correction unit 260 determines the position (y
DO to delete the range from 1) to position (y2)
An instruction is given to the M engine 220. That is, the second element “ul” is deleted.

FIG. 23B shows a state where the document 620 is displayed on the display device 62 after the above operation is performed. The operation intended by the user can be realized by the correction processing by the document correction unit 260.

FIG. 24 shows the data structure of the position information holding unit 240. The position information holding unit 240 includes a cursor position,
Holds position information in the structured document, such as the start point of the selection range, the end point of the selection range, and the bookmark position. The position information includes information of an element including the position and offset information within the element.

FIG. 25 shows the structured document 600 shown in FIG.
Is displayed on the display device 62. Now, two ranges 732, 734 have been selected and the cursor is at position 712. The range 732 corresponds to the first element “div” of the structured document 600 from the first character to the third character. Therefore, in FIG. 24, the first element “di
“v” is stored, and “1” is stored in the offset information of the start point of the range 1. The element information of the end point of the range 1 stores the first element “div”, and the range 1
“3” is stored in the offset information of the end point.
The same applies to other position information. The bookmark position is information that is not displayed on the screen 700 but is used as a bookmark for jumping from another position in the document.

FIG. 26 is a flowchart showing a method for automatically updating the position information of position information holding section 240. First, when a bookmark position is designated, a range is selected, or a cursor position is moved by a user, new position information is registered in the position information holding unit 240 (S302). Subsequently, a command for editing the document 600 is executed (S304). When the editing command is executed, if the element to be edited by the editing command corresponds to a node whose position information is registered, the process proceeds to Y in S306, and the position information is automatically corrected. (S308). Otherwise, the process proceeds to N in S306, and the position information is not automatically corrected.

FIGS. 27A and 27B show a specific example of the method for automatically correcting the position information shown in FIG. FIG. 27 (a)
Indicates that, when the position information is registered after the fourth character in the text data of the element “div”, the element “di”
An example when a line feed process is performed at a position after the second character of the text data of "v" is shown. At this time, the edit command execution unit 210 executes the line feed process and, at the same time, automatically corrects the position information held in the position information holding unit 240.
In this case, the position after the fourth character in the registered text data of the element “div” is positioned behind the second character of the newly added text data of the second element “div”. Is automatically corrected to that position.

FIG. 27B shows the case where the position information is registered after the fourth character of the text data of the element “div”, and the position data is registered after the second character of the text data of the element “div”. This shows an example in which the part up to the fifth character is deleted. At this time, the edit command execution unit 210 executes the process of deleting the selection range, and at the same time, automatically corrects the position information held in the position information holding unit 240. In this case, since the position after the fourth character in the registered text data of the element “div” has already disappeared, the text data of the element “div”
Automatic correction after the second character.

As described above, the position information held in the position information holding unit 240 is automatically corrected with the editing operation of the node in which the position information is registered. The display can be updated automatically. Further, since the position information is automatically updated by the operation of the DOM engine 220, even when editing a document by a plurality of users, if the editing process is performed by another user, the position information is automatically updated. Can be updated. Also, when developing a plug-in unit 500 having a function of editing a document, the DOM engine 220 automatically updates the position information, so that processing on the document can be performed without worrying about the position information. .

FIGS. 28A and 28B are diagrams for explaining a mutation event for transmitting to the display unit 300 that the document has been processed by the editing process. FIG. 28A shows an example in which “Ueo” is deleted from the text data “Aiueo” of the element “div”. At this time, the DOM engine 220
Issues a mutation event to notify the display unit 300 that the text data of the element “div” has been changed.

FIG. 28B shows an example in which the line feed key is pressed at the position after "i" in the text data "aiueo" of the element "div". At this time, the edit command execution unit 210 first deletes “Ueo” from the text data of the element “div”. Subsequently, the new second element “div” is replaced with the original first element “di”.
v ". Then, the second element “di
“Ueo” is added as text data of “v”.
At this time, the edit command execution unit 210 does not cause the DOM engine 220 to issue a mutation event for each of the three operations described above, but notifies the DOM engine 220 that the first element “div” has been updated. An event and a mutation event notifying that the second element “div” has been inserted are issued. According to this, it is possible to prevent useless issuance of the mutation event, and to speed up the processing.

As described above, the edit command execution unit 210
Issues a plurality of mutation events collectively even when performing a plurality of DOM operations when executing one editing command. Thereby, the processing can be speeded up. In general, it is sufficient to extract the smallest element that includes all the operated element groups and issue a mutation event that notifies that the element has been updated. If an element that encompasses all the elements that have been operated on has a very large amount of content, it takes a lot of time to re-render all of the elements. A mutation event may be individually issued for each of the performed elements.

FIG. 29 shows the cancellation / re-execution processing control unit 4
00 is shown. Cancel re-execution processing control unit 400
Includes a cancellation / re-execution processing holding unit 408 for executing the cancellation processing and the re-execution processing, and a processing state holding unit 406 for holding the current processing state. The cancellation / re-execution processing holding unit 408 holds objects having each process included in the command 410 and its reverse process as a method in the order of the processes. In FIG. 29, for convenience of explanation, a method 402 for executing the cancellation process included in the object held in the cancellation / re-execution process holding unit 408 is illustrated.
And a method 404 for executing re-execution processing,
It is shown in a separate box. When the various commands 410 are executed, if the command is a command that can be canceled, objects having each operation in the command 410 as a method are sequentially sent to the cancellation / re-execution processing holding unit 408. Pile up. At this time, command 4
Information indicating which operation 10 corresponds to which operation is also stored.

When the execution request of the cancellation processing is transmitted via the user interface 100, the cancellation / reexecution processing control unit 400 executes the method for the cancellation processing among the objects held in the cancellation / reexecution processing holding unit 408. , From the latest operation, in the reverse order of stacking,
Execute only commands. At this time, the processing state holding unit 4
06 is moved by one command. Subsequently, when a cancellation processing execution request is further transmitted, a method for cancellation processing among the objects held in the cancellation / reexecution processing holding unit 408 is further stacked from the position of the processing state holding unit 406. The command is executed for one command in the reverse order. When the execution request of the re-execution processing is transmitted, the method for the re-execution processing among the objects held in the cancellation / re-execution processing holding unit 408 is changed from the position of the processing state holding unit 406 to the stacking order. Execute only one command in the same order.

FIGS. 30A and 30B are diagrams for explaining the operation of the cancellation / re-execution processing control unit 400. FIG. FIG. 30A shows that the edit command execution unit 210 executes a command to insert the text data “Kaki” at the position after “I” in the text data “Ai” of the element “Div” in the document. This is shown. As a result of executing this command, the text data of the element “div” is changed to “Aikaki”.

FIG. 30B shows a state in which objects for executing each operation in the command shown in FIG. 30A are stored in the cancellation / re-execution processing holding unit 408. The first object has, as an undo method 402, an operation of moving the cursor position before "U" in order to return the cursor position to the original position when the cancellation processing is executed. When re-executing, there is no need to perform the reverse operation of this operation.
4 is an empty operation that does nothing. Subsequently, the editing command execution unit 210 controls the display unit 30 so that the screen is not changed by another operation during execution of the command.
Requests that the screen be locked to zero. At this time, the object to be stacked second has an operation for locking the view as a redo method 404, and an operation for unlocking the view corresponding to the reverse operation is an undo method 4
02.

Subsequently, in order to return the screen to the original state when the cancellation processing is executed, the element "div"
The object having the operation of issuing the mutation event indicating that the text data has been updated as the undo method 402 is stored in the cancellation / reexecution processing holding unit 408.
Pile on. At the time of re-execution, there is no need to perform the reverse operation of this operation, so the redo method 404 is an empty operation. Subsequently, the DOM engine 220 outputs the element “di
"v" text data from "Ai" to "Aikakiu"
Change to At this time, the redo method 404 has an operation of changing the text data of the element “div” from “Aoi” to “Aikaki”, and the text data of the element “div” corresponding to the reverse operation is “Aikaki”. The object having the operation of changing from "" to "" as the undo method 402 is
Stacked on 8.

Subsequently, the edit command execution unit 210 issues a mutation event indicating that the text data of the element “div” has been updated, and transmits the mutation event to the display unit 300. At this time, this operation is performed using the redo method 404.
Object held as the cancellation / re-execution processing holding unit 40
Stacked on 8. When executing the cancellation process, there is no need to perform the reverse operation of this operation.
04 is an empty operation. Then, the edit command execution unit 2
10 instructs the display unit 300 to unlock the view. At this time, an object having this operation as the redo method 404 and having an operation to lock the view as the undo method 402 corresponding to the reverse operation of this operation is loaded on the cancellation / reexecution processing holding unit 408.

Finally, the edit command execution section 210 moves the cursor position to a position before "U". At this time, an object having this operation as the redo method 404 is loaded on the cancellation / reexecution processing holding unit 408. When executing the canceling process, it is not necessary to perform the reverse operation of this operation, so the undo method 404 is an empty operation.
As described above, the cancellation / re-execution processing holding unit 408 has each operation in the command as the redo method 404,
Objects having the reverse operation as an undo method 402 are sequentially stacked. When the editing command is executed, an object for mainly processing the DOM operation as one unit is stored in the cancellation / re-execution processing holding unit 40.
8 is piled up.

In the description of FIG. 30B, an object having an undo operation and a redo operation as methods is set as one storage unit, and the cancellation / reexecution processing holding unit 408 is used.
Was explained in the case of undo stack 4
02 and the redo stack 404 may be provided separately.
At this time, objects for executing the undo operation are stacked on the undo stack 402, and objects for executing the redo operation are stacked on the redo stack 402.

According to the above configuration, since it is not necessary to prepare a canceling process for each command, it is possible to reduce the trouble when developing a new command. The cancellation / re-execution processing control unit 400 can also control the cancellation / re-execution processing of the command executed by the plug-in unit 500. Therefore, when the plug-in unit 500 is developed, there is no need to prepare the cancellation processing, and the development is facilitated. Can be

FIG. 31 is a flowchart schematically showing the operation of the display unit 300. When the mutation event is transmitted from the editing unit 200 to the display unit 300, first, the rendering unit selection unit 310 acquires a namespace of data to be displayed (S402). Subsequently, the rendering unit selection unit 310 selects a rendering unit that renders the acquired namespace data (S404). If there is an appropriate rendering unit, the process proceeds to Y, where an instruction to execute the rendering process is sent to the rendering unit, and the rendering process is performed (S40).
6), the display unit 340 displays the result on the display device 62 (S410). If there is no suitable rendering unit, the process proceeds to N, the tree display processing unit 330 performs tree display processing (S408), and the display unit 340 displays the result on the display device 62 (S410).

FIG. 32 shows the rendering unit selection unit 3.
10 shows a structured document 630 used to explain the tree display processing unit 330 and the tree display processing unit 330. Document 630 is XHTM
L and a portion 634 described in MATHML. MATHML is a markup language for describing symbols and expressions used in the mathematical field.

FIG. 33 shows a MATHML plug-in unit 51 for processing a document described in MATHML.
0 by the document processing device 90 having the
This shows an example in which rendering processing is performed and displayed on the display device 62. When the display request of the document 630 is transmitted to the display unit 300, the rendering unit selection unit 310 causes the rendering unit 320 to send the portion 63 described in XHTML.
2 and instructs the MATHML plug-in unit 510 to render the portion 634 described in MATHML. The rendering unit 320 converts the part 63 described in XHTML
2 is performed to create a screen. MAT
The HML plug-in unit 510 performs a rendering process on the part 634 described in MATML to create a screen. The display unit 340 displays each screen on the display device 62.

FIG. 34 shows a MATHML plug-in unit 51 for processing a document described in MATHML.
0 by the document processing apparatus 90 having no
This shows an example in which 0 is rendered and displayed on the display device 62. When the display request of the document 630 is transmitted to the display unit 300, the rendering unit selection unit 310 causes the rendering unit 320 to send the part 6 described in XHTML.
32 for rendering processing. in this case,
The plug-in unit 500 for rendering the portion 634 described in MATHML is not mounted. The rendering unit selection unit 310
It is determined whether a style sheet for displaying the portion 632 described in ML can be obtained. If the style sheet can be obtained, the rendering unit 320 is instructed to perform the rendering process. If the style sheet cannot be obtained, the tree display processing unit 330 is instructed to perform tree display processing.

The rendering unit 320 performs a rendering process on the portion 632 described in XHTML to create a screen. The tree display processing unit 330 performs processing for displaying the portion 634 described in MATHML in a form in which the hierarchical structure can be understood, and creates a screen. The display unit 340
Each screen is displayed on the display device 62. In FIG. 34, a portion 634 described in MATHML is displayed as a tree in a window 730 provided in the document display unit 710.

At this time, editing of the data displayed in the window 730 may be prohibited. As described with reference to FIG. 19, the editing process of the data displayed in the window 730 may be performed only when the editing propriety determining unit 250 permits the editing. Editing processing involving a change in the hierarchical structure may be prohibited. An editing process of only text data that does not involve a change in the hierarchical structure may be permitted.

FIG. 35 shows an example in which a portion 634 described in MATHML is displayed in a window 730 with a scroll bar. The window 730 is provided so as to be able to scroll a portion 634 described in MATHML whose display attribute is unknown. As a result, even when the display attribute unknown data is very large, all data can be displayed in a limited area.

FIG. 36 shows an example in which the source of the portion 634 described in MATHML is displayed in a window 730 with a scroll bar. As described above, even when the document is displayed as it is, the user can know the hierarchical structure of the document.

According to the above configuration, even if data having unknown display attributes described in a unique tag set is present in a document, the data is displayed in the document display unit 71 in a form in which the hierarchical structure can be understood.
By displaying the content in 0, the contents of the document can be displayed in an easily understandable manner.

FIG. 37 is a flowchart showing the operation of the style setting section 322. The style setting unit 322
Set the display attributes to be satisfied by each element described in the style sheet. First, the style setting unit 322 acquires a default style sheet and sets display attributes described in the default style sheet (S502).
The default style sheet is a style sheet that defines initial settings of the document processing apparatus 90, and is applied when the user does not specify a display attribute.

Subsequently, the style setting section 322 overwrites the display attribute described in the user style sheet (S504). The user style sheet is a style sheet defined as an initial setting by a user using the document processing apparatus 90, and is applied when a display attribute is not specified in a document. Since the display attributes described in the user style sheet are overwritten, they take precedence over the display attributes described in the default style sheet. For display attributes not described in the user style sheet, the display attributes described in the default style sheet are applied.

Next, the style setting section 322 determines whether or not an author style sheet has been designated (S506). If the author style sheet has been specified, the process proceeds to Y and overwrites the display attributes described in the author style sheet (S508). The author style sheet is a style sheet defined as a display attribute applied to the entire document by the author who edited the document, and is applied when a display attribute is not specified for an element in the document. Since the display attributes described in the author style sheet are overwritten, they take precedence over the display attributes described in the default style sheet and the user style sheet. For display attributes not described in the author style sheet, display attributes described in the default style sheet or user style sheet are applied. If the author style sheet has not been specified, the process proceeds to N, the affirmative setting of the display attribute is omitted, and the process proceeds to S510.

Subsequently, the style setting section 322 determines whether or not a display attribute is specified for the element (S51).
0). If a display attribute is specified for the element, the process proceeds to Y, and the display attribute described in the author style sheet is overwritten and set (S512). The display attribute specified directly to the element is overwritten, so that it takes precedence over the display attributes described in all style sheets. If no display attribute is specified for the element, the display attribute described in the default style sheet, user style sheet, or author style sheet is applied. If the display attribute is not specified for the element, the process proceeds to N and the display attribute setting step is omitted. With the above, the style setting unit 322
Operation ends.

FIG. 38 is a flowchart showing details of the display attribute setting steps (S502, S504, and S508) shown in FIG. The style setting unit 322
The element name of the target element for which a style is to be set is obtained (S522). Subsequently, the display attribute to be applied to the element is searched using the element name as a key, and the display attribute is set (S524). Then, in the target element, class
It is determined whether an attribute such as an attribute or an id attribute is designated (S526). N if no attributes are specified
To end the display attribute setting process. If the attribute has been specified, the process proceeds to Y, and the attribute name of the target element is further acquired (S528). Next, a display attribute is searched using the attribute name as a key, and the display attribute is set (S530).
This completes the display attribute setting process. If a hash table using the attribute name as a key is not prepared, the search step (S530) using the hash table is not performed.

FIG. 39 is a flowchart showing details of the display attribute search / setting step (S524 and S530) shown in FIG. The style setting unit 322 acquires a hash value based on the acquired element name of the target element (S542). The hash value may be calculated from, for example, the ASCII code value of the element name. continue,
A hash table is searched using the obtained hash value as a key (S544). For hash tables,
Details will be described with reference to FIG.

If the hash value does not exist in the hash table, it means that the display attribute of the target element has not been specified, so the flow advances to N of S546 to terminate the process without setting the display attribute. If a hash value exists in the hash table, Y in S546
Then, it is determined whether there is a plurality of matching selectors corresponding to the hash values (S548). If there are a plurality of suitable selectors, the process proceeds to Y, narrows down the suitable selectors, and obtains a selector that matches the target element (S55).
0). Subsequently, the display attribute set in the selector matching the target element is set in the target element (S552). If there is only one matching selector,
N, and change the display attribute set for the selector to
The target element is set (S552). Thus, the display attribute search / setting process ends.

FIGS. 40A and 40B show examples of hash tables. FIG. 40A shows an example of a hash table in which classification is not performed based on element attributes. The hash value is calculated from the element name of the element of the lowest hierarchy in the selector. For example, the hash value of the element name “body” is 8. In this hash table, since the attribute is not classified, the hash value of the element “div” is the same as the hash value of the element “div” to which the attribute “reference 1” is specified. Selector "d
“iv p” corresponds to the element “p” which is a descendant element of the element “div”. At this time, since the hash value is calculated from the element name of the element of the lowest hierarchy, “div
The hash value of “p” is the same as the hash value of “p”.

A method for setting the display attribute of the target element “div” using the hash table shown in FIG. 40A will be described. Here, the class attribute “reference 2” is specified for the target element “div”. First, a hash value is calculated from the element name “div”. The hash value calculated from the element name “div” is
14. Subsequently, a hash table is searched using the hash value 14 as a key. Then the matching selector is
It can be seen that they are "div", "div. Reference 1", and "div. Reference 2". Subsequently, the selector for which the display attribute is to be set is obtained by comparing each of the matching selectors with the target element. Here, "di
v "and" div. reference 2 ",
Set the display attribute specified in "div", then
The display attribute specified in “div. Reference 2” is overwritten and set.

FIG. 40B shows an example of a hierarchical hash table further classified according to the attribute of the element. The selectors corresponding to the hash value 14 are “div”, “di”
v. Reference 1 "," div. Reference 2 ", and" div.
Reference 2 # abc ". Among them, “div. Reference 1”, “div. Reference 2”, and “div. Reference 2 #”
Since the attribute “abc” is specified, it is further classified into a hash table using the attribute name as a key. The element “div” for which the attribute “reference 1” is specified is classified into the hash value 5, and the element “div” for which the attribute “reference 2” is specified is classified into the hash value 11.

A method of setting the display attribute of the target element <divclass = “reference 2”> using the hash table shown in FIG. 40B will be described. First, a hash value is calculated from the element name “div”. The hash value calculated from the element name “div” is 14. Subsequently, a hash table is searched using the hash value 14 as a key. Then, “div” is first selected as the matching selector. Subsequently, the selector for which the display attribute is to be set is obtained by comparing each of the matching selectors with the target element. Here, since “div” and “div. Reference 2” correspond, first, “div”
Is set, and then the display attribute specified in “div. Reference 2” is overwritten.

In the present embodiment, the matching selector is searched using the hash table. However, the search may be executed using a method such as a binary tree. According to the above configuration,
The style setting process can be sped up.

FIG. 41 is a flowchart showing the operation of the layout processing section 324. First, a float block placed forward from the line before the editing position is removed from the layout for rearrangement, and is saved in the queue in the order of the appearance position on the source (S602). continue,
The text data of the paragraph including the editing position is laid out again (S604). Text data is sequentially arranged in a line rectangle in which the text data can be arranged. Next, the paragraph after the editing position is shifted (S606). S6
When the number of lines in the paragraph changes according to 04, a gap or overlap occurs between the next paragraph and the next paragraph, so that the subsequent paragraph is shifted in the vertical direction to eliminate the gap. Subsequently, it is determined whether or not there is any laid-out float block saved in the queue (S608).

If there is a float block in the queue,
Proceeding to Y, it is determined whether a float block can be arranged (S610). In other words, as long as there is a float block waiting to be placed in the queue, it is always determined whether or not placement is possible at the beginning of the line. If the arrangement is possible, the process proceeds to Y and the float block is laid out (S612). Then, again at S60
Returning to step 8, the layout processing of the float block is performed until an unplaceable float block appears or there are no float blocks waiting to be placed in the queue. If the float block could not be arranged in S610, the process proceeds to N and the line layout processing of the text data is performed (S614). The text data is sequentially arranged in the line rectangle, and the processing is terminated when one line is arranged.

Subsequently, it is determined whether or not it is the end of the document or the end of the table cell (S622). That is, it is determined whether or not text data to be arranged still remains. If it remains, the process proceeds to N and determines again whether or not the float block can be arranged. If it is at the end of the document or at the end of the table cell, the process proceeds to Y to set a virtual line for determining whether or not the float block can be arranged (S
624). When the float block remaining in the queue is arranged in the last row, a virtual row is set immediately below the lower side of the innermost arranged float block overlapping the float block. Thereafter, when it is determined whether or not the placement-waiting float block saved in the queue can be placed again, the determination is made at the beginning of this virtual row.

In S608, if there are no more float blocks waiting to be laid out in the queue, the process proceeds to N and there is no overlap or gap between the line rectangle of the first line of the next paragraph and the float block. It is determined whether or not there is (S616). If there is an overlap or a gap, the process proceeds to N, and the paragraph is laid out to the end (S61).
8). After that, the process proceeds to S616 again. If there is no overlap or gap, the process proceeds to Y, and the subsequent paragraphs are shifted (S620). Thus, the relayout processing when the document is edited is completed.

FIG. 42 shows an example of a structured document used for explaining the operation of the layout processing unit 324. The structured document 640 is a document described in XHTML. An image file is embedded in the first paragraph of the document 640 and specified to be displayed right-aligned.

FIG. 43 shows a state where document 640 shown in FIG. 42 is displayed on display device 62. Image 642 is displayed right-justified. The text data of each paragraph is laid out so as not to overlap the image 642.

FIG. 44 shows how the layout processing unit 324 manages text data as line rectangles when performing layout processing. The layout processing unit 324 manages floating blocks such as images, tables, vertical writing blocks, and tree display windows, and lines of text data as rectangular data. The layout processing section 324 determines whether or not the layout is correctly performed by checking whether or not these rectangular data overlap.

FIGS. 45A, 45B, and 45C show documents 640
FIG. 10 is a diagram for explaining an operation of the layout processing unit 324 when a range 644 is deleted. FIG.
(A) shows a state in which the range 644 is selected from the document 640. The user can input a range 64 through the input device 60.
When the delete command is further executed after selecting the display unit 4, the editing unit 200 performs necessary processing, and the display unit 3
A mutation event is transmitted to 00. At this time, the layout processing unit 324 re-lays out the part after the editing part.

In this case, there is no float block placed forward from the row before the deleted row, and no float block is saved in the queue. First, the text data of the second paragraph is laid out again. Since the range 644 has been deleted from the text data of the second paragraph, the second to fourth lines disappear. Subsequently, the third and fourth paragraphs are shifted upward. The result is shown in FIG. This state is not actually displayed. Here, as a result of the shift processing, it is checked whether or not there is an overlap or a gap between the row rectangular data and the rectangular data of the floating block. In this case, the row rectangular data of the first line of the third paragraph and the rectangular data of the image 642 overlap, and the layout is not correct in this state. Therefore, the third paragraph is laid out again so as not to overlap the image 642. The text data of the third paragraph is arranged in a newly set line rectangle so as not to overlap with the image 642. As a result, when the height of a paragraph changes due to an increase or decrease in lines, the paragraphs after that paragraph and the lines included therein are shifted. The result is shown in FIG.

Similarly, in the fourth and subsequent paragraphs, it is checked whether or not there is an overlap or gap between the row rectangular data and the rectangular data of the float block at the beginning of each line. The first line of the fourth paragraph has no overlap with the float block. Furthermore, there is no gap that previously avoided the float block. That is, the line rectangle extends from the left end to the right end of the document display unit 710. At this time, since there is no change in the layout after this line, the check of the overlap or gap of the line is finished, and the line after this line is shifted.
In this case, the state shown in FIG. 45C corresponds to a state where the layout is correctly performed.

FIG. 46 shows another example of a structured document used for explaining the operation of the layout processing unit 324. The structured document 650 is a document described in XHTML. The first paragraph of the document 650 contains 3 image files.
One is specified to be displayed right-aligned, and the other two are specified to be displayed left-aligned.

FIG. 47 shows a state where the document 650 shown in FIG. 46 is displayed on the display device 62. Image 652 is displayed right-justified. Images 654 and 656 are displayed left-justified. The text data of each paragraph is laid out so as not to overlap with the images 652, 654, and 656. The float block is
In principle, positioning is performed on a line-by-line basis. That is, the y-coordinates of the upper side of the row and the upper side of the float block match. If it is placed below the end of the document or the last row of the table cell, it is positioned in pixels. Now, the range 658 has been selected.

FIGS. 48 to 50 show the contents of the document 650.
Layout processing unit 32 when range 658 is deleted
4 is a diagram for explaining the operation of FIG. FIG.
Of the 50, the range 658 is deleted, the images 654 and 656 advanced from the line before the deleted line are saved in the queue 660, the second paragraph is laid out, and the third paragraph is shifted. This shows the state when the processing is performed. In the queue 660, in the order of appearance positions on the source,
Image 654 and image 656 are stacked in the buffer.

FIG. 49 shows how the third paragraph is laid out again. First, from the state of FIG. 48, since the float blocks are stacked in the queue, it is determined whether or not it can be arranged in the line immediately below the second paragraph. In this case, since arrangement is not possible, the first line of the third paragraph is subjected to line layout processing. Subsequently, it is determined whether or not a float block can be arranged in a line immediately below the first line of the third paragraph. Since the image 654 can be arranged, the image 654 is arranged left-aligned.
Further, it is determined whether or not the image 656 can be arranged. Since the image 656 cannot be placed, the third
Line layout the second line of the paragraph. As described above, the arrangement of the float block is checked for each line feed, and if the arrangement is not possible, the line layout of the text data is performed. FIG. 49 shows a state in which the line layout has been completed up to the end of the third paragraph.

FIG. 50 shows how the image 656 is laid out. In FIG. 49, when the layout is completed up to the end of the document, since the image 656 still remains in the queue 660, a virtual line is set. The virtual line is an image 65 that overlaps when the image 656 is placed in the last line.
4 is set immediately below the lower side. At the beginning of this line,
It is checked whether the image 656 can be arranged. Since the image 656 can be arranged, it is arranged left-aligned. This completes the document 650 re-layout process.

According to the above configuration, a layout conforming to the CSS specification can be realized. Further, when there is no overlap or gap with the float block at the time of a new paragraph, the following paragraphs are not laid out and the shift processing is performed, so that the time required for redisplay can be reduced.
According to the method of the present embodiment, in many cases, it is not necessary to determine whether or not there is an overlap or gap between float blocks, so that high-speed processing can be realized.

The floppy disk 56 or the CD-ROM 58 as an example of the recording medium can store some or all of the functions of the terminal 10 described in the present application. The floppy disk 106 can store some or all of the functions of other devices. These programs may be read directly from the recording medium to the RAM and executed.

In this embodiment, the method of processing a document in the XHTML format and the XML format has been described as an example of a structured document.
The present invention can also be applied to a structured document described using GML, MHEG, HTML, other formats, and formats extended or limited thereto.

As described above, the present invention has been described using the embodiment. However, the technical scope of the present invention is not limited to the scope described in the above embodiment. It is apparent to those skilled in the art that various changes or improvements can be added to the above embodiment. It is apparent from the description of the appended claims that embodiments with such changes or improvements can be included in the technical scope of the present invention.

[0136]

As is apparent from the above description, according to the present invention, a document processing apparatus capable of appropriately processing a structured document, a document processing method usable by the document processing apparatus, and a method thereof are described. A computer-readable recording medium on which a program to be executed by a computer is recorded can be provided.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a state in which a program for causing a computer to execute a document processing method according to an embodiment is distributed via a network.

FIG. 2 is a diagram illustrating a configuration of a computer.

FIG. 3 is a diagram showing schematic functional blocks of a document processing apparatus 90 according to the embodiment of the present invention.

FIG. 4 is a diagram showing more detailed functional blocks of the user interface 100.

FIG. 5 is a diagram showing more detailed functional blocks of the editing unit 200.

FIG. 6 is a diagram showing more detailed functional blocks of the display unit 300.

FIG. 7 is a diagram illustrating a structured document 600 that can be processed by the document processing apparatus 90.

FIG. 8 is a block diagram showing the structure of the document processing apparatus 90 when the structured document 60 is used.
0 is read and the display unit 300
FIG. 6 is a diagram showing a state where the image is displayed on the screen 2;

FIG. 9 is a diagram illustrating a structured document 600 after an editing process has been executed.

FIG. 10 is a diagram showing a screen 700 after an editing process has been executed.

FIG. 11 is a flowchart showing an operation of the menu control unit 140.

FIG. 12 is a diagram showing a structured document 610 described in XML.

FIG. 13 is a schematic diagram showing the hierarchical structure of a portion 616 whose name space is “sample” in the structured document 610 in an easily understandable manner.

FIG. 14 is a diagram illustrating a state in which a menu is displayed when the cursor 712 is at a position (4) in FIG.

FIG. 15 is a diagram illustrating a relationship between an editing position in a document 610 and a tag that can be inserted at that position.

FIG. 16 is a diagram illustrating a state where a menu is displayed in a state where a range 724 is selected.

FIG. 17 is a diagram illustrating a relationship between an editing position in a document 610 and a tag whose range can be tagged.

FIG. 18 is a diagram illustrating a state in which a menu is displayed by right-clicking the mouse in the document display unit 710 when the cursor 712 is at the position (4) in FIG.

FIG. 19 is a flowchart showing the operation of the editing suitability judging section 250.

FIG. 20 is a flowchart showing the operation of the document correction unit 260.

FIGS. 21A and 21B are diagrams illustrating a document correction unit 260;
FIG. 9 is a diagram for explaining an example of the operation of FIG.

FIGS. 22A and 22B show a document correction unit 260;
FIG. 10 is a diagram for explaining another example of the operation of FIG.

FIGS. 23A and 23B are diagrams for explaining the operation of the document correction unit 260 when an edit command for deleting a selected range is executed in FIG. 22B. is there.

FIG. 24 is a diagram showing a data configuration of a position information holding unit 240.

FIG. 25 shows a structured document 600 shown in FIG. 7;
Is a view showing a state in which is displayed on the display device 62. FIG.

FIG. 26 is a flowchart illustrating a method for automatically updating the position information of the position information holding unit 240.

27 (a) and 27 (b) are diagrams showing a specific example of the position information automatic correction method shown in FIG. 26.

FIGS. 28A and 28B are diagrams illustrating a mutation event for transmitting to the display unit 300 that the document has been processed by the editing process.

FIG. 29 is a block diagram showing a cancel re-execution processing control unit 4;
FIG. 2 is a diagram showing a configuration of a 00.

FIGS. 30A and 30B are diagrams for explaining the operation of the cancellation / re-execution processing control unit 400. FIGS.

FIG. 31 is a flowchart schematically showing an operation in the display unit 300.

FIG. 32 shows a rendering unit selection unit 3
FIG. 10 is a diagram illustrating a structured document 630 used for explaining a tree display processing unit and a tree display processing unit.

FIG. 33 is a MATHML plug-in unit 51 for processing a document described in MATHML.
0 by the document processing device 90 having the
FIG. 7 is a diagram showing an example in which is rendered and displayed on a display device 62.

FIG. 34 is a MATHML plug-in unit 51 for processing a document described in MATHML.
0 by the document processing apparatus 90 having no
FIG. 6 is a diagram showing an example in which 0 is rendered and displayed on a display device 62.

FIG. 35 is a diagram showing an example in which a portion 634 described in MATHML is displayed in a window 730 with a scroll bar.

FIG. 36 is a diagram showing an example in which the source of a portion 634 described in MATHML is displayed in a window 730 with a scroll bar.

FIG. 37 is a flowchart showing the operation of the style setting unit 322.

FIG. 38 is a flowchart showing details of the display attribute setting steps (S502, S504, and S508) shown in FIG. 37.

FIG. 39 is a flowchart showing details of display attribute search / setting steps (S524 and S530) shown in FIG. 38.

FIGS. 40A and 40B are diagrams illustrating examples of a hash table. FIG.

FIG. 41 is a flowchart showing the operation of the layout processing unit 324.

FIG. 42 is a diagram showing a structured document 640 used for explaining the operation of the layout processing unit 324.

FIG. 43 is a view showing a state where the document 640 shown in FIG. 42 is displayed on the display device 62.

FIG. 44 is a diagram illustrating a state where text data is managed as a line rectangle when the layout processing unit 324 performs a layout process.

FIGS. 45 (a), (b), and (c) show a document 640;
FIG. 10 is a diagram for explaining an operation of the layout processing unit 324 when a range 644 is deleted.

FIG. 46 is a diagram showing a structured document 650 used for explaining the operation of the layout processing unit 324.

FIG. 47 is a view showing a state where the document 650 shown in FIG. 46 is displayed on the display device 62.

FIG. 48 shows a range 658 of a document 650.
FIG. 10 is a diagram for explaining an operation of the layout processing unit 324 when is deleted.

FIG. 49 is a diagram showing a range 658 of a document 650;
FIG. 10 is a diagram for explaining an operation of the layout processing unit 324 when is deleted.

FIG. 50 is a view showing a range 658 of a document 650;
FIG. 10 is a diagram for explaining an operation of the layout processing unit 324 when is deleted.

[Explanation of symbols]

10 internet, 20 download server,
Reference Signs List 30 user terminal, 40 document server, 50 editing terminal, 60 input device, 62 display device, 64 communication device, 66 CPU, 68 memory, 70 hard disk, 72 external storage device, 90 document processing device, 100 user interface, 110
Event analysis unit, 120 event map, 13
0 UI command execution unit, 140 menu control unit,
200 editing unit, 210 editing command execution unit, 220 DOM engine, 230 document holding unit, 240 position information holding unit, 250 editing suitability judging unit, 260 document correcting unit, 300 display unit,
310 rendering unit selection unit, 320 rendering unit, 322 style setting unit, 324 layout processing unit, 330 tree display processing unit, 340
Display, 400 cancellation / re-execution processing control unit, 4
02 Undo stack, 404 Redo stack,
410 commands, 500 plug-in units,
660 queues, 700 screens, 702 menu bar, 704 toolbar, 706 horizontal ruler,
708 vertical ruler, 710 document display part, 712
Cursor, 730 window

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 3/00 651 G06F 3/00 651B 17/30 140 17/30 140 412 412

Claims (9)

[Claims] 1. A method for processing a structured document in which data in the document is classified into a plurality of components having a hierarchical structure, wherein when the editing process is performed on the document, the editing process is performed. Obtaining a hash value corresponding to the target component; and applying the hash value to the component with reference to a hash table in which the hash value is associated with a display attribute to be applied to the component. Obtaining a display attribute to be applied, and applying the display attribute to the data belonging to the component. 2. The document processing apparatus according to claim 1, wherein the hash value is calculated based on an element name of the component. 3. The method according to claim 2, wherein the hash value is calculated based on the element name of the lowest hierarchy among the element names of the constituent elements. 4. The apparatus according to claim 1, wherein the hash table further includes a second hash table in which the hash value is associated with a display attribute to be applied to a class attribute value of the component. 3. The method according to any one of 3. 5. The structured document includes SGML, XML,
The method according to any one of claims 1 to 4, wherein the method is described in any one of MHEG, HTML, XHTML, and an extended or limited form thereof. 6. The display attribute according to claim 1, wherein the display attribute is described in one of CSS, XSL, and a format extended or limited thereto.
The method according to any of the above. 7. A computer-readable storage medium storing a program for causing a computer to execute the method according to claim 1. Description: 8. A program for storing a program for causing a computer to execute the method according to claim 1; and a communication device for reading the program from the recording medium and distributing the program to the computer. Server device characterized by the above-mentioned. 9. A document processing apparatus for processing a structured document in which data in a document is classified into a plurality of components having a hierarchical structure, wherein a hash value for acquiring a hash value corresponding to the component is provided. An acquisition unit, and a display attribute acquisition unit that acquires a display attribute to be applied to the component by referring to a hash table in which the hash value is associated with a display attribute to be applied to the component. A document processing apparatus characterized by the above-mentioned.