locales: Translated using Weblate (German)

Currently translated at 6.2% (2 of 32 strings)

Co-authored-by: Ettore Atalan <atalanttore@googlemail.com>
Translate-URL: https://hosted.weblate.org/projects/klipper/canbus_troubleshooting/de/
Translation: Klipper/CANBUS_Troubleshooting

docs/locales/de/LC_MESSAGES/CANBUS_Troubleshooting.po

@@ -4,7 +4,8 @@ msgstr ""
 "Report-Msgid-Bugs-To: yifeiding@protonmail.com\n"
 "PO-Revision-Date: 2023-10-30 09:04+0000\n"
 "Last-Translator: Ettore Atalan <atalanttore@googlemail.com>\n"
-"Language-Team: German <https://hosted.weblate.org/projects/klipper/canbus_troubleshooting/de/>\n"
+"Language-Team: German <https://hosted.weblate.org/projects/klipper/"
+"canbus_troubleshooting/de/>\n"
 "Language: de\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -23,7 +24,7 @@ msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 3 (header)
 msgid "Verify CAN bus wiring"
-msgstr ""
+msgstr "CAN-Bus-Verkabelung überprüfen"
 
 #: docs/CANBUS_Troubleshooting.md:block 4 (paragraph)
 msgid ""
@@ -33,10 +34,10 @@ msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 5 (paragraph)
 msgid ""
-"Be sure there are exactly two 120 Ohm [terminating "
-"resistors](CANBUS.md#terminating-resistors) on the CAN bus. If the resistors"
-" are not properly installed then messages may not be able to be sent at all "
-"or the connection may have sporadic instability."
+"Be sure there are exactly two 120 Ohm [terminating resistors](CANBUS."
+"md#terminating-resistors) on the CAN bus. If the resistors are not properly "
+"installed then messages may not be able to be sent at all or the connection "
+"may have sporadic instability."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 6 (paragraph)
@@ -63,8 +64,8 @@ msgstr ""
 #: docs/CANBUS_Troubleshooting.md:block 9 (paragraph)
 msgid ""
 "The Klipper log file will report a `Stats` line once a second when the "
-"printer is active. These \"Stats\" lines will have a `bytes_invalid` counter"
-" for each micro-controller. This counter should not increment during normal "
+"printer is active. These \"Stats\" lines will have a `bytes_invalid` counter "
+"for each micro-controller. This counter should not increment during normal "
 "printer operation (it is normal for the counter to be non-zero after a "
 "RESTART and it is not a concern if the counter increments once a month or "
 "so). If this counter increments on a CAN bus micro-controller during normal "
@@ -89,16 +90,16 @@ msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 11 (ordered list)
 msgid ""
-"Some Linux kernel builds for embedded devices have been known to reorder CAN"
-" bus messages. It may be necessary to use an alternative Linux kernel or to "
+"Some Linux kernel builds for embedded devices have been known to reorder CAN "
+"bus messages. It may be necessary to use an alternative Linux kernel or to "
 "use alternative hardware that supports mainstream Linux kernels that do not "
 "exhibit this problem."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 12 (paragraph)
 msgid ""
-"Reordered messages is a severe problem that must be fixed. It will result in"
-" unstable behavior and can lead to confusing errors at any part of a print."
+"Reordered messages is a severe problem that must be fixed. It will result in "
+"unstable behavior and can lead to confusing errors at any part of a print."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 13 (header)
@@ -109,8 +110,7 @@ msgstr ""
 msgid ""
 "The CAN bus messages sent to and from the micro-controller are handled by "
 "the Linux kernel. It is possible to capture these messages from the kernel "
-"for debugging purposes. A log of these messages may be of use in "
-"diagnostics."
+"for debugging purposes. A log of these messages may be of use in diagnostics."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 15 (paragraph)
@@ -135,8 +135,8 @@ msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 19 (paragraph)
 msgid ""
-"One can view the resulting log file (`mycanlog` in the example above) to see"
-" each raw CAN bus message that was sent and received by Klipper. "
+"One can view the resulting log file (`mycanlog` in the example above) to see "
+"each raw CAN bus message that was sent and received by Klipper. "
 "Understanding the content of these messages will likely require low-level "
 "knowledge of Klipper's [CANBUS protocol](CANBUS_protocol.md) and Klipper's "
 "[MCU commands](MCU_Commands.md)."
@@ -150,8 +150,8 @@ msgstr ""
 msgid ""
 "One may use the `parsecandump.py` tool to parse the low-level Klipper micro-"
 "controller messages contained in a candump log. Using this tool is an "
-"advanced topic that requires knowledge of Klipper [MCU "
-"commands](MCU_Commands.md). For example:"
+"advanced topic that requires knowledge of Klipper [MCU commands]"
+"(MCU_Commands.md). For example:"
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 22 (code)
@@ -160,10 +160,10 @@ msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 23 (paragraph)
 msgid ""
-"This tool produces output similar to the [parsedump "
-"tool](Debugging.md#translating-gcode-files-to-micro-controller-commands). "
-"See the documentation for that tool for information on generating the "
-"Klipper micro-controller data dictionary."
+"This tool produces output similar to the [parsedump tool](Debugging."
+"md#translating-gcode-files-to-micro-controller-commands). See the "
+"documentation for that tool for information on generating the Klipper micro-"
+"controller data dictionary."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 24 (paragraph)
@@ -189,10 +189,9 @@ msgstr ""
 #: docs/CANBUS_Troubleshooting.md:block 27 (paragraph)
 msgid ""
 "The [Sigrok Pulseview](https://sigrok.org/wiki/PulseView) software along "
-"with a low-cost [logic "
-"analyzer](https://en.wikipedia.org/wiki/Logic_analyzer) can be useful for "
-"diagnosing CAN bus signaling. This is an advanced topic likely only of "
-"interest to experts."
+"with a low-cost [logic analyzer](https://en.wikipedia.org/wiki/"
+"Logic_analyzer) can be useful for diagnosing CAN bus signaling. This is an "
+"advanced topic likely only of interest to experts."
 msgstr ""
 
 #: docs/CANBUS_Troubleshooting.md:block 28 (paragraph)
@@ -209,17 +208,17 @@ msgstr ""
 #: docs/CANBUS_Troubleshooting.md:block 30 (paragraph)
 msgid ""
 "The above picture was taken while using Pulseview with a \"Saleae clone\" "
-"logic analyzer. The Sigrok and Pulseview software was installed on a desktop"
-" machine (also install the \"fx2lafw\" firmware if that is packaged "
+"logic analyzer. The Sigrok and Pulseview software was installed on a desktop "
+"machine (also install the \"fx2lafw\" firmware if that is packaged "
 "separately). The CH0 pin on the logic analyzer was routed to the CAN Rx "
 "line, the CH1 pin was wired to the CAN Tx pin, and GND was wired to GND. "
 "Pulseview was configured to only display the D0 and D1 lines (red \"probe\" "
 "icon center top toolbar). The number of samples was set to 5 million (top "
-"toolbar) and the sample rate was set to 24Mhz (top toolbar). The CAN decoder"
-" was added (yellow and green \"bubble icon\" right top toolbar). The D0 "
+"toolbar) and the sample rate was set to 24Mhz (top toolbar). The CAN decoder "
+"was added (yellow and green \"bubble icon\" right top toolbar). The D0 "
 "channel was labeled as RX and set to trigger on a falling edge (click on "
-"black D0 label at left). The D1 channel was labeled as TX (click on brown D1"
-" label at left). The CAN decoder was configured for 1Mbit rate (click on "
+"black D0 label at left). The D1 channel was labeled as TX (click on brown D1 "
+"label at left). The CAN decoder was configured for 1Mbit rate (click on "
 "green CAN label at left). The CAN decoder was moved to the top of the "
 "display (click and drag green CAN label). Finally, the capture was started "
 "(click \"Run\" at top left) and a packet was transmitted on the CAN bus "