From f56e6b0bda636cc8f49352596cab5daab189ceb3 Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Thu, 12 Jun 2025 01:10:07 +0000 Subject: [PATCH] New Crowdin translations - zh-CN --- docs/zh/concept/events_interface.md | 86 ++++++++++++++--------------- 1 file changed, 43 insertions(+), 43 deletions(-) diff --git a/docs/zh/concept/events_interface.md b/docs/zh/concept/events_interface.md index 98609f916b..a9a9ca34ea 100644 --- a/docs/zh/concept/events_interface.md +++ b/docs/zh/concept/events_interface.md @@ -71,42 +71,42 @@ Explanations and requirements: - `/* EVENT`: This tag indicates that a comment defines metadata for the following event. - **event_name**: the event name (`events::ID(event_name)`). - - must be unique within the whole source code of PX4. - As a general convention, prefix it with the module name, or the source file for larger modules. - - must be a valid variable name, i.e. must not contain spaces, colons, etc. - - from that name, a 24 bit event ID is derived using a hash function. - This means as long as the event name stays the same, so will the ID. + - must be unique within the whole source code of PX4. + As a general convention, prefix it with the module name, or the source file for larger modules. + - must be a valid variable name, i.e. must not contain spaces, colons, etc. + - from that name, a 24 bit event ID is derived using a hash function. + This means as long as the event name stays the same, so will the ID. - **Log Level**: - - valid log levels are the same as used in the MAVLink [MAV_SEVERITY](https://mavlink.io/en/messages/common.html#MAV_SEVERITY) enum. - In order of descending importance these are: + - valid log levels are the same as used in the MAVLink [MAV_SEVERITY](https://mavlink.io/en/messages/common.html#MAV_SEVERITY) enum. + In order of descending importance these are: - ```plain - Emergency, - Alert, - Critical, - Error, - Warning, - Notice, - Info, - Debug, - Disabled, - ``` + ```plain + Emergency, + Alert, + Critical, + Error, + Warning, + Notice, + Info, + Debug, + Disabled, + ``` - - Above we specify a separate external and internal log level, which are the levels displayed to GCS users and in the log file, respectively: `{events::Log::Error, events::LogInternal::Info}`. - For the majority of cases you can pass a single log level, and this will be used for both exernal and internal cases. - There are cases it makes sense to have two different log levels. - For example an RTL failsafe action: the user should see it as Warning/Error, whereas in the log, it is an expected system response, so it can be set to `Info`. + - Above we specify a separate external and internal log level, which are the levels displayed to GCS users and in the log file, respectively: `{events::Log::Error, events::LogInternal::Info}`. + For the majority of cases you can pass a single log level, and this will be used for both exernal and internal cases. + There are cases it makes sense to have two different log levels. + For example an RTL failsafe action: the user should see it as Warning/Error, whereas in the log, it is an expected system response, so it can be set to `Info`. - **Event Message**: - - Single-line, short message of the event. - It may contain template placeholders for arguments (e.g. `{1}`). For more information see below. + - Single-line, short message of the event. + It may contain template placeholders for arguments (e.g. `{1}`). For more information see below. - **Event Description**: - - Detailed, optional event description. - - Can be multiple lines/paragraphs. - - It may contain template placeholders for arguments (e.g. `{2}`) and supported tags (see below) + - Detailed, optional event description. + - Can be multiple lines/paragraphs. + - It may contain template placeholders for arguments (e.g. `{2}`) and supported tags (see below) #### Arguments and Enums @@ -125,35 +125,35 @@ Text format for event message description: - characters can be escaped with \\ - These have to be escaped: '\\\\', '\\<', '\\{'. + These have to be escaped: '\\\\', '\\<', '\\{'. - supported tags: - - Profiles: `CONTENT` + - Profiles: `CONTENT` - `CONTENT` will only be shown if the name matches the configured profile. - This can be used for example to hide developer information from end-users. + `CONTENT` will only be shown if the name matches the configured profile. + This can be used for example to hide developer information from end-users. - - URLs: `CONTENT`. - If `href` is not set, use `CONTENT` as `URL` (i.e.`https://docs.px4.io` is interpreted as `https://docs.px4.io`) + - URLs: `CONTENT`. + If `href` is not set, use `CONTENT` as `URL` (i.e.`https://docs.px4.io` is interpreted as `https://docs.px4.io`) - - Parameters: `PARAM_NAME` + - Parameters: `PARAM_NAME` - - no nested tags of the same type are allowed + - no nested tags of the same type are allowed - arguments: template placeholders that follow python syntax, with 1-based indexing (instead of 0) - - general form: `{ARG_IDX[:.NUM_DECIMAL_DIGITS][UNIT]}` + - general form: `{ARG_IDX[:.NUM_DECIMAL_DIGITS][UNIT]}` - UNIT: + UNIT: - - m: horizontal distance in meters - - m_v: vertical distance in meters - - m^2: area in m^2 - - m/s: speed in m/s - - C: temperature in degrees celsius + - m: horizontal distance in meters + - m_v: vertical distance in meters + - m^2: area in m^2 + - m/s: speed in m/s + - C: temperature in degrees celsius - - `NUM_DECIMAL_DIGITS` only makes sense for real number arguments. + - `NUM_DECIMAL_DIGITS` only makes sense for real number arguments. ## 日志