WO2019041889A1 - Wording modifying method and device - Google Patents

Abstract

A wording modifying method, comprising: obtaining an attribute of a wording to be corrected, correcting the wording to be corrected in a local database according to the obtained attribute of the wording to be corrected, and submitting a synchronization application to a central database; approving the synchronization application submitted to the central database, and if the approval is passed, synchronizing the corrected wording in the local database to the central database; and obtaining a source code file of one or more branches, modifying the source code file according to the corrected wording in the central database, compiling and verifying the modified source code file, and then putting same into a code server.

Description

Entry modification method and term modification device Technical field

The present disclosure relates to, but is not limited to, the field of network data processing technology, and in particular to a term modification method and a term modification device.

Background technique

Terminal internationalization needs to translate the words on the user interface (User Interface, UI) of each country to meet user needs. Because the terms on the UI have professional and local habits, they are not accurately described by professional translators. Therefore, customers or front-time testers often ask the current terms to be inaccurate and need to be re-translated and provide specific translation results. The developer then modifies the source code based on these translations, compiles and verifies it, and finally provides the correct version to the front tester.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

There are too many human interventions to implement the above-mentioned front-entry fault modification, which often takes several days, work inefficiency, and the suitability of any one of the terms requires developers to modify, compile, and verify in the source code. Great waste.

The present disclosure provides a term modification method and a term modification device, which can improve the work efficiency of term fault modification.

An embodiment of the present disclosure provides a method for modifying a term, including:

Obtaining an attribute of the item to be corrected, correcting the item to be corrected in a local database according to the obtained attribute of the item to be corrected, and submitting a synchronization application to the central database;

The synchronization application submitted to the central database is approved, and when the approval is passed, the corrected entries in the local database are synchronized to the central database;

Obtain source code files for one or more branches, modify the source code files according to the corrected entries in the central database, and compile and verify them to join the code server.

In an exemplary embodiment, the attributes of the term include a term primary key and a term value.

In an exemplary embodiment, the attribute of the term further includes an entry number for indicating the number of terms of the two-dimensional node.

In an exemplary embodiment, the obtaining the attributes of the term to be corrected further includes:

Obtaining a source code file of the first language, and extracting the first term data including the term primary key and the first language term value;

Obtaining a source code file of the second language, and extracting second term data including a term primary key and a second language term value;

The first term data and the second term data are combined into a total term data including a term primary key, a first language term value, and a second language term value, and the total term data is stored in a local database.

In an exemplary embodiment, the storing the total term data into a local database includes:

The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table.

In an exemplary embodiment, before the obtaining the attribute of the term to be corrected, the method further includes:

Obtain source code files of all languages, extract term data including entry primary key and various language term values, and store the extracted term data in a central database.

In an exemplary embodiment, the source code file is modified according to the corrected terms in the central database, including:

Synchronizing the corrected terms in the central database to an intermediate file;

The source code file is modified according to the corrected entry in the intermediate file.

The embodiment of the present disclosure further provides an entry modification device, including a correction unit, an approval unit, and a join unit, wherein:

The correction unit is configured to: obtain an attribute of the item to be corrected, correct the item to be corrected in the local database according to the acquired attribute of the item to be corrected, submit a synchronization application to the central database, and notify the approval unit;

The approval unit is set to: receive the notification of the correction unit, approve the synchronization application submitted to the central database, and when the approval is passed, synchronize the corrected entries in the local database to the central database, and notify the joining unit;

The merge unit is set to: receive the notification of the approval unit, obtain the source code file of one or more branches, modify the source code file according to the corrected entry in the central database, and compile and verify and merge into the code server.

In an exemplary embodiment, the attributes of the term include a term primary key and a term value.

In an exemplary embodiment, the method further includes extracting a merging unit, the extracting merging unit is configured to: acquire a source code file of the first language, and extract the first vocabulary data including the vocabulary primary key and the first language vocabulary value Obtaining a source code file of the second language, extracting second term data including a term primary key and a second language term value; combining the first term data and the second term data into a terminating primary key, first The total term data of the language term value and the second language term value, and the total term data is stored in the local database.

In an exemplary embodiment, the extracting and merging unit is set to:

The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed, implement the above-described term modification method.

The technical solution of the present disclosure has the following beneficial effects:

The term modification method and the term modification device provided by the present disclosure reduce the intermediate communication link by correcting the term to be corrected in the local database, synchronizing to the central database, and then combining the source code files of one or more branches. , greatly reducing labor costs, improving the efficiency of the modification of the terminology, and accumulating a constantly enriched central database.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a schematic flowchart diagram of a method for modifying a term according to an embodiment of the present disclosure;

2 is a schematic structural diagram of a term modification device according to a first embodiment of the present disclosure;

3 is a schematic structural diagram of an apparatus for modifying a term according to a second embodiment of the present disclosure;

4 is a schematic structural diagram of a term modification system according to an alternative embodiment of the present disclosure;

5 is a schematic diagram of a format of a table field defined by a term modification system according to an alternative embodiment of the present disclosure;

6 is a schematic flowchart of a method for modifying a term of a term modification system according to an alternative embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a new entry learning translation process of the term modification system according to an alternative embodiment of the present disclosure.

Preferred embodiment of the present disclosure

Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

As shown in FIG. 1, a method for modifying a term according to the present disclosure includes the following steps:

Step 101: Acquire an attribute of the item to be corrected, correct the item to be corrected in a local database according to the acquired attribute of the item to be corrected, and submit a synchronization application to the central database;

Optionally, the attributes of the term include a term key id and a term value.

Optionally, before the step 101, the method further includes:

Obtaining a source code file of the first language, and extracting the first term data including the term primary key and the first language term value;

Obtaining a source code file of the second language, and extracting second term data including a term primary key and a second language term value;

The first term data and the second term data are combined into a total term data including a term primary key, a first language term value, and a second language term value, and the total term data is stored in a local database.

Optionally, the storing the total term data into a local database, including:

The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table.

It is worth noting that the sources of the two first languages or the second languages can be determined by determining whether the similarity between the paths of the source code files of the two first languages or the second languages is greater than a preset similarity threshold. Whether the code file belongs to the same original source code file. For example, if the path of the source code file of a first language or a second language is A\B\C\D, the path of the source code file of another first language or the second language is B\C\D, if The similarity between the paths defining the source code files of the two first languages or the second languages is the ratio of the same number of folders to the maximum number of folders, and the same folder is B, C, D, so The similarity is 3/4, and if the preset similarity threshold is 70%, the source code files of the two first languages or the second languages are considered to belong to the same original source code file.

Optionally, before the step 101, the method further includes:

Obtain source code files of all languages, extract term data including entry primary key and various language term values, and store the extracted term data in a central database.

It is worth noting that the more customized versions of mobile terminals, the greater the translation of the entries. For UI entries in different countries of the same language family, it is not necessary to re-translate all of them, and you can also borrow translations from other countries in the same language system, which can greatly reduce translation costs. By storing the entry values of various languages in the central database, when it is necessary to translate the entry of a newly customized terminal into another small language, first find out whether the database contains the term to be translated and the corresponding small language value. When the words to be translated and the corresponding small language values are included, the existing translations can be directly used.

Optionally, the attribute of the term further includes an item id for indicating a number of terms of the value of the two-dimensional node.

It is worth noting that the item number is used to describe the attributes of the child nodes within the two-dimensional node. For example, the following two-dimensional data contains three item attributes, which are described by item0, item1, and item2, respectively:

<string array name (string-array name)="preferred network mode selection_world mode (preferred_network_mode_choices_world_mode)">

<item>global (Global)</item>

<item>Long Term Evolution (LTE)/Code Division Multiple Access (CDMA)</item>

<item>LTE/Global System for Mobile Communication (GSM)/Universal Mobile Telecommunications System (UMTS)</item>

</string-array>.

Optionally, before the step 101, the method further includes:

Obtaining a source code file of the first language, and extracting first term data including a term primary key, an item number, and a first language term value;

Obtaining a source code file of the second language, and extracting second item data including a term primary key, an item number, and a second language term value;

Combining the first term data and the second term data into a total term data including a term primary key, an entry number, a first language term value, and a second language term value, and storing the total term data to the local In the database.

Optionally, before the step 101, the method further includes:

Obtain source code files of all languages, extract term data including entry primary key, entry number and various language term values, and store the extracted term data in a central database.

Step 102: Approve the synchronization application submitted to the central database, and when the approval is passed, synchronize the corrected entries in the local database to the central database;

It is worth noting that the approval here can be manual approval or automated approval. For example, if it is an automated approval, the semantics, grammar and sentence structure of the entry can be checked by the relevant translation software; if it is manually approved, it can be passed. More professional and more localized manual inspections are approved.

Step 103: Acquire one or more branch source code files, modify the source code file according to the corrected terms in the central database, and compile and verify and merge into the code server.

Optionally, the modifying the source code file according to the corrected term in the central database comprises:

Synchronizing the corrected terms in the central database to an intermediate file;

The source code file is modified according to the corrected entry in the intermediate file.

Optionally, the intermediate file is an Excel format file.

As shown in FIG. 2, a term modification device according to the present disclosure includes a correction unit 201, an approval unit 202, and a join unit 203, wherein:

The correcting unit 201 is configured to: obtain an attribute of the item to be corrected, correct the item to be corrected in a local database according to the acquired attribute of the item to be corrected, and submit a synchronization application to the central database, and notify Approval unit 202;

The approval unit 202 is configured to: receive the notification of the correction unit 201, and approve the synchronization application submitted to the central database, and when the approval is passed, synchronize the corrected entries in the local database to the central database, and notify the integration. Unit 203;

The merging unit 203 is configured to: receive the notification of the approval unit 202, acquire the source code file of one or more branches, modify the source code file according to the corrected entry in the central database, and compile and verify the code into the code. server.

Optionally, the attributes of the entry include a term primary key id and a term value.

Optionally, the attribute of the correction unit 201 according to the acquired term to be corrected may be according to the term primary key.

Optionally, as shown in FIG. 3, the term modification device further includes an extract and merge unit 204, configured to: obtain a source code file of the first language, and extract a first value including a term primary key and a first language term value. Term data; acquiring a source code file of the second language, extracting second term data including a term primary key and a second language term value; and combining the first term data and the second term data into a terminating primary key The total term data of the first language term value and the second language term value, and the total term data is stored in the local database.

Optionally, the extraction and merge unit 204 is configured to:

The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table.

Optionally, the extract and merge unit 204 is further configured to:

Obtain source code files of all languages, extract term data including entry primary key and various language term values, and store the extracted term data in a central database.

Optionally, the attribute of the term further includes an item number item id for indicating the number of terms of the two-dimensional node.

Optionally, the extract and merge unit 204 is further configured to:

Obtaining a source code file of the first language, extracting first term data including a term primary key, an entry number, and a first language term value; acquiring a source code file of the second language, extracting the entry primary key, the entry number, and the The second term data of the second language term value; combining the first term data and the second term data into a total word including the term primary key, the item number, the first language term value, and the second language term value Strip data and store the total term data in a local database.

Optionally, the extract and merge unit 204 is further configured to:

Obtain source code files of all languages, extract term data including entry primary key, entry number and various language term values, and store the extracted term data in a central database.

Optionally, the joining unit 203 is configured to:

Synchronizing the corrected terms in the central database to an intermediate file;

The source code file is modified according to the corrected entry in the intermediate file.

Optionally, the intermediate file is an Excel format file.

The embodiments of the present disclosure also provide an alternative embodiment to explain the present disclosure.

As shown in FIG. 4, the entry modification system of the optional embodiment includes a Git script, a terminology tool, a central database of terms, and an online modification of the terminology software of the mobile phone, wherein:

The Git script is set to: obtain an eXtensible Markup Language (xml) file of a different Git repository, and encapsulate the entry tool command, update the entry to be entered into the xml file, and then pass the Git script. Uploaded to the Git repository;

The term tool is set to: provide conversion of xml file and Excel file, and also provide xml file into Structured Query Language (SQL) database (Data Base, DB) file to modify the entry software of mobile phone online Use, and synchronize the functions to be entered into the entry from the central database of the entry;

The central database of the entry is set to: a database for storing various language terms, and also provides a network interface for the term reference function and various modified terms;

The mobile phone online modification term software is a client software. When an error term is found on the UI interface, the online error editing term is used to obtain the attribute of the error entry, and then the local SQL DB library of the mobile phone filters out whether the attribute is present. The entry, when there is a term for the attribute, obtains a data item with the attribute entry, and then corrects the data item with the correct data, and finally uploads it to the central database of the entry.

It is worth noting that Git is an open source version control software developed to help manage Linux kernel development. It can efficiently and quickly handle project version management from very small to very large.

As shown in Figure 5, the entry is stored in the form of a node in xml format. A node has multiple attributes and a value of a term, where the primary key id (indicated by attribute 1 in Figure 5) and the node word. The bar values form a dictionary pair, so that the dictionary pairs of the two languages (the English term is the reference language) are merged, and the two languages constituting a key id form a comparison item, considering that there are some small node lists in some nodes. Two-dimensional nodes (regardless of three-dimensional nodes), so on the basis of the previous, add an attribute item id (indicated by attribute 2 in Figure 5) to describe the attributes of the child nodes. Since the nodes of the second dimension have some attributes, some do not. The attribute has only the value (term), so the item id only records the sequence number of the child node.

For example, there is one-dimensional data as follows:

<string name (string name) = "phone application label" product ("phoneAppLabel" product)="tablet" (tablet data) (Cellular Data) </string>

Among them, phoneAppLabel is the key id, and Cellular Data is the English value (values);

If it is a small language, the corresponding one-dimensional data is:

<string name="phoneAppLabel"product="tablet">small language value </string>

Another example is the following two-dimensional data:

<string-array name="preferred_network_mode_choices_world_mode">

<item>Global</item>

<item>LTE/CDMA</item>

<item>LTE/GSM/UMTS</item>

</string-array>

The above two-dimensional data has three item attributes, which are described by 0, 1, and 2, respectively.

That is to say, each table data will have four attributes: key id, item id, English term value and other language term values, but the data belongs to the xml information in a certain directory, that is, there is another directory. The information is not described. The module is used to describe this temporarily, indicating that the data belongs to a module. The actual meaning of the module is assigned by the relative path of the xml file, which is the relative path between the path of the entry tool and the xml file. And written in the first column of the first row of each Excel, the format is module _key id, the fourth row of the first row specifies the specific other language names.

The term tool provides the following command functions:

Xml2excel conversion: First extract the data of the three attributes of key id, item id and English term value from the English xml file, and then select an xml file of another language to extract the key id, item id and other language terms. The attribute data, then the three attribute data lists of two different languages are merged into one four attribute data list, and the merge principle is as follows:

The key id of the English language is used. If the key id is also available in other languages, the entries in other languages are filled in the English-based data list as the fourth attribute. If not, you don't have to fill it out. After this, it can be determined whether the key id has been translated by whether the fourth attribute is empty. Finally, the information is saved into different Excel files as required and provided for use by others.

Xml2sql conversion: similar to the xml2excel conversion instruction (represented by instruction 1) function, but the data extracted from the xml file is stored in the DB file that can be used by SQL for the mobile phone to modify the entry software query.

Excel2xml conversion: Contrary to the xml2excel conversion command function, the translated Excel file entries are merged into the xml file.

Sync2excel conversion: download the required entry from the central database of the entry, the generated Excel file is the same as the Excel file format generated by the xml2excel function.

All2excel conversion: xml2excel conversion instructions generate Excel tables in two languages, and all2excel is a large table that combines all defined language column attributes.

For the commercially available mobile phone terminal, there is only one Git repository set to store the mobile phone source code version at the beginning, which has a relatively stable resource xml file and directory structure. But with platform upgrades, custom developments, and Git repositories pulled out by various stable projects, some directory results are the same, but the directory names have changed; even more so, the directory structure has changed. The consequence of this is that the relative path is too many as the module name (key id), but the xml file inside is similar. As a result, the central database of entries will be very large as the number of modules increases, and in fact many of the entries are duplicated.

To this end, we can find ways to avoid too many modules, the essence of which is how to merge similar modules. The optional operation is to map multiple similar directories into one directory. Although there is a many-to-one mapping relationship, there is only one such correspondence in each Git repository, so there is actually a one-to-one relationship for a specific Git repository operation, which means that it cannot be imported due to ambiguity. .

Windows, Linux, and Ios are possible because you can't restrict the deployment of the term tool on any system. So the term tool uses the Python language (Python is an object-oriented interpreted computer programming language), ensuring that the term tool can No porting. However, there are differences in the handling of certain details between different operating systems, such as slashes and backslashes. The definition of the module [relative path] has slashes or backslashes, and these modules need to be described in the configuration file. You cannot define multiple ini configuration files, but you should be adaptive. Therefore, the definition of the module is based on the backslash of Window. Regardless of which operating system is exported, the output modules are backslashes, and then the backslash and slash are replaced according to the actual operating system to solve the problem. difference.

Module mapping is used as a configuration item for the terminology tool, for a simple example:

Basemodule=packages\zte\VideoPlayer\res,packages\VideoPlayer\res

Packages\zte\VideoPlayer\res=VideoPlayer\res

Packages\VideoPlayer\res=VideoPlayer\res

First, the original module is uniformly assigned to the basemodule configuration item, and then a mapped configuration item is assigned to each original module;

Instructions:

Xml2excel command: first traverse the current folder, get all the original module list, and then compare with the basemodule module one by one to confirm whether to do mapping, when the comparison confirms to do the mapping, there can be a mapping relationship behind From which the mapped module is obtained.

As shown in FIG. 6, the entry modification method of this alternative embodiment may include the following steps:

The mobile phone entry acquisition software matches a data item from the local database file through the main attribute of the entry, and then submits the application to the central database of the entry;

The central database approval of the entry (either through manual approval or through automated approval), after adding a new unincorporated data flag, and then notifying the automatic update system;

After receiving the notification of the unincorporated data, the automatic update system calls the Sync2excel command (indicated by the instruction 2) to synchronize the unincorporated data in the central database to the local Excel file;

The Git script traverses the xml file of one or more branches according to the existing repository definition, and then calls the excel2xml command to merge the modified entry into the xml file, and then automatically compiles the entire code. When there is no error, it indicates that excel2xml is merged. Correct, and finally can be integrated into the Git repository, thus enabling online modification of the terms.

The translation process of the new entry is shown in Figure 7. First, all the defined language column attributes are merged together by the All2xml instruction (represented by the instruction 3) in the entry tool to create a large table and save it to the center of the entry. In the database; when there is a new custom xml resource, first merge the term data of different languages into a list of four attribute data through the xml2excel conversion instruction in the entry tool, and find out the untranslated term data, that is, other The vocabulary value of the vocabulary is empty, and then the reference data in the central database of the vocabulary is used for reference comparison. When there are corresponding values of other linguistic terms, they can be directly used for reference and converted from the word by sync2excel. The central database download needs to be merged into the entry, and then the translated Excel file entry is merged into the xml file by the excel2xml conversion instruction (represented by instruction 4).

The term modification method and the term modification device provided by the present disclosure reduce the intermediate communication link by correcting and synchronizing to the central database in the local database, and then combining the source code files of one or more branches, thereby greatly reducing the manpower The cost has improved the efficiency of the change of the terminology and accumulated a constantly enriched central database.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed, implement the above-described term modification method.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may be implemented by using a software function module. The form is implemented. The present disclosure is not limited to any specific form of combination of hardware and software.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. The computer storage medium includes, but is not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), and Electrically Erasable Programmable Read-only Memory (EEPROM). Flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, disk storage or other magnetic storage device, or Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

A person skilled in the art can understand that the technical solutions of the present disclosure may be modified or equivalent, without departing from the spirit and scope of the present disclosure, and should be included in the scope of the claims of the present disclosure.

Industrial applicability

The term modification method and the term modification device provided by the present disclosure reduce the intermediate communication link by correcting the term to be corrected in the local database, synchronizing to the central database, and then combining the source code files of one or more branches. , greatly reducing labor costs, improving the efficiency of the modification of the terminology, and accumulating a constantly enriched central database.

Claims (11)

A method of modifying a clause, including: Obtaining an attribute of the item to be corrected, correcting the item to be corrected in a local database according to the obtained attribute of the item to be corrected, and submitting a synchronization application to the central database; The synchronization application submitted to the central database is approved, and when the approval is passed, the corrected entries in the local database are synchronized to the central database; Obtain the source code file of one or more branches, modify the source code file according to the corrected entry in the central database, and compile and verify it and merge it into the code server. The term modification method according to claim 1, wherein the attribute of the term includes a term primary key and a term value. The term modification method according to claim 2, wherein the attribute of the term further includes an entry number indicating a number of terms of the word value of the two-dimensional node. The method for modifying a term according to claim 2, before the obtaining the attribute of the term to be corrected, the method further includes: Obtaining a source code file of the first language, and extracting the first term data including the term primary key and the first language term value; Obtaining a source code file of the second language, and extracting second term data including a term primary key and a second language term value; The first term data and the second term data are combined into a total term data including a term primary key, a first language term value, and a second language term value, and the total term data is stored in a local database. The term modification method according to claim 4, wherein said storing the total term data in a local database comprises: The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table. The method for modifying a term according to claim 2, before the obtaining the attribute of the term to be corrected, the method further includes: Obtain source code files of all languages, extract term data including entry primary key and various language term values, and store the extracted term data in a central database. The vocabulary modification method according to claim 1, wherein the source code file is modified according to the corrected entry in the central database, including: Synchronizing the corrected terms in the central database to an intermediate file; The source code file is modified according to the corrected entry in the intermediate file. A term modification device includes a correction unit, an approval unit, and a join unit, wherein: The correction unit is configured to: obtain an attribute of the item to be corrected, correct the item to be corrected in the local database according to the acquired attribute of the item to be corrected, submit a synchronization application to the central database, and notify the approval unit; The approval unit is configured to: receive the notification of the correction unit, and approve the synchronization application submitted to the central database, and when the approval is passed, synchronize the corrected entries in the local database to the central database, and notify the joining unit; The merge unit is set to: receive the notification of the approval unit, obtain the source code file of one or more branches, modify the source code file according to the corrected entry in the central database, and compile and verify and merge into the code server. The term modification device according to claim 8, wherein the attribute of the term includes a term primary key and a term value. The term modification device according to claim 9, further comprising: Extracting the merging unit, the extracting and merging unit is configured to: obtain a source code file of the first language, extract the first vocabulary data including the vocabulary primary key and the first linguistic vocabulary value; obtain the source code file of the second language, and extract a second term data including a term primary key and a second language term value; combining the first term data and the second term data into a term containing the primary key, the first language term value, and the second language term value The total term data, and the total term data is stored in the local database. The term modification device according to claim 10, wherein said extraction and merge unit is set to: The path of the source code file of the first language or the path of the source code file of the second language is stored in the local database, and the first term data and the second term data belonging to the same original source code file are stored to the local database. In the same data table.

Images