Klipper

Command_Templates

Spanish

Translate

Zen

Translation

English

Spanish

Needs editing

Sign in to save the translation.

Skip

	English	Spanish	Actions
	This document provides information on implementing G-Code command sequences in gcode_macro (and similar) config sections.	Este documento proporciona información sobre G-Code y implementando las secuencias de comandes en gcode_macro (y lo similar) secciones de configuración
	G-Code Macro Naming	El nombrado macro de G-Code
	Case is not important for the G-Code macro name - MY_MACRO and my_macro will evaluate the same and may be called in either upper or lower case. If any numbers are used in the macro name then they must all be at the end of the name (eg, TEST_MACRO25 is valid, but MACRO25_TEST3 is not).
	Formatting of G-Code in the config
	Indentation is important when defining a macro in the config file. To specify a multi-line G-Code sequence it is important for each line to have proper indentation. For example:
	Note how the `gcode:` config option always starts at the beginning of the line and subsequent lines in the G-Code macro never start at the beginning.

Loading…

dingyifei

Suggestion accepted

English

Spanish 153 characters edited Current translation Translated

a year ago

Euph_xTc-

Suggestion added

English

Spanish 154 characters edited

a year ago

Browse all string changes

Things to check

Double space

Translation contains double space

Mismatched full stop

Source and translation do not both end with a full stop

Glossary

English	Spanish
No related strings found in the glossary.

String information

Screenshot context

Screenshot 2021-06-21 at 09-12-20 KevinOConnor klipper-translations

Flags

md-text

String age

2 years ago

Last updated

11 months ago

Source string age

2 years ago

Translation file

docs/locales/es/LC_MESSAGES/Command_Templates.po, string 1