Translation status

100 Strings 0%
Browse Translate
4,491 Words 0%
30,801 Characters 0%

Strings status

Strings Words Characters
100 4,491 30,801
All strings Browse Translate Zen
100 4,491 30,801
Unfinished strings Browse Translate Zen
100 4,491 30,801
Untranslated strings Browse Translate Zen
100 4,491 30,801
Unfinished strings without suggestions Browse Translate Zen
100 4,491 30,801
Strings without a label Browse Translate Zen

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 KevinOConnor User avatar Neko-vecter 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: Automated Gettext Update(Manually Triggered) 69d82c5ec
GitHub authored 3 weeks ago
Last commit in Weblate locales: Translated using Weblate (Portuguese) 80e41e928
User avatar dieguesmosken authored 4 days ago
Weblate repository https://hosted.weblate.org/git/klipper/readme/
File mask docs/locales/*/LC_MESSAGES/Code_Overview.po
Translation file Download docs/locales/dua/LC_MESSAGES/Code_Overview.po
Last change April 3, 2024, 7:36 a.m.
Last author None
12 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 100 4,491 30,801
Approved 0% 0 0% 0 0% 0
Waiting for review 0% 0 0% 0 0% 0
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 100 100% 4,491 100% 30,801
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar None

Resource updated

  1. Klipper
  2. Code_Overview
  3. Duala
The “docs/locales/dua/LC_MESSAGES/Code_Overview.po” file was changed. 3 weeks ago
User avatar None

String added in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
Klipper uses an [iterative solver](https://en.wikipedia.org/wiki/Root-finding_algorithm) to generate the step times for each stepper. For efficiency reasons, the stepper pulse times are generated in C code. The moves are first placed on a "trapezoid motion queue": `ToolHead._process_moves() -> trapq_append()` (in klippy/chelper/trapq.c). The step times are then generated: `ToolHead._process_moves() -> ToolHead._advance_move_time() -> ToolHead._advance_flush_time() -> MCU_Stepper.generate_steps() -> itersolve_generate_steps() -> itersolve_gen_steps_range()` (in klippy/chelper/itersolve.c). The goal of the iterative solver is to find step times given a function that calculates a stepper position from a time. This is done by repeatedly "guessing" various times until the stepper position formula returns the desired position of the next step on the stepper. The feedback produced from each guess is used to improve future guesses so that the process rapidly converges to the desired time. The kinematic stepper position formulas are located in the klippy/chelper/ directory (eg, kin_cart.c, kin_corexy.c, kin_delta.c, kin_extruder.c).
 
3 weeks ago
User avatar None

String added in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
LookAheadQueue.flush() determines the start and end velocities of each move.
 
3 weeks ago
User avatar None

String added in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
LookAheadQueue.add_move() places the move object on the "look-ahead" queue.
 
3 weeks ago
User avatar None

String added in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
The ToolHead class (in toolhead.py) handles "look-ahead" and tracks the timing of printing actions. The main codepath for a move is: `ToolHead.move() -> LookAheadQueue.add_move() -> LookAheadQueue.flush() -> Move.set_junction() -> ToolHead._process_moves()`.
 
3 weeks ago
User avatar None

Resource updated

  1. Klipper
  2. Code_Overview
  3. Duala
The “docs/locales/dua/LC_MESSAGES/Code_Overview.po” file was changed. a year ago
User avatar None

String updated in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
Task, init, and command functions always run with interrupts enabled (however, they can temporarily disable interrupts if needed). These functions should avoid long pauses, delays, or do work that lasts a significant time. (Long delays in these "task" functions result in scheduling jitter for other "tasks" - delays over 100us may become noticeable, delays over 500us may result in command retransmissions, delays over 100ms may result in watchdog reboots.) These functions schedule work at specific times by scheduling timers.
 
a year ago
User avatar None

Resource updated

  1. Klipper
  2. Code_Overview
  3. Duala
File “docs/locales/dua/LC_MESSAGES/Code_Overview.po” was added. 2 years ago
User avatar None

String updated in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
Prefer writing explicit values to IO registers instead of using read-modify-write operations. That is, if updating a field in an IO register where the other fields have known values, then it is preferable to explicitly write the full contents of the register. Explicit writes produce code that is smaller, faster, and easier to debug.
 
2 years ago
User avatar None

String updated in the repository

  1. Klipper
  2. Code_Overview
  3. Duala
Avoid using "C bitfields" to access IO registers; prefer direct read and write operations of 32bit, 16bit, or 8bit integers. The C language specifications don't clearly specify how the compiler must implement C bitfields (eg, endianness, and bit layout), and it's difficult to determine what IO operations will occur on a C bitfield read or write.
 
2 years ago
Browse all translation changes