!8368 翻译已完成7560+6910+7609+7536+7374+7426+6771+7373

Merge pull request !8368 from shawn_he/7560-a

en/device-dev/subsystems/subsys-aiframework-tech-codemanage.md

@@ -15,15 +15,19 @@ In the overall planning of the AI engine framework, northbound SDKs are a part o
 
 -   SDK code directory: //foundation/ai/engine/services/client/algorithm\_sdk
 
-    e.g. //foundation/ai/engine/services/client/algorithm\_sdk/cv
+    Examples:
+    
+    //foundation/ai/engine/services/client/algorithm\_sdk/cv
 
-    e.g. //foundation/ai/engine/services/client/algorithm\_sdk/nlu
+    //foundation/ai/engine/services/client/algorithm\_sdk/nlu
 
 -   Plug-in code directory: //foundation/ai/engine/services/server/plugin
 
-    e.g. //foundation/ai/engine/services/server/plugin/cv
+    Examples:
 
-    e.g. //foundation/ai/engine/services/server/plugin/nlu
+    //foundation/ai/engine/services/server/plugin/cv
+
+    //foundation/ai/engine/services/server/plugin/nlu
 
 
 ## Rule: Store all external APIs provided by plug-ins in the  **interfaces/kits**  directory of the AI subsystem.<a name="section2551029111312"></a>

en/device-dev/subsystems/subsys-boot-init-jobs.md

@@ -160,6 +160,20 @@ A job is a command set, where you can manage the commands to be executed. A maxi
                         Small and standard systems
                     </td>
                 </tr>
+                <tr height="162" style="height:121.5pt">
+                    <td height="162" class="xl6621952" width="140" style="height:121.5pt;border-top: none;width:105pt">
+                        write
+                    </td>
+                    <td class="xl6621952" width="215" style="border-top:none;border-left:none; width:161pt">
+                        write filename value<br>Example:<br>write /data/testfile 0
+                    </td>
+                    <td class="xl6621952" width="225" style="border-top:none;border-left:none; width:169pt">
+                        Writes a file. <strong>filename</strong> and <strong>value</strong> respectively indicate the absolute file path and the string to write.
+                    </td>
+                    <td class="xl6621952" width="190" style="border-top:none;border-left:none; width:143pt">
+                        Standard system
+                    </td>
+                </tr>
                 <tr height="185" style="height:138.75pt">
                     <td height="185" class="xl6621952" width="140" style="height:138.75pt;border-top: none;width:105pt">
                         stop
@@ -300,6 +314,20 @@ A job is a command set, where you can manage the commands to be executed. A maxi
                         Small and standard systems
                     </td>
                 </tr>
+                <tr height="162" style="height:121.5pt">
+                    <td height="162" class="xl6621952" width="140" style="height:121.5pt;border-top: none;width:105pt">
+                        syncexec
+                    </td>
+                    <td class="xl6621952" width="215" style="border-top:none;border-left:none; width:161pt">
+                        syncexec <i>Path of the executable file</i> <i>Parameters passed by the executable file</i><br>Example:<br>syncexec /system/bin/udevadm trigger
+                    </td>
+                    <td class="xl6621952" width="225" style="border-top:none;border-left:none; width:169pt">
+                        Runs an executable file synchronously. The **wait** function will be called to wait for the child process to end. The command must not contain more than 10 parameters.
+                    </td>
+                    <td class="xl6621952" width="190" style="border-top:none;border-left:none; width:143pt">
+                        Standard system
+                    </td>
+                </tr>
                 <tr height="231" style="height:173.25pt">
                     <td height="231" class="xl6621952" width="140" style="height:173.25pt;border-top: none;width:105pt">
                         mknode

en/device-dev/subsystems/subsys-boot-init-service.md

@@ -114,7 +114,7 @@ The service management module is available only for the mini system and standard
 By parsing the <strong>*.cfg</strong> file, you can obtain **service** fields, and then set and start the service.
 
 ### Parameters
-   **Table 1** Description of service fields
+   **Table 1** Description of service fields<a name="table14737791471"></a>
 <table border="0" cellpadding="0" cellspacing="0" width="737" style="border-collapse: collapse;table-layout:fixed;width:554pt;border-spacing: 0px;font-variant-ligatures: normal; font-variant-caps: normal;orphans: 2;widows: 2;-webkit-text-stroke-width: 0px; text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial">
             <tbody>
                 <tr height="24" style="height:18.0pt">
@@ -208,11 +208,11 @@ By parsing the <strong>*.cfg</strong> file, you can obtain **service** fields, a
                         importance
                     </td>
                     <td class="xl6621805" width="196" style="border-top:none;border-left:none; width:147pt">
-                        Current service priority.
+                        Service priority (for the standard system) or service importance (for the mini system).
                     </td>
                     <td class="xl6621805" width="242" style="border-top:none;border-left:none; width:182pt">
                         Standard system: The service priority ranges from -20 to 19. A value beyond the range is invalid.<br>
-                        Small system: The value <strong>0</strong> indicates an unimportant process and a value greater than <strong>0</strong> indicates an important process.
+                        Small system: The value <strong>0</strong> indicates that a system restart is not required, and a value greater than <strong>0</strong> indicates the opposite.
                     </td>
                     <td class="xl6621805" width="173" style="border-top:none;border-left:none; width:130pt">
                         Small and standard systems
@@ -362,7 +362,7 @@ By parsing the <strong>*.cfg</strong> file, you can obtain **service** fields, a
    | option | Socket option. This field is passed when **setsockopt** is called. Currently, the available options include <strong>SOCKET_OPTION_PASSCRED</strong>, <strong>SOCKET_OPTION_RCVBUFFORCE</strong>, <strong>SOCK_CLOEXEC</strong>, and <strong>SOCK_NONBLOCK</strong>.|
 
 ### Available APIs
-  **Table 3** FD proxy APIs
+  **Table 3** FD proxy APIs<a name="table14737791479"></a>
    | API    | Function| Description |
    | ---------- |  ----------  |--------|
    | int *ServiceGetFd(const char *serviceName, size_t *outfdCount) | Obtains the proxy FD from the init process.| Return value: Returns the pointer to the fd array if the operation is successful; returns **NULL** otherwise. (Note: Manual release is required.)<br>Arguments:<br> **serviceName**: service name.<br>**outfdCount**: length of the returned fd array.|

en/readme/location.md

@@ -8,7 +8,7 @@ With the location awareness capability offered by OpenHarmony, mobile devices wi
 
 Your application can call location-specific APIs to obtain the location information of a mobile device for offering location-based services such as drive navigation and motion track recording.
 
-Basic Concepts
+**Basic Concepts**
 
 Location awareness helps determine where a mobile device locates. The system identifies the location of a mobile device with its coordinates, and uses location technologies such as Global Navigation Satellite System (GNSS) and network positioning (for example, base station positioning or WLAN/Bluetooth positioning) to provide diverse location-based services. These advanced location technologies make it possible to obtain the accurate location of the mobile device, regardless of whether it is indoors or outdoors.
 
@@ -28,6 +28,10 @@ Location awareness helps determine where a mobile device locates. The system ide
 
     WLAN or Bluetooth positioning estimates the current location of a mobile device based on the locations of WLANs and Bluetooth devices that can be discovered by the device. The location accuracy of this technology depends on the distribution of fixed WLAN access points (APs) and Bluetooth devices around the device. A high density of WLAN APs and Bluetooth devices can produce a more accurate location result than base station positioning. This technology also requires access to the network.
 
+**Figure 1** ** Location subsystem architecture**<a name="fig4460722185514"></a>  
+
+![](figures/location_En-1.png)
+![](figures/location_En-1.png)
 
 ## Directory Structure<a name="section161941989596"></a>
 
@@ -102,7 +106,8 @@ The following table describes APIs available for obtaining device location infor
 **Obtaining the device location information:**
 
 1. Before using basic location capabilities, check whether your application has been granted the permission to access the device location information. If not, your application needs to obtain the permission from the user.
-     The system provides the following location permissions:
+
+   The system provides the following location permissions:
    - ohos.permission.LOCATION
    
    - ohos.permission.LOCATION_IN_BACKGROUND
@@ -131,7 +136,7 @@ The following table describes APIs available for obtaining device location infor
    }
    ```
 
-   For details about the configuration fields, see the description of the **module.json** file.
+   For details about the configuration fields, see [Application Package Structure Configuration File](../application-dev/quick-start/stage-structure.md).
 
 2. Import the **geolocation** module by which you can implement all APIs related to the basic location capabilities.
      
@@ -204,7 +209,8 @@ The following table describes APIs available for obtaining device location infor
    ```
 
 4. Instantiate the **Callback** object for the system to report location results.
-     Your application needs to implement the callback defined by the system. When the system successfully obtains the real-time location of a device, it will report the location result to your application through the callback interface. Your application can implement the callback interface in such a way to complete your own service logic.
+
+   Your application needs to implement the callback defined by the system. When the system successfully obtains the real-time location of a device, it will report the location result to your application through the callback interface. Your application can implement the callback interface in such a way to complete your own service logic.
      
    ```
    var locationChange = (location) => {
@@ -239,6 +245,7 @@ The following table describes APIs available for obtaining device location infor
 **Converting the coordinates and geocoding information:**
 
 > **NOTE**
+> 
 > The **GeoConvert** instance needs to access backend services to obtain information. Therefore, before performing the following steps, ensure that your device is connected to the network.
 
 1. Import the **geolocation** module by which you can implement all APIs related to the geocoding and reverse geocoding conversion capabilities.
@@ -248,6 +255,7 @@ The following table describes APIs available for obtaining device location infor
    ```
 
 2. Obtain the conversion result.
+
    - Call **getAddressesFromLocation** to convert coordinates into geographical location information.
         
       ```
@@ -258,6 +266,7 @@ The following table describes APIs available for obtaining device location infor
       ```
 
       Your application can obtain the **GeoAddress** list that matches the specified coordinates and then read location information from it. For details, see the *API Reference*.
+
    - Call **getAddressesFromLocationName** to convert geographic description into coordinates.
         
       ```