CN111209075B - Multilingual interface maintenance method, system, storage medium and intelligent device - Google Patents

Multilingual interface maintenance method, system, storage medium and intelligent device Download PDF

Info

Publication number
CN111209075B
CN111209075B CN202010070814.8A CN202010070814A CN111209075B CN 111209075 B CN111209075 B CN 111209075B CN 202010070814 A CN202010070814 A CN 202010070814A CN 111209075 B CN111209075 B CN 111209075B
Authority
CN
China
Prior art keywords
language
update
target
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.)
Active
Application number
CN202010070814.8A
Other languages
Chinese (zh)
Other versions
CN111209075A (en
Inventor
向庭锋
熊友军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ubtech Robotics Corp
Original Assignee
Ubtech Robotics Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ubtech Robotics Corp filed Critical Ubtech Robotics Corp
Priority to CN202010070814.8A priority Critical patent/CN111209075B/en
Publication of CN111209075A publication Critical patent/CN111209075A/en
Application granted granted Critical
Publication of CN111209075B publication Critical patent/CN111209075B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • G06F9/454Multi-language systems; Localisation; Internationalisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Energy 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 multi-language interface maintenance method, a multi-language interface maintenance system, a storage medium and intelligent equipment, wherein the multi-language interface maintenance method comprises the following steps: acquiring an update event of a language file, wherein the language file is used for recording interface language and corresponding attributes thereof, and the update event refers to 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; pushing the target language file to a display interface of an online target user corresponding to the target user identifier. The method and the device can enable maintenance of the multilingual interface to be simpler, more convenient and more effective, thereby improving maintenance efficiency.

Description

Multilingual interface maintenance method, system, storage medium and intelligent device
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 multilingual interface.
Background
With the development of the software technology in China, more and more software systems are sold to different countries in China, so that the systems support multiple languages necessarily. With the development of computer visualization, user interfaces are playing an important role 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, it is often necessary to provide different interface language displays, for example, the user may select a chinese interface, an english interface, or a german interface, etc. For this reason, it is often necessary in software systems to provide a user interface in multiple languages, i.e. to provide different users with corresponding user interfaces for their needs.
In the prior art, maintenance of a multi-language interface is generally that a language generates an independent file, and when modification and new addition are needed, the corresponding file is modified and added. However, the addition and modification of language files can create multiple fragmented versions, the versions delivered to different staff may not be consistent, errors in operation and dyssynchrony between files can easily occur, resulting in difficulty in maintaining a multi-language interface.
Disclosure of Invention
The embodiment of the application provides a multilingual interface maintenance method, a system, a storage medium and intelligent equipment, which can solve the problems that the increment and the modification of language files can generate a plurality of fragment versions, versions transmitted to different staff are possibly inconsistent, misoperation and dyssynchrony among the files are easy to occur, and therefore, the multilingual interface maintenance is difficult.
In a first aspect, an embodiment of the present application provides a method for maintaining a multilingual interface, including:
acquiring an update event of a language file, wherein the language file is used for recording interface language and corresponding attributes thereof, and the update event refers to 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;
pushing the target language file to a display interface of an online target user corresponding to the target user identifier.
In a possible implementation manner of the first aspect, the step of obtaining an update event of a language file includes:
acquiring a language request sent by an operation user, wherein the language request carries the language type of the operation user request;
searching a language resource package corresponding to the language type;
and extracting the appointed 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 a plurality of update events exist, 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 ordered updating events to obtain target language files.
In a possible implementation manner of the first aspect, the updating event includes a user identifier, and the step of updating the language file based on the updating 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 update events according to the priority of the operation user;
and sequentially updating the language files according to the ordered 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 a plurality of update events exist, acquiring attribute fields in the update events;
merging attribute fields in a 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 step of merging attribute fields in a plurality of update events to generate a target update event includes:
if the same attribute fields exist in the plurality of updating events and the attribute field values of the same attribute fields are different, acquiring the priority of the operation user corresponding to the user identification in each updating event;
and merging a plurality of update events according to the attribute fields and the update operations thereof in the update events corresponding to the operation users with higher priority, and generating a target update event.
In a possible implementation manner of the first aspect, the multi-language interface maintenance method 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 a language resource package version corresponding to the target language file in the server according to the target language file, and generating and storing a new version of language resource package;
and pushing the language resource package of the new version to the appointed intelligent terminal.
In a second aspect, embodiments of the present application provide a multilingual interface maintenance system, including:
the system comprises an updating event acquisition unit, a processing unit and a processing unit, wherein the updating event acquisition unit is used for acquiring an updating event of a language file, the language file is used for recording interface language and corresponding attributes thereof, and the updating event refers to updating operation of an operating user on the language file;
the target language file acquisition unit is used for updating the language file based on the updating event to obtain a target language file;
the user identification acquisition unit is used for acquiring the target user identification of the online target user;
and the file pushing unit is used for pushing the target language file to a display interface of the online target user corresponding to the target user identifier.
In a third aspect, an embodiment of the present application provides an intelligent device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the multi-language interface maintenance method according to the first aspect when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, which when executed by a processor 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 that, when run on a smart device, causes the smart device to perform the multi-language interface maintenance method as described in the first aspect above.
In the embodiment of the application, the update event of the language file is used for recording the interface language and the attribute corresponding to the interface language, the update event refers to the update operation of the operation user on the language file, then the language file is updated based on the update event to obtain the target language file, the target user identification of the online target user is obtained, and then the target language file is pushed to the display interface of the online target user corresponding to the target user identification, so that different users can timely obtain the language files updated by other users, data omission and non-uniformity caused by fragment versions are avoided, and maintenance of the multi-language interface is simpler, more convenient and effective, thereby improving the maintenance efficiency.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of an implementation of a method for maintaining a multilingual interface according to an embodiment of the present application;
fig. 2 is a flowchart of a specific implementation of a multilingual interface maintenance method S101 provided in an embodiment of the present application;
FIG. 3 is a flowchart of a specific implementation of updating language files according to time in the multi-language interface maintenance method provided in the embodiment of the present application;
FIG. 4 is a flowchart of a specific implementation of updating a language file according to a user priority in the multi-language interface maintenance method provided in the embodiment of the present application;
FIG. 5 is a flowchart of a specific implementation of updating a language file according to a merge update event in the multi-language interface maintenance method provided in the embodiment of the present application;
FIG. 6 is a flowchart of an implementation of a method for maintaining a multi-language interface according to another embodiment of the present application;
FIG. 7 is a block diagram of a multi-language interface maintenance system provided by an embodiment of the present application;
fig. 7a is a block diagram of the target language file acquiring unit according to the embodiment of the present application;
FIG. 7b is a block diagram illustrating the structure of an event merge module provided by an embodiment of the present application;
FIG. 7c is a block diagram of a multi-language interface maintenance system provided in accordance with 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 configurations, 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 should 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 any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Reference in the 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 application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
The multi-language interface maintenance method provided by the embodiment of the application can be applied to intelligent terminals such as a server and a super mobile personal computer (ultra-mobile personal computer, UMPC), and the specific type of the intelligent terminal is not limited.
Fig. 1 shows an implementation flow of the multilingual interface maintenance method provided in the embodiment of the present application, where the method flow includes steps S101 to S104. The specific implementation principle of each step is as follows:
s101: and acquiring an update event of a language file, wherein the language file is used for recording interface languages and corresponding attributes thereof, and the update event refers to update operation of an operation user on the language file.
Multiple languages are involved in the multi-language interface, typically one language generates an independent language file. Users such as research personnel or translation personnel can modify and update the language file. The language file may be a language table, and the relevant attribute of the language in the multi-language interface is recorded in the form of the table. The language file generally contains attributes such as keywords, translation content, modification time, modifier, etc., and in the case of one embodiment, the modification time and modifier are hidden attributes, and by default, are not displayed on the interface, and records are stored in the server. The updating event refers to updating operation of the language file by an operation user, and the updating operation specifically comprises adding, modifying, deleting 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 described in detail below:
a1: and acquiring 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 that may be provided by the multi-language interface, such as English, french, german, and the like. The operating user selects the required language category by sending a language request.
A2: and searching a language resource package corresponding to the language type. In this embodiment, different language types correspond to different language resource packages. The language resource package comprises language resource information needed by the language displayed on an interface, and specifically comprises all records corresponding to the language types in a database. And storing the language resource information in a specific file format to generate a language resource information catalog of the 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 the appointed 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 content, etc. of the language category are extracted from the language resource package.
Optionally, in the embodiment of the present application, the language request sent by the operation user carries a type of the operation user, and according to the type of the operation user, specified content corresponding to the type of the operation user is extracted from the language resource package, so as to generate a language file. Specifically, when the operation user is a developer, according to the language type requested in the language request, reading the language character string resource file in the corresponding format in the language resource package corresponding to the language type, and generating a language file. When the operation user is a translator, reading and analyzing a language character string resource file in a corresponding format in a 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 a 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 operation 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.
Alternatively, as an embodiment of the present application, as shown in fig. 3, the step S102 specifically includes:
b1: if a plurality of update events exist, the update events are ordered 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 the plurality of operation users may be obtained, where the update event carries update time of the update operation of the language file by the operation user, and the update time is ordered according to the sequence of the update time, for example, update events with preceding update time are ordered and update events with following update time are ordered.
B2: and sequentially updating the language files according to the ordered 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 files are sequentially updated 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, and step S102 specifically includes:
c1: if a plurality of update events exist and the update time carried by each update event is the same, the priority of the operation user corresponding to the user identifier in each update event is obtained. 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 ordering condition of the updating event according to the priority of the operation user corresponding to the user identification in the updating event.
C2: and sequencing the update events according to the priority of the operation user. In the embodiment of the application, the update events can be ordered 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 by priority of the operating user. Specifically, if the same attribute field does not exist in the plurality of updating events, that is, each operation user performs updating operation on different attribute fields of the language file, the updating events are ordered from high to low according to the priority of the operation user; if the same attribute field exists in the plurality of updating events, that is, each operation user performs updating operation on the same attribute field of the language file, the updating events are ordered from low to high according to the priority of the operation user, and the updating of the same attribute field is performed on the basis of the operation user with higher priority.
And C3: and sequentially updating the language files according to the ordered updating events to obtain target language files.
In the embodiment of the application, when a plurality of operation users perform update operation on the same language file at the same time, the update events are ordered according to the priority of the operation users, and the language file is sequentially updated according to the order, so that update conflict is avoided, update efficiency is improved, and user experience is enhanced.
Alternatively, as an embodiment of the present application, as shown in fig. 5, the step S102 specifically includes:
d1: and if a plurality of update events exist, acquiring attribute fields in the update events. The update event includes an update operation of an attribute field in the language file by an operating user.
D2: and merging attribute fields in a plurality of update events to generate a target update event. In this embodiment of the present application, when obtaining update events of a plurality of operation users, the update events of the plurality of operation users are combined, and specifically, the step D2 includes:
d21: and if the same attribute fields exist in the plurality of updating events and the updating operations of the same attribute fields are different, acquiring the priority of the operation user corresponding to the user identification in each updating event. Specifically, if the same attribute fields exist in the plurality of update events and the update operations of the same attribute fields are the same, the same attribute fields in the plurality of update events are combined.
D22: and merging a plurality of update events according to the attribute fields and the update operations thereof in the update events corresponding to the operation users with higher priority, and generating a target update event. If the same attribute field exists in the plurality of update events and the update operations of the same attribute field are different, different operation users are determined to respectively perform different update operations on the same attribute field, the priority of the operation users is obtained according to the user identification, and the plurality of update events are combined according to the priority of the operation users, so that a target update event is generated. 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 the same attribute field by an operation user with higher priority is reserved, the update operation of the same attribute field by an operation user with lower priority is removed, and then a target update event is generated. The target update event comprises different attribute fields and update operations thereof in a plurality of update events, and the update operations of the same attribute fields and operation users with higher priority in the plurality of update 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 perform update operation on the same language file at the same time, a plurality of update events are combined to generate the target update event, and then 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 obtaining the target user identification of the online target user.
Specifically, the online target user comprises a user currently online, and specifically comprises a user currently online and operating the language file in an interface. In the embodiment of the application, the operation user can update the language file online or offline.
104: pushing the target language file to a display interface of an online target user corresponding to the target user identifier.
Specifically, the target language file is pushed to the display interface of the online target user corresponding to the target user identifier in real time, so that data synchronization is ensured when a plurality of people edit the same language file together, data omission and non-uniformity caused by fragment versions are avoided, and maintenance efficiency can be improved. And for the offline user, pushing the target language file to a display interface of the online target user corresponding to the target user identifier when the offline user is detected to be online.
In the embodiment of the application, the update event of the language file is used for recording the interface language and the attribute corresponding to the interface language, the update event refers to the update operation of the operation user on the language file, then the language file is updated based on the update event to obtain the target language file, the target user identification of the online target user is obtained, and then the target language file is pushed to the display interface of the online target user corresponding to the target user identification, so that different users can timely obtain the language files updated by other users, data omission and non-uniformity caused by fragment versions are avoided, and maintenance of the multi-language interface is simpler, more convenient and effective, thereby improving the maintenance efficiency.
As an embodiment of the present application, as shown in fig. 6, the multi-language interface maintenance method provided in the 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 the server in real time. The target language files cached in the cache location can be cleared according to the user instruction, or the target language files cached in the cache location can be cleared periodically.
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 transferred from the cache location to a designated memory location of the server. The specified memory location may be user specified and the target language file may be permanently stored.
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 a new version of language resource package. In this embodiment, before detecting a save request of an operation user, the language resource package version 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 transferred to the appointed memory position of the server, and generating and storing a new version of language resource package.
E4: and pushing the language resource package of the new version to the appointed intelligent terminal. The designated intelligent terminal may be a developer's intelligent terminal. Illustratively, the developer may be notified by mail or other notification that a new version of the language resource package exists.
In the embodiment of the application, the target language file obtained by updating the language file based on the updating event is cached in real time, when the storage request of an operation user is detected, the target language file is transferred from the cache position to the 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 new version language resource package is generated and stored, finally the new version language resource package is pushed to the appointed intelligent terminal, the user is informed of the new version language resource package in time, the purpose of keeping the data consistent is effectively ensured, and the efficiency of multi-language interface maintenance can be further improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Corresponding to the multilingual interface maintenance method described in the above embodiments, fig. 7 shows a block diagram of the multilingual interface maintenance system provided in the embodiment of the present application, and for convenience of explanation, only the portions related to the embodiments of the present application are shown.
Referring to fig. 7, the multi-language 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 pushing 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 attribute corresponding to the interface language, and the update event is an update operation of an operation user on the language file;
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 the online target user corresponding to the target user identifier.
Optionally, the update event acquisition 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 appointed content from the language resource package and generating a language file.
Alternatively, the target language file acquisition unit 72 includes:
the first ordering module is used for ordering 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 ordered updating events to obtain target language files.
Alternatively, the target language file acquisition unit 72 includes:
the priority acquisition module is used for acquiring the priority of the operation user corresponding to the user identifier in each update event if a plurality of update events exist and the update time carried by each update event is the same;
the second ordering module is used for ordering the update 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 ordered updating events to obtain target language files.
Alternatively, as shown in fig. 7a, the target language file acquisition unit 72 includes:
a field obtaining module 7201, configured to obtain an attribute field in the update event if there are a plurality of update events;
an event merging module 7202, configured to merge attribute fields in a plurality of update events to generate a target update event;
and 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 submodule 72021 is used for acquiring the priority of the operation user corresponding to the user identifier in each updating event if the same attribute field exists in a plurality of updating events and the attribute field values of the same attribute field are different;
the update event merging submodule 72022 is used for merging a plurality of update events according to the attribute fields and the update operations thereof in the update events corresponding to the operation users with higher priorities to generate target update events.
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 transferring unit 76, configured to transfer the target language file from the cache location to a designated memory location of the server if the save request of the operating user is detected;
a version updating unit 77, configured to update, according to the target language file, a version of a language resource package corresponding to the target language file in the server, and generate and store a new version of the language resource package;
and the resource package pushing unit 78 is configured to push the new version of the language resource package to the specified intelligent terminal.
In the embodiment of the application, the update event of the language file is used for recording the interface language and the attribute corresponding to the interface language, the update event refers to the update operation of the operation user on the language file, then the language file is updated based on the update event to obtain the target language file, the target user identification of the online target user is obtained, and then the target language file is pushed to the display interface of the online target user corresponding to the target user identification, so that different users can timely obtain the language files updated by other users, data omission and non-uniformity caused by fragment versions are avoided, and maintenance of the multi-language interface is simpler, more convenient and effective, thereby improving the maintenance efficiency.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.
Embodiments of the present application also provide a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement steps of any of the multiple language interface maintenance methods as represented in fig. 1-6.
The embodiment of the application also provides an intelligent device, which comprises a memory, a processor and computer readable instructions stored in the memory and capable of running on the processor, wherein the steps of any multi-language interface maintenance method as shown in fig. 1 to 6 are realized when the processor executes the computer readable instructions.
Embodiments of the present application also provide a computer program product that, when run on a server, causes the server to perform the steps of implementing any one of the multiple language interface maintenance methods as represented in fig. 1-6.
Fig. 8 is a schematic diagram of a smart device according to 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 various multi-language interface maintenance method embodiments described above, such as steps S101 through S104 shown in fig. 1. Alternatively, the processor 80, when executing the computer readable instructions 82, performs the functions of the modules/units of the apparatus embodiments described above, such as the functions of units 71-74 shown in fig. 7.
For example, 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 complete the present application. The one or more modules/units may be a series of computer readable instruction segments capable of performing specific functions describing 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. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the smart device 8 and is not meant to be limiting as the smart device 8 may include more or fewer components than shown, or may combine certain components, or different components, e.g., the smart device 8 may also include input-output devices, network access devices, buses, etc.
The processor 80 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. 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 smart device 8, such as a hard disk or a memory of the smart 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) or the like, which are 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 for storing 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, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a 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 process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, 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, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (9)

1. A method for maintaining a multi-lingual interface, comprising:
acquiring a language request sent by an operation user, wherein the language request carries the language type of the operation user request and the type of the operation user; searching a language resource package corresponding to the language type; extracting appointed content corresponding to the operation user type from the language resource package according to the operation user type to generate a language file, wherein when the operation user is a developer, according to the language type requested in the language request, the language character string resource file in a corresponding format in the language resource package corresponding to the language type is read to generate the language file, when the operation user is a translator, according to the language type requested in the language request, the language character string resource file in a corresponding format in the language resource package corresponding to the language type is read and analyzed to obtain a language array, and the language file is generated according to the language array;
acquiring an update event of the language file, wherein the language file is used for recording interface language and corresponding attributes thereof, and the update event refers to 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;
pushing the target language file to a display interface of an online target user corresponding to the target user identifier.
2. The 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 a plurality of update events exist, 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 ordered updating events to obtain target language files.
3. The method of claim 1, wherein the update event includes a user identifier, and the step of updating the language file based on the update event to obtain a 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 update events according to the priority of the operation user;
and sequentially updating the language files according to the ordered updating events to obtain target language files.
4. The 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 a plurality of update events exist, acquiring attribute fields in the update events;
merging attribute fields in a 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.
5. The method of claim 4, wherein the step of merging attribute fields in a plurality of update events to generate a target update event comprises:
if the same attribute fields exist in the plurality of updating events and the attribute field values of the same attribute fields are different, acquiring the priority of the operation user corresponding to the user identification in each updating event;
and merging a plurality of update events according to the attribute fields and the update operations thereof in the update events corresponding to the operation users with higher priority, and generating a target update event.
6. 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 a language resource package version corresponding to the target language file in the server according to the target language file, and generating and storing a new version of language resource package;
and pushing the language resource package of the new version to the appointed intelligent terminal.
7. A multi-lingual interface maintenance system, comprising:
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 and the type of the operation user;
the resource package searching module is used for searching the language resource package corresponding to the language type;
the language file generation module is used for extracting appointed content corresponding to the operation user type from the language resource package according to the operation user type to generate a language file, wherein when the operation user is a developer, the language file is generated by reading a language character string resource file in a corresponding format in the language resource package corresponding to the language type according to the language type requested in the language request, and when the operation user is a translator, the language file is read and analyzed according to the language type requested in the language request to obtain a language array and the language file is generated according to the language array;
the updating event acquisition unit is used for acquiring an updating event of the language file, wherein the language file is used for recording interface languages and corresponding attributes thereof, and the updating event refers to updating operation of an operating user on the language file;
the target language file acquisition unit is used for updating the language file based on the updating event to obtain a target language file;
the user identification acquisition unit is used for acquiring the target user identification of the online target user;
and the file pushing unit is used for pushing the target language file to a display interface of the online target user corresponding to the target user identifier.
8. A smart device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the multi-language interface maintenance method of any one of claims 1 to 6 when the computer program is executed by the processor.
9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the multi-language interface maintenance method of any one of claims 1 to 6.
CN202010070814.8A 2020-01-21 2020-01-21 Multilingual interface maintenance method, system, storage medium and intelligent device Active CN111209075B (en)

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 CN111209075A (en) 2020-05-29
CN111209075B true 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)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113010244B (en) * 2021-02-24 2023-05-26 上海莉莉丝网络科技有限公司 Language resource database, language resource management platform and language resource management system

Citations (6)

* Cited by examiner, † Cited by third party
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
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

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9442744B2 (en) * 2012-02-23 2016-09-13 Microsoft Technology Licensing, Llc Multilingual build integration for compiled applications
US9035884B2 (en) * 2012-10-17 2015-05-19 Nuance Communications, Inc. Subscription updates in multiple device language models

Patent Citations (6)

* Cited by examiner, † Cited by third party
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
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

Also Published As

Publication number Publication date
CN111209075A (en) 2020-05-29

Similar Documents

Publication Publication Date Title
CN107506451B (en) Abnormal information monitoring method and device for data interaction
US8010499B2 (en) Database staging area read-through or forced flush with dirty notification
CN111324610A (en) Data synchronization method and device
EP1195675A1 (en) Comment driven processing
CN109669925B (en) Management method and device of unstructured data
CN111143422B (en) Data retrieval method, data retrieval device, storage medium and electronic equipment
JP2014199569A (en) Source program analysis system, source program analysis method, and program
US10755091B2 (en) Method and apparatus for retrieving image-text block from web page
CN109815240A (en) For managing method, apparatus, equipment and the storage medium of index
CN112948486A (en) Batch data synchronization method and system and electronic equipment
CN112306594A (en) Rendering method and device based on mobile terminal and storage medium
CN111209075B (en) Multilingual interface maintenance method, system, storage medium and intelligent device
CN110109981B (en) Information display method and device for work queue, computer equipment and storage medium
CN112711398A (en) Method, device and equipment for generating buried point file and storage medium
JP7033115B2 (en) Search processing method and device based on clipboard data
CN103809915B (en) The reading/writing method of a kind of disk file and device
CN110287338B (en) Industry hotspot determination method, device, equipment and medium
CN115640279A (en) Method and device for constructing data blood relationship
CN111563123B (en) Real-time synchronization method for hive warehouse metadata
Le Zou et al. On synchronizing with web service evolution
CN112988583A (en) Method and device for testing syntax compatibility of database
CN114169318A (en) Process identification method, apparatus, device, medium, and program
CN110727677B (en) Method and device for tracing blood relationship of table in data warehouse
CN113127574A (en) Service data display method, system, equipment and medium based on knowledge graph
CN112612866A (en) Knowledge base text synchronization method and device, electronic equipment and storage medium

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