!22449 翻译已完成21307+21821+21840+22024

Merge pull request !22449 from shawn_he/21821-d

en/application-dev/dfx/hitracemeter-guidelines.md

@@ -17,11 +17,11 @@ hiTraceMeter provides APIs for system performance tracing. You can call the APIs
 
 ## Constraints
 
-Due to the asynchronous I/O feature of JS, the hiTraceMeter module provides only asynchronous APIs.
+- Due to the asynchronous I/O feature of JS, the hiTraceMeter module provides only asynchronous APIs.
 
 ## Available APIs
 
-The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference](../reference/apis/js-apis-hitracemeter.md).
+The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference]( ../reference/apis/js-apis-hitracemeter.md).
 
 **APIs for performance tracing**
 
@@ -35,51 +35,11 @@ The performance tracing APIs are provided by the **hiTraceMeter** module. For de
 
 In this example, distributed call chain tracing begins when the application startup execution page is loaded and stops when the service usage is completed.
 
-1. Create a JS application project. In the displayed **Project** window, choose **entry** > **src** > **main** > **js** > **default** > **pages** > **index**, and double-click **index.js**. Add the code to implement performance tracing upon page loading. The sample code is as follows:
+1. Create a project, and call hiTraceMeter APIs in the service logic to implement performance tracing.
  
-   ```js
-   import hiTraceMeter from '@ohos.hiTraceMeter'
+   - **ArkTS application project**
 
-   export default {
-       data: {
-           title: ""
-       },
-       onInit() {
-           this.title = this.$t('strings.world');
-
-           // Start trace tasks with the same name concurrently.
-           hiTraceMeter.startTrace("business", 1);
-           // Keep the service process running.
-           console.log(`business running`);
-           hiTraceMeter.startTrace("business", 2);  // Start the second trace task with the same name while the first task is still running. The tasks are running concurrently and therefore their taskId must be different.
-           // Keep the service process running.
-           console.log(`business running`);
-           hiTraceMeter.finishTrace("business", 1);
-           // Keep the service process running.
-           console.log(`business running`);
-           hiTraceMeter.finishTrace("business", 2);
-
-           // Start trace tasks with the same name in serial mode.
-           hiTraceMeter.startTrace("business", 1);
-           // Keep the service process running.
-           console.log(`business running`);
-           hiTraceMeter.finishTrace("business", 1);  // End the first trace task.
-           // Keep the service process running.
-           console.log(`business running`);
-           hiTraceMeter.startTrace("business", 1);   // Start the second trace task with the same name in serial mode.
-           // Keep the service process running.
-           console.log(`business running`);
-
-           let traceCount = 3;
-           hiTraceMeter.traceByValue("myTestCount", traceCount);
-           traceCount = 4;
-           hiTraceMeter.traceByValue("myTestCount", traceCount);
-           hiTraceMeter.finishTrace("business", 1);
-       }
-   }
-   ```
-
-2. Create an ArkTs application project. In the displayed **Project** window, choose **entry** > **src** > **main** > **ets** > **pages** > **index**, and double-click **index.js**. Add the code to implement performance tracing upon page loading. For example, if the name of the trace task is **HITRACE\_TAG\_APP**, the sample code is as follows:
+      Create an ArkTS application project. In the displayed **Project** window, choose **entry** > **src** > **main** > **ets** > **pages** > **index**, and double-click **index.js**. Add the code to implement performance tracing upon page loading. For example, if the name of the trace task is **HITRACE\_TAG\_APP**, the sample code is as follows:
     
       ```ts
       import hitrace from '@ohos.hiTraceMeter';
@@ -142,7 +102,53 @@ In this example, distributed call chain tracing begins when the application star
       }
       ```
 
-3. Click the run button on the application page. Then, run the following commands in sequence in shell:
+   - **JS application project**
+
+      Create a JS application project. In the displayed **Project** window, choose **entry** > **src** > **main** > **js** > **default** > **pages** > **index**, and double-click **index.js**. Add the code to implement performance tracing upon page loading. The sample code is as follows:
+
+      ```js
+      import hiTraceMeter from '@ohos.hiTraceMeter'
+
+      export default {
+          data: {
+              title: ""
+          },
+          onInit() {
+              this.title = this.$t('strings.world');
+
+              // Start trace tasks with the same name concurrently.
+              hiTraceMeter.startTrace("business", 1);
+              // Keep the service process running.
+              console.log(`business running`);
+              hiTraceMeter.startTrace("business", 2);  // Start the second trace task with the same name while the first task is still running. The tasks are running concurrently and therefore their taskId must be different.
+              // Keep the service process running.
+              console.log(`business running`);
+              hiTraceMeter.finishTrace("business", 1);
+              // Keep the service process running.
+              console.log(`business running`);
+              hiTraceMeter.finishTrace("business", 2);
+
+              // Start trace tasks with the same name in serial mode.
+              hiTraceMeter.startTrace("business", 1);
+              // Keep the service process running.
+              console.log(`business running`);
+              hiTraceMeter.finishTrace("business", 1);  // End the first trace task.
+              // Keep the service process running.
+              console.log(`business running`);
+              hiTraceMeter.startTrace("business", 1);   // Start the second trace task with the same name in serial mode.
+              // Keep the service process running.
+              console.log(`business running`);
+
+              let traceCount = 3;
+              hiTraceMeter.traceByValue("myTestCount", traceCount);
+              traceCount = 4;
+              hiTraceMeter.traceByValue("myTestCount", traceCount);
+              hiTraceMeter.finishTrace("business", 1);
+          }
+      }
+      ```
+ 
+2. Click the run button on the application page. Then, run the following commands in sequence in shell:
  
    ```shell
    hdc shell

en/application-dev/reference/errorcodes/errorcode-i18n.md

-# i18n Error Codes
+# I18N Error Codes
 
 > **NOTE**
 >
@@ -8,7 +8,7 @@
 
 **Error Message**
 
-Unspported para value.
+param value not valid
 
 **Description**
 
@@ -21,21 +21,3 @@ Invalid parameter values are probably due to incorrect parameter types.
 **Solution**
 
 Check whether the parameter type is correct.
-
-## 890002 Incorrect Configuration Option
-
-**Error Message**
-
-Unspported option value.
-
-**Description**
-
-This error code is reported if an I18N API is called with invalid option values specified.
-
-**Possible Causes**
-
-Invalid option values are probably due to incorrect option types.
-
-**Solution**
-
-Check whether the option type is correct.