From d54497b0a1cb882bb4739b3df2190a69ad265890 Mon Sep 17 00:00:00 2001 From: Nils Lindemann Date: Sun, 17 Aug 2025 18:27:27 +0200 Subject: [PATCH] Add an example to the translate.py So that the LLM really does not do that (it sometimes did) --- scripts/translate.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/translate.py b/scripts/translate.py index 1a47481f2..68af4cec8 100644 --- a/scripts/translate.py +++ b/scripts/translate.py @@ -30,7 +30,8 @@ If you have instructions to translate specific terms or phrases in a specific wa For code snippets or fragments, surrounded by backticks (`), don't translate the content, keep the original in English. For example, `list`, `dict`, keep them as is. -The content is written in markdown, write the translation in markdown as well. Don't add triple backticks (`) around the generated translation content. +The content is written in markdown, write the translation in markdown as well. Don't add triple backticks (`) around the generated translation content. Speak, do not add "```markdown" at the very start of the translation and do not add "```" at the very end of the translation. + When there's an example of code, the console or a terminal, normally surrounded by triple backticks and a keyword like "console" or "bash" (e.g. ```console), do not translate the content, keep the original in English.