Translation verification method and device, vehicle and storage medium

Abstract

The application relates to a translation verification method and device, a vehicle and a storage medium, and particularly relates to the technical field of verification. The method comprises the following steps: acquiring basic data of a vehicle-mounted application; determining a translation verification process and a translation verification language type of the vehicle-mounted application according to the basic data, wherein the translation verification process comprises multiple translation verification stages; for any translation verification stage, determining a translation comparison list corresponding to the translation verification stage and the translation verification language type and to-be-verified translation information; and combining the translation comparison list and the to-be-verified translation information to determine a translation verification result corresponding to the translation verification stage and the translation verification language type. The method avoids translation verification deviation caused by experience factors and improves the accuracy of the translation verification result. The method adapts to multilingual translation verification requirements, improves the problem that manual verification is limited by language reserves, standardizes the whole-process operation of vehicle-mounted application translation verification in a standardized and staged process, and improves the efficiency and quality of vehicle-mounted application translation verification work.

Description

Technical Field

[0001] This application relates to the field of verification technology, and in particular to a translation verification method, apparatus, vehicle, and storage medium. Background Technology

[0002] As vehicles are sold in the global market, they need to be used in dozens or even hundreds of countries and regions. Accordingly, in-vehicle applications need to support dozens or even hundreds of languages. Therefore, it is necessary to translate the content of in-vehicle applications into the languages ​​used in each region and to verify the translation.

[0003] Current technology typically involves translation and verification work being done manually by professionals. However, since professionals rely on their own experience for verification, the results are prone to bias due to limitations imposed by their experience. Furthermore, the number of languages ​​that professionals are proficient in is limited, making it difficult to meet the verification needs in multilingual scenarios. Ultimately, this affects the efficiency and quality of translation and verification. Summary of the Invention

[0004] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this application provides a translation verification method, apparatus, vehicle and storage medium.

[0005] Firstly, this application provides a translation verification method, including: Obtain basic data for in-vehicle applications; Based on the aforementioned basic data, the translation verification process and translation verification language type of the in-vehicle application are determined, and the translation verification process includes multiple translation verification stages. For any of the translation verification stages, determine the translation comparison list corresponding to the translation verification stage and the translation verification language type, as well as the translation verification information to be translated; By combining the translation comparison list with the translation verification information, the translation verification result corresponding to the translation verification stage and the translation verification language type is determined.

[0006] In a further optional implementation, the basic data includes an identifier and a version; The process of determining the translation verification process and translation verification language type for the in-vehicle application based on the aforementioned basic data includes: Obtain the mapping relationship of the translation verification process, as well as the mapping relationship of the translation verification language type; Based on the translation verification process mapping relationship, the translation verification process corresponding to the identifier and the version is determined, and the translation verification process is determined as the translation verification process of the vehicle application; Based on the translation verification language type mapping relationship, the translation verification language type corresponding to the identifier and the version is determined, and the translation verification language type is determined as the translation verification language type of the vehicle application.

[0007] In a further optional implementation, determining the translation comparison list corresponding to the translation verification stage and the translation verification language type includes: Obtain the mapping relationship of the translation comparison list; Based on the mapping relationship of the translation comparison list, the translation comparison list corresponding to the translation verification stage and the translation verification language type is determined.

[0008] In a further optional implementation, determining the translation verification information corresponding to the translation verification language type in the translation verification stage includes: Obtain the target image corresponding to the translation verification stage and the translation verification language type; From the target image, extract the translation verification information corresponding to the translation verification language type in the translation verification stage.

[0009] In a further optional implementation, the step of combining the translation comparison list with the translation verification information to determine the translation verification stage and the translation verification language type corresponding to the translation verification stage includes: Each translated string in the translation comparison list is matched and queried with the verification information to be translated; If each translation string in the translation comparison list is successfully matched in the translation verification information, then the translation verification result corresponding to the translation verification language type in the translation verification stage is determined to be passed; If any translation string fails to match, the translation verification result corresponding to the translation verification language type in the translation verification stage is determined to be unsuccessful.

[0010] In a further optional implementation, obtaining the target image corresponding to the translation verification stage and the translation verification language type includes: The image acquisition component acquires multiple target images corresponding to the translation verification stage and the translation verification language type at specified time intervals.

[0011] In a further optional implementation, the image acquisition component acquires multiple target images corresponding to the translation verification stage and the translation verification language type at specified time intervals, including: The image acquisition component acquires multiple initial images corresponding to the translation verification stage and the translation verification language type at specified time intervals. The initial images are compressed at a specified compression ratio to obtain multiple compressed images; The multiple compressed images are used as multiple target images corresponding to the translation verification language type in the translation verification stage.

[0012] In a further optional implementation, the step of extracting the translation verification information corresponding to the translation verification language type from the target image includes: Initial translation verification information is extracted from each of the multiple target images; Deduplication is performed on all initial verification information to be translated to obtain deduplicated translation verification information; The deduplication translation verification information is used as the translation verification information to be translated corresponding to the translation verification language type in the translation verification stage.

[0013] In a further optional implementation, after determining the translation verification result corresponding to the translation verification stage and the translation verification language type, the method further includes: The translation verification results corresponding to the translation verification stage and the translation verification language type are summarized to generate a translation verification review report.

[0014] Secondly, this application provides a translation verification device, comprising: The data acquisition module is used to acquire basic data for in-vehicle applications; The process language determination module is used to determine the translation verification process and translation verification language type of the vehicle application based on the basic data. The translation verification process includes multiple translation verification stages. The list information determination module is used to determine, for any of the translation verification stages, the translation comparison list corresponding to the translation verification stage and the translation verification language type, as well as the translation verification information to be translated. The verification result determination module is used to combine the translation comparison list with the verification information to be translated to determine the translation verification result corresponding to the translation verification stage and the translation verification language type.

[0015] Thirdly, this application provides a vehicle including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the translation verification method described in any of the first aspects.

[0016] Fourthly, this application provides a computer-readable storage medium storing a program for a translation verification method, wherein when the program for the translation verification method is executed by a processor, it implements the steps of the translation verification method described in any of the first aspects.

[0017] The beneficial effects of this application are: This application obtains basic data from in-vehicle applications, determines the translation verification process and language types based on this data, and utilizes a multi-stage translation verification process. For each stage, it matches a translation comparison list with the verification information for the corresponding language type, and combines this list with the verification information to determine the corresponding verification result. This replaces the traditional manual verification process that relies on the experience of professionals, avoiding the biases caused by experience-based factors and improving the accuracy of the verification results. Furthermore, this application adapts to different language types based on the basic data of in-vehicle applications, overcoming the limitations of traditional manual verification due to the limited number of languages ​​available. It adapts to the translation verification needs in multilingual scenarios, and the standardized, staged translation verification process regulates the entire translation verification process for in-vehicle applications, avoiding the subjectivity and limitations of manual verification and improving the efficiency and quality of in-vehicle application translation verification. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A schematic diagram illustrating the implementation process of a translation verification method provided in this application embodiment; Figure 2 This is a schematic diagram illustrating the implementation process of a method for determining the translation verification process and the translation verification language type for in-vehicle applications, provided in an embodiment of this application. Figure 3 A schematic diagram illustrating the implementation process of a method for determining a translation verification stage and a translation comparison list corresponding to the translation verification language type, provided in an embodiment of this application; Figure 4 A schematic diagram illustrating the implementation process of a method for determining the translation verification stage and the translation verification language type corresponding to the verification information to be translated, provided in an embodiment of this application; Figure 5 A schematic diagram illustrating the implementation process of a method for determining the translation verification stage and the translation verification language type corresponding to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a translation verification device provided in an embodiment of this application; Figure 7 This is a structural schematic diagram of a vehicle provided in an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0022] like Figure 1 The diagram shown is a schematic representation of the implementation process of a translation verification method provided in this application. This method is applied to vehicles and may specifically include the following steps: S101, obtains basic data for in-vehicle applications.

[0023] In this embodiment, basic data of the in-vehicle application is obtained; wherein, the basic data includes at least an identifier (e.g., application name) and version. By obtaining the basic data of the in-vehicle application, accurate data support can be provided for subsequent translation verification processes and the determination of the translation verification language type.

[0024] S102, based on the basic data, determine the translation verification process and the translation verification language type for in-vehicle applications. The translation verification process includes multiple translation verification stages.

[0025] In this embodiment, based on basic data, the translation verification process and language type for in-vehicle applications are determined. The translation verification process includes multiple stages. Obtaining the corresponding translation verification process and language type based on the basic data reduces translation verification deviations caused by differences in human experience. Furthermore, the translation verification process with multiple stages allows for refined breakdown of the translation verification work, adapting to translation verification scenarios with different language types, and improving the standardization and applicability of the translation verification work.

[0026] S103, for any translation verification stage, determine the translation comparison list corresponding to the translation verification stage and the translation verification language type, as well as the information to be translated and verified.

[0027] In this embodiment, for any translation verification stage, a translation comparison list corresponding to the translation verification stage and the language type to be verified, as well as the information to be translated and verified, are determined. Obtaining a dedicated translation comparison list and information to be translated and verified for each translation verification stage enables precise translation verification by stage and language, providing each stage with its own specific reference and effectively improving the precision of the translation verification process.

[0028] S104. Combining the translation comparison list and the translation verification information, determine the translation verification results corresponding to the translation verification stage and the translation verification language type.

[0029] In this embodiment, the translation verification result corresponding to the translation verification stage and the language type is determined by combining the translation comparison list and the information to be verified. The translation verification result is determined based on the determined translation comparison list and the information to be verified, replacing subjective manual translation verification with standardized data comparison, thus avoiding the influence of human experience bias on the translation verification result and improving the efficiency and quality of the translation verification work.

[0030] This application embodiment acquires basic data from in-vehicle applications, determines the translation verification process and language type based on this data, and utilizes a multi-stage translation verification process. For each stage, a translation comparison list and verification information for the corresponding language type are matched, and the corresponding verification result is determined by combining these two lists. This replaces the traditional manual verification process that relies on the experience of professionals, avoiding the biases caused by experience-based factors and improving the accuracy of the verification results. Furthermore, this application embodiment adapts to different language types based on the basic data of in-vehicle applications, overcoming the limitations of traditional manual verification due to the limited number of languages ​​available. It adapts to the translation verification needs in multilingual scenarios, and the standardized, staged translation verification process regulates the entire translation verification process for in-vehicle applications, avoiding the subjectivity and limitations of manual verification and improving the efficiency and quality of in-vehicle application translation verification.

[0031] In the embodiments of this application, such as Figure 2 As shown, the specific execution steps of S102, "Based on the basic data, determine the translation verification process and translation verification language type for the vehicle application. The translation verification process includes multiple translation verification stages," are as follows: S201, obtain the translation verification process mapping relationship and the translation verification language type mapping relationship.

[0032] In this embodiment, the vehicle pre-stores translation verification process mapping relationships and translation verification language type mapping relationships; the vehicle then retrieves these mapping relationships from its storage. The translation verification process mapping relationships include multiple sets of identifiers, versions, and translation verification processes corresponding one-to-one with each version. The translation verification language type mapping relationships include multiple sets of identifiers, versions, and translation verification language types corresponding one-to-one with each version.

[0033] For example, the mapping relationship of the translation verification process is shown in Table 1:

[0034] Table 1 For example, the language type mapping relationship for translation verification is shown in Table 2:

[0035] Table 2 S202, based on the translation verification process mapping relationship, determines the translation verification process corresponding to the identifier and version, and identifies the translation verification process as the translation verification process for in-vehicle applications.

[0036] Based on the translation verification process mapping relationship, the translation verification process corresponding to the identifier and version is determined, and this process is then used as the translation verification process for in-vehicle applications. Specifically, the identifier and version are matched within the translation verification process mapping relationship, and the successfully matched translation verification process is designated as the translation verification process corresponding to that identifier and version. By relying on the standardized translation verification process mapping relationship and combining it with the identifier and version of the in-vehicle application to determine a dedicated translation verification process, the standardized translation verification process replaces subjective manual judgment, reducing errors caused by human factors and ensuring the accuracy and adaptability of the in-vehicle application translation verification process.

[0037] S203, based on the translation verification language type mapping relationship, determines the translation verification language type corresponding to the identifier and version, and determines the translation verification language type as the translation verification language type for the vehicle application.

[0038] Based on the translation verification language type mapping relationship, the translation verification language type corresponding to the identifier and version is determined, and this translation verification language type is then designated as the translation verification language type for in-vehicle applications. Specifically, the identifier and version are matched within the translation verification language type mapping relationship, and the successfully matched translation verification language type is designated as the translation verification language type corresponding to the identifier and version. By relying on the translation verification language type mapping relationship and combining it with the basic parameters of in-vehicle applications to determine a dedicated translation verification language type, it can adapt to the language verification needs of different in-vehicle applications, overcome the limitations of manual language reserves, and effectively broaden the applicable scenarios for translation verification work.

[0039] In the embodiments of this application, such as Figure 3 As shown, the specific execution steps of "determining the translation comparison list corresponding to the translation verification stage and the translation verification language type" in S103 are as follows: S301, obtain the translation comparison list mapping relationship.

[0040] In this embodiment, the vehicle stores a translation comparison list mapping relationship in advance; the translation comparison list mapping relationship is obtained from the vehicle storage; and standardized data support is provided for the subsequent determination of the translation comparison list.

[0041] For example, the mapping relationship of the translation comparison list is shown in Table 3:

[0042] Table 3 S302, Based on the translation comparison list mapping relationship, determine the translation comparison list corresponding to the translation verification stage and the translation verification language type.

[0043] In this embodiment, a translation comparison list corresponding to each translation verification stage and language type is determined based on the translation comparison list mapping relationship. Specifically, the translation verification stage and language type are matched in the translation comparison list mapping relationship, and the successfully matched translation comparison list is determined as the translation comparison list corresponding to each translation verification stage and language type. By relying on the translation comparison list mapping relationship to determine a translation comparison list specific to each translation verification stage and language type, standardized translation verification reference content can be invoked for different verification scenarios, achieving accurate correspondence between different translation verification stages and different translation verification language types, effectively improving the relevance and standardization of the translation verification reference.

[0044] In the embodiments of this application, such as Figure 4 As shown, the specific execution steps of "determining the translation verification stage and the translation verification language type corresponding to the verification information to be translated" in S103 are as follows: S401, Obtain the target image corresponding to the translation verification stage and the translation verification language type.

[0045] In this embodiment, target images corresponding to the translation verification stage and the translation verification language type are obtained. By obtaining target images corresponding to the translation verification stage and the translation verification language type, the data source carrier corresponding to each translation verification stage of the translation verification work is accurately located, providing an accurate carrier for the extraction of the translation verification information to be translated in subsequent translation verification stages.

[0046] Specifically, an image acquisition component (such as Android Debug Bridge, ADB) is used to acquire multiple target images corresponding to the translation verification stage and the language type being verified, at specified time intervals (e.g., 0.2 seconds). The specified time interval is generated based on the statistical response time of the in-vehicle infotainment system (IVS) application, adapting to the application's interface refresh rate and effectively preventing omissions of verification information. The number of target images is generated based on the IVS application's interface refresh frequency and verification scenario requirements, adapting to the application's dynamic display rhythm, avoiding information gaps associated with single-image acquisition, and ensuring the completeness and comprehensiveness of the extracted verification information. This provides a complete image data foundation for subsequent translation verification work combined with the translation comparison list.

[0047] Furthermore, using an image acquisition component, multiple initial images corresponding to the translation verification stage and the translation verification language type are acquired at specified time intervals. These initial images are then compressed at a specified compression ratio (e.g., 70%) to obtain multiple compressed images. These compressed images are then used as multiple target images corresponding to the translation verification stage and the translation verification language type. The specified compression ratio is generated based on the vehicle's image resolution, adapting to the characteristics of vehicle image acquisition and display. While ensuring the clarity of the target images and preserving details, this effectively reduces the image data size, improves the overall processing efficiency of image acquisition and subsequent information extraction, and provides efficient and reliable image data support for the accurate extraction of information to be translated and verified.

[0048] S402, Extract the translation verification information corresponding to the translation verification language type from the target image.

[0049] In this embodiment, translation verification information corresponding to the translation verification stage and the translation verification language type is extracted from the target image. Extracting this information from the acquired target image ensures accurate acquisition of the required translation verification information for each stage of the translation verification process, guaranteeing that the extracted information matches each stage and providing complete and effective data support for subsequent translation verification work based on the translation comparison list.

[0050] Specifically, initial verification information to be translated is extracted from multiple target images; all initial verification information to be translated is deduplicated to obtain deduplicated verification information; this deduplicated verification information is used as the verification information to be translated for the current verification stage and the corresponding language type. This process eliminates duplicate verification content generated during the acquisition of multiple target images, ensuring the completeness and accuracy of the verification information to be translated while avoiding interference from redundant information. It guarantees the uniqueness and accuracy of the verification information to be translated for the current verification stage and the corresponding language type, further improving the effectiveness and standardization of subsequent verification work. This provides accurate and reliable data support for subsequent precise verification work based on the translation comparison list.

[0051] Furthermore, multiple target images are input into a preset translation verification model, and the preset translation verification model extracts initial verification information to be translated from the multiple target images respectively.

[0052] In the embodiments of this application, such as Figure 5 As shown, the specific execution steps of "combining the translation comparison list and the translation verification information to determine the translation verification stage and the translation verification language type corresponding to the translation verification result" in S104 are as follows: S501, Match each translated string in the translation comparison list with the verification information to be translated.

[0053] In this embodiment, each translated string in the translation comparison list is matched with the verification information to be translated. By matching all standard translated strings in the translation comparison list with the verification information to be translated one by one, the standardized content and the actual in-vehicle display content are compared item by item, clarifying the correspondence between the standardized content and the actual in-vehicle display content. This provides a quantitative and reliable comparison basis for the subsequent accurate determination of the translation verification results, ensuring the comprehensiveness and rigor of the verification comparison process.

[0054] Furthermore, using a pre-defined translation verification model, each translated string in the translation comparison list is matched and queried against the verification information to be translated.

[0055] S502, if all the translation strings in the translation comparison list are successfully matched in the translation verification information, then the translation verification result corresponding to the translation verification language type is determined to be passed.

[0056] In this embodiment of the application, if all the translation strings in the translation comparison list are successfully matched in the translation verification information, the translation verification result corresponding to the translation verification language type is determined to be passed; if all translation strings are successfully matched, the verification is determined to be passed, and the in-vehicle display text corresponding to the translation verification language type is completely in line with the standard translation specifications, and there are no translation omissions, mistranslations, or omissions.

[0057] S503, if any translation string fails to match, the translation verification result corresponding to the translation verification language type is determined to be unsuccessful.

[0058] In this embodiment, if any translation string fails to match, the translation verification result corresponding to the translation verification stage and the translation verification language type is determined to be unsuccessful. By determining that verification fails for any case of translation string mismatch, the system accurately identifies translation omissions, mistranslations, and omissions in the translation verification stage and the translation verification language type, preventing flawed translations from remaining in the vehicle system application and ensuring the translation verification quality of each stage and each translation verification language type.

[0059] In this embodiment, the translation verification results corresponding to the translation verification stages and language types are summarized to generate a translation verification review report. This integrates all verification data and judgment results from each translation verification stage and language type, enabling systematic organization and visual storage of translation verification results. It comprehensively records the translation verification status of in-vehicle multilingual text, providing a complete and traceable basis for the optimization, version iteration, and quality review of in-vehicle translation content, thereby improving the integrity and standardization of in-vehicle translation verification work.

[0060] In this embodiment of the application, the translation verification model generation process is as follows: In this embodiment, the translation verification model is based on a multimodal large language model; for example, the GPT-4o pre-trained model with visual image understanding, multilingual text recognition, and semantic matching decision-making capabilities is selected.

[0061] Sample data covering different identifiers and versions of in-vehicle applications was collected to construct a training dataset for the translation verification model. The sample data covers all translation verification stages and all language types. Each sample set includes the target image for the corresponding scenario, the information to be translated and verified, a translation comparison list, and corresponding translation verification result labels. Specifically, target image samples were prepared according to specified time intervals and compression ratios, consistent with the target image generation standards in the actual translation verification process. Translation verification result labels were generated by professional verifiers according to standardized translation verification procedures, ensuring the accuracy and standardization of the label data. By constructing a standardized training dataset covering all scenarios and types, comprehensive data support is provided for model training, ensuring that the trained model can adapt to the translation verification needs of various in-vehicle applications.

[0062] The training dataset is input into the model base, with the training objective of achieving the entire process of "extracting translation verification information from target images, querying string matching in translation comparison lists, and automatically determining translation verification results." The model's network parameters are iteratively updated to specifically enhance its visual image understanding, multilingual text recognition, and semantic matching decision-making capabilities. During training, balanced training weights are assigned to samples at each translation verification stage and for each translation verification language type to avoid scenario adaptation bias and ensure stable verification performance across different in-vehicle applications, verification stages, and language scenarios.

[0063] A validation dataset is drawn from the training dataset according to a preset ratio. After each round of training, the performance of the current model is validated using the validation dataset. Validation metrics include the accuracy of extracting the validation information to be translated, the accuracy of matching the translated string, and the accuracy of judging the translation validation result. Based on the validation results, the model parameters are tuned. For translation validation stages and language types with low validation accuracy, sample data for corresponding scenarios is supplemented and reinforcement training is carried out to gradually improve the model's translation validation accuracy across all scenarios.

[0064] When the accuracy rates of information extraction, translation string matching, and translation verification result determination in the verification dataset all reach the preset accuracy thresholds, and the fluctuation range of the verification metrics in consecutive preset training rounds is less than the preset fluctuation threshold, model training is terminated, and the final translation verification model is generated. The preset accuracy threshold is set according to the quality requirements of in-vehicle application translation verification, and the preset fluctuation threshold is set according to the model's operational stability requirements, ensuring that the generated translation verification model has both high verification accuracy and high operational stability, and can be deployed on vehicles to perform standardized in-vehicle application translation verification tasks.

[0065] A detailed example of an embodiment in this application is shown below: Before the release of the in-vehicle navigation application V1.0.0, a multilingual localization quality verification was conducted, covering five languages: English, Japanese, Korean, French, and German. The verification process included basic text translation verification, interface copy translation verification, scenario-based wording translation verification, and final compliance review, to identify and eliminate mistranslations, omissions, and abnormal translation loading issues.

[0066] Obtain basic data for the in-vehicle navigation application, including information that identifies it as an in-vehicle navigation application and its version is V1.0.0. Also, upload the APK installation package of the in-vehicle navigation application V1.0.0 to provide accurate data support for subsequent translation verification process matching, translation verification language type determination, and translation comparison list construction.

[0067] The server parses each in-vehicle application APK and configures process rules, generating translation verification process mapping relationships and translation verification language type mapping relationships, and synchronizes them to the vehicle-side storage. It then retrieves these mapping relationships from the vehicle-side storage. The translation verification process mapping relationship includes multiple sets of identifiers, versions, and translation verification processes corresponding one-to-one with each version. The translation verification language type mapping relationship includes multiple sets of identifiers, versions, and translation verification language types corresponding one-to-one with each version.

[0068] The translation verification process mapping relationship contains a set of corresponding data: when the identifier is an in-vehicle navigation application and the version is V1.0.0, the corresponding translation verification process is the navigation translation verification process, which includes the basic text translation verification stage, the interface copy translation verification stage, the scenario dialogue translation verification stage, and the final compliance review stage.

[0069] The translation verification language type mapping relationship contains a set of corresponding data: when the identifier is an in-vehicle navigation application and the version is V1.0.0, the corresponding translation verification language type is English, Japanese, Korean, French, and German.

[0070] The system matches the in-vehicle navigation application and its version V1.0.0 within the translation verification process mapping relationship. Upon successful matching, the corresponding translation verification process is designated as the navigation translation verification process, and this process is then defined as the translation verification process for the in-vehicle navigation application V1.0.0. By relying on standardized mapping relationships to match dedicated verification processes, a standardized process replaces subjective human judgment, reducing human error and ensuring the accuracy and adaptability of the translation verification process.

[0071] Matching the identifier of the in-vehicle navigation application and version V1.0.0 in the translation verification language type mapping relationship, after successful matching, determining that the corresponding translation verification language types are English, Japanese, Korean, French and German, and determining the above languages as the translation verification language types of the in-vehicle navigation application V1.0.0. Matching exclusive verification languages based on the mapping relationship can meet the multilingual release requirements of in-vehicle navigation applications, get rid of the limitation of manual language reserve, and broaden the applicable scenarios of verification work.

[0072] A detailed description is given by taking the basic text translation verification stage and the English language as an example, and the execution logic of other translation verification stages and languages is consistent: The server parses the APK installation package of the in-vehicle navigation application V1.0.0, extracts all string resources in res / values / strings.xml, constructs the translation comparison list mapping relationship based on the string resources and synchronizes it to the vehicle terminal for storage; the translation comparison list mapping relationship is obtained from the vehicle terminal storage, which provides standardized data support for the determination of the translation comparison list.

[0073] The translation comparison list mapping relationship includes a set of corresponding data: when the identifier and version are the in-vehicle navigation application V1.0.0, the translation verification stage is the basic text translation verification stage, and the translation verification language types are English, Japanese, Korean, French and German, the corresponding translation comparison list is the basic text translation comparison list; the basic text translation comparison list includes the English entries Welcome, Start Navigation, Route Planning, Traffic Reminder, the Japanese entries ようこそ, ナビゲーション開始, ルート計画, 交通通知, the Korean entries , , , French entries: Bienvenue, Lancer la navigation, Planification d'itinéraire, Alertetrafic; German entries: Willkommen, Navigation starten, Routenplanung, Verkehrshinweis.

[0074] The basic text translation verification stage matches the English text within a translation comparison list mapping relationship. Successfully matched comparison lists are then used to define the corresponding English text comparison lists for the basic text translation verification stage, including lists for Welcome, Start Navigation, Route Planning, and Traffic Reminder. Based on this mapping relationship, a dedicated comparison list is created, and standardized reference content is invoked for each verification scenario, improving the relevance and standardization of the verification reference.

[0075] Using the Android Debug Bridge (ADB), multiple initial images corresponding to the English text are obtained at specified time intervals of 0.2 seconds during the basic text translation verification stage. These initial images are then compressed at a compression ratio of 70% to obtain multiple compressed images. These compressed images are then used as multiple target images corresponding to the English text during the basic text translation verification stage.

[0076] The specified time interval is generated based on the statistical response time of the vehicle-mounted application, adapting to the refresh rhythm of the vehicle-mounted application interface and avoiding the omission of information to be translated and verified; the specified compression ratio is generated based on the resolution of the vehicle-mounted image, reducing the image data size while ensuring image clarity and preserving details, thereby improving the overall processing efficiency of image acquisition and information extraction.

[0077] Multiple target images are input into a preset translation verification model. The model extracts initial verification information from each target image. All initial verification information is deduplicated to obtain deduplicated translation verification information. This deduplicated translation verification information is then used as the corresponding verification information for the English text in the basic text translation verification stage.

[0078] By eliminating duplicate verification content generated from multiple image collections through deduplication, redundant information interference is avoided while ensuring the integrity and completeness of the information. This guarantees the uniqueness and accuracy of the information to be translated and verified, providing accurate and reliable data support for subsequent verification work.

[0079] By using a pre-set translation verification model, the Welcome, StartNavigation, Route Planning, and Traffic Reminder in the basic text translation comparison list are matched and queried with the information to be translated and verified one by one. This enables a step-by-step comparison between the standard translation content and the actual content displayed on the vehicle's infotainment system, providing a quantitative and reliable basis for the verification result determination and ensuring the comprehensiveness and rigor of the verification and comparison process.

[0080] If Welcome, Start Navigation, Route Planning, and Traffic Reminder all match successfully, the translation verification result of the basic text translation verification stage and the corresponding English is determined to be passed. This means that the in-vehicle display text at the current stage fully complies with the standard translation specifications and there are no translation omissions, mistranslations, or missing translations.

[0081] If any translation string fails to match, the translation verification result of the basic text translation verification stage and the corresponding English text is determined to be unsuccessful. This accurately identifies translation deficiencies, mistranslations, and omissions in the corresponding language at the current stage, preventing flawed translations from being stored in the vehicle's infotainment system and ensuring the quality of translation verification.

[0082] Repeat the above process to complete the interface text translation verification stage, scenario dialogue translation verification stage, final compliance review stage, and all verification work for Japanese, Korean, French, and German languages. Then, summarize the translation verification results for all translation verification stages and all translation verification language types to generate a translation verification review report. This report fully records the translation verification status of multilingual text in the in-vehicle navigation application, providing a complete and traceable basis for translation content optimization and rectification, version iteration, and quality review, thereby improving the completeness and standardization of in-vehicle application translation verification work.

[0083] In another embodiment of this application, a translation verification device is also provided, the device as follows: Figure 6 As shown, it includes: a data acquisition module 601, a process language determination module 602, a list information determination module 603, and a verification result determination module 604.

[0084] The data acquisition module 601 is used to acquire basic data for in-vehicle applications.

[0085] The process language determination module 602 is used to determine the translation verification process and translation verification language type of the vehicle application based on the basic data. The translation verification process includes multiple translation verification stages.

[0086] The list information determination module 603 is used to determine, for any of the translation verification stages, the translation comparison list corresponding to the translation verification language type and the information to be translated and verified.

[0087] The verification result determination module 604 is used to combine the translation comparison list with the verification information to be translated to determine the translation verification result corresponding to the translation verification stage and the translation verification language type.

[0088] In another embodiment of this application, a vehicle is also provided, characterized in that it includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus. Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the translation verification method described in any of the foregoing method embodiments.

[0089] The vehicle provided in this application embodiment uses a processor that executes a program stored in memory to obtain basic data of the in-vehicle application. Based on this basic data, the processor determines the translation verification process and language type for the in-vehicle application. Relying on a translation verification process that includes multiple stages, it matches a translation comparison list and verification information for each stage with the corresponding language type. The processor then combines the translation comparison list and the verification information to determine the corresponding translation verification result. This replaces the traditional manual translation verification method that relies on the experience of professionals, avoiding the biases caused by experience-based factors in manual translation verification and improving the accuracy of the verification results. Furthermore, this application adapts to different language types based on the basic data of the in-vehicle application, overcoming the limitations of traditional manual translation verification due to the limited number of languages ​​available. It adapts to the translation verification needs in multilingual scenarios, and the standardized, staged translation verification process regulates the entire process of in-vehicle application translation verification, avoiding the subjectivity and limitations of manual translation verification and improving the efficiency and quality of in-vehicle application translation verification.

[0090] The communication bus 704 mentioned in the above-mentioned vehicle can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus 704 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0091] Communication interface 702 is used for communication between the aforementioned vehicle and other devices.

[0092] The memory 703 may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0093] The processor 701 mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0094] In another embodiment of this application, a computer-readable storage medium is also provided, on which a program for a translation verification method is stored, wherein when the program for the translation verification method is executed by a processor, it implements the steps of the translation verification method described in any of the foregoing method embodiments.

[0095] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0096] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A translation verification method, characterized in that, include: Acquire basic data for in-vehicle applications; Based on the aforementioned basic data, the translation verification process and translation verification language type of the in-vehicle application are determined, and the translation verification process includes multiple translation verification stages. For any of the translation verification stages, determine the translation comparison list corresponding to the translation verification stage and the translation verification language type, as well as the translation verification information to be translated; By combining the translation comparison list with the translation verification information, the translation verification result corresponding to the translation verification stage and the translation verification language type is determined.

2. The method according to claim 1, characterized in that, The basic data includes an identifier and a version; The process of determining the translation verification process and translation verification language type for the in-vehicle application based on the aforementioned basic data includes: Obtain the mapping relationship of the translation verification process, as well as the mapping relationship of the translation verification language type; Based on the translation verification process mapping relationship, the translation verification process corresponding to the identifier and the version is determined, and the translation verification process is determined as the translation verification process of the vehicle application; Based on the translation verification language type mapping relationship, the translation verification language type corresponding to the identifier and the version is determined, and the translation verification language type is determined as the translation verification language type of the vehicle application.

3. The method according to claim 1, characterized in that, The method for determining the translation comparison list corresponding to the translation verification stage and the translation verification language type includes: Obtain the mapping relationship of the translation comparison list; Based on the mapping relationship of the translation comparison list, the translation comparison list corresponding to the translation verification stage and the translation verification language type is determined.

4. The method according to claim 3, characterized in that, The step of determining the translation verification stage and the translation verification language type corresponding to the translation verification information to be translated includes: Obtain the target image corresponding to the translation verification stage and the translation verification language type; From the target image, extract the translation verification information corresponding to the translation verification language type in the translation verification stage.

5. The method according to claim 4, characterized in that, The step of combining the translation comparison list with the translation verification information to determine the translation verification stage and the translation verification language type to determine the translation verification result includes: Each translated string in the translation comparison list is matched and queried with the verification information to be translated; If each translation string in the translation comparison list is successfully matched in the translation verification information, then the translation verification result corresponding to the translation verification language type in the translation verification stage is determined to be passed; If any translation string fails to match, the translation verification result corresponding to the translation verification language type in the translation verification stage is determined to be unsuccessful.

6. The method according to claim 4, characterized in that, The step of obtaining the target image corresponding to the translation verification stage and the translation verification language type includes: The image acquisition component acquires multiple target images corresponding to the translation verification stage and the translation verification language type at specified time intervals.

7. The method according to claim 6, characterized in that, The image acquisition component acquires multiple target images corresponding to the translation verification stage and the translation verification language type at specified time intervals, including: The image acquisition component acquires multiple initial images corresponding to the translation verification stage and the translation verification language type at specified time intervals. The initial images are compressed at a specified compression ratio to obtain multiple compressed images; The compressed images are used as target images corresponding to the translation verification language type in the translation verification stage.

8. The method according to claim 7, characterized in that, The step of extracting the translation verification information corresponding to the translation verification language type from the target image includes: Initial translation verification information is extracted from each of the multiple target images; Deduplication is performed on all initial verification information to be translated to obtain deduplicated translation verification information; The deduplication translation verification information is used as the translation verification information to be translated corresponding to the translation verification language type in the translation verification stage.

9. The method according to any one of claims 1 to 8, characterized in that, After determining the translation verification result corresponding to the translation verification stage and the translation verification language type, the method further includes: The translation verification results corresponding to the translation verification stage and the translation verification language type are summarized to generate a translation verification review report.

10. A translation verification device, characterized in that, include: The data acquisition module is used to acquire basic data for in-vehicle applications; The process language determination module is used to determine the translation verification process and translation verification language type of the vehicle application based on the basic data. The translation verification process includes multiple translation verification stages. The list information determination module is used to determine, for any of the translation verification stages, the translation comparison list corresponding to the translation verification stage and the translation verification language type, as well as the translation verification information to be translated. The verification result determination module is used to combine the translation comparison list with the verification information to be translated to determine the translation verification result corresponding to the translation verification stage and the translation verification language type.

11. A vehicle, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the translation verification method according to any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program for a translation verification method, which, when executed by a processor, implements the steps of the translation verification method according to any one of claims 1-9.

Images