New Crowdin translations - zh-CN (#24563)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

Author: PX4BuildBot

docs/zh/actuators/index.md

@@ -10,4 +10,4 @@
 
 ## See Also
 
-- [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。
+- [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。

docs/zh/advanced/gimbal_control.md

@@ -129,7 +129,7 @@ The on-screen gimbal control can be used to move/test a connected MAVLink camera
 
 2. Open QGroundControl and enable the on-screen camera control (Application settings).
 
-   ![Quadrotor(x500) with gimbal (Front-facing) in Gazebo](../../assets/qgc/fly/gimbal_control_x500gz.png)
+  ![Quadrotor(x500) with gimbal (Front-facing) in Gazebo](../../assets/qgc/fly/gimbal_control_x500gz.png)
 
 3. Make sure the vehicle is armed and flying, e.g. by entering with `commander takeoff`.
 

docs/zh/advanced/parameters_and_configurations.md

@@ -128,21 +128,21 @@ You add some "boilerplate" code to regularly listen for changes in the [uORB Top
 
 - **px4_platform_common/module_params.h** to get the `DEFINE_PARAMETERS` macro:
 
-  ```cpp
-  #include <px4_platform_common/module_params.h>
-  ```
+ ```cpp
+ #include <px4_platform_common/module_params.h>
+ ```
 
 - **parameter_update.h** to access the uORB `parameter_update` message:
 
-  ```cpp
-  #include <uORB/topics/parameter_update.h>
-  ```
+ ```cpp
+ #include <uORB/topics/parameter_update.h>
+ ```
 
 - **Subscription.hpp** for the uORB C++ subscription API:
 
-  ```cpp
-  #include <uORB/Subscription.hpp>
-  ```
+ ```cpp
+ #include <uORB/Subscription.hpp>
+ ```
 
 Derive your class from `ModuleParams`, and use `DEFINE_PARAMETERS` to specify a list of parameters and their associated parameter attributes.
 参数的名称必须与其参数元数据定义相同。
@@ -194,7 +194,7 @@ void Module::parameters_update()
 - `_parameter_update_sub.updated()` tells us if there is _any_ update to the `param_update` uORB message (but not what parameter is affected).
 - If there has been "some" parameter updated, we copy the update into a `parameter_update_s` (`param_update`), to clear the pending update.
 - Then we call `ModuleParams::updateParams()`.
-  This "under the hood" updates all parameter attributes listed in our `DEFINE_PARAMETERS` list.
+ This "under the hood" updates all parameter attributes listed in our `DEFINE_PARAMETERS` list.
 
 The parameter attributes (`_sys_autostart` and `_att_bias_max` in this case) can then be used to represent the parameters, and will be updated whenever the parameter value changes.
 
@@ -267,12 +267,12 @@ YAML meta data is intended as a full replacement for the **.c** definitions.
 - An example of YAML definitions being used can be found in the MAVLink parameter definitions: [/src/modules/mavlink/module.yaml](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/module.yaml).
 - 通过添加到 cmake 构建系统中注册一个 YAML 文件
 
-  ```cmake
-  MODULE_CONFIG
-  	module.yaml
-  ```
+ ```cmake
+ MODULE_CONFIG
+ 	module.yaml
+ ```
 
-  to the `px4_add_module` section of the `CMakeLists.txt` file of that module.
+ to the `px4_add_module` section of the `CMakeLists.txt` file of that module.
 
 #### 多实例（模块化）YAML 元数据
 

docs/zh/advanced/system_tunes.md

@@ -52,7 +52,7 @@ On Windows, one option is to use _Melody Master_ within _Dosbox_.
 7. 当您准备好时保存音乐：
    - Press **F2** to give the tune a name and save it in the _/Music_ sub folder of your Melody Master installation.
    - Press **F7**, the scroll down the list of output formats on the right to get to ANSI.
-     The file will be exported to the _root_ of the Melody Master directory (with the same name and a file-type specific extension).
+      The file will be exported to the _root_ of the Melody Master directory (with the same name and a file-type specific extension).
 
 8. 打开文件。
    输出可能看起来像这样：

docs/zh/advanced_config/advanced_flight_controller_orientation_leveling.md

@@ -23,7 +23,7 @@ You can locate the parameters in QGroundControl as shown below:
 1. Open QGroundControl menu: **Settings > Parameters > Sensor Calibration**.
 2. The parameters as located in the section as shown below (or you can search for them):
 
-   ![FC Orientation QGC v2](../../assets/qgc/setup/sensor/fc_orientation_qgc_v2.png)
+  ![FC Orientation QGC v2](../../assets/qgc/setup/sensor/fc_orientation_qgc_v2.png)
 
 ## Parameter Summary
 

docs/zh/advanced_config/bootloader_update.md

@@ -52,80 +52,80 @@ The following steps explain how you can "manually" update the bootloader using a
 1. Get a binary containing the bootloader (either from dev team or [build it yourself](#building-the-px4-bootloader)).
 
 2. Get a [Debug Probe](../debug/swd_debug.md#debug-probes-for-px4-hardware).
-   Connect the probe your PC via USB and setup the `gdbserver`.
+  Connect the probe your PC via USB and setup the `gdbserver`.
 
 3. Go into the directory containing the binary and run the command for your target bootloader in the terminal:
 
-   - FMUv6X
+  - FMUv6X
 
-     ```sh
-     arm-none-eabi-gdb px4_fmu-v6x_bootloader.elf
-     ```
+    ```sh
+    arm-none-eabi-gdb px4_fmu-v6x_bootloader.elf
+    ```
 
-   - FMUv6X-RT
+  - FMUv6X-RT
 
-     ```sh
-     arm-none-eabi-gdb px4_fmu-v6xrt_bootloader.elf
-     ```
+    ```sh
+    arm-none-eabi-gdb px4_fmu-v6xrt_bootloader.elf
+    ```
 
-   - FMUv5
+  - FMUv5
 
-     ```sh
-     ```
+    ```sh
+    ```
 
-   ::: info
-   H7 Bootloaders from [PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) are named with pattern `*._bootloader.elf`.
-   Bootloaders from [PX4/PX4-Bootloader](https://github.com/PX4/PX4-Bootloader) are named with the pattern `*_bl.elf`.
+  ::: info
+  H7 Bootloaders from [PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) are named with pattern `*._bootloader.elf`.
+  Bootloaders from [PX4/PX4-Bootloader](https://github.com/PX4/PX4-Bootloader) are named with the pattern `*_bl.elf`.
 
 :::
 
 4. The _gdb terminal_ appears and it should display the following output:
 
-   ```sh
-   GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
-   Copyright (C) 2017 Free Software Foundation, Inc.
-   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
-   This is free software: you are free to change and redistribute it.
-   There is NO WARRANTY, to the extent permitted by law.
-   Type "show copying"    and "show warranty" for details.
-   This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
-   Type "show configuration" for configuration details.
-   For bug reporting instructions, please see:
-   <http://www.gnu.org/software/gdb/bugs/>.
-   Find the GDB manual and other documentation resources online at:
-   <http://www.gnu.org/software/gdb/documentation/>.
-   For help, type "help".
-   Type "apropos word" to search for commands related to "word"...
-   Reading symbols from px4fmuv5_bl.elf...done.
-   ```
+  ```sh
+  GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
+  Copyright (C) 2017 Free Software Foundation, Inc.
+  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+  This is free software: you are free to change and redistribute it.
+  There is NO WARRANTY, to the extent permitted by law.
+  Type "show copying"    and "show warranty" for details.
+  This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
+  Type "show configuration" for configuration details.
+  For bug reporting instructions, please see:
+  <http://www.gnu.org/software/gdb/bugs/>.
+  Find the GDB manual and other documentation resources online at:
+  <http://www.gnu.org/software/gdb/documentation/>.
+  For help, type "help".
+  Type "apropos word" to search for commands related to "word"...
+  Reading symbols from px4fmuv5_bl.elf...done.
+  ```
 
 5. Find your `<dronecode-probe-id>` by running an `ls` command in the **/dev/serial/by-id** directory.
 
 6. Now connect to the debug probe with the following command:
 
-   ```sh
-   tar ext /dev/serial/by-id/<dronecode-probe-id>
-   ```
+  ```sh
+  tar ext /dev/serial/by-id/<dronecode-probe-id>
+  ```
 
 7. Power on the Pixhawk with another USB cable and connect the probe to the `FMU-DEBUG` port.
 
-   ::: info
-   If using a Dronecode probe you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).
+  ::: info
+  If using a Dronecode probe you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).
 
 :::
 
 8. Use the following command to scan for the Pixhawk\`s SWD and connect to it:
 
-   ```sh
-   (gdb) mon swdp_scan
-   (gdb) attach 1
-   ```
+  ```sh
+  (gdb) mon swdp_scan
+  (gdb) attach 1
+  ```
 
 9. 将二进制文件加载到 Pixhawk 中 ：
 
-   ```sh
-   (gdb) load
-   ```
+  ```sh
+  (gdb) load
+  ```
 
 After the bootloader has updated you can [Load PX4 Firmware](../config/firmware.md) using _QGroundControl_.
 
@@ -146,8 +146,8 @@ Currently only FMUv2 and some custom firmware includes the desired bootloader.
 
 2. [Update the Firmware](../config/firmware.md#custom) with an image containing the new/desired bootloader.
 
-   ::: info
-   The updated bootloader might be supplied in custom firmware (i.e. from the dev team), or it or may be included in the latest main branch.
+  ::: info
+  The updated bootloader might be supplied in custom firmware (i.e. from the dev team), or it or may be included in the latest main branch.
 
 :::
 
@@ -156,7 +156,7 @@ Currently only FMUv2 and some custom firmware includes the desired bootloader.
 4. [Find and enable](../advanced_config/parameters.md) the parameter [SYS_BL_UPDATE](../advanced_config/parameter_reference.md#SYS_BL_UPDATE).
 
 5. 重新启动（断开/重新连接飞控板）。
-   Bootloader 更新只需要几秒钟即可完成。
+  Bootloader 更新只需要几秒钟即可完成。
 
 Generally at this point you may then want to [update the firmware](../config/firmware.md) again using the correct/newly installed bootloader.
 
@@ -176,25 +176,25 @@ Early FMUv2 [Pixhawk-series](../flight_controller/pixhawk_series.md#fmu_versions
 1. 插入 SD 卡（使能引导日志记录，便于调试任何可能的问题）。
 
 2. [Update the Firmware](../config/firmware.md) to PX4 _master_ version (when updating the firmware, check **Advanced settings** and then select **Developer Build (master)** from the dropdown list).
-   _QGroundControl_ will automatically detect that the hardware supports FMUv2 and install the appropriate Firmware.
+  _QGroundControl_ will automatically detect that the hardware supports FMUv2 and install the appropriate Firmware.
 
-   ![FMUv2 update](../../assets/qgc/setup/firmware/bootloader_update.jpg)
+  ![FMUv2 update](../../assets/qgc/setup/firmware/bootloader_update.jpg)
 
-   等待飞控重启。
+  等待飞控重启。
 
 3. [Find and enable](../advanced_config/parameters.md) the parameter [SYS_BL_UPDATE](../advanced_config/parameter_reference.md#SYS_BL_UPDATE).
 
 4. 重新启动（断开/重新连接飞控板）。
-   Bootloader 更新只需要几秒钟即可完成。
+  Bootloader 更新只需要几秒钟即可完成。
 
 5. Then [Update the Firmware](../config/firmware.md) again.
-   This time _QGroundControl_ should autodetect the hardware as FMUv3 and update the Firmware appropriately.
+  This time _QGroundControl_ should autodetect the hardware as FMUv3 and update the Firmware appropriately.
 
-   ![FMUv3 update](../../assets/qgc/setup/firmware/bootloader_fmu_v3_update.jpg)
+  ![FMUv3 update](../../assets/qgc/setup/firmware/bootloader_fmu_v3_update.jpg)
 
-   ::: info
-   If the hardware has the [Silicon Errata](../flight_controller/silicon_errata.md#fmuv2-pixhawk-silicon-errata) it will still be detected as FMUv2 and you will see that FMUv2 was re-installed (in console).
-   在这种情况下，您将无法安装 FMUv3 硬件。
+  ::: info
+  If the hardware has the [Silicon Errata](../flight_controller/silicon_errata.md#fmuv2-pixhawk-silicon-errata) it will still be detected as FMUv2 and you will see that FMUv2 was re-installed (in console).
+  在这种情况下，您将无法安装 FMUv3 硬件。
 
 :::
 

docs/zh/advanced_config/compass_power_compensation.md

@@ -48,7 +48,7 @@ The process is demonstrated for a multicopter, but is equally valid for other ve
    - 解锁无人机，然后缓缓将油门推到最大。
    - 慢慢将油门降到0
    - 给无人机加锁
-     &#062; <strong x-id="1">Note</strong> 谨慎地进行测试，并密切注意振动情况。
+      &#062; <strong x-id="1">Note</strong> 谨慎地进行测试，并密切注意振动情况。
 
    ::: info
    Perform the test carefully and closely monitor the vibrations.

docs/zh/advanced_config/esc_calibration.md

@@ -94,29 +94,29 @@ Flight control systems that can't power the autopilot via USB will need a [diffe
 
    - The minimum value for a motor (default: `1100us`) should make the motor spin slowly but reliably, and also spin up reliably after it was stopped.
 
-     You can confirm that a motor spins at minimum (still without propellers) in [Actuator Testing](../config/actuators.md#actuator-testing), by enabling the sliders, and then moving the test output slider for the motor to the first snap position from the bottom.
-     当你将滑块从解锁到最小值时，正确的值应该使电机立即和可靠地旋转。
+      You can confirm that a motor spins at minimum (still without propellers) in [Actuator Testing](../config/actuators.md#actuator-testing), by enabling the sliders, and then moving the test output slider for the motor to the first snap position from the bottom.
+      当你将滑块从解锁到最小值时，正确的值应该使电机立即和可靠地旋转。
 
-     要找到“最佳”最小值，请将滑块移动到底部(禁用)。
-     Then increase the PWM output's `disarmed` setting in small increments (e.g. 1025us, 1050us, etc), until the motor starts to spin reliably (it is better to be a little too high than a little too low).
-     Enter this value into the `minimum` setting for all the motor PWM outputs, and restore the `disarmed` output to `1100us`.
+      要找到“最佳”最小值，请将滑块移动到底部(禁用)。
+      Then increase the PWM output's `disarmed` setting in small increments (e.g. 1025us, 1050us, etc), until the motor starts to spin reliably (it is better to be a little too high than a little too low).
+      Enter this value into the `minimum` setting for all the motor PWM outputs, and restore the `disarmed` output to `1100us`.
 
    - The maximum value for a motor (default: `1900us`) should be chosen such that increasing the value doesn't make the motor spin any faster.
 
-     You can confirm that the motor spins quickly at the maximum setting in [Actuator Testing](../config/actuators.md#actuator-testing), by moving the associated test output slider to the top position.
+      You can confirm that the motor spins quickly at the maximum setting in [Actuator Testing](../config/actuators.md#actuator-testing), by moving the associated test output slider to the top position.
 
-     To find the "optimal" maximum value, first move the slider to the bottom (disarmed).
-     Then increase the PWM output's `disarmed` setting to near the default maximum (`1900`) - the motors should spin up.
-     Listen to the tone of the motor as you increase the PWM maximum value for the output in increments (e.g. 1925us, 1950us, etc).
-     The optimal value is found at the point when the sound of the motors does not change as you increase the value of the output.
-     Enter this value into the `maximum` setting for all the motor PWM outputs, and restore the `disarmed` output to `1100us`.
+      To find the "optimal" maximum value, first move the slider to the bottom (disarmed).
+      Then increase the PWM output's `disarmed` setting to near the default maximum (`1900`) - the motors should spin up.
+      Listen to the tone of the motor as you increase the PWM maximum value for the output in increments (e.g. 1925us, 1950us, etc).
+      The optimal value is found at the point when the sound of the motors does not change as you increase the value of the output.
+      Enter this value into the `maximum` setting for all the motor PWM outputs, and restore the `disarmed` output to `1100us`.
 
    - The disarmed value for a motor (default: `1000us`) should make the motor stop and stay stopped.
 
-     You can confirm this in [Actuator Testing](../config/actuators.md#actuator-testing) by moving the test output slider to the snap position at the bottom of the slider and observing that the motor does not spin.
+      You can confirm this in [Actuator Testing](../config/actuators.md#actuator-testing) by moving the test output slider to the snap position at the bottom of the slider and observing that the motor does not spin.
 
-     If the ESC spins with the default value of 1000us then the ESC is not properly calibrated.
-     If using an ESC that can't be calibrated, you should reduce the PWM output value for the output to below where the motor does not spin anymore (such as 950us or 900us).
+      If the ESC spins with the default value of 1000us then the ESC is not properly calibrated.
+      If using an ESC that can't be calibrated, you should reduce the PWM output value for the output to below where the motor does not spin anymore (such as 950us or 900us).
 
    ::: info
    VTOL and fixed-wing motors do not need any special PWM configuration.