"prompt": "Translate the following ClickHouse documentation text from English to Russian. Ensure the following rules are followed:\n - This content may be part of a document, so maintain the original html tags and markdown formatting used in Docusaurus, including any headings, code blocks, lists, links, and inline formatting like bold or italic text. Code blocks should be preserved using ` and ```.\n - Ensure that no content, links, explicit heading ids (denoted by {{#my-explicit-id}}), or references are omitted or altered during translation, preserving the same amount of information as the original text.\n - Do not translate code, URLs, or any links within markdown. Mark down links must be preserved and never modified. Urls in text should be surrounded by white space and never have adjacent Russian characters.\n - Ensure the markdown is MDX 3 compatible - escaping < and > with < and > and avoiding the creation of unclosed xml tags.\n - Do not add new code delimiters which are not present in the original content e.g. '```html', even if the content appears to contain this type.\n - Do not translate terms which indicate setting names. These are denoted by lower case and underscore e.g. live_view_heartbeat_interval.\n - Never translate terms which are in all caps (this also applies to fields in the YAML frontmatter). These can be SQL statements so we don't want to translate them. For example do not translate SET ROLE as УСТАНОВИТЬ РОЛЬ, CREATE ROLE as СОЗДАТЬ РОЛЬ or RENAME as ПЕРЕИМЕНОВАТЬ etc.\n - Translate the title (if appropriate), sidebar_label (if appropriate), keywords (list of single quoted strings) and description in yaml metadata blocks if they exist. Ensure these are wrapped in single quotes. Make sure not to add YAML frontmatter if it doesn't exist, and do not ever add entries to the frontmatter.\n - This translation is intended for users familiar with ClickHouse, databases, and IT terminology, so use technically accurate and context-appropriate language. Keep the translation precise and professional, reflecting the technical nature of the content.\n - Strive to convey the original meaning clearly, adapting phrases where necessary to maintain natural and fluent Russian.\n - Use letter ё rather than е where appropriate. For example, it should be лёгкий instead of легкий \n - Do not hallucinate ``` on the last line of translated content.\n- don't translate 'map' as 'карта' when the context is as a function."
0 commit comments