JP2008257354A - Electronic device, method for creating web page, and program for creating web page - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an electronic device capable of properly maintaining the performance of response to requests about Web pages in making the Web pages compatible with multiple languages. <P>SOLUTION: The electronic device has a translation means for creating translated XSL data by using a storage device that records display character strings for a plurality of identifiers for each language, and replacing the identifiers included in XSL data by the display character strings; an information processing means for implementing information processing according to a Web page request received via a network, and outputting the information processing result as XML data; and an XSLT conversion means for creating HTML data by applying the translated XSL data to the XML data, and performing XSLT conversion. When the display character strings corresponding to the identifiers included in the XSL data are detected from the storage device, the translation means ends a search for the display character strings about the identifies. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an electronic device, a Web page generation method, and a Web page generation program, and more particularly to an electronic device, a Web page generation method, and a Web page generation program that generate a multilingual Web page.

  In recent years, Web pages that are display data for providing various types of information on the Internet have been found to provide designs and information display formats to users. A prominent example of displaying the same information in different display formats is display in different languages. In other words, users using Web pages do not always use the same language. One user will request display in Japanese, and another user will request display in English, French, etc.

  On the other hand, in an embedded device such as an image processing apparatus, the device status, stored document information, spooled jobs, address books used for FAX, e-mail, etc. are connected via a network. There are some which are provided by a web page in a terminal or the like. As an advantage of providing such information by a Web page, if there is a general-purpose Web browser on the terminal side, special software may not be installed, it does not depend on the platform on the terminal side, and is not on the device side. However, information can be confirmed at a remote location. Even in a Web page provided by such a device, it is desirable that the same information can be displayed in different languages and display formats depending on the user, as in a general Web server.

For example, Patent Document 1 includes an XSLT (XML Stylesheet Language Transformations) processor, and the XSLT processor outputs format data (XSL (eXtensible Stylesheet) for XML (eXtensible Markup Language) data output as a processing result of a Web application. An image processing apparatus that generates HTML data (Web page) by executing XSLT conversion by applying (Language) data) is described. In the image processing apparatus, the format data is created so that it can be used in common for each language. That is, parts that differ for each language are described by identifiers (key character strings). A display character string corresponding to the key character string is defined for each language in XML data called a language table. When generating a Web page in the image forming apparatus, the XSLT processor uses the language table corresponding to the display language to execute the XSLT conversion based on the format data, so that the key character string is replaced by the display language. HTML data is generated.
JP-A-2005-32230

  However, the XSLT processor is configured to extract all data that matches a pattern when searching for XML data. Therefore, in the image processing apparatus according to Patent Literature 1, when the XSLT processor searches the language table for a display character string corresponding to the key character string, scanning of the language table is continued even after the display character string is detected. The

  FIG. 1 is a diagram for explaining a search process for a language table by an XSLT processor. In the language table of FIG. 1, a genext element is described for each display character string. The value of the key attribute of the gentext element indicates a key character string, and the value of the text attribute indicates a display character string.

  In the figure, arrows a1 and a2 indicate the scanning process by the XSLT processor when searching the display character string for the key character string “ATALK”. That is, even if the XSLT processor performs the scan indicated by the arrow a1 and detects “ATALK”, the XSLT processor continues the scan indicated by the arrow a2 thereafter. Therefore, in this case, unnecessary search time is required for the scanning indicated by the arrow a2.

  The search for the language table is executed when a Web page is generated, that is, after a Web page is requested from a client and before the Web page is returned. Therefore, the search performance for the language table greatly affects the performance of the response to the Web page request from the client. However, if the translation is performed by the XLST processor as described above, the response may be deteriorated.

  The present invention has been made in view of the above points, and in realizing multilingual support of a Web page, an electronic apparatus, a Web page generation method, and an electronic device that can appropriately maintain the response performance to a Web page request, And providing a Web page generation program.

  In order to solve the above problem, the present invention replaces the identifier included in the XSL data with the display character string using a storage device in which display character strings for a plurality of identifiers are recorded for each language. A translation means for generating translated XSL data, an information processing means for executing information processing in response to a request for a Web page received via a network, and outputting the result of the information processing as XML data; XSLT conversion means for generating HTML data by applying translated XSL data to the XML data and executing XSLT conversion, and the translation means includes a plurality of identifiers recorded from the storage device. When a display character string corresponding to the identifier included in the XSL data is detected, a search for the display character string related to the identifier is performed. Characterized in that it end.

  In such an image processing apparatus, the performance of a response to a request for a Web page can be appropriately maintained when realizing multilingual support of the Web page.

  According to the present invention, it is possible to provide an electronic device, a Web page generation method, and a Web page generation program that can appropriately maintain the performance of response to a Web page request in realizing multilingual support of the Web page. .

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, an image processing apparatus will be described as a specific example of an electronic apparatus and an embedded device. Here, the embedded device is used as a general term. For example, a program that realizes a specific function and a processor that processes the program, such as a telephone, a printer, a television, an air conditioner, and a portable information terminal. General equipment that is pre-installed.

  FIG. 2 is a diagram illustrating a configuration example of the image processing apparatus according to the embodiment of the present invention. 2, the image processing apparatus 10 includes hardware resources for performing individual image processing such as a plotter engine 203 and a scanner engine 204, an engine control board 202, an OS 201, a system management service 106, and a network service 107. A memory management service 108, an operation panel management service 109, an engine management service 110, and various applications such as a copy application 101, a fax application 102, a printer application 103, and an information providing application 104. Software resources such as the various applications are recorded in a storage device (not shown) included in the image processing apparatus 10 and function by being processed by a CPU (not shown) included in the image processing apparatus 10.

  The engine control board 202 controls individual functions of the image processing apparatus 10 such as the plotter engine 203 and the scanner engine 204, and provides the functions of the engine control board 202 to the OS 201 and the like through an engine I / F (interface).

  The OS 201 is an operating system such as UNIX (registered trademark), and executes various software implemented as applications such as the copy application 101 and the fax application 102 in parallel as processes.

  A system management service 106, a network service 107, a memory management service 108, an operation panel management service 109, and an engine management service 110 provide respective functions to a higher-level application such as the copy application 101 through an API (Application Programming Interface). is there. That is, the system management service 106 provides a function related to system management, and the network service 107 provides a function related to network communication. The memory management service 108 provides functions related to memory management, and the operation panel management service 109 provides functions related to an operation panel (operation panel) installed in the image processing apparatus 10. Further, the engine management service 110 provides a function for controlling the plotter engine 203 and the scanner engine 204 via the engine control board 202.

  The copy application 101 is a copy application, and the fax application 102 is a facsimile application. The printer application 103 is a printer application having a page description language (PDL), PCL, and postscript (PS). The information providing application 104 executes a process for generating a Web page that displays information requested from the terminal 20.

  The information providing application 104 will be described in more detail. FIG. 3 is a diagram for explaining a functional configuration example of the information providing application. In FIG. 3, an image processing apparatus 10 includes a terminal 20 and a terminal 30 representing a PC (Personal Computer), a PDA (Personal Digital (Data) Assistants), or a mobile phone, a resource server 50, the Internet, a LAN, or the like. Network 40 (whether wired or wireless).

  In the functional blocks of the image processing apparatus 10 in the figure, Web applications 12 a and 12 b (hereinafter collectively referred to as “Web application 12”), the translation unit 14, and the XSLT processor 15 are functions of the information providing application 104. include.

  On the other hand, the embedded Web server 11 and the embedded Web client 17 are part of the functions of the network service 107.

  The storage area 16 is a storage area configured on the ROM and RAM of the image processing apparatus 10. In the storage area 16, application data 161, untranslated format data 162, image data 164, script data 165, language table position information 166, and the like are stored.

  The application data 161 is data that is referred to when the web application 12 generates a web page, and includes information itself to be posted on the web page, information that is a basis for generating information to be posted on the web page, and the like. It is data.

  The untranslated format data 162 is data in the XSL format in which format information of a Web page is defined, and is stored in the storage area 16 as a file for each Web page. The untranslated format data 162 is described by an identifier for identifying a display character string in a portion whose display format (display character string) differs depending on a language (natural language such as Japanese or English) used for displaying a Web page. Has been.

  The image data 164 is GIF (Graphic Interchange Format) data or the like displayed on the Web page provided to the terminal 20. The script data 165 is data defined by a Java (registered trademark) script or the like, and is included in a Web page provided to the terminal 20.

  The language table position information 166 is information (for example, URL) indicating the storage position of the language table. The language table is XML format data in which a display character string is defined for each language type for information whose display character string is different depending on a language (display language) used for displaying a Web page. The language table 163 is stored in the storage device of the resource server 50.

  The embedded Web server 11 is a daemon program that controls HTTP communication with the terminal 20 or the like, interprets an HTTP request transmitted from the terminal 20 or the like, and calls the Web application 12. The embedded Web server 11 further transmits a Web page, which is HTML data generated in the image processing apparatus 10 in response to the HTTP request, to the terminal 20 or the like. In the present embodiment, the following Web page is used as a specific example.

  FIG. 4 is a diagram illustrating a display example of a Web page generated in the present embodiment. A web page 210 shown in FIG. 4 displays setting information related to the network function in the image processing apparatus 10 in English. A description 2011 indicates that the AppleTalk protocol can be used, and a description 2012 indicates a network number.

  The HTTP request includes information for identifying the display language. That is, it is selected on the terminal 20 or the like by which display language the Web page is displayed.

  The Web application 12 is a program that executes information processing in response to a request from the terminal 20 or the like, and outputs information to be displayed on the Web page as the processing result as XML (eXtensible Markup Language) data. Accordingly, a plurality of instances (Web application 12a, Web application 12b, etc.) are mounted. The XML data generated by the web application 12 is hereinafter referred to as “base data”.

  The translation unit 14 uses the language table 163 to replace (translate) a portion (identifier) having a different display character string according to the display language in the untranslated format data 162 using the language table 163. . The format data output as a result of translation performed on the untranslated format data 162 is referred to as translated format data 167.

  The XSLT processor 15 is a program that executes XSL conversion based on XML data and XSL data, and generates XML data, HTML data, and the like according to the format information of the XSL data. The XSLT processor 15 is commonly used regardless of the types of a plurality of Web applications, and generates HTML data based on the XML data generated by the Web application 12.

  The embedded Web client 17 is a program module for providing a function as a Web client to a function in the image processing apparatus 10. In the present embodiment, the Web client 17 transmits an HTTP request including an acquisition request for the language table 163 to the resource server 50 based on the language table position information 166 in response to a request from the translation unit 14. The language table 163 is acquired from the server 50.

  The resource server 50 is a computer having a function as a Web server, and has a language table 163. The resource server 50 returns an HTTP response including the language table 163 in response to the HTTP request that requests the language table 163.

  Note that the resource server 50 is not necessarily a computer, and may be a device having a function as a Web server, like the image processing apparatus 10. When the resource server 50 is configured by an image processing device, for example, the image processing device 10 may be configured by a low-end model, and the image processing device as the resource server 50 may be configured by a high-end model.

  Further, the language table 163 does not necessarily have to be managed in an external device of the image processing apparatus 10 and may be stored in the storage area 16 of the image processing apparatus 10. In this case, the embedded Web client 17 is not necessary.

  Hereinafter, the processing procedure of the image processing apparatus 10 will be described. First, the translation process of the untranslated format data 162 will be described. FIG. 5 is a sequence diagram for explaining the translation processing of untranslated format data in the first embodiment. The processing in FIG. 5 is executed at least when the image processing apparatus 10 is started up, for example, until the first Web page request is received after the image processing apparatus 10 is started up. That is, the translated form data 167 is not necessarily resident in the storage area 16.

  For example, when the image processing apparatus 10 is activated, the translation unit 14 acquires the untranslated format data 162 from the storage area 16 (S101).

  FIG. 6 is a diagram illustrating a definition example of untranslated format data. In the definition of the untranslated format data 162 in FIG. 6, the description 1621 and the description 1622 correspond to the description 2011 and the description 2012 in FIG. 4, respectively.

  Descriptions 1621a and 1622a are information (identifiers) for identifying character strings displayed as item names in the descriptions 2011 and 2012 in FIG. That is, the display of the item name differs depending on the language, and the untranslated format data 162 is data that is used regardless of the type of the language, and is not an actual display character string (AppleTalk, Network No.) but a display character string. The display information is designated by an identifier for identifying (hereinafter referred to as “key character string”). The key character string is described in a format such as @ [<key character string>] @. Therefore, in the description 1621a and the description 1621b, “ATALK” and “AT_NET_NO” correspond to the key character string. “@ [” And “] @” are symbols indicating the start and end of the key character string (hereinafter referred to as “key character string identification symbols”).

  Subsequently, the translation unit 14 acquires the language table 163 via the embedded Web client 17 (S102).

  FIG. 7 is a diagram illustrating a definition example of the English language language table. In the language table 163 of FIG. 7, a genext element is described for each display character string. The value of the key attribute of the gentext element indicates a key character string, and the value of the text attribute indicates a display character string. For example, the description 1631 defines that the display character string corresponding to the key character string ATALK is “AppleTalk”. The description 1632 defines that the display character string corresponding to the key character string AT_NET_NO is “Network No.”. FIG. 7 shows the English language table 163, but in other language tables 163, display character strings are defined in different languages for the same key character string.

  Subsequently, the translation unit 14 translates the key character string in the untranslated format data 162 using the language table 163 of each language, and generates translated format data 167 for each language (S103).

  FIG. 8 is a diagram illustrating an example of definition of translated English format data. The description content of the translated format data 167 shown in FIG. 8 is the same as the untranslated format data 162 shown in FIG. 6 except for the translated part. The descriptions 1671 and 1672 in FIG. This corresponds to the description 1621 and the description 1622.

  In FIG. 8, the description 1671a and the description 1672a correspond to the translated portions. That is, the description 1671a is replaced with “AppleTalk” defined as a display character string for the key character string “ATALK” in the English language table 163. Also, the description 1671b is replaced with “Network No.” defined as a display character string for the key character string “AT_NET_NO” in the English language table 163.

  For other languages, translated format data 167 is generated for each language based on the same untranslated format data 162.

  Here, what is translated is a portion (a static portion) where the display content does not change according to the processing result of the Web application 12a, such as the item name displayed on the Web page 210.

  Subsequently, the translation unit 14 stores the generated translated format data 167 in the storage area 16 (on the RAM) (S104).

  Next, processing when the image processing apparatus 10 generates a Web page in response to a request from the terminal 20 will be described. FIG. 9 is a sequence diagram for explaining Web page generation processing in the first embodiment.

  When the user of the terminal 20 inputs the URL of the image processing apparatus 10 in the Web browser 21 of the terminal 20 to refer to the predetermined information of the image processing apparatus 10, the Web browser 21 A request is made to provide a Web page that displays predetermined information (HTTP request) (S111).

  The embedded Web server 11 that has received the HTTP request calls the Web application 12 corresponding to the HTTP request (S112). The web application 12 executes predetermined processing with reference to the application data 161 and the like, and generates XML data (base data) having information to be displayed on the web page based on the processing result (S113). In the present embodiment, the Web application 12 acquires setting information related to the network function of the image processing apparatus 10 and outputs it as base data.

  FIG. 10 is a diagram illustrating a definition example of base data. In the base data 121 of FIG. 10, the character string “en” enclosed in the urlLang tag in the description 1211 is information for identifying the display language requested from the terminal 20 or the like, and is specified in the HTTP request. Output according to the display language. In the present embodiment, “en” is a character string indicating English. Therefore, the description 1211 specifies that an English version Web page is requested.

  The description 1212 and the description 1213 relate to information displayed on the Web page 210. That is, the character string “true” enclosed in the appleTalk tag in the description 1212 is a value indicating whether or not the AppleTalk protocol can be used in the image processing apparatus 10, and the character string “1234” enclosed in the networkNo tag in the description 1213 is , A value indicating a network number.

  Subsequently, the Web application 12 requests the XSLT processor 15 to generate HTML data for displaying the information included in the base data 121 as the Web page 210 (S114). The XSLT processor 15 executes XSLT conversion based on the translated format data 167 corresponding to the Web page in the language requested in the HTTP request and the base data 121, and generates HTML data (S115).

  FIG. 11 is a diagram illustrating a definition example of English version HTML data generated by the XSLT processor. In the definition example of the HTML data 220 in FIG. 11, a description 221 and a description 222 correspond to the description 2011 and the description 2012 in FIG. 4, respectively.

  The character string “AppleTalk” in the description 2211 of the HTML data 220 is obtained by the XSLT processor 15 outputting “AppleTalk” in the description 1671a of the translated format data 167 as it is. The character string “Network No.” in the description 2221 of the HTML data 220 is obtained by the XSLT processor 15 outputting “Network No.” in the description 1672a of the translated format data 167 as it is.

  On the other hand, the description 2212 of the HTML data 220 is output by the XSLT processor 15 based on the description 1671b of the translated format data 167 and the value (true) in the description 1222 of the base data 121. The description 2222 of the HTML data 220 is output by the XSLT processor 15 based on the description 1672b of the translated format data 167 and the value (1234) in the description 1223 of the base data 121.

  That is, the XSLT processor 15 uses the element name (character string surrounded by tags) (“appleTalk”, “networkNo”) as the tag name for the descriptions 1671b and 1672b of the translated format data 167. A search is performed from the data 121, and the value of the searched element (“true”, “1234”) is output to the HTML data 220. Such processing contents are defined in templates applied to the description 1671 and description 1672 of the translated format data 167. Note that “true” is converted to a key character string as “@ [true] @” in the HTML data 220, but this point is also defined in the template.

  For the description 1671 of the translated form data 167, a template named “optionBoolean” (hereinafter referred to as “optionBoolean template”) is applied based on the description 1671c. In the optionBoolean template, the character string (“AppleTalk”) related to the description 1671a is passed as the value of the variable named “titleText”, and the character string (“appleTalk”) related to the description 1671b is passed to the name “target”. Passed as variable value.

  FIG. 12 is a diagram illustrating a definition example of the optionBoolean template. In the definition example of the optionBoolean template 168 in FIG. 12, the description 1681 searches the base data 121 for an element having the tag value (“appleTalk”) as the tag name, and sets the value (“true”) to the name “value”. It is defined to be assigned to a variable. The description 1682 defines that a character string in which the value of a value variable is surrounded by “@ [” and “] @” key character string identification symbols is assigned to a variable named valueTrans. Note that the portion indicated by reference numeral 1683 describes the definition for outputting the value of titleText and the value of valueTrans to the HTML data 220, but is omitted in the figure for convenience.

  On the other hand, a template named “editValue” (hereinafter referred to as “editValue template”) is applied to the description 1672 of the translated format data 167 based on the description 1672c. In the editValue template, the character string (“Network No.”) related to the description 1672a is delivered as a value of a variable named “titleText”, and the character string (“networkNo”) related to the description 1672b is called “target”. Passed as the value of the name variable.

  FIG. 13 is a diagram showing a definition example of the editValue template. In the definition example of the editValue template 169 in FIG. 13, in the description 1691, an element having the tag value (“networkNo”) as the tag name is searched from the base data 121, and the value (“1234”) is named value. It is defined to be assigned to a variable. In the portion indicated by reference number 1692, a definition for outputting the value of the titleText and the value of the value to the HTML data 220 is described, but is omitted in the drawing for convenience.

  Note that the optionBoolean template 168 and the editValue template 169 may be stored in a file different from the untranslated format data 162. This is because if the template is included in the untranslated format data 162, the template is also included in the translated format data 167 generated for each language, which increases the memory consumption.

  By the way, “@ [true] @” in the description 2212 of the HTML data 220 in FIG. 11 indicates that the character string “true” is a key character string, that is, a translation target. Therefore, hereinafter, the HTML data 220 is referred to as “untranslated HTML data 220”.

  The XSLT processor 15 outputs the generated untranslated HTML data 220 to the translation unit 14 (S116). The translation unit 14 translates the key character string in the untranslated HTML data 220 using the language table 163 of the display language (English here), and generates translated HTML data (translated HTML data) (S117). .

  FIG. 14 is a diagram illustrating a definition example of translated HTML data in the English version. The translated HTML data 220a in FIG. 14 is obtained by translating the untranslated HTML data 220 in FIG. That is, in the description 2212a of the translated HTML data 220a, “true” that is the key character string is replaced with “Enable”. The target to be translated here is a value output as a processing result of the Web application 12, that is, a part (dynamic part) that changes according to the processing result of the Web application 12. That is, the true value such as “true” or “false” is a value processed by the program, and when the network setting is valid or invalid, “true” or “false” is displayed as it is. Does not look good. Therefore, in the present embodiment, such a portion is also configured to be translatable according to the display language. For example, if the display language is Japanese, “true” is translated to “valid”.

  Subsequently, the translation unit 14 outputs the translated HTML data 220a to the embedded Web server 11 (S118). The embedded Web server 11 transmits the translated HTML data 220a as an HTTP response to the Web browser 21 of the terminal 20 (S119). The web browser 21 displays the web page 210 based on the translated HTML data 220a. Thereby, the user can browse the Web page in a desired language.

  Next, the process in step S103 of FIG. 5 will be described in more detail. FIG. 15 is a flowchart for explaining the process of generating translated format data by the translation unit.

  The translation unit 14 executes translated processing for all languages supported by the image processing apparatus 10 (S201) and for all untranslated format data 162 for each Web page (S202). Data 167 is generated (S203), and when the translation of all untranslated format data 162 is completed (YES in S202), the translated format data 167 is stored in the storage area 16 (S204).

  Next, the translation process performed by the translation unit 14 executed in step S203 of FIG. 15 and step S117 of FIG. 9 will be described. FIG. 16 is a flowchart for explaining the translation processing by the translation unit.

  First, a character string (key character string) to be translated is searched from untranslated format data 167 or untranslated HTML data 220 (hereinafter referred to as “untranslated data” when collectively referred to) (S251). The search is performed based on the detection of the key character string identification symbol. When the key character string is searched (YES in S252), the display character string corresponding to the key character string is searched from the language table 163 (S253). Here, unlike the general-purpose XSLT processor 15, the translation unit 14 is a program created exclusively for the translation of the untranslated format data 167 and the untranslated HTML data 220. The search is terminated when is found (detected).

  FIG. 17 is a diagram for explaining the language table search processing by the translation unit. FIG. 17 shows an example of searching for a display character string corresponding to the key character string “ATALK”. An arrow a1 indicates that the translation unit 14 stops scanning the language table 163 when a key character string to be searched is detected. Therefore, the performance of the search process can be improved as compared with the XSLT processor 15 that continues scanning even when a key character string to be searched is searched.

  When the display character string is searched (YES in S254), the key character string in the untranslated data is replaced with the searched display character string (S255). When the translation is completed for all key character strings in the untranslated data (NO in S252), the translation process is terminated.

  In the above description, the language table 163 has been described as XML data. However, since the translation unit 14 is not an XSLT processor, the language table 163 does not necessarily need to be XML data. For example, information corresponding to the language table 163 may be registered in a database.

  FIG. 18 is a diagram illustrating an example of a language table constructed on a database. In the language table 163a shown in FIG. 18, a key (key character string) and a text (display character string) are associated with each other. By constructing the language table 163a on the database, for example, a display character string for the key character string can be retrieved at higher speed by logic such as binary tree search.

  As described above, according to the image processing apparatus 10 in the first embodiment, the format data is translated and stored in advance before the Web page request is received. Moreover, since the translation is performed not by the XSLT processor 15 but by the translation unit 14 dedicated for translation, the search process of the language table 163 is speeded up. Therefore, the response when a web page is requested from the terminal 20 can be improved.

  Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Therefore, the points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 19 is a sequence diagram for explaining the translation processing of untranslated format data in the second embodiment. FIG. 19 shows processing executed instead of FIG. 5 in the second embodiment. In FIG. 19, the same steps as those in FIG.

  For example, when the image processing apparatus 10 is activated, the translation unit 14 acquires the untranslated format data 162 from the storage area 16 (S301). In the untranslated format data 162 in the second embodiment, not only a static part but also a dynamic part is included as a translation target (key character string). For example, the dynamic portion corresponds to a portion whose display character string differs according to the setting information (in-machine information) of the image document processing apparatus 10.

  Whether the key character string is a static part or a dynamic part is identified by a difference in the key character string identification symbol. That is, the key character string identification symbol indicating the key character string related to the static portion is different from the key character string identification symbol indicating the key character string related to the dynamic portion.

  Subsequently, the translation unit 14 acquires the language table 163 via the embedded Web client 17 (S302). Subsequently, the translation unit 14 translates the key character string related to the static part in the untranslated format data 162 using the language table 163 of each language, and generates translated format data 167 for each language (S303). ). The translation of the static part is referred to as “primary translation”, and the translated form data 167 generated as a result of the primary translation is referred to as “primary translated form data 167”. The primary translated form data 167 is form data that remains untranslated for the dynamic part. The translation unit 14 stores the generated primary translated form data 167 in the storage area 16 (on the RAM) (S304).

  Thereafter, for example, when the in-flight information of the image processing apparatus 10 is updated (S305), the translation unit 14 acquires the primary translated form data 167 and the updated in-flight information (for example, application data 161). (S306) Based on the in-flight information, the untranslated portion (key character string related to the dynamic portion) in the primary translated form data 167 is translated using the language table 163 (S307). For example, in the second embodiment, the language table 163 defines display character strings for key character strings according to values such as in-flight information. Therefore, the translation unit 14 sets the current in-flight information value from the display character strings defined in the language table 163 for the key character string related to the dynamic part in the primary translated form data 167. A corresponding display character string is acquired, and the key character string is replaced with the display character string. The translation of the dynamic part is referred to as “secondary translation”, and the format data generated as a result of the secondary translation is referred to as “secondary translated format data 167a”.

  Subsequently, the translation unit 14 stores the generated secondary translated form data 167a in the storage area 16 (on the RAM) (S308).

  Next, processing when the image processing apparatus 10 according to the second embodiment generates a Web page will be described. FIG. 20 is a sequence diagram for explaining Web page generation processing in the second embodiment. 20, the same steps as those in FIG. 9 are denoted by the same step numbers, and the description thereof is omitted.

  In FIG. 20, step S115 in FIG. 9 is replaced with step S115a. That is, in step S115a, the XSLT processor 15 generates HTML data using the secondary translated form data 167a.

  Next, the process of generating secondary translated form data in step S307 in FIG. 19 will be described. FIG. 21 is a flowchart for explaining generation processing of secondary translated form data by the translation unit.

  The translation unit 14 performs the secondary translation (secondary translation) for all languages supported by the image processing apparatus 10 (S401) and for all primary translated form data 167 for each Web page (S402). It is determined whether or not there is a key character string to be subjected to (S403). For the primary translated form data 167 having the secondary translation portion, secondary translated form data 167a is generated by performing secondary translation (S404). When the secondary translation for all of the primary translated form data 167 having the secondary translation portion is completed (YES in S402), the secondary translated form data 167a is stored in the storage area 16 (S405).

  As described above, according to the image processing apparatus 10 in the second embodiment, even if the format data includes a dynamic portion, it can be translated in advance. Therefore, the response when a web page is requested from the terminal 20 can be improved. In addition, it is suitable that the part made into the object of secondary translation is the information which is hardly updated. The secondary translated form data 167a is created and saved in advance. Even if information that is frequently updated is translated in advance, the information is updated when a Web page is requested. This is because a situation may occur in which the translation has to be performed again.

  In the second embodiment, the example in which the translation has two stages (primary translation and secondary translation) has been described. However, the translation may be divided into n stages and the n-th translation may be executed. .

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

It is a figure for demonstrating the search process with respect to the language table by an XSLT processor. It is a figure which shows the structural example of the image processing apparatus in embodiment of this invention. It is a figure for demonstrating the function structural example of an information provision application. It is a figure which shows the example of a display of the web page produced | generated in this Embodiment. It is a sequence diagram for demonstrating the translation process of the untranslated format data in 1st embodiment. It is a figure which shows the example of a definition of untranslated format data. It is a figure which shows the example of a definition of the language table of an English version. It is a figure which shows the example of a definition of translated form data of an English version. It is a sequence diagram for demonstrating the production | generation process of the web page in 1st embodiment. It is a figure which shows the example of a definition of base data. It is a figure which shows the example of a definition of the English version HTML data produced | generated by the XSLT processor. It is a figure which shows the example of a definition of optionBoolean template. It is a figure which shows the example of a definition of editValue template. It is a figure which shows the example of a definition of translated HTML data of an English version. It is a flowchart for demonstrating the production | generation process of the translated format data by a translation part. It is a flowchart for demonstrating the translation process by a translation part. It is a figure for demonstrating the search process of the language table by a translation part. It is a figure which shows the example of the language table constructed | assembled on the database. It is a sequence diagram for demonstrating the translation process of the untranslated format data in 2nd embodiment. It is a sequence diagram for demonstrating the production | generation process of the web page in 2nd embodiment. It is a flowchart for demonstrating the production | generation process of the secondary translated form data by a translation part.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Image processing apparatus 11 Embedded Web server 12a, 12b Web application 14 Translation part 15 XSLT processor 16 ROM
20, 30 Terminal 21 Web browser 40 Network 50 Resource server 101 Copy application 102 Fax application 103 Printer application 104 Information providing application 106 System management service 107 Network service 108 Memory management service 109 Operation panel management service 110 Engine management service 161 Application data 162 Untranslated Format data 163 Language table 164 Image data 165 Script data 166 Language table position information 167 Translated format data 201 OS
202 Engine control board 203 Plotter engine 204 Scanner engine

Claims (12)

Translating means for generating translated XSL data by replacing the identifier included in the XSL data with the display character string using a storage device in which display character strings for a plurality of identifiers are recorded for each language. ,
Information processing means for executing information processing in response to a request for a Web page received via a network and outputting the result of the information processing as XML data;
XSLT conversion means for generating HTML data by applying the translated XSL data to the XML data and performing XSLT conversion;
The translating means ends the search of the display character string related to the identifier when the display character string corresponding to the identifier included in the XSL data is detected from the storage device in which a plurality of the identifiers are recorded. An electronic device characterized by that.   The electronic apparatus according to claim 1, wherein the translation unit generates the translated XSL data before a request for the Web page is received.   The electronic device according to claim 2, wherein the translation unit generates the translated XSL data when the electronic device is activated. The XSLT converting means converts the information included in the XML data into the identifier and outputs the identifier to the HTML data,
4. The translating means replaces the identifier included in the HTML data with the display character string using the storage device in which the display character string for the identifier is recorded. An electronic device according to claim 1. A web page generation method executed by an electronic device,
A translation procedure for generating translated XSL data by replacing the identifier included in the XSL data with the display character string using a storage device in which display character strings for a plurality of identifiers are recorded for each language; ,
An information processing procedure for executing information processing in response to a request for a web page received via a network and outputting the result of the information processing as XML data;
An XSLT transformation procedure for generating HTML data by applying the translated XSL data to the XML data and performing an XSLT transformation;
In the translation procedure, when a display character string corresponding to the identifier included in the XSL data is detected from the storage device in which a plurality of the identifiers are recorded, the search of the display character string related to the identifier is terminated. A Web page generation method characterized by the above.   6. The Web page generation method according to claim 5, wherein the translation procedure generates the translated XSL data before a request for the Web page is received.   The Web page generation method according to claim 6, wherein the translation procedure generates the translated XSL data when the electronic device is activated. The XSLT conversion procedure converts information included in the XML data into the identifier and outputs the identifier to the HTML data.
8. The translation procedure, wherein the identifier included in the HTML data is replaced with the display character string using the storage device in which the display character string for the identifier is recorded. A Web page generation method according to claim 1. On the computer,
A translation procedure for generating translated XSL data by replacing the identifier included in the XSL data with the display character string using a storage device in which display character strings for a plurality of identifiers are recorded for each language; ,
An information processing procedure for executing information processing in response to a request for a web page received via a network and outputting the result of the information processing as XML data;
An XSLT transformation procedure for generating HTML data by applying the translated XSL data to the XML data and performing an XSLT transformation;
In the translation procedure, when a display character string corresponding to the identifier included in the XSL data is detected from the storage device in which a plurality of the identifiers are recorded, the search of the display character string related to the identifier is terminated. A Web page generation program characterized by the above.   10. The Web page generation program according to claim 9, wherein the translation procedure generates the translated XSL data before a request for the Web page is received.   The Web page generation program according to claim 10, wherein the translation procedure generates the translated XSL data when the electronic apparatus is activated. The XSLT conversion procedure converts information included in the XML data into the identifier and outputs the identifier to the HTML data.
12. The translation procedure according to any one of claims 9 to 11, wherein the translation procedure replaces the identifier included in the HTML data with the display character string using the storage device in which the display character string for the identifier is recorded. A Web page generation program according to claim 1.

Images