Remove human-oriented sections from core style guide

Oleksandr Pysaryukrequested to merge
opysaryuk-main-patch-6128 into main

Description

Removing the following sections from gitlab-translation-styleguide.md. These are human-translator guidance that is either redundant with the system prompt, or not actionable for an LLM-based agent:

  1. Core Principles (all 6 items) is redundant or not meaningful for an LLM agent. "Understand First" is how LLMs work by default. "Translate Naturally" is verbatim in the system prompt ("Reconstruct content for natural expression... Translate for meaning, not word-for-word"). "Use Approved Terminology" is enforced by system prompt steps 2 and 4. "Adapt Culturally" is vague, the language-specific guides are a better place to handle that. "Preserve Technical Content" is a less detailed duplication of the Technical Content Rules section in the same file.
  2. Common Mistakes to Avoid (all 7 items) , here every item is either redundant with the system prompt (like references to word-for-word, terminology, over-localization), or redundant within the style guide itself (filenames covered in Blog Translation Rules, LOCALE-SPECIFIC comments covered in Terminology/Never Translate), or not meaningful for an LLM (ignoring context, literal idioms - are things that LLM are unlikely to do deliberately).
  3. Document new terms for updates appears twice (Core Principles and Terminology 5-step process). Vague and not actionable, i.e. document where, how? 🤔
  4. Using Approved Terminology (5-step process) is fully redundant. System prompt step 2 loads the termbase with full URLs, system prompt "Mission and approach" states "All terminology must match the official termbase exactly", and step 4 validates 100% compliance. Every step in this process is already enforced by the system prompt.

Related

Type of Change

  • New feature
  • Bug fix
  • Documentation update
  • Style guide or terminology update
  • Configuration change
  • Other (please describe)

Changelog Entry

  • Changelog entry added to CHANGELOG.md
  • Entry is in the [Unreleased] section
  • Used appropriate category (Added/Changed/Fixed/Deprecated/Removed/Security)
  • Included MR reference at the end of the entry (e.g., (!123))
Edited by Oleksandr Pysaryuk

Merge request reports