CN111209075A - Multi-language interface maintenance method, system, storage medium and intelligent device - Google Patents
Multi-language interface maintenance method, system, storage medium and intelligent device Download PDFInfo
- Publication number
- CN111209075A CN111209075A CN202010070814.8A CN202010070814A CN111209075A CN 111209075 A CN111209075 A CN 111209075A CN 202010070814 A CN202010070814 A CN 202010070814A CN 111209075 A CN111209075 A CN 111209075A
- Authority
- CN
- China
- Prior art keywords
- language
- update
- target
- language file
- updating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012423 maintenance Methods 0.000 title claims abstract description 50
- 238000004590 computer program Methods 0.000 claims description 14
- 238000012163 sequencing technique Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000012986 modification Methods 0.000 description 8
- 230000004048 modification Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 239000012634 fragment Substances 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000003607 modifier Substances 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/454—Multi-language systems; Localisation; Internationalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application is applicable to the technical field of information synchronization, and provides a multilingual interface maintenance method, a system, a storage medium and intelligent equipment, which comprise the following steps: acquiring an update event of a language file, wherein the language file is used for recording an interface language and corresponding attributes thereof, and the update event refers to the update operation of an operation user on the language file; updating the language file based on the updating event to obtain a target language file; acquiring a target user identifier of an online target user; and pushing the target language file to a display interface of the online target user corresponding to the target user identification. The method and the device can enable the maintenance of the multi-language interface to be simpler, more convenient and more effective, and therefore the maintenance efficiency is improved.
Description
Technical Field
The present application relates to the field of information synchronization technologies, and in particular, to a method, a system, a storage medium, and an intelligent device for maintaining a multi-language interface.
Background
With the development of software technology strength in China, more and more software systems in China are sold to different countries, so that the support of multiple languages by the systems becomes necessary. With the development of computer visualization, user interfaces have an important position in software systems. The user interacts through a User Interface (UI) of the software system to realize operations such as information display and input. In order to facilitate various users to perform corresponding operations, different interface language displays are often required to be provided, for example, the user can select a chinese interface, an english interface, or a german interface, etc. For this reason, a user interface capable of providing multiple languages is generally required in a software system, that is, a corresponding user interface can be provided for different users according to the needs of the users.
In the prior art, maintenance of a multi-language interface generally means that an independent file is generated by one language, and when modification and addition are needed, the corresponding file is modified and added. However, the increment and modification of the language file can generate a plurality of fragmented versions, the versions transmitted to different workers are possibly inconsistent, misoperation is easy to occur, and the file is asynchronous, so that the maintenance of the multi-language interface is difficult.
Disclosure of Invention
The embodiment of the application provides a multilingual interface maintenance method, a multilingual interface maintenance system, a storage medium and intelligent equipment, and can solve the problems that a plurality of fragmented versions are generated due to increment and modification of a language file, the versions transmitted to different workers are possibly inconsistent, misoperation is easy to occur, and asynchronization among files is easy to occur, so that the multilingual interface is difficult to maintain.
In a first aspect, an embodiment of the present application provides a multilingual interface maintenance method, including:
acquiring an update event of a language file, wherein the language file is used for recording an interface language and corresponding attributes thereof, and the update event refers to the update operation of an operation user on the language file;
updating the language file based on the updating event to obtain a target language file;
acquiring a target user identifier of an online target user;
and pushing the target language file to a display interface of the online target user corresponding to the target user identification.
In a possible implementation manner of the first aspect, the step of obtaining an update event of the language file includes:
acquiring a language request sent by an operating user, wherein the language request carries the language type of the operating user request;
searching a language resource packet corresponding to the language type;
and extracting specified content from the language resource package to generate a language file.
In a possible implementation manner of the first aspect, the step of updating the language file based on the update event to obtain a target language file includes:
if the number of the update events is multiple, sequencing the update events according to the sequence of the update time according to the update time carried by each update event;
and sequentially updating the language files according to the sequenced updating events to obtain target language files.
In a possible implementation manner of the first aspect, the update event includes a user identifier, and the step of updating the language file based on the update event to obtain the target language file includes:
if a plurality of update events exist and the update time carried by each update event is the same, acquiring the priority of the operation user corresponding to the user identifier in each update event;
sorting the updating events according to the priority of the operation user;
and sequentially updating the language files according to the sequenced updating events to obtain target language files.
In a possible implementation manner of the first aspect, the step of updating the language file based on the update event to obtain a target language file includes:
if the number of the update events is multiple, acquiring an attribute field in the update event;
combining attribute fields in the plurality of update events to generate a target update event;
and updating the language file according to the target updating event to obtain a target language file.
In a possible implementation manner of the first aspect, the merging and merging attribute fields in a plurality of update events to generate a target update event includes:
if the same attribute field exists in the plurality of updating events and the attribute field values of the same attribute field are different, acquiring the priority of the operation user corresponding to the user identifier in each updating event;
and combining a plurality of update events according to the attribute fields and the update operation thereof in the update events corresponding to the operation users with higher priority to generate target update events.
In a possible implementation manner of the first aspect, the method for maintaining a multi-language interface further includes:
caching the target language file to a cache position of a server;
if the storage request of the operation user is detected, the target language file is transferred from the cache position to the appointed memory position of the server;
updating the language resource package version corresponding to the target language file in the server according to the target language file, and generating and storing a language resource package of a new version;
and pushing the language resource package of the new version to a specified intelligent terminal.
In a second aspect, an embodiment of the present application provides a multilingual interface maintenance system, including:
the system comprises an update event acquisition unit, a language file processing unit and a language file processing unit, wherein the update event acquisition unit is used for acquiring an update event of a language file, the language file is used for recording an interface language and corresponding attributes of the interface language, and the update event refers to the update operation of an operation user on the language file;
a target language file obtaining unit, configured to update the language file based on the update event to obtain a target language file;
the user identification acquisition unit is used for acquiring a target user identification of an online target user;
and the file pushing unit is used for pushing the target language file to a display interface of an online target user corresponding to the target user identifier.
In a third aspect, an embodiment of the present application provides an intelligent device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor, when executing the computer program, implements the multilingual interface maintenance method according to the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, where a computer program is stored, and when executed by a processor, the computer program implements the multilingual interface maintenance method according to the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product, which, when running on an intelligent device, causes the intelligent device to execute the multilingual interface maintenance method according to the first aspect.
In the embodiment of the application, by acquiring an update event of a language file, the language file is used for recording an interface language and corresponding attributes of the interface language, the update event refers to an update operation of an operating user on the language file, then updating the language file based on the update event to obtain a target language file, acquire a target user identifier of an online target user, and then push the target language file to a display interface of the online target user corresponding to the target user identifier, so that different users can acquire updated language files of other users in time, data omission and inconsistency caused by fragment versions are avoided, maintenance of a multi-language interface is enabled to be simpler, more convenient and more effective, and maintenance efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a flowchart illustrating an implementation of a multi-language interface maintenance method according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating an implementation of a multilingual interface maintenance method S101 according to an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating an embodiment of updating language files according to time in a multilingual interface maintenance method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating an embodiment of updating language files according to user priorities in a multilingual interface maintenance method according to the present application;
FIG. 5 is a flowchart illustrating an embodiment of updating a language file according to a merge update event in a multilingual interface maintenance method according to an embodiment of the present application;
FIG. 6 is a flowchart illustrating an implementation of a multi-language interface maintenance method according to another embodiment of the present application;
FIG. 7 is a block diagram of a multi-language interface maintenance system according to an embodiment of the present application;
FIG. 7a is a block diagram of a target language file obtaining unit according to an embodiment of the present application;
FIG. 7b is a block diagram of an event merging module according to an embodiment of the present disclosure;
FIG. 7c is a block diagram of a multilingual interface maintenance system according to another embodiment of the present application;
fig. 8 is a schematic diagram of an intelligent device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
The multilingual interface maintenance method provided by the embodiment of the application can be applied to intelligent terminals such as servers and ultra-mobile personal computers (UMPCs), and the specific types of the intelligent terminals are not limited at all.
Fig. 1 shows an implementation process of a multilingual interface maintenance method provided in an embodiment of the present application, where the method process includes steps S101 to S104. The specific realization principle of each step is as follows:
s101: the method comprises the steps of obtaining an update event of a language file, wherein the language file is used for recording an interface language and corresponding attributes of the interface language, and the update event refers to the update operation of an operation user on the language file.
Multiple languages are involved in the multilingual interface, typically one language creating a separate language file. The user such as a developer or a translator can make modification updates to the language file. The language file can be embodied as a language table, and relevant attributes of languages in the multi-language interface are recorded in the form of the table. The language file generally comprises attributes such as keywords, translation contents, modification time and modifiers, and in one embodiment, the modification time and the modifiers are hidden attributes, are not displayed on an interface by default, and store records in a server. The update event refers to an update operation of the language file by an operation user, and the update operation specifically includes addition, modification, deletion and the like. In the embodiment of the application, the update event of the language file can be acquired in real time.
As an embodiment of the present application, fig. 2 shows a specific implementation flow of step S101 of the multilingual interface maintenance method provided in the embodiment of the present application, which is detailed as follows:
a1: the method comprises the steps of obtaining a language request sent by an operation user, wherein the language request carries the language type of the operation user request. The language categories include various languages such as english, french, germany, etc., that the multi-language interface may provide. The operating user selects the desired language class by sending a language request.
A2: and searching the language resource packet corresponding to the language type. In this embodiment, different language categories correspond to different language resource packages. The language resource package comprises language resource information required by displaying the language on an interface, and specifically comprises all records corresponding to the language type in the database. And storing the language resource information in a specific file format to generate a language resource information directory of a file in the specific format, wherein the language resource information comprises a language character string resource file and a language array generated by analyzing the corresponding language character string resource file.
A3: and extracting specified content from the language resource package to generate a language file. Specifically, the specified content refers to a pre-specified attribute and an attribute field value. For example, keywords, translation contents, and the like of the language category are extracted from the language resource package.
Optionally, in this embodiment of the present application, the language request sent by the operating user carries a type of the operating user, and according to the type of the operating user, specified content corresponding to the type of the operating user is extracted from the language resource package, so as to generate a language file. Specifically, when the operating user is a developer, the language character string resource file in the corresponding format in the language resource package corresponding to the language type is read according to the language type requested in the language request, and a language file is generated. When the operating user is a translator, reading and analyzing the language character string resource file with the corresponding format in the language resource package corresponding to the language type according to the language type requested in the language request to obtain a language array, and generating the language file according to the language array.
S102: and updating the language file based on the updating event to obtain a target language file.
In the embodiment of the application, the updating operation of the language file by the operating user is determined according to the updating event, and the language file is updated based on the updating operation, so that the target language file is obtained.
Optionally, as an embodiment of the present application, as shown in fig. 3, the step S102 specifically includes:
b1: and if the number of the update events is multiple, sequencing the update events according to the sequence of the update time according to the update time carried by each update event. Specifically, in the embodiment of the present application, the update operation of the language file by multiple operation users may be obtained, where the update event carries the update time of the language file updated by the operation user, and the update times are sorted according to the sequence of the update times, for example, an update event with a previous update time is arranged before an update event with a later update time is arranged after the update event with the previous update time.
B2: and sequentially updating the language files according to the sequenced updating events to obtain target language files.
In the embodiment of the application, when a plurality of operation users update the same language file, the language file is updated in sequence according to the sequence of the update events, so that update conflicts are avoided.
Optionally, as an embodiment of the present application, the update event includes a user identifier, as shown in fig. 4, the step S102 specifically includes:
c1: and if a plurality of update events exist and the update time carried by each update event is the same, acquiring the priority of the operation user corresponding to the user identifier in each update event. The user identification is used for identifying the operation user, and the user identification also corresponds to the priority of the identified operation user. When a plurality of operation users perform updating operation on the same language file, under the condition that the updating time is the same, determining the sequencing condition of the updating event according to the priority of the operation users corresponding to the user identification in the updating event.
C2: and sequencing the updating events according to the priority of the operation user. In the embodiment of the application, the update events can be sorted from high to low according to the priority of the operation user; in another embodiment, the update events may be ordered from low to high priority by the operating user. Specifically, if the same attribute field does not exist in a plurality of update events, namely each operation user performs update operation on different attribute fields of the language file, the update events are sorted from high to low according to the priority of the operation user; if the same attribute field exists in a plurality of updating events, namely each operating user performs updating operation on the same attribute field of the language file, the updating events are sorted from low to high according to the priority of the operating users, and the operating users with higher priority are used for updating the same attribute field.
C3: and sequentially updating the language files according to the sequenced updating events to obtain target language files.
In the embodiment of the application, when a plurality of operation users update the same language file at the same time, the update events are sorted according to the priority of the operation users, and the language file is updated in sequence according to the sorting, so that update conflicts are avoided, the update efficiency is improved, and the user experience is enhanced.
Optionally, as an embodiment of the present application, as shown in fig. 5, the step S102 specifically includes:
d1: and if the number of the update events is multiple, acquiring the attribute field in the update event. The update event comprises an update operation of the operation user on the attribute field in the language file.
D2: and combining attribute fields in the plurality of update events to generate a target update event. In this embodiment of the application, when obtaining update events of multiple operation users, the update events of the multiple operation users are merged, and specifically, the step D2 specifically includes:
d21: if the same attribute fields exist in a plurality of updating events and the updating operations of the same attribute fields are different, the priority of the operation user corresponding to the user identifier in each updating event is obtained. Specifically, if the same attribute field exists in a plurality of update events and the update operation of the same attribute field is the same, the same attribute field in the plurality of update events is merged.
D22: and combining a plurality of update events according to the attribute fields and the update operation thereof in the update events corresponding to the operation users with higher priority to generate target update events. If the same attribute field exists in the plurality of update events and the update operations of the same attribute field are different, determining that different operation users respectively perform different update operations on the same attribute field, acquiring the priority of the operation users according to the user identification, and combining the plurality of update events according to the priority of the operation users to generate the target update event. Specifically, a plurality of update events are combined, different attribute fields and update operations thereof are combined, for the same attribute field in the plurality of update events, the update operation of an operation user with higher priority on the same attribute field is reserved, the update operation of an operation user with lower priority on the same attribute field is removed, and then a target update event is generated. The target updating event comprises different attribute fields in a plurality of updating events and updating operation thereof, and updating operation of the same attribute fields and operation users with higher priority in the plurality of updating events on the same attribute fields,
d3: and updating the language file according to the target updating event to obtain a target language file.
In the embodiment of the application, when a plurality of operation users update the same language file at the same time, a plurality of update events are combined to generate a target update event, and the language file is updated according to the target update event, so that the efficiency of updating and maintaining the language file can be improved, and repeated updating is avoided.
S103: and acquiring a target user identifier of the online target user.
Specifically, the online target users include users who are currently online, specifically users who are currently online and interface to operate the language file. In the embodiment of the application, the operation user can update the language file online or offline.
104: and pushing the target language file to a display interface of the online target user corresponding to the target user identification.
Specifically, the target language file is pushed to a display interface of an online target user corresponding to the target user identifier in real time, so that data synchronization is guaranteed when multiple people edit the same language file together, data omission and inconsistency caused by fragment versions are avoided, and maintenance efficiency can be improved. And for the offline user, when the offline user is detected to be online, pushing the target language file to a display interface of the online target user corresponding to the target user identifier.
In the embodiment of the application, by acquiring an update event of a language file, the language file is used for recording an interface language and corresponding attributes of the interface language, the update event refers to an update operation of an operating user on the language file, then updating the language file based on the update event to obtain a target language file, acquiring a target user identifier of an online target user, and then pushing the target language file to a display interface of the online target user corresponding to the target user identifier, so that different users can acquire updated language files of other users in time, data omission and inconsistency caused by fragment versions are avoided, maintenance of a multi-language interface is enabled to be simpler, more convenient and more effective, and maintenance efficiency is improved.
As an embodiment of the present application, as shown in fig. 6, a method for maintaining a multilingual interface provided in an embodiment of the present application further includes:
e1: and caching the target language file to a cache position of a server. In this embodiment, the target language file is cached to a cache location of a server in real time. The target language files cached in the cache position can be cleared according to a user instruction, or the target language files cached in the cache position can be periodically cleared.
E2: and if the storage request of the operation user is detected, the target language file is transferred from the cache position to the appointed memory position of the server. In this embodiment, when a save request of an operating user is detected, the target language file is only transferred from the cache location to a specified memory location of the server. The specified memory location may be user-specified and may permanently store the target language file.
E3: and updating the language resource package version corresponding to the target language file in the server according to the target language file, and generating and storing the language resource package of the new version. In this embodiment, before the storage request of the operation user is detected, the version of the language resource package corresponding to the target language file is not updated. And updating the language resource package version corresponding to the target language file in the server according to the target language file which is transferred to the appointed memory position of the server, and generating and storing the language resource package of the new version.
E4: and pushing the language resource package of the new version to a specified intelligent terminal. The designated intelligent terminal may be an intelligent terminal of a developer. For example, the developer may be notified of the existence of the new version of the language resource package by mail or other notification means.
In the embodiment of the application, a target language file obtained by updating the language file based on the update event is cached in real time, when a storage request of an operation user is detected, the target language file is transferred from the cache position to an appointed memory position of the server, the language resource package version corresponding to the target language file in the server is updated according to the target language file, a language resource package of a new version is generated and stored, and finally the language resource package of the new version is pushed to an appointed intelligent terminal to inform the user of the existence of the language resource package of the new version in time, so that the aim of keeping data consistent is effectively fulfilled, and the efficiency of maintaining a multi-language interface can be further improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Corresponding to the multilingual interface maintenance method described in the foregoing embodiment, fig. 7 shows a block diagram of a structure of the multilingual interface maintenance system provided in the embodiment of the present application, and for convenience of description, only the portions related to the embodiment of the present application are shown.
Referring to fig. 7, the multilingual interface maintenance system includes: an update event acquisition unit 71, a target language file acquisition unit 72, a user identification acquisition unit 73, a file push unit 74, wherein:
an update event obtaining unit 71, configured to obtain an update event of a language file, where the language file is used to record an interface language and a corresponding attribute of the interface language, and the update event refers to an update operation performed on the language file by an operation user;
a target language file obtaining unit 72, configured to update the language file based on the update event to obtain a target language file;
a user identifier obtaining unit 73, configured to obtain a target user identifier of an online target user;
and the file pushing unit 74 is configured to push the target language file to a display interface of an online target user corresponding to the target user identifier.
Optionally, the update event obtaining unit 71 includes:
the language request acquisition module is used for acquiring a language request sent by an operation user, wherein the language request carries the language type of the operation user request;
the resource package searching module is used for searching the language resource package corresponding to the language type;
and the language file generation module is used for extracting the specified content from the language resource package and generating a language file.
Optionally, the target language file obtaining unit 72 includes:
the first sequencing module is used for sequencing the update events according to the sequence of the update time according to the update time carried by each update event if the update events are multiple;
and the first updating module is used for sequentially updating the language files according to the sequenced updating events to obtain target language files.
Optionally, the target language file obtaining unit 72 includes:
the priority obtaining module is used for obtaining the priority of the operation user corresponding to the user identifier in each updating event if the updating events are multiple and the updating time carried by each updating event is the same;
the second sequencing module is used for sequencing the updating events according to the priority of the operation user;
and the second updating module is used for sequentially updating the language files according to the sequenced updating events to obtain target language files.
Alternatively, as shown in fig. 7a, the target language file obtaining unit 72 includes:
a field obtaining module 7201, configured to obtain an attribute field in the update event if there are multiple update events;
an event merging module 7202 configured to merge attribute fields in the multiple update events to generate a target update event;
a third updating module 7203, configured to update the language file according to the target update event, so as to obtain a target language file.
Optionally, as shown in fig. 7b, the event merging module 7202 includes:
the priority determining sub-module 72021 is configured to, if the same attribute field exists in multiple update events and the attribute field values of the same attribute field are different, obtain the priority of the operation user corresponding to the user identifier in each update event;
the update event merging submodule 72022 is configured to merge multiple update events according to the attribute fields and the update operations thereof in the update events corresponding to the operation users with higher priorities, and generate a target update event.
Optionally, as shown in fig. 7c, the multilingual interface maintenance system further includes:
a file caching unit 75, configured to cache the target language file to a cache location of a server;
a file dump unit 76, configured to dump the target language file from the cache location to an appointed memory location of the server if a storage request of the operation user is detected;
a version updating unit 77, configured to update, according to the target language file, a language resource package version corresponding to the target language file in the server, and generate and store a language resource package of a new version;
and the resource package pushing unit 78 is configured to push the language resource package of the new version to the specified intelligent terminal.
In the embodiment of the application, by acquiring an update event of a language file, the language file is used for recording an interface language and corresponding attributes of the interface language, the update event refers to an update operation of an operating user on the language file, then updating the language file based on the update event to obtain a target language file, acquiring a target user identifier of an online target user, and then pushing the target language file to a display interface of the online target user corresponding to the target user identifier, so that different users can acquire updated language files of other users in time, data omission and inconsistency caused by fragment versions are avoided, maintenance of a multi-language interface is enabled to be simpler, more convenient and more effective, and maintenance efficiency is improved.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
Embodiments of the present application further provide a computer-readable storage medium, which stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of any one of the multilingual interface maintenance methods shown in fig. 1 to 6 are implemented.
The embodiment of the present application further provides an intelligent device, which includes a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer readable instructions to implement the steps of any one of the multilingual interface maintenance methods shown in fig. 1 to 6.
The embodiment of the present application further provides a computer program product, which, when running on a server, causes the server to execute the steps of implementing any one of the multilingual interface maintenance methods shown in fig. 1 to 6.
Fig. 8 is a schematic diagram of an intelligent device provided in an embodiment of the present application. As shown in fig. 8, the smart device 8 of this embodiment includes: a processor 80, a memory 81, and computer readable instructions 82 stored in the memory 81 and executable on the processor 80. The processor 80, when executing the computer readable instructions 82, implements the steps of the above-described various multi-language interface maintenance method embodiments, such as the steps S101-S104 shown in fig. 1. Alternatively, the processor 80, when executing the computer readable instructions 82, implements the functions of the modules/units in the device embodiments described above, such as the functions of the units 71 to 74 shown in fig. 7.
Illustratively, the computer readable instructions 82 may be partitioned into one or more modules/units that are stored in the memory 81 and executed by the processor 80 to accomplish the present application. The one or more modules/units may be a series of computer-readable instruction segments capable of performing specific functions, which are used to describe the execution of the computer-readable instructions 82 in the smart device 8.
The smart device 8 may be a server. The smart device 8 may include, but is not limited to, a processor 80, a memory 81. Those skilled in the art will appreciate that fig. 8 is merely an example of a smart device 8 and does not constitute a limitation of the smart device 8 and may include more or less components than those shown, or combine certain components, or different components, for example, the smart device 8 may also include input-output devices, network access devices, buses, etc.
The Processor 80 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may be an internal storage unit of the intelligent device 8, such as a hard disk or a memory of the intelligent device 8. The memory 81 may also be an external storage device of the Smart device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, provided on the Smart device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the smart device 8. The memory 81 is used to store the computer readable instructions and other programs and data required by the smart device. The memory 81 may also be used to temporarily store data that has been output or is to be output.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to an apparatus/terminal device, recording medium, computer Memory, Read-Only Memory (ROM), Random-access Memory (RAM), electrical carrier wave signals, telecommunications signals, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A multi-language interface maintenance method is characterized by comprising the following steps:
acquiring an update event of a language file, wherein the language file is used for recording an interface language and corresponding attributes thereof, and the update event refers to the update operation of an operation user on the language file;
updating the language file based on the updating event to obtain a target language file;
acquiring a target user identifier of an online target user;
and pushing the target language file to a display interface of the online target user corresponding to the target user identification.
2. The multi-lingual interface maintenance method of claim 1, wherein the step of obtaining an update event of a language file comprises:
acquiring a language request sent by an operating user, wherein the language request carries the language type of the operating user request;
searching a language resource packet corresponding to the language type;
and extracting specified content from the language resource package to generate a language file.
3. The multi-lingual interface maintenance method of claim 1, wherein the step of updating the language file based on the update event to obtain a target language file comprises:
if the number of the update events is multiple, sequencing the update events according to the sequence of the update time according to the update time carried by each update event;
and sequentially updating the language files according to the sequenced updating events to obtain target language files.
4. The multi-lingual interface maintenance method of claim 1, wherein the update event includes a user identifier, and wherein the step of updating the language file based on the update event to obtain the target language file comprises:
if a plurality of update events exist and the update time carried by each update event is the same, acquiring the priority of the operation user corresponding to the user identifier in each update event;
sorting the updating events according to the priority of the operation user;
and sequentially updating the language files according to the sequenced updating events to obtain target language files.
5. The multi-lingual interface maintenance method of claim 1, wherein the step of updating the language file based on the update event to obtain a target language file comprises:
if the number of the update events is multiple, acquiring an attribute field in the update event;
combining attribute fields in the plurality of update events to generate a target update event;
and updating the language file according to the target updating event to obtain a target language file.
6. The multi-lingual interface maintenance method of claim 5, wherein the step of merging the attribute fields of the plurality of update events to generate the target update event comprises:
if the same attribute field exists in the plurality of updating events and the attribute field values of the same attribute field are different, acquiring the priority of the operation user corresponding to the user identifier in each updating event;
and combining a plurality of update events according to the attribute fields and the update operation thereof in the update events corresponding to the operation users with higher priority to generate target update events.
7. The multi-language interface maintenance method of claim 1, further comprising:
caching the target language file to a cache position of a server;
if the storage request of the operation user is detected, the target language file is transferred from the cache position to the appointed memory position of the server;
updating the language resource package version corresponding to the target language file in the server according to the target language file, and generating and storing a language resource package of a new version;
and pushing the language resource package of the new version to a specified intelligent terminal.
8. A multi-language interface maintenance system, comprising:
the system comprises an update event acquisition unit, a language file processing unit and a language file processing unit, wherein the update event acquisition unit is used for acquiring an update event of a language file, the language file is used for recording an interface language and corresponding attributes of the interface language, and the update event refers to the update operation of an operation user on the language file;
a target language file obtaining unit, configured to update the language file based on the update event to obtain a target language file;
the user identification acquisition unit is used for acquiring a target user identification of an online target user;
and the file pushing unit is used for pushing the target language file to a display interface of an online target user corresponding to the target user identifier.
9. An intelligent device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the multilingual interface maintenance method of any of claims 1-7 when the computer program is executed by the processor.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a multilingual interface maintenance method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010070814.8A CN111209075B (en) | 2020-01-21 | 2020-01-21 | Multilingual interface maintenance method, system, storage medium and intelligent device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010070814.8A CN111209075B (en) | 2020-01-21 | 2020-01-21 | Multilingual interface maintenance method, system, storage medium and intelligent device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111209075A true CN111209075A (en) | 2020-05-29 |
| CN111209075B CN111209075B (en) | 2024-02-09 |
Family
ID=70785310
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010070814.8A Active CN111209075B (en) | 2020-01-21 | 2020-01-21 | Multilingual interface maintenance method, system, storage medium and intelligent device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111209075B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113010244A (en) * | 2021-02-24 | 2021-06-22 | 上海莉莉丝网络科技有限公司 | Language resource database, language resource management platform and language resource management system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6205418B1 (en) * | 1997-06-25 | 2001-03-20 | Lucent Technologies Inc. | System and method for providing multiple language capability in computer-based applications |
| CN102109958A (en) * | 2011-03-04 | 2011-06-29 | 深圳市开立科技有限公司 | Method and system for realizing multilingual user interface |
| CN102364437A (en) * | 2011-09-22 | 2012-02-29 | 厦门游家网络有限公司 | Multi-language site development system and implementation method thereof |
| US20130226555A1 (en) * | 2012-02-23 | 2013-08-29 | Microsoft Corporation | Multilingual Build Integration for Compiled Applications |
| US20140108018A1 (en) * | 2012-10-17 | 2014-04-17 | Nuance Communications, Inc. | Subscription updates in multiple device language models |
| US9262407B1 (en) * | 2014-09-19 | 2016-02-16 | International Business Machines Corporation | Optimization of a multi-language user interface layout via reverse pseudo-translation |
| CN107193545A (en) * | 2017-04-07 | 2017-09-22 | 广东省科技基础条件平台中心 | Multilingual co-development device, the method and system of a kind of component-oriented |
| US9875269B1 (en) * | 2014-03-12 | 2018-01-23 | Sprint Communications Company L.P. | Collaborative editing in self-contained single page applications |
-
2020
- 2020-01-21 CN CN202010070814.8A patent/CN111209075B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6205418B1 (en) * | 1997-06-25 | 2001-03-20 | Lucent Technologies Inc. | System and method for providing multiple language capability in computer-based applications |
| CN102109958A (en) * | 2011-03-04 | 2011-06-29 | 深圳市开立科技有限公司 | Method and system for realizing multilingual user interface |
| CN102364437A (en) * | 2011-09-22 | 2012-02-29 | 厦门游家网络有限公司 | Multi-language site development system and implementation method thereof |
| US20130226555A1 (en) * | 2012-02-23 | 2013-08-29 | Microsoft Corporation | Multilingual Build Integration for Compiled Applications |
| US20140108018A1 (en) * | 2012-10-17 | 2014-04-17 | Nuance Communications, Inc. | Subscription updates in multiple device language models |
| US9875269B1 (en) * | 2014-03-12 | 2018-01-23 | Sprint Communications Company L.P. | Collaborative editing in self-contained single page applications |
| US9262407B1 (en) * | 2014-09-19 | 2016-02-16 | International Business Machines Corporation | Optimization of a multi-language user interface layout via reverse pseudo-translation |
| CN107193545A (en) * | 2017-04-07 | 2017-09-22 | 广东省科技基础条件平台中心 | Multilingual co-development device, the method and system of a kind of component-oriented |
Non-Patent Citations (1)
| Title |
|---|
| 草莓味的咩酱: "YiCAT教程 (4) 译员如何玩转YiCAT之基础篇", pages 1 - 5 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113010244A (en) * | 2021-02-24 | 2021-06-22 | 上海莉莉丝网络科技有限公司 | Language resource database, language resource management platform and language resource management system |
| CN113010244B (en) * | 2021-02-24 | 2023-05-26 | 上海莉莉丝网络科技有限公司 | Language resource database, language resource management platform and language resource management system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111209075B (en) | 2024-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7149971B2 (en) | Method, apparatus, and system for providing multi-language character strings within a computer | |
| EP2041672B1 (en) | Methods and apparatus for reusing data access and presentation elements | |
| EP1054330A2 (en) | Information management apparatus providing efficient management of multimedia titles in a client-server network | |
| CN110955428A (en) | Page display method and device, electronic equipment and medium | |
| US11030083B2 (en) | Systems and methods for reducing storage required for code coverage results | |
| JP2004102803A (en) | Bulletin board system and method for displaying information | |
| US20080250052A1 (en) | Repopulating a database with document content | |
| CN107515866B (en) | Data operation method, device and system | |
| CN111008020A (en) | Method for analyzing logic expression into general query statement | |
| CN112306594A (en) | Rendering method and device based on mobile terminal and storage medium | |
| CN110334302B (en) | Complex Web application front-end runtime analysis method | |
| CN110109981B (en) | Information display method and device for work queue, computer equipment and storage medium | |
| CN112559913B (en) | Data processing method, device, computing equipment and readable storage medium | |
| CN108694172B (en) | Information output method and device | |
| CN113486215A (en) | Data display method, device and equipment based on data relevance | |
| CN111209075B (en) | Multilingual interface maintenance method, system, storage medium and intelligent device | |
| CN110287338B (en) | Industry hotspot determination method, device, equipment and medium | |
| CN116775488A (en) | Abnormal data determination method, device, equipment, medium and product | |
| CN113407678B (en) | Knowledge graph construction method, device and equipment | |
| CN113179183B (en) | Service switch state control device and method | |
| Le Zou et al. | On synchronizing with web service evolution | |
| CN114817803A (en) | Page skipping method and device and electronic equipment | |
| CN109923538A (en) | Text retrieval device, text searching method and computer program | |
| CN112988300A (en) | Method and device for displaying text in page, storage medium and electronic equipment | |
| US20160117352A1 (en) | Apparatus and method for supporting visualization of connection relationship |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |