New Crowdin updates (#578)

* New translations readme.md (Korean) * New translations readme.md (Chinese Simplified) * New translations storm32.md (Korean) * New translations storm32.md (Chinese Simplified) * New translations all.md (Korean) * New translations all.md (Chinese Simplified) * New translations ardupilotmega.md (Korean) * New translations ardupilotmega.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations loweheiser.md (Korean) * New translations loweheiser.md (Chinese Simplified) * New translations example_c_udp.md (Korean) * New translations example_c_udp.md (Chinese Simplified) * New translations ardupilotmega.md (Korean) * New translations ardupilotmega.md (Chinese Simplified)
mavlink · Dec 4, 2024 · fedda2a · fedda2a
1 parent f5384b7
commit fedda2a
Show file tree

Hide file tree

Showing 14 changed files with 606 additions and 52 deletions.
diff --git a/ko/mavgen_c/example_c_udp.md b/ko/mavgen_c/example_c_udp.md
@@ -1,6 +1,6 @@
 # MAVLink C UDP Example
 
-The [MAVLink UDP Example](https://github.com/mavlink/mavlink/tree/master/examples/linux) is a simple C example that sends some data to _QGroundControl_ using MAVLink over UDP.
+The [MAVLink UDP Example](https://github.com/mavlink/mavlink/tree/master/examples/c) is a simple C example that sends some data to _QGroundControl_ using MAVLink over UDP.
 _QGroundControl_ responds with heartbeats and other messages, which are then printed by this program.
 
 :::info
@@ -31,12 +31,12 @@ The following instructions show how to build and run the example.
    You can put/generate the library wherever you like, but the build command below assumes they are located in directory named **include** below the MAVLink root directory.
    :::
 
-2. Open a terminal and navigate to [examples/linux](https://github.com/mavlink/mavlink/tree/master/examples/linux)
+2. Open a terminal and navigate to [examples/c](https://github.com/mavlink/mavlink/tree/master/examples/c)
 
 3. Compile with GCC using the following command:
 
    ```sh
-   gcc -std=c99 -I ../../include/common -o mavlink_udp mavlink_udp.c
+   gcc -std=c99 -I ../../include/common -o mavlink_udp udp_example.c
    ```
 
    ::: info
@@ -64,7 +64,7 @@ The following instructions show how to build and run the example.
 6. The example should start displaying the received data in the terminal:
 
    ```sh
-   ~/github/mavlink/examples/linux$ ./mavlink_udp
+   ~/github/mavlink/examples/c$ ./mavlink_udp
    Bytes Received: 17
    Datagram: fe 09 00 ff 00 00 00 00 00 00 06 08 c0 04 03 19 87
    Received packet: SYS: 255, COMP: 0, LEN: 9, MSG ID: 0

diff --git a/ko/messages/README.md b/ko/messages/README.md
@@ -0,0 +1,66 @@
+<!-- THIS FILE IS AUTO-GENERATED FROM XML: https://github.com/mavlink/mavlink/blob/master/doc/mavlink_xml_to_markdown.py (Do not update mavlink-devguide) -->
+
+# XML Definition Files & Dialects
+
+MAVLink definitions files can be found in [mavlink/message definitions](https://github.com/mavlink/mavlink/blob/master/message_definitions/).
+These can roughly be divided into:
+
+- [Standard definitions](#standard-definitions) - core definitions shared by many flight stacks
+- [Test definitions](#test-definitions) - definitions to support testing and validation
+- [Dialects](#dialects) - _protocol-_ and _vendor-specific_ messages, enums and commands
+
+## Standard Definitions
+
+The following XML definition files are considered standard/core (i.e. not dialects):
+
+- [minimal.xml](minimal.md) - the minimum set of entities (messages, enums, MAV_CMD) required to set up a MAVLink network.
+- [standard.xml](standard.md) - the standard set of entities that are implemented by almost all flight stacks (at least 2, in a compatible way).
+  This `includes` [minimal.xml](minimal.md).
+- [common.xml](common.md) - the set of entities that have been implemented in at least one core flight stack.
+  This `includes` [standard.xml](minimal.md)
+
+> **Note** We are still working towards moving the truly standard entities from **common.xml** to **standard.xml**
+> Currently you should include [common.xml](common.md)
+
+In addition:
+
+- [development.xml](development.md) - XML definitions that are _proposed_ for inclusion in the standard definitions.
+  These are work in progress.
+
+## Test Definitions
+
+The following definitions are used for testing and dialect validation:
+
+- [all.xml](all.md) - This includes all other XML files, and is used to verify that there are no ID clashes (and can potentially be used by GCS to communicate with any core dialect).
+- [test.xml](test.md) - Test XML definition file.
+
+## Dialects  {#dialects}
+
+MAVLink _dialects_ are XML definition files that define _protocol-_ and _vendor-specific_ messages, enums and commands.
+
+> **Note** Vendor forks of MAVLink may contain XML entities that have not yet been pushed into the main repository (and will not be documented).
+
+Dialects may _include_ other MAVLink XML files, which may in turn contain other XML files (up to 5 levels of XML file nesting are allowed - see `MAXIMUM_INCLUDE_FILE_NESTING` in [mavgen.py](https://github.com/ArduPilot/pymavlink/blob/master/generator/mavgen.py#L44)).
+A typical pattern is for a dialect to include [common.xml](../messages/common.md) (containing the _MAVLink standard definitions_), extending it with vendor or protocol specific messages.
+
+The dialect definitions are:
+
+- [cubepilot.xml](cubepilot.md)
+- [python_array_test.xml](python_array_test.md)
+- [ardupilotmega.xml](ardupilotmega.md)
+- [common.xml](common.md)
+- [development.xml](development.md)
+- [matrixpilot.xml](matrixpilot.md)
+- [ASLUAV.xml](ASLUAV.md)
+- [csAirLink.xml](csAirLink.md)
+- [all.xml](all.md)
+- [storm32.xml](storm32.md)
+- [icarous.xml](icarous.md)
+- [test.xml](test.md)
+- [AVSSUAS.xml](AVSSUAS.md)
+- [uAvionix.xml](uAvionix.md)
+- [minimal.xml](minimal.md)
+- [paparazzi.xml](paparazzi.md)
+- [standard.xml](standard.md)
+- [ualberta.xml](ualberta.md)
+- [loweheiser.xml](loweheiser.md)
diff --git a/ko/messages/all.md b/ko/messages/all.md
@@ -2,7 +2,7 @@
 
 # Dialect: all
 
-This dialect is intended to `include` all other [dialects](../messages/index.md) in the [mavlink/mavlink](https://github.com/mavlink/mavlink) repository (including [external dialects](https://github.com/mavlink/mavlink/tree/master/external/dialects#mavlink-external-dialects)).
+This dialect is intended to `include` all other [dialects](../messages/README.md) in the [mavlink/mavlink](https://github.com/mavlink/mavlink) repository (including [external dialects](https://github.com/mavlink/mavlink/tree/master/external/dialects#mavlink-external-dialects)).
 
 Dialects that are in **all.xml** are guaranteed to not have clashes in messages, enums, enum ids, and MAV_CMDs.
 This ensure that:
@@ -57,9 +57,9 @@ span.warning {
 
 | Type                       | Defined | Included |
 | -------------------------- | ------- | -------- |
-| [Messages](#messages)      | 0       | 364      |
-| [Enums](#enumerated-types) | 0       | 235      |
-| [Commands](#mav_commands)  | 216     | 0        |
+| [Messages](#messages)      | 0       | 372      |
+| [Enums](#enumerated-types) | 0       | 236      |
+| [Commands](#mav_commands)  | 218     | 0        |
 
 The following sections list all entities in the dialect (both included and defined in this file).