JP2021082088A - Information processing device, control method thereof, program, and storage medium - Google Patents

Abstract

To provide a series of display processing of a structured document capable of improving the readability of auxiliary information in the case when reading kanas which are attached to kanjis as auxiliary information annotated to kanjis is more important when understanding the document depending on the age, the nationality, etc. of a user.SOLUTION: An information processing device 100 includes: an acquisition unit 111 that acquires a structured document; a determination unit 112 that determines whether the description of the structured document includes predetermined annotation information; a conversion unit 114 configured to, when determined that annotation information is included, convert the description of the structured document so that a piece of auxiliary information included in the annotation information is embedded in the body of the structured document; and a display control unit 115 that controls to display the structured document on a display unit according to the description of the converted structured document.SELECTED DRAWING: Figure 1

Description

The present invention relates to a display process of a structured document.

In the HTML document used as the content of the website, ruby can be treated as one of the expressions of the character string. Ruby is annotation information for the text of the content, and is displayed as auxiliary information for adding annotations to the target character string. In the case of Japanese, it is used to indicate reading kana as auxiliary information for the kanji to be annotated, and to indicate the meaning as auxiliary information for the compound words and idioms to be annotated. In general, auxiliary information is displayed at the top of the annotation target for horizontal writing and to the right of the annotation target for vertical writing, with characters smaller than the characters in the text.

On the other hand, in recent years, even information processing devices having a small display area such as smartphones, tablet terminals, and portable game machines have an opportunity to browse websites including ruby. In order to display a document in a font size with good visibility on a device having a small display area, the number of characters that can be displayed per screen is smaller than that on a device having a large display area. On top of that, when the auxiliary information is displayed, the line spacing is widened, so that the amount of information that can be accommodated on one screen is further reduced. Therefore, in Patent Document 1, it is possible to display a document in which auxiliary information is hidden according to the size of the display area of the display unit.

Japanese Unexamined Patent Publication No. 2014-119868

Depending on the age, nationality, etc. of the user, the reading kana, which is auxiliary information, may be more important than the kanji to be annotated in understanding the document. However, in general, auxiliary information is often displayed between lines in characters smaller than the text, so that it can be said that the readability is low for a viewer who places more importance on auxiliary information. Patent Document 1 proposes to switch the display / non-display of the auxiliary information, but does not consider that there is an environment in which the content of the auxiliary information is more important to the text.

The present invention has been made to solve the above-mentioned problems, and one of the objects of the present invention is to improve the readability of annotation information contained in a structured document.

In order to solve the above problems, the information processing apparatus of the present invention includes an acquisition means for acquiring a structured document, a determination means for determining whether or not a predetermined annotation information is included in the description of the structured document, and the determination. When it is determined by the means that there is annotation information, the conversion means for converting the description of the structured document so that the auxiliary information included in the annotation information is embedded in the body of the structured document, and the converted structured document. The present invention includes a display control means for displaying the structured document on the display device according to the description of the above.

According to the present invention, the readability of the annotation information included in the structured document of the structured document including the ruby notation is improved.

The block diagram which shows an example of the hardware configuration and the functional configuration of an information processing apparatus. The figure which shows an example of the HTML document including the annotation information, and the drawing result. The block diagram which shows an example of GUI of the application which displays an HTML document. The figure which shows an example of the HTML document after conversion and the drawing result. The figure which shows an example of the HTML document after conversion and the drawing result. The figure which shows an example of the HTML document after conversion and the drawing result. A flowchart shows an example of the main processing executed by the information processing device. The flowchart which shows an example of the document conversion process executed by an information processing apparatus. The block diagram which shows an example of GUI of the application which displays an HTML document. The figure which shows an example of the HTML document and the drawing result.

Hereinafter, embodiments according to the present invention will be described in detail with reference to the drawings. The configurations described in the following embodiments are typical examples, and the scope of the present invention is not necessarily limited to those specific configurations.

<First Embodiment>
As the first embodiment, when a browser application installed on a tablet terminal browses an HTML document containing annotation information, the processing of displaying the annotation information in a format converted by a conversion method selected by the user from a plurality of options. An example of is described. In the following embodiments, the "commentary information" refers to a description portion of the description of the HTML document for expressing a comment on the document body. Further, the "annotation target" refers to the character string to be annotated in the document body, and the "auxiliary information" refers to the character string described as an annotation.

FIG. 1A is a block diagram showing a hardware configuration of the information processing apparatus according to the present embodiment. In the present embodiment, the information processing device 100 assumes a tablet terminal as an example. However, the information processing device 100 can be applied to the present embodiment as long as it is a device having a browser function and capable of viewing HTML documents, such as a smartphone, various wearable devices, a game machine, or a personal computer. The information processing device 100 includes a controller unit 101, an operation device 102, a display device 103, a storage device 104, and a communication device 108 that control the entire information processing device as main components.

The controller unit 101 includes a CPU 105, a ROM 106, and a RAM 107. The CPU 105 executes the processing of each processing unit in the information processing apparatus 100. The ROM 106 stores various programs executed by the CPU 105 and data required by the programs. Further, the RAM 107 is composed of SRAM, DRAM, etc., and is for storing program control variables and the like. Further, various work buffers are also stored in the RAM 107. The storage device 104 is composed of a hard disk or the like and is for storing file data such as documents and images. The operation device 102 is a device for the user to perform various input operations, and is composed of a pointing device, a keyboard, and the like. In the present embodiment, the touch panel linked with the display device 103 is the operation device 102. The display device 103 is for notifying the user of the display by using an LCD, an LED, or the like. The communication device 108 is an interface for connecting to a network. As a connection method, there are LAN, USB and the like.

The information processing device 100 represented by the present embodiment executes an application program (hereinafter, referred to as a browser) that interprets and draws the acquired Web content. The browser is stored in the ROM 106 or the storage device 104, reads into the RAM 107, and the CPU 105 executes the process. The GUI and Web contents constituting the browser are drawn on the display device 103, and receive an instruction from the user in response to the input from the operation device 102. When the Web content is acquired via the network, the processing is performed via the communication device 108.

FIG. 1B is a block diagram schematically showing a configuration of software realized by the controller unit 101 in the present embodiment. Each functional unit is realized by the CPU 105 expanding the program stored in the ROM 106 into the RAM 107 and executing processing according to each flowchart described later. Then, the execution result of each process is held in the RAM 107. Further, for example, when hardware is configured as an alternative to software processing using the CPU 105, a calculation unit or a circuit corresponding to the processing of each functional unit described here may be configured.

The acquisition unit 111 performs a process of acquiring the HTML document specified by the browser. In the present embodiment, when the document in the information processing device 100 is specified by the input using the operation device 102, the HTML document stored in the storage device 104 is acquired. When a document outside the information processing device 100 is specified in the URL, the HTML document is acquired via the communication device 108.

The determination unit 112 determines whether or not the annotation element exists in the HTML document. Generally, in HTML, a <ruby> element is defined as an element (hereinafter referred to as an annotation element) for specifying annotation information, the annotation target for ruby is the <ruby> element, and the auxiliary information is the <rt> element. It is specified. In addition, it is defined that an information processing device or a browser that does not have a function of notating auxiliary information in the upper part or the right part of an annotation target specifies alternative notation information used to express the auxiliary information in the <rp> element. ing. The determination unit 112 analyzes the HTML document acquired by the acquisition unit 111 and determines the presence or absence of the <ruby> element.

The selection unit 113 selects a notation method for converting the ruby notation based on the user input when it is determined that the determination unit 112 has annotation information. In the present embodiment, the display device 103 displays a GUI for selecting the notation method of the annotation information from a plurality of options, and the selection unit 113 selects the notation method according to the options selected by the user input. The conversion unit 114 performs a process of converting the HTML document acquired by the acquisition unit 111 according to the notation method selected by the selection unit 113. In the present embodiment, the <rt> element and the <rp> element included in the <ruby> element whose existence has been confirmed by the determination unit 112 are interpreted, and the notation of the annotation target, the auxiliary information, and the alternative notation information is changed.

In addition, element detection and structure conversion of a structured document such as an HTML document can be performed by a structure analysis tool. For example, when a structured document is input, a structural analysis tool generates a DOM (Document Object Model) tree in which elements, texts, attributes, and the like constituting the document are represented by a tree structure as objects. Each object that constitutes the DOM tree is called a node, and each node of element, text, and attribute is called an element node, text node, and attribute node. As an operation on the DOM tree, it is possible to acquire a specified node, add a node, delete a node, and the like. The DOM tree can also be serialized and output as a structured document. Extraction of <ruby> elements and conversion of HTML documents performed by the determination unit 112 and the conversion unit 114 are realized by using this structural analysis tool.

The display control unit 115 is a functional unit that controls the contents displayed on the display device 103. In the present embodiment, the execution screen of the browser including the GUI and the data obtained by converting the HTML document acquired by the acquisition unit 111 by the conversion unit 114 are drawn and output to the display device 103.

FIG. 2 is a diagram showing an example of an HTML document including annotation information and a drawing result thereof. In the HTML document 201, five annotation informations are specified by the <ruby> element. Specifically, for the annotation targets "Kuru", "Hakumei", "Clothing", "Ten", and "Mt. Amanoka", the <rt> elements are "ki", "shirotahe", and " "Koromo", "Ama", and "Kaguyama" are designated as auxiliary information. If the browser cannot display the annotation target and the auxiliary information side by side, the <rp> element is specified to distinguish the annotation target and the auxiliary information by using "[" and "]" as alternative notation information. There is. In the case of the information processing apparatus 100 capable of expressing auxiliary information in parallel as an annotation target, the drawing result 202 is displayed.

FIG. 3 is a diagram showing an example of a screen of a GUI (Graphical User Interface) of a browser that displays an HTML document in the present embodiment. The window 301 is composed of a location field 302 for designating the HTML document to be displayed and a drawing area 304 for drawing the layout result of the HTML document. In the location column 302, it is assumed that the HTML document shown in FIG. 2 is specified. In the example of FIG. 3, the dialog 303 is popped up on the drawing area 304. In the present embodiment, the dialog 303 is displayed when it is determined that the annotation information exists in the acquired HTML document. The buttons 305 to 312 are buttons corresponding to the options for selecting the notation method of the annotation information, and exemplify the result of converting a part of the HTML document. The selection unit 113 selects the notation method associated with the button pressed by the user. The conversion unit 114 converts the HTML document so as to realize the notation according to the selected notation method. In this embodiment, the dialog 303 presents the user with the following eight options. Here, the user is assumed to be a viewer who browses the Web content.

-Option 1: The button 305 corresponds to a notation method in which the annotation target is deleted from the text and the auxiliary information is inserted into the text by using the alternative notation information specified in advance in the HTML document. The alternative notation information makes the auxiliary information distinguishable from other character strings in the text.
Option 2: The button 306 corresponds to a notation method in which auxiliary information is inserted immediately after the annotation target in the text by using the alternative notation information specified in advance in the HTML document. The alternative notation information makes the auxiliary information distinguishable from other character strings in the text.
Option 3: Button 307 corresponds to a notation method in which the annotation target is deleted from the text, auxiliary information is inserted into the text, and parentheses "(", ")" are inserted before and after the supplementary information. By inserting parentheses, the auxiliary information can be distinguished from other character strings in the text.
-Option 4: The button 308 corresponds to a notation method in which auxiliary information is inserted immediately after the annotation target in the text and parentheses "(", ")" are inserted before and after the auxiliary information. By inserting parentheses, the auxiliary information can be distinguished from other character strings in the text.
Option 5: Button 309 corresponds to a notation method in which the annotation target is deleted from the text, the auxiliary information is inserted into the text, and the auxiliary information is underlined. By adding an underline, the auxiliary information can be distinguished from other character strings in the text.
Option 6: The button 310 corresponds to a notation method in which auxiliary information is inserted immediately after the annotation target in the text and the auxiliary information is underlined. By adding an underline, the auxiliary information can be distinguished from other character strings in the text.
Option 7: Button 311 corresponds to a notation method in which the annotation target is deleted from the text, the auxiliary information is inserted into the text, and spaces are inserted before and after the supplementary information. By inserting a space, the auxiliary information can be distinguished from other character strings in the text.
Option 8: Button 312 corresponds to a notation method that does not convert the HTML document, that is, displays auxiliary information between lines as before.

However, the above eight options are examples, and the options are not limited to these. Only a part of the above eight may be adopted, and another option may be added. For example, in the HTML document, when the <ruby> element including the <rp> element which is the alternative notation information does not exist, the option 1 and the option 2 related to the <rp> element may be excluded from the options. In that case, in the window 301, the buttons 305 and 306 may be hidden or grayed out to indicate that they are inoperable. In addition, an HTML document in which a <ruby> element including a <rp> element and a <ruby> element not included may be acquired may be acquired. When option 1 or option 2 can be selected for such a document, the <ruby> element that does not include the <rp> element is converted according to the predetermined option among the other options. You may.

Next, with reference to FIGS. 4 to 6, an example of the HTML document converted by the conversion unit 114 according to the options 1 to 7 and the drawing result thereof will be described. In each case, the case where the HTML document 201 of FIG. 2 is converted is illustrated.

<Conversion process corresponding to option 1>
FIG. 4A illustrates the HTML document conversion result and the drawing result executed when the button 305 is operated (when option 1 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 deletes the annotation target from the description of the HTML document, and then embeds the auxiliary information and the alternative notation information specified in the <rp> element in the text. The HTML document 401 is an HTML document conversion result according to option 1. The annotation target that appears immediately after the <ruby> element, <rp> element, <rt> element, and <ruby> element is deleted from the HTML document 201, and the HTML document is converted so that alternative notation information remains. By this conversion, the drawing result 402 is such that the alternative notation information and the auxiliary information are displayed at the position of the annotation target information.

<Conversion process corresponding to option 2>
FIG. 4B illustrates the HTML document conversion result and the drawing result executed when the button 306 is operated (when option 2 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 embeds the alternative notation information specified in the <rp> element after the annotation target in the text in the description of the HTML document. The HTML document 403 is the HTML document conversion result when the option 2 is selected. The <ruby> element, <rp> element, and <rt> element are deleted from the HTML document 201, and the HTML document is converted so that the alternative notation information remains. This conversion results in a drawing result 404 that displays alternative notation information and auxiliary information following the annotation target.

<Conversion process corresponding to option 3>
FIG. 5A illustrates the HTML document conversion result and the drawing result executed when the button 307 is operated (when option 3 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 deletes the annotation target from the description of the HTML document, and then embeds the auxiliary information and the parentheses "(", ")" in the text. The HTML document 501 is the conversion result of the HTML document when option 3 is selected. From the HTML document 201, the <ruby> element, the <rp> element, the <rt> element, the alternative notation information specified by the <rp> element, and the annotation target appearing immediately after the <ruby> element have been deleted. In addition, parentheses are inserted before and after the auxiliary information. By this conversion, auxiliary information enclosed in parentheses is displayed at the position to be annotated as in the drawing result 602.

<Conversion process corresponding to option 4>
FIG. 5B illustrates the HTML document conversion result and the drawing result executed when the button 308 is operated (when option 3 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 embeds auxiliary information and parentheses "(", ")" in the text after the annotation target in the text in the description of the HTML document. The HTML document 503 is the conversion result of the HTML document when the option 4 is selected. The alternative notation information specified by the <ruby> element, the <rp> element, the <rt> element, and the <rp> element has been deleted from the HTML document 201. In addition, parentheses are inserted before and after the auxiliary information. By this conversion, auxiliary information enclosed in parentheses is displayed following the annotation target as in the drawing result 604.

<Conversion process corresponding to option 5>
FIG. 6A illustrates the HTML document conversion result and the drawing result executed when the button 309 is operated (when option 5 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 deletes the annotation target from the description of the HTML document, embeds the auxiliary information in the text, and further adds an underlined decoration to the auxiliary information. The HTML document 601 is the conversion result of the HTML document when the option 5 is selected. The alternative notation information specified by the <ruby> element, the <rp> element, the <rt> element, and the <rp> element, and the annotation target appearing immediately after the <ruby> element have been deleted from the HTML document 201. Furthermore, a <u> element that specifies the underlined notation is inserted so as to surround the auxiliary information. By this conversion, the underlined auxiliary information is displayed in place of the annotation target, as in the drawing result 602.

<Conversion process corresponding to option 6>
FIG. 6B illustrates the HTML document conversion result and the drawing result executed when the button 310 is operated (when option 6 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 embeds auxiliary information after the annotation target in the text in the description of the HTML document, and further adds an underlined decoration to the auxiliary information. The HTML document 603 is the conversion result of the HTML document when the option 6 is selected. The alternative notation information specified by the <ruby> element, the <rp> element, the <rt> element, and the <rp> element has been deleted from the HTML document 201. Furthermore, an insert <u> element that specifies the underlined notation is inserted so as to surround the auxiliary information. By this conversion, the underlined auxiliary information is displayed following the annotation target as in the drawing result 604. In Options 5 and 6, the example of decorating the characters with underline is given, but the option to convert the HTML document so that it is written with other decorations such as bold, italic change, change of character color, etc. is not limited to underline. May be provided.

<Conversion process corresponding to option 7>
FIG. 6C illustrates the HTML document conversion result and the drawing result executed when the button 311 is operated (when option 7 is selected) in the dialog 303 of FIG. In this case, the conversion unit 114 deletes the annotation target from the description of the HTML document, and then embeds the auxiliary information and the space in the text. The HTML document 605 is the conversion result of the HTML document when the option 7 is selected. The alternative notation information specified by the <ruby> element, the <rp> element, the <rt> element, and the <rp> element, and the annotation target appearing immediately after the <ruby> element have been deleted from the HTML document 201. In addition, spaces are inserted before and after the auxiliary information.

However, if the <ruby> element is at the beginning of the line, it is inserted only after the auxiliary information, and if it is at the end of the sentence, it is inserted only before the auxiliary information. In addition, when <ruby> elements are continuous, unnecessary spaces are prevented from being inserted by not inserting duplicate spaces. For example, since it can be determined that "clothing" is located at the beginning of a sentence by a line break of <br>, a space is inserted only after the auxiliary information. If there is no text after "Mt. Amanoka", it is judged to be the end of the sentence, and a space is inserted only before the auxiliary information. By this conversion, auxiliary information surrounded by a space is displayed at the position to be annotated as in the drawing result 606.

When option 8 is selected, the HTML document described in FIG. 2 and the drawing result are maintained.

Next, using the flowchart shown in FIG. 7, the main flow of the processing executed by the information processing apparatus 100 in the present embodiment will be described. Hereinafter, each process (step) of the flowchart will be described by adding S at the beginning of the reference numerals. In the present embodiment, when the location of the Web content (HTML document) to be displayed is specified in the browser, the processing of the flowchart of FIG. 7 is started.

In S701, the acquisition unit 111 acquires the HTML document. In the present embodiment, when the location of the document is specified by the URL in the location field 302 of FIG. 3, the destination specified by the URL is accessed to acquire the HTML document. If it is specified in the http scheme, the URL specified is accessed via the communication device 108, and if it is specified in the file scheme, the specified file is accessed and acquired. In S702, the determination unit 112 determines whether the HTML document contains annotation information. In the case of the present embodiment, it is determined whether the description of the HTML document includes a <ruby> element which is an annotation element. For example, an HTML parser that parses HTML is used to determine if it contains a <ruby> element. If it is determined that the annotation information is included (S702-YES), the process proceeds to S703. If it is determined that the annotation information is not included (S702-NO), the process proceeds to S706.

In S703, the display control unit 115 draws a GUI screen including a plurality of options and displays it on the display device 103 in order to allow the user to select the notation method of the annotation information. In the case of this embodiment, the dialog 303 of FIG. 3 is popped up. In S704, the selection unit 113 acquires the selection result of the notation method input to the user. In the present embodiment, in the dialog 303 of FIG. 3, it is determined which button is pressed and the selected option is specified. The information of the specified option is held in the RAM 107. In S705, the conversion unit 114 converts the HTML document by the notation method according to the options specified in S704. Details of the HTML document conversion process executed in S705 will be described later. In S706, the HTML document is drawn by the display control unit 115 and displayed on the display device 103. The HTML document displayed when proceeding from S702 to S706 is the document acquired in S701. When proceeding from S705 to S706, it is a document corresponding to the option selected in S704.

In the flowchart of FIG. 9 described above, each time an HTML document including annotation information is acquired, a GUI including a plurality of options is presented to the user and a selection is requested each time, but the present embodiment is limited to this format. Not done. For example, as one of the setting items of the browser, for example, at the time of initial use, a GUI including a plurality of options may be presented to the user and the selection result by the user may be retained. Further, any of options 1 to 8 may be specified in advance as an initial setting, and the information may be retained. In such a case, when the HTML document including the annotation information is acquired, the presentation of GUI (S703) is omitted, the notation method is specified by acquiring the retained selection result (S704), and the conversion is performed. (S705).

FIG. 8 is a flowchart showing the flow of the HTML document conversion process performed by the conversion unit 114 in S705. In S801, the conversion unit 114 performs parsing processing of the HTML document. For example, a DOM tree is generated by a parsing tool using an HTML document as input. In S802, the conversion unit 114 extracts all <ruby> elements of the HTML document. For example, all the <ruby> element nodes in the DOM tree generated in S801 are acquired. In the case of HTML document 201, the <ruby> elements related to the annotation targets "coming", "white mystery", "clothing", "heaven", and "Mt. Amanoka" are extracted.

In S803, the conversion unit 114 determines whether there is an unprocessed <ruby> element in the HTML document. If it is not determined to be an unprocessed <ruby> element (S803-NO), the conversion process is terminated. If it is determined that there is an unprocessed <ruby> element (S803-YES), the process proceeds to S804. In S804, the conversion unit 114 determines one of the unprocessed <ruby> elements as the processing target. For example, select the <ruby> element that appears earliest in an HTML document. In the case of HTML document 201, the processing target is sequentially from the annotation target "coming".

In S805, the conversion unit 114 extracts one information unit that depends on the <ruby> element to be processed. Here, the information unit is one or more character sets belonging to the <ruby> element, or an element surrounded by the elements, and specifically, each of the child nodes belonging to the <ruby> element node to be processed. is there.

In S806, the conversion unit 114 determines whether the extracted information unit is an annotation target. If it is determined that the annotation is to be made (S806-YES), the process proceeds to S807. If it is not determined to be an annotation target (S806-NO), the process proceeds to S808. In the present embodiment, if the child node of the extracted <ruby> element node is a text node, it is determined that it is an annotation target. In S807, the conversion unit 114 executes processing for the annotation target according to the notation method (option) selected in S704. Details of the processing according to each selection will be described later.

In S808, the conversion unit 114 determines whether the extracted information unit is a <rp> element. If it is determined to be a <rp> element (S808-YES), the process proceeds to S809. If it is not determined to be a <rp> element (S808-NO), the process proceeds to S810. In S809, the conversion unit 114 executes processing for the <rp> element according to the notation method (option) selected in S704. Details of the processing according to each selection will be described later.

In S810, the conversion unit 114 determines whether the extracted information unit is a <rt> element. If it is determined that the element is <rt> (S810-YES), the process proceeds to S811. If it is not determined to be a <rt> element (S810-NO), the process proceeds to S812. In S811, the conversion unit 114 executes processing for the <rt> element according to the notation method (option) selected in S704. Details of the processing according to each selection will be described later.

In S812, it is determined whether or not there is an unprocessed information unit under the <ruby> element to be processed. If it is determined that there is an unprocessed information unit (S812-YES), the process proceeds to S805. In the present embodiment, if there is an unprocessed child node under the target <ruby> element node, the process proceeds to S805. If it is not determined that there is an unprocessed information unit (S812-NO), the process proceeds to S813. In S813, the conversion unit 114 deletes the <ruby> element to be processed, and proceeds to S803. In this embodiment, the target <ruby> element node is deleted as an operation on the DOM tree. In the step leading to this process, the child node of the <ruby> element node is in a state of being deleted or replaced with the parent node. By replacing the information with the parent node, it is possible to display the annotation target, alternative notation information, and auxiliary information in a state that reflects the higher-level document information, that is, the same document expression as the parent node. As a result, the notation is such that auxiliary information is embedded in the sentence. Here, the document representation is setting information applied when displaying characters, and includes font size, character color, font, and other decorations.

By the process described above, the HTML document including the annotation information is converted into the notation method selected by the user input. It is also possible to create a file by writing out the serialized text of the converted DOM tree. Next, when each option is selected, specific processing executed in S807, S809, and S811 in the flowchart of FIG. 8 will be described. However, examples of duplicate specific processing methods will be omitted as appropriate.

<When option 1 is selected>
In S807, the conversion unit 114 deletes the annotation target from the HHTML document. In this embodiment, as an operation on the DOM tree, the text node to be annotated is deleted. In S809, the conversion unit 114 leaves the alternative notation information in the <rp> element and deletes the <rp> element from the description in the HTML document. In the present embodiment, as an operation on the DOM tree, a text node indicating alternative notation information which is a child node of the <rp> element node is replaced with a parent node of the <ruby> element node. At that time, a text node is placed at a position following the <ruby> element node. After arranging, delete the <rp> element node.

In S811, the conversion unit 114 leaves the auxiliary information in the <rt> element and deletes the <rt> element. In the present embodiment, as an operation on the DOM tree, a text node indicating auxiliary information that is a child node of the <rt> element node is replaced with a parent element of the <ruby> element node. At that time, the node is arranged at the position based on the position where the text node of the alternative notation information is replaced in S809. After arranging, delete the <rt> element node.

For example, when the processing target is a <ruby> element annotating the "heaven" of the HTML document 201, the text node indicating the "heaven" to be annotated is deleted in S807. In S809, it is replaced with the parent node of the text node <ruby> element node indicating "[", "]" which is the alternative notation information. In S811, the text node indicating "Ama", which is auxiliary information, is replaced with the parent node of the <ruby> element node. The position to be replaced is between the text nodes indicating the alternative notation information "[" and "]".

<When option 2 is selected>
In S807, the conversion unit 114 leaves an annotation target. In the present embodiment, as an operation on the DOM tree, the text node to be annotated is replaced with the parent node of the <ruby> element node. At that time, a text node is placed at a position following the <ruby> element node.

The processing in S809 and S811 is the same as in the case of option 1. That is, the text node indicating the alternative notation information and the text node indicating the auxiliary information are replaced with the parent node.

For example, when the processing target is a <ruby> element annotating the "heaven" of the HTML document 201, in S807, the text node indicating the "heaven" to be annotated is replaced with the parent node. In S809, it is replaced after "heaven" among the parent nodes of the text node <ruby> element node indicating "[", "]" which is the alternative notation information. In S811, the text node indicating "Ama", which is auxiliary information, is replaced with the parent node of the <ruby> element node. The position to be replaced is between the text nodes indicating the alternative notation information "[" and "]".

<When option 3 is selected>
When option 3 is selected in S704, the processing in S807 is the same as in the case of option 1. That is, the text node to be annotated is deleted. In S809, the conversion unit 114 deletes the <rp> element node from the description in the HTML document. In the present embodiment, as an operation on the DOM tree, the entire <rp> element node is deleted while the text node indicating the alternative notation information is subordinated.

In S811, the conversion unit 114 inserts parentheses before and after the auxiliary information and deletes the <rt> element. In the present embodiment, as an operation on the DOM tree, a text node indicating auxiliary information that is a child node of the <rt> element node is replaced with a parent element of the <ruby> element node. At that time, text nodes indicating "(" and ")" are added before and after the text node indicating auxiliary information, respectively. Furthermore, the <rt> element node is deleted.

For example, when the processing target is a <ruby> element that annotates the "heaven" of the HTML document 201, the text node indicating the "heaven" to be annotated is deleted in S807, and the <rp> is deleted in S809. The element node is deleted. In S811, the text node indicating "Ama", which is auxiliary information, and the text node indicating "(", ")" are replaced with the parent node of the <ruby> element node in the order of "(Ama)".

<When option 4 is selected>
When option 4 is selected in S704, the processing in S807 is the same as in the case of option 2. That is, the text node to be annotated is replaced with the parent node. Further, the processing in S809 and S811 is the same as in the case of option 3. That is, the <rp> element node is deleted, and the text node indicating the auxiliary information and the text node indicating "(", ")" are replaced with the parent elements of the <ruby> element node.

For example, when the processing target is a <ruby> element annotating the "heaven" of the HTML document 201, in S807, the text node indicating the "heaven" to be annotated is replaced with the parent node. In S809, the <rp> element node is deleted. In S811, the text node indicating "Ama", which is auxiliary information, and the text node indicating "(", ")" are "(Ama)" after "Heaven" among the parent nodes of the <ruby> element node. It is replaced in the order of.

<When option 5 is selected>
When option 5 is selected in S704, the processing in S807 and S809 is the same as in the case of option 3. That is, the text node to be annotated and the <rp> element node are deleted. In S811, the conversion unit 114 underlines the auxiliary information and deletes the <rt> element. In the present embodiment, as an operation on the DOM tree, a <u> element node indicating the underline decoration for the character string is generated, and a text node indicating auxiliary information is used as a child node. Then, the <u> element node is replaced as a child node with respect to the parent element of the <ruby> element node, and the <rt> element node is deleted.

For example, when the processing target is a <ruby> element that annotates the "heaven" of the HTML document 201, the text node indicating the "heaven" to be annotated is deleted in S807, and the <rp> is deleted in S809. The element node is deleted. In S811, a <u> element node having "Ama", which is auxiliary information, as a child node is generated, and is replaced with a parent node of the <ruby> element node.

<When option 6 is selected>
When option 6 is selected in S704, the processing in S807 is the same as in the case of option 4. That is, the text node to be annotated is replaced with the parent node. Further, the processing in S809 and S811 is the same as in the case of option 5. That is, the <rp> element node is deleted, and the text node indicating the auxiliary information and the <u> element node having the text node of the auxiliary information as a child node are replaced with the parent element of the <ruby> element node.

For example, when the processing target is a <ruby> element annotating the "heaven" of the HTML document 201, in S807, the text node indicating the "heaven" to be annotated is replaced with the parent node. In S809, the <rp> element node is deleted. In S811, a <u> element node having "Ama", which is auxiliary information, as a child node is generated, and is replaced after "heaven" among the parent nodes of the <ruby> element node.

<When option 7 is selected>
When option 7 is selected in S704, the processing in S807 and S809 is the same as in the case of option 3. That is, the text node to be annotated and the <rp> element node are deleted. In S811, the conversion unit 114 inserts a space before and after the auxiliary information and deletes the <rt> element. In the present embodiment, as an operation on the DOM tree, a text node indicating auxiliary information that is a child node of the <rt> element node is replaced with a parent element of the <ruby> element node. Then, add a text node indicating a space before and after the text node indicating auxiliary information. At that time, following the position where the node is replaced in S809, the text node is arranged in the order of space, auxiliary information, and space. After arranging, delete the <rt> element node. However, if the target <ruby> element is at the beginning of a line or at the end of a sentence, spaces are inserted only after and before the auxiliary information, respectively. Whether it is the beginning of a line or the end of a sentence is determined based on the element following the target <ruby> element or the parent element. For example, if the <br> element indicating a line break is before the <ruby> element, it is determined to be the beginning of the sentence, and if it is after it, it is determined to be the end of the sentence.

For example, when the processing target is a <ruby> element that annotates the "heaven" of the HTML document 201, the text node indicating the "heaven" to be annotated is deleted in S807, and the <rp> is deleted in S809. The element node is deleted. In S811, the parent node of the <ruby> element node is replaced with a text node indicating "Ama" which is auxiliary information, and a text node indicating a space is replaced before and after "Ama".

<When option 8 is selected>
When option 7 is selected in S704, no conversion is performed in any of S807, S809, and S811, and the process proceeds to the next step. As a result, in S706, the drawing result 202 is displayed.

The processing executed in the present embodiment has been described above in the flow charts of FIGS. 9 and 8. This process embeds auxiliary information in the body rather than between the lines. Since the characters representing the auxiliary information are displayed in a font size larger than that displayed between the lines, the readability of the auxiliary information itself can be improved. Further, according to the present embodiment, the user can select the notation method of the auxiliary information embedded in the text. Therefore, it is possible to use a notation method that is easy for individual users to read. Further, since it is possible to select whether to exclude the characters to be annotated from the text, if the size of the display area is not sufficient, the display efficiency can be improved by not displaying the annotation target.

As a modification, a notation method not included in the above-mentioned options 1 to 8 may be added to the options. For example, after adjusting the font size of the auxiliary information to be larger than when it is displayed between lines and smaller than the characters belonging to the text, the auxiliary information is also larger than when it is displayed between the lines depending on the notation method embedded in the text. It is possible to improve the readability of. In this case, the drawing width required to draw the entire character string can be smaller than when the font size of the text is applied to the auxiliary information.

Specifically, for example, in S811 of FIG. 8, the drawing width when the annotation target is laid out and drawn by the conversion unit 114, and the drawing width when the auxiliary information is laid out and drawn instead of the annotation target. Is calculated. If the drawing width when laying out the auxiliary information exceeds the drawing width when laying out the annotation target, adjust the font size of the auxiliary information to a smaller size. The font size is determined so that the font size is larger than the font size when the auxiliary information is displayed between the lines, and the drawing width when laying out the auxiliary information is close to the drawing width when laying out the annotation target. To. After determining the font size, create a <font> element node whose child node is a text node that represents auxiliary information, and specify the font size in the attribute node. Make the node of the <font> element a child node with respect to the parent node of the <ruby> element node. For example, the annotation target "Amanoka" has 3 characters, and its auxiliary information "Kaguyama" has 4 characters. If "Amanoka" is replaced with "Kaguyama", a larger drawing width will be required. .. By setting "Kaguyama" to a font size that does not exceed the drawing width of "Mt. Amanoka", it is possible to prevent the drawing width from becoming wide. Depending on the text, line breaks may occur when the drawing width is widened, but by selecting this notation method, the drawing width is not widened, so the list of information can be maintained.

Further, in the description of the first embodiment, all the <ruby> elements in the HTML document are converted to a specific notation method, but the <ruby> element whose notation is changed according to the content of the annotation target is selected. It may be deformed. For example, in the dialog 303 that allows the user to select the notation method, the annotation target is set to "all" in advance, but the user may be allowed to select the annotation target to be converted. For example, it is possible to convert only complicated kanji based on a predetermined standard, or to convert kanji learned in a certain grade or higher.

FIG. 9 shows an example of the GUI screen of the browser that displays the HTML document of the browser. Elements common to FIG. 3 are numbered the same. The difference between the window 901 and the window 301 of FIG. 3 is that the user can select the annotation target to be converted in the dialog 303. In the annotation target selection operation unit 902, the annotation target can be selected from "all", "complex characters", and "by grade of acquisition". "By grade of acquisition" is a pull-down type operation part, and the kanji to be acquired in each grade defined in advance can be specified as an annotation target.

When "complex characters" are selected, the kanji glyphs are classified according to the complexity, and the annotation information including the complicated kanji is converted. The calculation of the complexity of the glyph is determined to be complicated when, for example, one Chinese character is regarded as a rectangular image and the number of pixels to be drawn as the Chinese character is a ratio of a certain threshold or more among all the pixels of the image. In this case, "heaven", which expresses characters with a small number of pixels, is not complicated, and "incense", which requires a large number of pixels, is classified as a highly complex kanji, and "Kouguyama" including "incense" is converted into notation. I do.

If "By grade of acquisition" is specified, the kanji will be classified using the Kanji distribution table for each grade, which summarizes the kanji learned by elementary school students in advance for each grade. For example, when the user selects "4th grade or higher", it is determined that the notation conversion is performed if the annotation target includes the kanji learned in the 4th grade or higher. The notation of "heaven" learned in the first grade of elementary school is not converted, but the notation of "Mt. Amanoka" including the "tool" learned in the fourth grade of elementary school and above is converted. By making the annotation target selectable by the user as described above, it is possible to describe the annotation suitable for the user's age and preference.

As another modification, even when the <ruby> element exists in the HTML document, it may be switched whether to convert the display of the auxiliary information based on the size of the drawing area required for the drawing result. .. Specifically, if the drawing result when the HTML document is converted requires a drawing area larger than the drawing result when the HTML document is not converted, the conversion result may not be output. The conversion unit 114 performs conversion processing while retaining the information of the HTML document before conversion, compares the drawing areas before and after conversion, discards the conversion result when conversion is no longer necessary, and discards the original HTML. Keep the document. Such deformation may be particularly effective in a small device or the like in which the size of the display area for displaying the drawing result is small.

For example, FIG. 10 shows the difference in the drawing area of drawing when a certain HTML document is not converted into notation and when the notation is converted. This is an example of drawing an HTML document configured to display phonetic spelling in each kanji. The drawing result 1001 shows the drawing result when the HTML document is not converted into notation. The drawing result 1002 is a drawing result when converted by the notation method according to the option 4. When each notation is laid out and the heights of the drawing areas are compared, the drawing area in the height direction is required when the notation conversion is performed as compared with the case where the notation is not converted. On a device having a small screen, the display efficiency may be lowered and the time and effort for scrolling the Web content may be increased.

Therefore, in the modified example, it is finally determined that the HTML document is not converted based on the comparison between the size of the display area provided in the device and the height of the drawing area of the HTML document before and after the conversion process of the flowchart of FIG. The process may be added to the flowchart of FIG. The process of calculating the height of the drawing area of the HTML document can be calculated by using the document layout function originally possessed by this browser. Further, this modification may be turned ON / OFF by user setting. The user selects OFF when he / she wants to prioritize readability improvement of auxiliary information, and ON when he / she wants to prioritize display efficiency. By being able to select OFF, it is possible to avoid a situation in which the user feels uncomfortable in a situation where conversion is not performed even though the notation method is selected in S704.

Further, the auxiliary information conversion process described in the first embodiment may be one function of the browser. That is, regardless of the size of the display area of one device, whether or not the conversion process can be executed may be provided as a setting item so that switching may be possible. When the conversion process is not executed, it is possible to prioritize viewing the document with an appearance in line with the intention of the Web content designer. When executing the conversion process, it is possible to provide a highly flexible Web content browsing environment in consideration of the age, nationality, etc. of the user. Further, when the conversion process is not executed, it is possible to give priority to viewing the document with an appearance in line with the intention of the designer of the Web content.

<Other Embodiments>
The present invention supplies a program that realizes one or more functions of the above-described embodiment to a system or device via a network or storage medium, and one or more processors in the computer of the system or device reads and executes the program. It can also be realized by the processing to be performed. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

111 Acquisition unit 112 Judgment unit 113 Selection unit 114 Conversion unit 115 Display control unit

Claims (18)

How to get a structured document and
A determination means for determining whether or not the description of the structured document includes predetermined annotation information, and
When the determination means determines that there is annotation information, a conversion means for converting the description of the structured document so that the auxiliary information included in the annotation information is embedded in the body of the structured document.
A display control means for displaying the structured document on the display device according to the description of the converted structured document, and
An information processing device characterized by having. The first aspect of claim 1, wherein the auxiliary information is arranged at a position in the description of the structured document in which the same document expression as the information higher than the annotation information is reflected by the conversion by the conversion means. Information processing equipment. The information processing apparatus according to claim 2, wherein the document expression includes a font size. When the determination means determines that the annotation information is present, the conversion means further includes a selection means for selecting a notation method from a plurality of notation methods of the auxiliary information based on the user input, and the conversion means said the selection. The information processing apparatus according to any one of claims 1 to 3, wherein the conversion process according to the notation method selected by the means is executed. The user input is an input of an operation for designating one option from a plurality of options corresponding to a plurality of notation methods of the auxiliary information displayed on the display device by the display control means. The information processing device according to claim 4. The plurality of notation methods of the auxiliary information include a method of notating the auxiliary information so as to be distinguishable from other character strings in the text by using the alternative notation information included in the annotation information. The information processing apparatus according to claim 4 or 5. A plurality of notation methods of the auxiliary information include a method of notating the auxiliary information so as to be distinguishable from other character strings in the main text by inserting parentheses together with the auxiliary information in the main text. Item 6. The information processing apparatus according to any one of Items 4 to 6. The plurality of notation methods of the auxiliary information include a method of notating the auxiliary information inserted in the text so as to be distinguishable from other character strings in the text by adding a predetermined decoration. The information processing apparatus according to any one of claims 4 to 7. A plurality of notation methods of the auxiliary information include a method of notating the auxiliary information so as to be distinguishable from other character strings in the main text by inserting a space together with the auxiliary information in the main text. Item 2. The information processing apparatus according to any one of Items 4 to 8. The plurality of notation methods of the auxiliary information include a notation method in which the annotation target to be annotated by the auxiliary information is deleted from the main text of the structured document and then the auxiliary information is embedded in the main text, and the annotation target is included. The information processing apparatus according to any one of claims 4 to 9, further comprising a notation method in which the auxiliary information is embedded in the text after being left in the text of the structured document. The auxiliary information is a character string written in ruby.
The conversion means according to claim 1 to 10, further comprising adjusting the font size of the auxiliary information to be embedded in the text to be larger than that displayed between lines and smaller than the characters belonging to the text. The information processing apparatus according to any one of the following items. The conversion means calculates the complexity of characters, and when the calculated complexity of the annotation target annotated by the auxiliary information includes characters equal to or greater than a predetermined threshold value, the structure is such that the auxiliary information is embedded in the text. The information processing apparatus according to any one of claims 1 to 11, wherein the converted document is converted. The conversion means classifies the characters to be annotated by the auxiliary information based on a predetermined character classification table, and when the characters belonging to the designated classification are included in the annotation target, the auxiliary information is added. The information processing apparatus according to any one of claims 1 to 12, wherein the structured document is converted so as to be embedded in a text. When the size of the area required to draw the structured document converted by the conversion means is larger than the size of the area required to draw the structured document before being converted by the conversion means. The information processing apparatus according to any one of claims 1 to 13, wherein the structured document converted by the conversion means is not displayed by the display control means. The information processing apparatus according to any one of claims 1 to 14, wherein the structured document is an HTML document, and the annotation information is a <ruby> element. It is a control method for information processing equipment.
Acquisition process to acquire structured documents by acquisition means,
A determination step of determining whether the description of the structured document includes predetermined annotation information by the determination means, and
When it is determined that there is annotation information in the determination step, a conversion step of converting the description of the structured document so that the auxiliary information included in the annotation information is embedded in the body of the structured document by the conversion means.
A display control step of displaying the structured document on the display device according to the description of the converted structured document by the display control means.
A method for controlling an information processing device, which comprises. A program that causes the computer to function as the information processing device according to any one of claims 1 to 15 by being read by a computer and executed. A computer-readable storage medium comprising storing the program according to claim 17.

Images