CN109947711B - Automatic multi-language file management method in IOS project development process - Google Patents
Automatic multi-language file management method in IOS project development process Download PDFInfo
- Publication number
- CN109947711B CN109947711B CN201810960765.8A CN201810960765A CN109947711B CN 109947711 B CN109947711 B CN 109947711B CN 201810960765 A CN201810960765 A CN 201810960765A CN 109947711 B CN109947711 B CN 109947711B
- Authority
- CN
- China
- Prior art keywords
- character string
- file
- string
- character
- judging whether
- 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
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
Abstract
The invention discloses a method for automatically managing multilingual files in the development process of an IOS project, which comprises the following steps: s1: acquiring the contents of all character string macro files and subfolders in the project engineering folder; s2: analyzing the translation document into HashMap < String > types and loading the HashMap < String > types into a memory; s3: analyzing character strings in the character String macro file, and adding the analyzed character strings into an ArrayList < String > object so as to further generate a corresponding String file; s4: and determining the names of folders in which the output files are located according to the generated files in the formats, and meeting different requirements by inputting the names of the folders by self. The invention is used for improving the development efficiency, reducing errors caused by human factors and facilitating the maintenance of post-stage modularization.
Description
Technical Field
The invention relates to the technical field of IOS engineering files, in particular to an automatic multi-language file management method in the IOS project development process.
Background
Today, many APPs have demands of overseas markets, so that all character strings displayed to users in a project need to be translated and configuration work of localized files is performed. The conventional method is to write the source character string and the corresponding translation result into a file with a suffix of ". String" in a specified format (for example, "hello" = "hello";) so that the following problems exist: 1. often, the number of character strings in one project is many, hundreds of character strings are few, thousands of character strings are many, and the character strings are unified in one file, so that later management is inconvenient; 2. an app project is usually completed by cooperation of multiple persons, each is responsible for a part of relatively independent modules, and multiple persons commonly maintain the same document, which may have contradiction or conflict; 3. in the translation process, the same Chinese expression may need different translations in different scenes, but in the same document, the same Chinese expression cannot be used; 4. in the development process, when a developer writes character strings such as "@" hello "in codes, no prompt for code completion exists, errors are easy to occur in writing a large number of localized character strings, and once the character strings in a string document (such as @" hello | "are more than one punctuation mark) are not completely matched, correct translation results cannot be displayed.
Disclosure of Invention
In view of the above-mentioned drawbacks of the prior art, an object of the present invention is to provide an automated multi-language file management method in the process of developing IOS projects, which is used for improving development efficiency, reducing errors caused by human factors, and facilitating post-modular maintenance.
The invention aims at realizing the technical proposal, which is a multi-language file automatic management method in the development process of the IOS project, comprising the following steps:
s1: acquiring the contents of all character string macro files and subfolders in the project engineering folder;
s2: analyzing the translation document into HashMap < String > types and loading the HashMap < String > types into a memory;
s3: analyzing character strings in the character String macro file, and adding the analyzed character strings into an ArrayList < String > object so as to further generate a corresponding String file;
s4: and determining the names of folders in which the output files are located according to the generated files in the formats, and meeting different requirements by inputting the names of the folders by self.
Further, the step S1 includes:
s11: acquiring a folder object, and judging whether the acquired folder is an empty folder or not; if the file folder is empty, the step S12 is entered; otherwise, ending;
s12: starting traversing elements in the folder;
s13: acquiring the next element in the element array, and judging whether the next element is empty or not; if the air is empty, the step S14 is carried out; otherwise, ending;
s14: judging whether the element type is a file type, if so, entering step S15; otherwise, returning to the step S11;
s15: judging whether the folder name meets the characteristics, if so, adding the element into an output array, and returning to the step S13; and otherwise, ending.
Further, the step S2 further includes:
s21: creating an output stream object of the translation document;
s22: the output stream object reads the next row of character strings;
s23: judging whether the character string is empty or not, if so, entering step S24; otherwise, ending;
s24: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double oblique lines or does not contain equal signs; if yes, returning to the step S22; otherwise, step S25 is entered;
s25: respectively taking out the character strings at the left side and the right side according to the equal sign positions, and judging whether the lengths of the character strings at the two sides are not 0; if yes, the character strings on the left side and the right side are added into an output map in a key-value form, and the step S22 is returned; otherwise, the process returns to step S22.
Further, the step S3 includes:
s31: creating an output stream object of the character string macro file;
s32: the output stream object reads the next row of character strings and judges whether the character strings are empty or not; if the air is empty, the step S33 is performed; otherwise, ending;
s33: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double slashes or does not start with "# definition" or does not contain a '@'; if yes, return to step S32; otherwise, the process advances to step S34;
s34: intercepting character strings from '@' to the next double-quotation mark and removing head and tail spaces; judging that the character string length is not 0 and the array to be output does not contain the character string; if yes, go to step S35; otherwise, return to step S32;
s35: and adding the character string into the character string array to be output, and returning to the step S32.
Further, the step S4 includes:
s41: traversing the macro definition file array;
s42: acquiring a next macro definition file in the array, and judging whether an object in the file is empty or not; if yes, go to step S43; otherwise, ending;
s43: analyzing the macro file into a character string array and creating a file content character string content;
s44: traversing the character strings in the array;
s45: acquiring a next character string, and judging whether the character string is not empty; if it is empty, the process proceeds to step S46; otherwise, step S48 is entered;
s46: searching value in the HasMap object by taking the character string as a key, and judging whether the value is not empty; if the value exists, splicing the key and the value into a format character string required by the strings; otherwise, adding a double-diagonal stroke in front of the key character string;
s47: before the new character string, adding a line feed escape character, and then adding the new character string to the end of content, and returning to the step S45;
s48: judging whether the designated folder name exists in the same directory of the macro file, if not, creating a designated folder, and then entering step S49; otherwise, directly proceed to step S49;
s49: and generating a file with the same name as the character string macro file but with the suffix of the file, writing the content into the file, and returning to the step S42.
Due to the adoption of the technical scheme, the invention has the following advantages: by adopting the scheme of the invention, a developer can create a character string macro file according to specific requirements, the defined character string macro can be arbitrarily used in the development process, and all modifications can be completed in the macro file. When the localization character string is needed, only the address of the translation file and the directory address of the engineering folder are required to be specified, and a plurality of parameters, such as the prefix and the suffix of the file and the name of the folder required by the corresponding language, are formulated, so that the localization file can be automatically generated at the corresponding position, and the repeated labor time of a developer on multi-language localization is greatly reduced.
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention.
Drawings
The drawings of the present invention are described as follows:
FIG. 1 is a flow chart of a method for automatically managing multiple language files in an IOS project development process.
Fig. 2 is a schematic diagram of a recursive file acquisition process.
FIG. 3 is a schematic diagram of a process for parsing a translated document.
Fig. 4 is a schematic flow chart of parsing a string macro file.
FIG. 5 is a flow chart of generating a string file.
FIG. 6 is a schematic diagram of an interactive interface.
Detailed Description
The invention is further described below with reference to the drawings and examples.
Example 1, as shown in fig. 1 to 6; an automated multi-language file management method in the IOS project development process comprises the following steps:
s1: acquiring the contents of all character string macro files and subfolders in the project engineering folder;
s2: analyzing the translation document into HashMap < String > types and loading the HashMap < String > types into a memory;
s3: analyzing character strings in the character String macro file, and adding the analyzed character strings into an ArrayList < String > object so as to further generate a corresponding String file;
s4: and determining the names of folders in which the output files are located according to the generated files in the formats, and meeting different requirements by inputting the names of the folders by self.
The step S1 comprises the following steps:
s11: acquiring a folder object, and judging whether the acquired folder is an empty folder or not; if the file folder is empty, the step S12 is entered; otherwise, ending;
s12: starting traversing elements in the folder;
s13: acquiring the next element in the element array, and judging whether the next element is empty or not; if the air is empty, the step S14 is carried out; otherwise, ending;
s14: judging whether the element type is a file type, if so, entering step S15; otherwise, returning to the step S11;
s15: judging whether the folder name meets the characteristics, if so, adding the element into an output array, and returning to the step S13; and otherwise, ending.
The step S2 further includes:
s21: creating an output stream object of the translation document;
s22: the output stream object reads the next row of character strings;
s23: judging whether the character string is empty or not, if so, entering step S24; otherwise, ending;
s24: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double oblique lines or does not contain equal signs; if yes, returning to the step S22; otherwise, step S25 is entered;
s25: respectively taking out the character strings at the left side and the right side according to the equal sign positions, and judging whether the lengths of the character strings at the two sides are not 0; if yes, the character strings on the left side and the right side are added into an output map in a key-value form, and the step S22 is returned; otherwise, the process returns to step S22.
The step S3 includes:
s31: creating an output stream object of the character string macro file;
s32: the output stream object reads the next row of character strings and judges whether the character strings are empty or not; if the air is empty, the step S33 is performed; otherwise, ending;
s33: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double slashes or does not start with "# definition" or does not contain a '@'; if yes, return to step S32; otherwise, the process advances to step S34;
s34: intercepting character strings from '@' to the next double-quotation mark and removing head and tail spaces; judging that the character string length is not 0 and the array to be output does not contain the character string; if yes, go to step S35; otherwise, return to step S32;
s35: and adding the character string into the character string array to be output, and returning to the step S32.
The step S4 includes:
s41: traversing the macro definition file array;
s42: acquiring a next macro definition file in the array, and judging whether an object in the file is empty or not; if yes, go to step S43; otherwise, ending;
s43: analyzing the macro file into a character string array and creating a file content character string content;
s44: traversing the character strings in the array;
s45: acquiring a next character string, and judging whether the character string is not empty; if it is empty, the process proceeds to step S46; otherwise, step S48 is entered;
s46: searching value in the HasMap object by taking the character string as a key, and judging whether the value is not empty; if the value exists, splicing the key and the value into a format character string required by the strings; otherwise, adding a double-diagonal stroke in front of the key character string;
s47: before the new character string, adding a line feed escape character, and then adding the new character string to the end of content, and returning to the step S45;
s48: judging whether the designated folder name exists in the same directory of the macro file, if not, creating a designated folder, and then entering step S49; otherwise, directly proceed to step S49;
s49: and generating a file with the same name as the character string macro file but with the suffix of the file, writing the content into the file, and returning to the step S42.
By adopting the technical scheme, a developer can create a character string macro file according to specific requirements, the defined character string macro can be arbitrarily used in the development process, and all modifications can be completed in the macro file. When the localization character string is needed, only the address of the translation file and the directory address of the engineering folder are required to be specified, and a plurality of parameters, such as the prefix and the suffix of the file and the name of the folder required by the corresponding language, are formulated, so that the localization file can be automatically generated at the corresponding position, and the repeated labor time of a developer on multi-language localization is greatly reduced.
Example 2, as shown in fig. 1 to 6; the invention aims to provide a management method and a specific software implementation method in the multi-language localization development process of an IOS project, which are used for improving the development efficiency, reducing errors caused by human factors and facilitating the post-modular maintenance. In the project, a corresponding h suffix file is created according to the requirement of module division of a specific project, character strings to be displayed under the module are listed in a macro definition mode in the file, for example, "# definition hello@hello" ", when codes are written, the defined macro Hello" is used for replacing a source character string "@ Hello" ", so that a code complement prompt exists, and an input error prompts in the compiling process. The translation results of all the character strings in the project can be written in a file in a unified plain text format, each translation occupies one line, the character strings to be translated and the translation results are turned over by an equal sign ("="), and punctuation marks such as' hello! =hello-! ". The translation document, combined with the software designed by the invention (based on JAVA language), can generate a string file conforming to the multilingual localization specification at a corresponding position in the IOS engineering. The specific implementation method of the software is as follows:
1. and acquiring all the character string macro files (including contents in subfolders) under the engineering folder. The acquisition mode adopts a recursive traversal mode. In addition, when creating a string macro file, the file name should have a certain characteristic to distinguish the file from other.h files in the project, as shown in table 1:
table 1 custom fill out filename feature
| File prefix | Local | File suffix | .h | Containing characters |
Firstly, acquiring all file/folder lists under a project root directory, traversing each element, if the element type is the file type, judging whether the file name accords with a contracted naming rule (prefix, suffix or specific character string is contained), and if so, adding the file object into an output array, and judging the next element; if the element type is the folder type, acquiring a file/folder list in the folder, repeating the traversing method, and recursively calling the flow as shown in figure 2.
And analyzing the translation document into HashMap < String > types, and loading the HashMap < String > types into a memory for use. The format convention of the translation document is that a source character string and a translation character string are divided by an equal sign ("="), and a plurality of spaces are allowed before and after the source character string and the translation character string, so that a conversion result is not influenced. Each translation is distinguished in a line-feed fashion.
The analysis process of the translation file is that firstly, an input data stream object of the translation file is created through a bufferedReader class; then reading the character strings of each line in the file line by a readLine () method; when reading each line of character strings, firstly judging whether the line of character strings starts with "//" or not, if so, indicating that the line is annotated, and further reading the next line; if the symbol is not started by "//", judging whether a "=" symbol is contained, if the symbol is not contained, the line is regarded as having no translation content, the content of the next line is read, and when the symbol is contained by "=", the left character String of "=" is used as a key, and the right character String is used as a value and added into an object of HashMap < String, string > type for output; a specific implementation flow is shown in fig. 3.
3. And analyzing the character strings in the character string macro file, namely analyzing the 'hello' in the 'hello' character string. And adding the parsed character String into an ArrayList < String > object for further generation of a corresponding String file. An output stream Object of a string macro file is first created through the BufferedReader class, and then each row in the file is read through the Object, because the macro definition must be an independent row according to the file writing rules in the Object-c environment. After the space character of the first place is removed, if the character string of each line starts with double oblique lines, the character string of each line is annotated, and then the judgment of the next line is entered. Furthermore, according to the macro rule in the Object-C environment, each line must start with a "# definition" character string, and thus it is determined whether or not the line is a valid macro definition by judging whether or not to start with the character string. Under the condition that the line starts with "# definition", a character string from a ' @ ' character string to a double-quote ' ", wherein the character string is a character string needing to be locally translated in a string file; the specific implementation flow is shown in fig. 4.
4. A string format file is generated. According to the requirements of the strings file format, the source string and the translation string are respectively packed with double-quotation marks, and are connected by equal symbols (the source string is on the left and the translation string is on the right), and are terminated by a semicolon (';) symbol. And (3) traversing the character String array obtained in the step (3), taking the character String element as a key, inquiring a corresponding value in the HasMap < String, string > object analyzed in the step (2), if the value exists, splicing the key and the value into a format character String required by the strings, adding a line-changing escape character in front of the character String, and then adding the line-changing escape character into the end of the file character String to be output to the file.
According to the multi-language compilation mechanism of the IOS platform, it is determined what system language environment the translation in the file is applicable to, e.g., in the english environment, based on the folder name in which the files are located. Therefore, the names of the folders in which the files are located are determined according to the project requirements, and different requirements are met by inputting the folder names by themselves. As shown in the table 2 below,
table 2 custom input. Folder name where strings files reside
| Localized folder name | en.lproj |
The process of generating the strings file is shown in FIG. 5.
By adopting the scheme of the invention, a developer can create a character string macro file according to specific requirements, the defined character string macro can be arbitrarily used in the development process, and all modifications can be completed in the macro file. When the localization character string is needed, only the address of the translation file and the directory address of the engineering folder are required to be specified, and a plurality of parameters, such as the prefix and the suffix of the file and the name of the folder required by the corresponding language, are formulated, so that the localization file can be automatically generated at the corresponding position, and the repeated labor time of a developer on multi-language localization is greatly reduced.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical aspects of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the above embodiments, it should be understood by those of ordinary skill in the art that: modifications and equivalents may be made to the specific embodiments of the invention without departing from the spirit and scope of the invention, which is intended to be covered by the claims.
Claims (3)
1. An automatic management method for multilingual files in the IOS project development process is characterized by comprising the following steps:
s1: acquiring the contents of all character string macro files and subfolders in the project engineering folder;
s2: analyzing the translation document into HashMap < String > types and loading the HashMap < String > types into a memory;
s3: analyzing character strings in the character String macro file, and adding the analyzed character strings into an ArrayList < String > object so as to further generate a corresponding String file;
the step S3 includes:
s31: creating an output stream object of the character string macro file;
s32: the output stream object reads the next row of character strings and judges whether the character strings are empty or not; if the air is empty, the step S33 is performed; otherwise, ending;
s33: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double slashes or does not start with "# definition" or does not contain a '@'; if yes, return to step S32; otherwise, the process advances to step S34;
s34: intercepting character strings from '@' to the next double-quotation mark and removing head and tail spaces; judging that the character string length is not 0 and the array to be output does not contain the character string; if yes, go to step S35; otherwise, return to step S32;
s35: adding the character string into the character string array to be output, and returning to the step S32;
s4: determining the names of folders in which the output files are located according to the generated files in the formats, and meeting different requirements by inputting the names of the folders by self;
the step S4 includes:
s41: traversing the macro definition file array;
s42: acquiring a next macro definition file in the array, and judging whether an object in the file is empty or not; if yes, go to step S43; otherwise, ending;
s43: analyzing the macro file into a character string array and creating a file content character string content;
s44: traversing the character strings in the array;
s45: acquiring a next character string, and judging whether the character string is not empty; if it is empty, the process proceeds to step S46; otherwise, step S48 is entered;
s46: searching value in the HasMap object by taking the character string as a key, and judging whether the value is not empty; if the value exists, splicing the key and the value into a format character string required by the strings; otherwise, adding a double-diagonal stroke in front of the key character string;
s47: before the new character string, adding a line feed escape character, and then adding the new character string to the end of content, and returning to the step S45;
s48: judging whether the designated folder name exists in the same directory of the macro file, if not, creating a designated folder, and then entering step S49; otherwise, directly proceed to step S49;
s49: and generating a file with the same name as the character string macro file but with the suffix of the file, writing the content into the file, and returning to the step S42.
2. The method for automatically managing multilingual files in the IOS project development process according to claim 1, wherein the step S1 comprises:
s11: acquiring a folder object, and judging whether the acquired folder is an empty folder or not; if the file folder is empty, the step S12 is entered; otherwise, ending;
s12: starting traversing elements in the folder;
s13: acquiring the next element in the element array, and judging whether the next element is empty or not; if the air is empty, the step S14 is carried out; otherwise, ending;
s14: judging whether the element type is a file type, if so, entering step S15; otherwise, returning to the step S11;
s15: judging whether the folder name meets the characteristics, if so, adding the element into an output array, and returning to the step S13; and otherwise, ending.
3. The method for automatically managing multilingual files in the IOS project development process of claim 1, wherein the step S2 further comprises:
s21: creating an output stream object of the translation document;
s22: the output stream object reads the next row of character strings;
s23: judging whether the character string is empty or not, if so, entering step S24; otherwise, ending;
s24: removing space characters at the head and the tail of the character string, and judging whether the character string starts with double oblique lines or does not contain equal signs; if yes, returning to the step S22; otherwise, step S25 is entered;
s25: respectively taking out the character strings at the left side and the right side according to the equal sign positions, and judging whether the lengths of the character strings at the two sides are not 0; if yes, the character strings on the left side and the right side are added into an output map in a key-value form, and the step S22 is returned; otherwise, the process returns to step S22.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810960765.8A CN109947711B (en) | 2018-08-22 | 2018-08-22 | Automatic multi-language file management method in IOS project development process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810960765.8A CN109947711B (en) | 2018-08-22 | 2018-08-22 | Automatic multi-language file management method in IOS project development process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109947711A CN109947711A (en) | 2019-06-28 |
| CN109947711B true CN109947711B (en) | 2023-06-23 |
Family
ID=67005842
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810960765.8A Active CN109947711B (en) | 2018-08-22 | 2018-08-22 | Automatic multi-language file management method in IOS project development process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109947711B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111124479B (en) * | 2019-12-18 | 2024-03-22 | 北京像素软件科技股份有限公司 | Method and system for analyzing configuration file and electronic equipment |
| CN112181387A (en) * | 2020-09-09 | 2021-01-05 | 上海微亿智造科技有限公司 | Module management method in web multi-person collaborative development process |
| CN117707547B (en) * | 2024-02-05 | 2024-05-28 | 云筑信息科技(成都)有限公司 | Method for analyzing quotation relation among java items |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101276272A (en) * | 2007-03-28 | 2008-10-01 | 凌阳科技股份有限公司 | System and method for supporting multi-language user interface |
| CN103902275A (en) * | 2012-12-28 | 2014-07-02 | 北京新媒传信科技有限公司 | Method and system for achieving conversion of language versions of applications |
| CN105867920A (en) * | 2016-03-29 | 2016-08-17 | 海尔优家智能科技（北京）有限公司 | APP multi-language switching method and system |
| CN107463386A (en) * | 2017-08-31 | 2017-12-12 | 四川长虹电器股份有限公司 | A kind of management android applies multi-lingual method |
Family Cites Families (1)
| 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 |
-
2018
- 2018-08-22 CN CN201810960765.8A patent/CN109947711B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101276272A (en) * | 2007-03-28 | 2008-10-01 | 凌阳科技股份有限公司 | System and method for supporting multi-language user interface |
| CN103902275A (en) * | 2012-12-28 | 2014-07-02 | 北京新媒传信科技有限公司 | Method and system for achieving conversion of language versions of applications |
| CN105867920A (en) * | 2016-03-29 | 2016-08-17 | 海尔优家智能科技（北京）有限公司 | APP multi-language switching method and system |
| CN107463386A (en) * | 2017-08-31 | 2017-12-12 | 四川长虹电器股份有限公司 | A kind of management android applies multi-lingual method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109947711A (en) | 2019-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108762743B (en) | Data table operation code generation method and device | |
| CN109284145A (en) | The generation of multilingual configuration file and methods of exhibiting and device, equipment and medium | |
| CN109947711B (en) | Automatic multi-language file management method in IOS project development process | |
| CN110209387B (en) | Method and device for generating top-level HDL file and computer readable storage medium | |
| CN112379917A (en) | Browser compatibility improving method, device, equipment and storage medium | |
| CN115796190B (en) | Front-end internationalization multi-language conversion method and system based on vue and weback | |
| CN113076167A (en) | Code processing method and related equipment | |
| CN110109671A (en) | A kind of webpack label sizes pattern conversion method and device | |
| CN114281342A (en) | Automatic code generation method | |
| CN118245050A (en) | Front end frame assembly automatic conversion method, system, electronic device and storage medium | |
| CN110554860B (en) | Construction method and code generation method of software project natural language programming interface (NLI) | |
| CN111638930A (en) | Shell-based iOS multi-language script configuration method and system | |
| CN114238227A (en) | Chinese searching method, system and medium for software project source code | |
| CN113971044A (en) | Component document generation method, device, equipment and readable storage medium | |
| CN117270962B (en) | Method and device for processing coloring language, storage medium and electronic equipment | |
| CN117331963B (en) | Data access processing method and device, electronic equipment and storage medium | |
| CN116661794B (en) | Hardware description language semantic conversion method and device | |
| CN112148710B (en) | Micro-service library separation method, system and medium | |
| WO2022254487A1 (en) | Information processing program, information processing method, and information processing device | |
| CN114168189A (en) | Vue project code translation method, device and medium | |
| CN118193567A (en) | Method, device, equipment and medium for generating query statement and query service data | |
| CN117707673A (en) | Multilingual processing method, device, equipment and storage medium | |
| CN116384346A (en) | Text replacement method, device, terminal and medium based on HTML format | |
| CN117669502A (en) | Method, device and equipment for removing notes and printing sentences in webpage | |
| CN114048175A (en) | Multi-language file generation method and device |
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 |