WO2019071406A1

WO2019071406A1 - Front-end page internationalization processing method, application server and computer readable storage medium

Info

Publication number: WO2019071406A1
Application number: PCT/CN2017/105436
Authority: WO
Inventors: 陈飞; 向洁; 马会明
Original assignee: 深圳中兴力维技术有限公司
Priority date: 2017-10-10
Filing date: 2017-10-10
Publication date: 2019-04-18
Also published as: CN108885544B; CN108885544A

Abstract

A front-end page internationalization processing method, an application server and a computer readable storage medium. The method comprises: reading an attribute parameter that is set for a page root node, to obtain a path of an internationalization resource file that needs to be loaded on a current page (S402); acquiring a corresponding internationalization resource file according to the path, and loading same in a preset order (S404); parsing the internationalization resource file (S406); and replacing the content that needs to be internationalized on the page with the parsed internationalization content (S408). The solution above can realize, on a pure front-end page, internationalization of all contents of the page, and improve resource file loading efficiency.

Description

Front page internationalization method, application server and computer readable storage medium

Technical field

[0001] The present invention relates to the field of web page bursting technology, and in particular, to a front page page internationalization processing method, an application server, and a computer readable storage medium.

Background technique

[0002] Today's WEB front-end functions are more and more complex, and more and more functions can be realized. The requirements for front-end technicians are getting higher and higher, and the distinction between front-end and back-end is more detailed. Therefore, the international demand for pure front-end page information has also emerged, enabling front-end executives to focus on the front-end bursts without having to over-disperse.

[0003] At present, the international solution is mainly server back-end processing. Taking Java as an example, the Java back-end processes the template and outputs the assembled Html file. The solution requires the developer to master certain back-end technologies, such as JSP, Velocity, etc., and if you switch the burst platform, all pages need to be re-issued.

[0004] Another solution is to use a JavaScript (JS) scripting language for processing on front-end pages. The main purpose is to obtain the page locale through the JS language, and then load the corresponding resource file to replace the internationalization of the content that needs to be internationalized. This solution currently has the following problems:

[0005] All resource files need to be loaded at once, or each page loads a separate resource file. Loading all resource files at once can avoid duplication of internationalization, but it can lead to long periods of loading resources, affecting the user experience. If the private resource file is loaded separately for each page, the resource file can be divided to avoid the one-time loading speed being too slow, but the content will be repeated internationally. For example, "OK" will have many pages. If each page uses a separate resource file, it will result in the internationalization of the word "OK" in each resource file, causing duplicate work.

[0006] The current internationalization solution requires writing JS code on different pages, manually reassigning each tag that needs to be internationalized, and the code is huge and inconvenient to use. And they all focus on the internationalization of visible content, such as page content, input box content and display text on buttons, etc., and there is no genus for page elements. Sexual and other prompt content to achieve automatic internationalization, <input title='1 title "placeholder" prompt "> title and placeholder For these contents, the current internationalization program needs to manually write JS code to replace .

[0007] There is also an internationalization method that uses a specific symbol to match the regular expression internationalization on the page, because the custom special symbol is used as a label, and the JS language's native parsing method for Html content is discarded, which will cause JS language parsing. The efficiency of the page is reduced, reducing page loading efficiency.

technical problem

[0008] In view of this, the main purpose of the present invention is to provide a front-end page internationalization processing method and a corresponding application server, which aims to solve the problem of how to implement internationalization of all content of a page in a pure front-end page, and improve resource file loading. Technical issues of efficiency.

Problem solution

Technical solution

[0009] In order to achieve the above object, the present invention provides a front-end page internationalization processing method, the method comprising the steps of: reading an attribute parameter set by a root node of a page, and obtaining a path of an internationalized resource file to be loaded by the current page; The path acquires a corresponding internationalized resource file, and loads in a preset order; parses the internationalized resource file; and replaces the content that needs to be internationalized in the page with the parsed internationalized content.

[0010] Optionally, the method further includes the step before the step of reading the attribute parameter set by the root node of the page

: Configuring an internationalized resource file corresponding to the page; setting an attribute parameter at the root node of the page to correspond to a path of an internationalized resource file to be loaded on the current page.

[0011] Optionally, in the step of configuring the internationalized resource file corresponding to the page, the internationalized resource file stores the internationalized content in a key-value pair key-value mode, and the internationalized resource The file is named after the file name plus the language. In addition, an international resource resource file without a language suffix is configured, and the default default international content is stored as the default international resource file.

[0012] Optionally, the step of configuring the internationalized resource file corresponding to the page further includes: storing the internationalized content common to the plurality of pages in a common internationalized resource file.

[0013] Optionally, the preset order is: a public default international resource file, an internationalized resource file of a common corresponding locale, a default internationalized resource file of the page private, and a corresponding language ring of the page private. Internationalized resource documents.

[0014] Optionally, the step of setting an attribute parameter at the root node of the page specifically includes: setting a data-* attribute parameter for each label of the content that needs to be internationalized in the page, and configuring a current page. The path of the loaded internationalized resource file is stored in the json format, and the value of the data-* attribute parameter is a key value in the internationalized resource file.

[0015] Optionally, the step of setting an attribute parameter at the root node of the page further includes: if the content that needs to be internationalized is not the value of the input box or the content in the label, but an attribute of the label, Add an additional configuration item to the data-* attribute parameter to identify the attribute value that the label needs to be internationalized; if you need to internationalize multiple attributes of the label, use the English comma in the data-* attribute parameter. Separating a plurality of key values, and separating each of the internationalized tag attributes with a comma in the additional configuration item, the plurality of key values sequentially corresponding to the plurality of tag attributes.

[0016] Optionally, the step of parsing the internationalized resource file specifically includes: parsing the content stored in the internationalized resource file into a key-value mode, and storing by using a public map, wherein the key corresponds to the The key value in the internationalized resource file, the value is the corresponding internationalized content in the internationalized resource file, and the key value in the public map is unique, and the key in the post-loaded internationalized resource file will be overwritten first. The key in the loaded internationalization resource file.

[0017] Optionally, the step of replacing the content that needs to be internationalized in the page with the parsed internationalized content includes: traversing all tags in the page that have data-* attribute parameters set, according to The dat a-* attribute parameter queries the corresponding key value from the public map, thereby obtaining corresponding internationalized content, and replacing the content that needs to be internationalized in the page with the obtained internationalized content.

[0018] In order to achieve the above object, the present invention further provides an application server, where the application server includes: a memory, a processor, an audio device, and a front page page stored on the memory and operable on the processor. And the front-end page internationalization processing program is executed by the processor to implement the step of the front-end page internationalization processing method as described above.

[0019] In addition, in order to achieve the above object, the present invention further provides a computer readable storage medium, where the front end page internationalization processing program is stored on the computer readable storage medium, and the front end page internationalization processing program is processed by a processor. The steps of implementing the front-end page internationalization processing method as described above are performed.

[0020] The front page internationalization processing method, the application server, and the computer readable storage medium proposed by the present invention, The front-end and back-end pages of the website can be completely separated, so that the front-end pages are completely independent, and the front-end static pages are internationalized regardless of the platform of the back-end service and the language of the burst. Using the Html5 standard custom data data-* attribute parameter, through the configuration of the static page, directly use the public JS file to read and traverse the page data-* attribute configuration, no longer need to write a separate JS file for each page, convenient The need for internationalized content is replaced with the corresponding language content, which simplifies the workload of front-end internationalization and improves the efficiency of bursting. And it can realize the internationalization of the prompt content of the page content and prompt information, label custom attributes, etc., to meet the special needs of some pages.

Advantageous effects of the invention

Beneficial effect

[0021] The present invention uses a public international resource file and a page-localized international resource file to be dual-loaded, and can simultaneously load common internationalized resource files in different directories, and uniformly load some common international resources. The page's private international resources are loaded on demand to achieve a balance between reduced work of internationalized language data and page loading efficiency. And fully utilize the JS native parsing method and ajax features to ensure page parsing efficiency. Similarly, based on the browser's features, ajax will automatically cache the loaded internationalized resource files. The second time you hit the same page again, you don't need to repeatedly download the internationalized resource files, it will automatically read from the cache. take. Make full use of the browser's own caching mechanism, so that the efficiency of the second page loading is further improved.

Brief description of the drawing

DRAWINGS

1 is a schematic structural diagram of an application server according to a first embodiment of the present invention;

2 is a block diagram of a front-end page internationalization processing program according to a second embodiment of the present invention; [0024] FIG. 3 is a block diagram of a front-end page internationalization processing program according to a third embodiment of the present invention; 4 is a flowchart of a front-end page internationalization processing method according to a fourth embodiment of the present invention;

5 is a flowchart of a front-end page internationalization processing method according to a fifth embodiment of the present invention;

[0027] The implementation, functional features, and advantages of the present invention will be further described with reference to the accompanying drawings.

Embodiments of the invention The present invention will be further described in detail below with reference to the accompanying drawings and embodiments, in order to make the present invention. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

First Embodiment

[0030] As shown in FIG. 1, it is a schematic diagram of an architecture of an application server 2 proposed by the present invention. In this embodiment, the application server 2 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through a system bus. It is to be noted that Figure 1 only shows the application server 2 with components 11-13, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.

[0031] wherein the memory 11 includes at least one type of readable storage medium, including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), a random access memory. (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of the application server 2, such as a hard disk or memory of the application server 2. In other embodiments, the memory 11 may also be an external storage device of the application server 2, such as a plug-in hard disk equipped on the application server 2, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc. Of course, the memory 11 can also include both the internal storage unit of the application server 2 and its external storage device. In this embodiment, the memory 11 is generally used to store an operating system installed in the application server 2 and various types of application software, such as program code of the front page internationalization processing program 200. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.

[0032] The processor 12 may be a central processing unit in some embodiments (Central Processing)

Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 12 is typically used to control the overall operation of the application server 2. In this embodiment, the processor 12 is configured to run program code or processing data stored in the memory 11, for example, running the front-end page internationalization processing program 200 and the like.

The network interface 13 may include a wireless network interface or a wired network interface, which is typically used for A communication connection is established between the application server 2 and other electronic devices.

Second Embodiment

As shown in FIG. 2, a second embodiment of the present invention provides a front end page internationalization processing program 200.

[0036] In this embodiment, the front-end page internationalization processing program 200 includes a series of computer program instructions stored in the memory 11, and when the computer program instructions are executed by the processor 12, embodiments of the present invention may be implemented. The front end page is internationalized for processing operations. In some embodiments, the front end page globalization program 200 can be divided into one or more modules based on the particular operations implemented by the various portions of the computer program instructions. For example, in FIG. 2, the front end page globalization program 200 can be divided into a reading module 202, a loading module 204, a parsing module 206, and a replacement module 208. among them:

[0037] The reading module 202 is configured to read an attribute parameter set by the root node of the page, and obtain a path of the internationalized resource file that is required to be loaded by the current page.

[0038] Specifically, when a static page needs to be loaded, the public JS is used to read the data-* attribute parameter set by the root node of the page, to obtain a path of the internationalized resource file to be loaded on the page.

[0039] The data-* attribute parameter, for example, data-ilSn, configures a path of the internationalized resource file to be loaded on the current page, and stores the file in the json format. The path is a URL path for the client (browser) to download the internationalized resource file. The value of the data-* attribute parameter is a key value in the internationalized resource file. If the internationalized content is not the value of the input box or the content of the label, but an attribute of the label, such as title or placeholder, then an additional configuration item needs to be added in the data-* attribute parameter to identify the label. Property values that need to be internationalized, such as data-il8n-options.

[0040] If it is required to internationalize multiple attributes of the tag, separate multiple key values by using a comma in the data-* attribute parameter, and separate each of the additional configuration items with a comma The tag attribute, the multiple key values and the plurality of tag attributes need to be sequentially matched. For example, <a title= "title,, data-il8n=,, keyl, key2,,

The data-il8n-options="title,html">link </a> indicates that the title attribute "title" of the tag and the content "link" in the tag are internationalized as the contents of the internationalized resource file corresponding to keyl and key2.

[0041] The loading module 204 is configured to acquire a corresponding internationalized resource file according to the path, and load in a preset order.

[0042] Specifically, after obtaining the path of the internationalized resource file to be loaded by the current page, according to the page The locale, get the corresponding internationalized resource file. The internationalized resource file can be obtained through ajax technology.

[0043] The preset order is: a public internationalized resource file > a page-specific default internationalized resource file > an internationalized resource file of a page-specific corresponding locale. For example, for a page, there are three public international resource files common.properties, common_zh_CN.properties, common_en_US . properties , which are public default internationalization resource files, public Chinese internationalization resource files, and public English public international. The resource file, there are three internationalized resource files home.pro perties, home_zh_CN.properties, home_en_US .properties, which are private to the page, and the default internationalized resource file for this page, private Chinese internationalization. Resource files, private English internationalization resource files. During the loading process, the common default internationalization resource file common.properties is loaded first, and then the publicized internationalized resource file corresponding to the locale is loaded according to the locale, for example, Chinese, then the public Chinese internationalization resource file common_ _Z h_CN is loaded. .propertie _S , At this point, the public international resource file is loaded. Then, load the page's private internationalization resource file home.properties and the private Chinese internationalization resource file home_zh_CN.properties, so that all the internationalized resource files corresponding to the page are loaded.

[0044] By configuring a common internationalized resource file and a page-specific internationalized resource file and defining the preset order, the publicized international resource file does not need to be repeatedly loaded, reducing the internationalization of some common content repetition.

[0045] In this embodiment, the last loaded internationalized resource file has the highest priority for the same page.

[0046] The parsing module 206 is configured to parse the internationalized resource file.

[0047] Specifically, after loading the internationalized resource file successfully, the content stored in the internationalized resource file is parsed into a key-value mode, and is stored by using a public map. Where key corresponds to the key value in the resource file, and value is the corresponding internationalized content in the resource file. The public map provides a mapping relationship, in which elements are stored in the form of key-values, which can quickly find v alue according to the key. The key value in the public map is unique and cannot be repeated. If there is the same key, the key in the loaded internationalized resource file will overwrite the key in the previously loaded internationalized resource file. Therefore, if there is no corresponding international content in the internationalized resource file corresponding to the locale, the corresponding value in the default internationalized resource file is obtained. [0048] The replacement module 208 is configured to replace the content that needs to be internationalized in the page with the parsed internationalized content.

[0049] Specifically, after parsing the internationalized resource file, traversing all the tags in the page in which the data-* attribute parameter is set, and querying the corresponding map from the public Map according to the data-* attribute parameter. The key value is used to obtain the corresponding internationalized content, and the content that needs to be internationalized on the page is replaced with the obtained internationalized content.

[0050] If the tag is not traversed, if the tag does not have a corresponding data-* attribute parameter, the default attribute is used to internationalize, and the content that needs to be internationalized is replaced with the default international content. If the tag belongs to input, select, text area, it is an input control, and the input box value is replaced by the internationalized content. In the case of other tags, the content in the replacement tag is the internationalized content. Content internationalization can not only internationalize text, but also replace images or other Html content, allowing different locales to display different images.

Third Embodiment

As shown in FIG. 3, a third embodiment of the present invention provides a schematic diagram of a front-end page internationalization processing program 200. In this embodiment, the front-end page internationalization processing program 200 includes a configuration module 210 and a setting in addition to the reading module 202, the loading module 204, the parsing module 206, and the replacement module 208 in the second embodiment. Module 212.

[0053] The configuration module 210 is configured to configure an internationalized resource file corresponding to the page.

[0054] Specifically, the internationalized resource file stores the internationalized content in a key-value mode, and the internationalized resource file is named by a file name plus a language. In addition, the configuration module 210 can also configure an international resource resource file without a language suffix, and store the preset default internationalized content as a default internationalized resource file. When the internationalized resource file of the corresponding language cannot be found later or the internationalized content is not found in the internationalized resource file of the corresponding language, the default internationalized content can be obtained from the default internationalized resource file.

In other embodiments, the configuration module 210 configures the internationalized resource file to store the internationalized content common to multiple pages in a common internationalized resource file. For example, the internationalized content corresponding to the words "date", "confirm", "cancel", etc., can be stored in the publicized international resource file for all pages to call.

[0056] The setting module 212 is configured to set an attribute parameter at the root of the page to correspond to the current page. The path to the internationalized resource file.

[0057] Specifically, in this embodiment, a data-* attribute is added to a root node of a static page to be internationalized, and a data-* attribute parameter is set for each label of the content that needs to be internationalized in the page. For example, dat a-il8n, configure the path of the internationalized resource file to be loaded on the current page, and store it in json format. The path is a URL path for the client (browser) to download the internationalized resource file. The value of the data-* attribute parameter is a key value in the internationalized resource file. If the internationalized content is not the value of the input box or the content of the label, but an attribute of the label, such as title or placeholder, then an additional configuration item needs to be added in the data-* attribute parameter to identify the label. Property values that need to be internationalized, such as data-il8n-options.

[0058] If it is required to internationalize multiple attributes of the tag, separate multiple key values by using a comma in the data-* attribute parameter, and separate each of the additional configuration items with a comma The tag attribute, the multiple key values and the plurality of tag attributes need to be sequentially matched. For example, <a title= "title,, data-il8n=,, keyl, key2,,

[0059] If only a portion of the content of a line of text needs to be internationalized, an inline tag can be used to wrap the elements to be internationalized. For example, <a ><i data-il8n="key2">link</i>: 123456</a>, only for the content "link" internationalized by the <^><^> tag, outside the i tag The content will not be internationalized.

[0060] The Html page that needs to be internationalized is set by the data-* attribute parameter, so that all Html tags of the page can use a common JS file, and no additional operations need to be performed on js after setting once.

[0061] In other embodiments, the custom attribute parameters may also be read by setting other custom attribute parameters and then using JS's getAttribute or jQuery's attr method. The content configured in the custom attribute parameter can also be defined using an array or a string of specific punctuation. The configuration of the other format is similar to the data-* attribute parameter of the json format, and will not be described here.

[0062] After the configuration module 210 and the setting module 212 complete the configuration of the internationalized resource file corresponding to the page and the data-* attribute parameter, the page is loaded according to the data-*. The attribute parameter automatically reads the corresponding internationalized resource file, thereby outputting the internationalized content.

Fourth Embodiment [0064] As shown in FIG. 4, a fourth embodiment of the present invention provides a front page page internationalization processing method. The method includes the following steps:

[0065] S402. Read an attribute parameter set by the root node of the page, and obtain a path of the internationalized resource file to be loaded by the current page.

[0066] Specifically, when a static page needs to be loaded, the public JS is used to read the data-* attribute parameter set by the root node of the page, to obtain a path of the internationalized resource file to be loaded on the page.

[0067] The data-* attribute parameter, for example, data-ilSn, configures the path of the internationalized resource file to be loaded on the current page, and stores it in the json format. The path is a URL path for the client (browser) to download the internationalized resource file. The value of the data-* attribute parameter is a key value in the internationalized resource file. If the internationalized content is not the value of the input box or the content of the label, but an attribute of the label, such as title or placeholder, then an additional configuration item needs to be added in the data-* attribute parameter to identify the label. Property values that need to be internationalized, such as data-il8n-options.

[0068] If it is required to internationalize a plurality of attributes of the tag, a plurality of key values are separated by a comma in the data-* attribute parameter, and each of the additional configuration items is separated by a comma. The tag attribute, the multiple key values and the plurality of tag attributes need to be sequentially matched. For example, <a title= "title,, data-il8n=,, keyl, key2,,

[0069] S404. Acquire a corresponding internationalized resource file according to the path, and load in a preset order.

[0070] Specifically, after obtaining the path of the internationalized resource file to be loaded by the current page, the corresponding internationalized resource file is obtained according to the locale of the page. The internationalized resource file can be obtained through ajax technology.

[0071] The preset order is: a public default international resource file, an internationalized resource file of a common corresponding locale, a default internationalized resource file of the page private, and an internationalized resource file corresponding to the local language of the page. For example, for a page, there are three public international resource files common.prop erties, common_zh_CN.properties, common_en_US .properties, and another ¹ J is a public dog internationalization resource file, a public Chinese internationalization resource file. Public English international resource files, and three internationalized resource files home.properties, home_zh_CN.proper Ties . home_en_US.properties , which are the default internationalized resource files for the page, the private Chinese internationalization resource files, and the private English internationalization resource files. During the loading process, the public default internationalization resource file common.properties is loaded first, and then the publicized internationalized resource file corresponding to the locale is loaded according to the locale, for example, Chinese, then the public Chinese internationalization resource file co mmon_zh_CN is loaded. Properties, at this point, the public international resource file is loaded. Then, load the page's private internationalization resource file home.properties and the private Chinese internationalization resource file home_zh_CN.properties, so that all the internationalized resource files corresponding to the page are loaded.

[0072] By configuring a common internationalized resource file and a page-specific internationalized resource file and defining the preset order, the publicized international resource file does not need to be repeatedly loaded, reducing the internationalization of some common content duplication.

[0073] In this embodiment, the last loaded internationalized resource file has the highest priority for the same page.

[0074] S406. Parse the internationalized resource file.

[0075] Specifically, after the internationalized resource file is successfully loaded, the content stored in the internationalized resource file is parsed into a key-value mode, and is stored by using a public map. Where key corresponds to the key value in the resource file, and value is the corresponding internationalized content in the resource file. The public map provides a mapping relationship, wherein the elements are stored in the form of a key-value, which can quickly find a val _ue according to the key. The key value in the public map is unique and cannot be repeated. If there is the same key, the key in the loaded internationalized resource file will overwrite the key in the previously loaded internationalized resource file. Therefore, if there is no corresponding international content in the internationalized resource file corresponding to the locale, the corresponding value in the default internationalized resource file is obtained.

[0076] S408. Replace the content that needs to be internationalized in the page with the parsed internationalized content.

[0077] Specifically, after parsing the internationalized resource file, traversing all the tags in the page with the data-* attribute parameter, and querying the corresponding information from the public Map according to the data-* attribute parameter. The key value is used to obtain the corresponding internationalized content, and the content that needs to be internationalized on the page is replaced with the obtained internationalized content.

[0078] The traversal tag 吋, if the tag does not set the corresponding data-* attribute parameter, the default attribute is used to internationalize, and the content that needs to be internationalized is replaced with the default international content. If the tag belongs to input, select, and text area, it is an input control, and the input box value is replaced by the internationalized content. If it is another label, replace it The content within the tag is the internationalized content. Content internationalization can not only internationalize text, but also replace images or other Html content, so that different locales can display different images.

Fifth Embodiment

[0080] As shown in FIG. 5, a fifth embodiment of the present invention provides a front page page internationalization processing method. In this embodiment, the steps S506-S512 of the front-end page internationalization processing method are similar to the steps S402-S4 08 of the fourth embodiment, except that the method further includes steps S502-S504.

[0081] The method comprises the following steps:

[0082] S502. Configure an internationalization resource file corresponding to the page.

[0083] Specifically, the internationalized resource file stores the internationalized content in a key-value mode, and the internationalized resource file is named by a file name plus a language. In addition, the configuration module 210 can also configure an international resource resource file without a language suffix, and store the preset default internationalized content as a default internationalized resource file. When the internationalized resource file of the corresponding language cannot be found later or the internationalized content is not found in the internationalized resource file of the corresponding language, the default internationalized content can be obtained from the default internationalized resource file.

[0085] S504. Set an attribute parameter at the root node of the page to correspond to a path of the internationalized resource file to be loaded by the current page.

[0086] Specifically, in this embodiment, a data-* attribute is added to a root node of a static page to be internationalized, and a data-* attribute parameter is set for each label of the content that needs to be internationalized in the page. For example, dat a-il8n, configure the path of the internationalized resource file to be loaded on the current page, and store it in json format. The path is a URL path for the client (browser) to download the internationalized resource file. The value of the data-* attribute parameter is a key value in the internationalized resource file. If the internationalized content is not the value of the input box or the content of the label, but an attribute of the label, such as title or placeholder, the shell lj needs to add an additional configuration item to identify the data-* attribute parameter. The tag needs to be internationalized attribute values, such as data-il8n-options. [0087] If it is required to internationalize a plurality of attributes of the tag, a plurality of key values are separated by a comma in the data-* attribute parameter, and each of the additional configuration items is separated by a comma. The tag attribute, the multiple key values and the plurality of tag attributes need to be sequentially matched. For example, <a title= "title,, data-il8n=,, keyl, key2,,

[0088] If only a portion of the content of a line of text needs to be internationalized, an inline tag can be used to wrap the elements to be internationalized. For example, <a ><i data-il8n="key2">link</i>: 123456</a>, only for the content "link" internationalized by the <^><^> tag, outside the i tag The content will not be internationalized.

[0089] The Html page that needs to be internationalized is set by the data-* attribute parameter, so that all Html tags of the page can use a common JS file, and no additional operations need to be performed on js after setting once.

[0090] In other embodiments, the custom attribute parameters may also be read by setting other custom attribute parameters and then using JS's getAttribute or jQuery's attr method. The content configured in the custom attribute parameter can also be defined using an array or a string of specific punctuation. The configuration of the other format is similar to the data-* attribute parameter of the json format, and will not be described here.

[0091] S506. Read an attribute parameter set by the root node of the page, and obtain a path of the internationalized resource file.

[0092] Specifically, when a static page needs to be loaded, the public JS is used to read the data-* attribute parameter set by the root node of the page, to obtain a path of the internationalized resource file to be loaded on the page.

[0093] S508. Acquire a corresponding internationalized resource file according to the path, and load in a preset order.

[0094] Specifically, after obtaining the path of the internationalized resource file to be loaded by the current page, the corresponding internationalized resource file is obtained according to the locale of the page. The internationalized resource file can be obtained through ajax technology.

[0095] The preset order is: a public default international resource file, an internationalized resource file of a common corresponding locale, a default internationalized resource file of the page private, and an internationalized resource file corresponding to the local language of the page. For example, for a page, there are three public international resource files common.prop erties, common_zh_CN.properties, common_en_US .properties, and another ¹ J is a public dog internationalization resource file, a public Chinese internationalization resource file. Public English international resource files, and three internationalized resource files home.properties, home_zh_CN.proper Ties . home_en_US.properties , which are the default internationalized resource files for the page, the private Chinese internationalization resource files, and the private English internationalization resource files. During the loading process, the public default internationalization resource file common.properties is loaded first, and then the publicized internationalized resource file corresponding to the locale is loaded according to the locale, for example, Chinese, then the public Chinese internationalization resource file co mmon_zh_CN is loaded. Properties, at this point, the public international resource file is loaded. Then, load the page's private internationalization resource file home.properties and the private Chinese internationalization resource file home_zh_CN.properties, so that all the internationalized resource files corresponding to the page are loaded.

[0096] By configuring a common internationalized resource file and a page-specific internationalized resource file and defining the preset order, the publicized international resource file does not need to be repeatedly loaded, which reduces the internationalization of some common content.

[0097] In this embodiment, the last loaded internationalized resource file has the highest priority for the same page.

[0098] S510. Parse the internationalized resource file.

[0099] Specifically, after loading the internationalized resource file successfully, the content stored in the internationalized resource file is parsed into a key-value mode, and is stored by using a public map. Where key corresponds to the key value in the resource file, and value is the corresponding internationalized content in the resource file. The public map provides a mapping relationship, wherein the elements are stored in the form of a key-value, which can quickly find a val _ue according to the key. The key value in the public map is unique and cannot be repeated. If there is the same key, the key in the loaded internationalized resource file will overwrite the key in the previously loaded internationalized resource file. Therefore, if there is no corresponding international content in the internationalized resource file corresponding to the locale, the corresponding value in the default internationalized resource file is obtained.

[0100] S512. Replace the content that needs to be internationalized in the page with the parsed internationalized content.

[0101] Specifically, after parsing the internationalized resource file, traversing all the tags in the page in which the data-* attribute parameter is set, and querying the corresponding map from the public Map according to the data-* attribute parameter. The key value is used to obtain the corresponding internationalized content, and the content that needs to be internationalized on the page is replaced with the obtained internationalized content.

[0102] The traversal tag 吋, if the tag does not set the corresponding data-* attribute parameter, the default attribute is used to internationalize, and the content that needs to be internationalized is replaced with the default international content. If the tag belongs to input, select, and text area, it is an input control, and the input box value is replaced by the internationalized content. If it is another label, replace it The content within the tag is the internationalized content. Content internationalization can not only internationalize text, but also replace images or other Html content, so that different locales can display different images.

[0103] It is to be understood that the term "comprises", "comprising" or any other variants thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes Those elements, but also other elements not explicitly listed, or elements that are inherent to such a process, method, item or device. An element defined by the phrase "comprises a ..." without further restrictions does not exclude the presence of additional elements in the process, method, article, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing method can be implemented by means of software plus a necessary general hardware platform, and can also be implemented by hardware, but in many cases. The former is a better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

The preferred embodiments of the present invention have been described above with reference to the drawings, and are not intended to limit the scope of the invention.

The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments. In addition, although the logical order is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than the ones described herein.

A person skilled in the art can implement the invention in various modifications without departing from the scope and spirit of the invention. For example, the features of one embodiment can be used in another embodiment to obtain a further embodiment. Any modifications, equivalent substitutions and improvements made within the technical concept of the invention are intended to be within the scope of the invention.

Industrial applicability

[0107] The front page internationalization processing method, the application server and the computer readable storage medium proposed by the invention can completely separate the front and back pages of the website, so that the front end page is completely independent, and the platform of the back end service is completely complete. Independent of the implementation of the internationalization of the front-end static pages. Use the Html5 standard custom data data-* attribute parameter to read and traverse the page directly using the public JS file through the configuration of the static page. With the data-* attribute configuration, it is no longer necessary to write a separate JS file for each page. It is convenient to replace the internationalized content with the corresponding language content, which simplifies the front-end internationalization workload and improves the bursting efficiency. And it can realize the internationalization of the prompt content of the page content and prompt information, label custom attributes, etc., to meet the special needs of some pages.

In addition, the present invention uses a public international resource file and a page-localized international resource file to be dual-loaded, and can simultaneously load common internationalized resource files in different directories, and is uniformly loaded for some common international resources. Private international resources are loaded on demand to achieve a balance between reduced work of internationalized language data and page loading efficiency. And make full use of JS's native parsing and ajax features to ensure page parsing efficiency. Similarly, browser-based features, ajax will automatically cache the loaded international resource file, the second time you fight the same page again internationalization, do not need to repeatedly download the internationalized resource file, will automatically read from the cache take. Make full use of the browser's own caching mechanism, so that the efficiency of the second page loading is further improved. Therefore, it has industrial applicability.

Claims

Claim

A front-end page internationalization processing method is applied to an application server, and the method includes the following steps:

Read the attribute parameter set by the root node of the page to obtain the path of the internationalization resource file to be loaded on the current page;

Obtaining a corresponding internationalized resource file according to the path, and loading in a preset order; parsing the internationalized resource file; and replacing the content that needs to be internationalized in the page with the parsed internationalized content.

The front-end page internationalization processing method according to claim 1, wherein the method further comprises the step of: configuring an internationalized resource file corresponding to the page before the step of reading the attribute parameter set by the root node of the page;

The attribute parameter is set at the root node of the page to correspond to the path of the internationalization resource file to be loaded by the current page.

The front-end page internationalization processing method according to claim 2, wherein in the step of configuring the internationalized resource file corresponding to the page, the internationalized resource file is stored in a key-value pair key-value mode Internationalized content, the internationalized resource file is named by file name plus language. In addition, an international resource resource file without language suffix is configured, and the default default international content is stored as a default international resource file. . The method of processing the front-end page internationalization according to claim 3, wherein the step of configuring the internationalized resource file corresponding to the page further comprises: storing the internationalized content common to the plurality of pages in a common international resource. Within the file.

The front-end page internationalization processing method according to claim 4, wherein the preset order is: a public default internationalized resource file, an internationalized resource file of a common corresponding locale, and a default internationalized resource file of a private page. An internationalized resource file for the corresponding locale of the page.

The method for processing an internationalization of a front-end page according to claim 2, wherein the step of setting an attribute parameter at the root node of the page comprises:

Set a data-* attribute parameter for each label of the content in the page that needs to be internationalized. The path of the internationalized resource file to be loaded by the current page is configured to be stored in the json format, and the value of the data-* attribute parameter is a key value in the internationalized resource file. The method for processing an internationalization of a front-end page according to claim 6, wherein the step of setting an attribute parameter at the root node of the page further comprises:

If the internationalized content is not the value of the input box or the content of the label, but an attribute of the label, an additional configuration item is added to the data-* attribute parameter to identify that the label needs to be internationalized. Attribute value

If it is required to internationalize multiple attributes of the tag, separate multiple key values by using a comma in the data-* attribute parameter, and separate each internationalized tag with a comma in the additional configuration item. The attribute, the multiple key values and the plurality of label attributes correspond in order.

The front-end page internationalization processing method according to claim 2, wherein the step of parsing the internationalized resource file specifically includes:

The content stored in the internationalized resource file is parsed into a key-value mode, and is stored by using a public map, where key corresponds to a key value in the internationalized resource file, and value is a corresponding value in the internationalized resource file. In the internationalized content, the key value in the public map is unique, and the key in the post-loaded internationalized resource file overwrites the key in the previously loaded internationalized resource file.

The method of processing the front-end page internationalization according to claim 8, wherein the step of replacing the content that needs to be internationalized in the page with the internationalized content that is parsed comprises:

Traversing all the tags of the data-* attribute parameter in the page, and querying the corresponding key value from the public map according to the data-* attribute parameter, thereby obtaining corresponding internationalized content, and the page is The content that needs internationalization is replaced with the international content obtained. An application server, the application server includes: a memory, a processor, and a front-end page internationalization processing program stored on the memory and operable on the processor, wherein the front-end page internationalization processing program is The processor executes the steps of implementing the front-end page internationalization processing method according to any one of claims 1 to 9. [Claim 11] A computer readable storage medium, wherein the computer readable storage medium stores a front end page internationalization processing program, and the front end page internationalization processing program is executed by a processor to implement the right The step of the front page page internationalization processing method according to any one of claims 1 to 9.