Please sign in to see the alerts.

Overview

Project website www.klipper3d.org
Instructions for translators

The code blocks are included in the Gettext files in case if some comments need to be translated. You can add comments as well.

For code blocks without comment, please flag them as ignore-same, if you don't the permission, comment in a GitHub PR to let me know. For links that refer to a title inside an md file, please add a Link Modification Req tag.

The Gettext and markdown files in docs/locales are specific for languages.

Check contributing for current guidelines.

To merge a translation into the main Klipper repository, certain requirements have to be met. We are still determining the requirements and no merging is planned. - Yifei Ding
Project maintainers User avatar kingu User avatar Neko-vecter User avatar KevinOConnor User avatar dingyifei
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/Klipper3d/klipper-translations/
Repository branch translations
Last remote commit locales: Translated using Weblate (Danish) 27e1d5c9a
User avatar L4DK authored 4 days ago
Last commit in Weblate locales: Translated using Weblate (Russian) 5ad73bba4
User avatar dsa-t authored 2 months ago
Weblate repository https://hosted.weblate.org/git/klipper/readme/
File mask docs/locales/*/LC_MESSAGES/Multi_MCU_Homing.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 240 9,450 61,170
Source 8 315 2,039
Approved 0% 0 0% 0 0% 0
Waiting for review 30% 74 29% 2,825 29% 18,272
Translated 34% 82 33% 3,140 33% 20,311
Needs editing 0% 0 0% 0 0% 0
Read-only 3% 8 3% 315 3% 2,039
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 1% 1 1% 5 1% 44
Untranslated strings 65% 158 66% 6,310 66% 40,859
Last 12 months Previous

Activity in last 12 months

8 changes 21 changes 4 changes 8 changes 25 changes 28 changes 19 changes 25 changes 46 changes 1 change 24 changes 25 changes 3 changes 0 changes 20 changes 0 changes 18 changes 13 changes 20 changes 0 changes 12 changes 0 changes 12 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

9,450
Hosted words
240
Hosted strings
34%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+3%
Hosted words
+100%
+3%
Hosted strings
+100%
−1%
Translated
+35%
+100%
Contributors
—
User avatar None

Resource updated

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
File docs/locales/sk/LC_MESSAGES/Multi_MCU_Homing.po was added. 2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Note that an axis with multiple steppers (eg, `stepper_z` and `stepper_z1`) need to be on the same micro-controller in order to use multi-mcu homing. For example, if an endstop is on a separate micro-controller from `stepper_z` then `stepper_z1` must be on the same micro-controller as `stepper_z`.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Should Klipper detect a communication issue between micro-controllers during multi-mcu homing then it will raise a "Communication timeout during homing" error.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Stepper motor overshoot should not adversely impact the precision of the homing and probing procedure. The Klipper code will detect the overshoot and account for it in its calculations. However, it is important that the hardware design is capable of handling overshoot without causing damage to the machine.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
So, for example, if homing at 10mm/s then it is possible for an overshoot of up to 0.250mm (10mm/s * .025s == 0.250mm). Care should be taken when configuring multi-mcu homing to account for this type of overshoot. Using slower homing or probing speeds can reduce the overshoot.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
The overshoot occurs due to possible message transmission delays between the micro-controller monitoring the endstop and the micro-controllers moving the stepper motors. The Klipper code is designed to limit this delay to no more than 25ms. (When multi-mcu homing is activated, the micro-controllers send periodic status messages and check that corresponding status messages are received within 25ms.)
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
This feature can be useful to simplify wiring, as it may be more convenient to attach an endstop or probe to a closer micro-controller. However, using this feature may result in "overshoot" of the stepper motors during homing and probing operations.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Klipper supports a mechanism for homing with an endstop attached to one micro-controller while its stepper motors are on a different micro-controller. This support is referred to as "multi-mcu homing". This feature is also used when a Z probe is on a different micro-controller than the Z stepper motors.
 
2 weeks ago
User avatar None

String updated in the repository

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Multiple Micro-controller Homing and Probing
 
2 weeks ago
User avatar None

Changes committed

  1. Klipper
  2. Multi_MCU_Homing
  3. Slovak
Changes committed 2 weeks ago
Browse all component changes