> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gleef.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Translation Rules

> Create custom rules to guide AI translation behavior

# Translation Rules

Translation Rules allow you to customize how AI generates translations, ensuring consistency with your brand voice and style across all languages.

<img width="2204" src="https://mintcdn.com/gleef/tXnFupSgBwtDVBoF/images/studio/rules.png?fit=max&auto=format&n=tXnFupSgBwtDVBoF&q=85&s=2506ca7e43532777badd621036a83380" alt="translation rules screenshot" data-path="images/studio/rules.png" />

## Creating Rules

### Rule Setup

1. **Navigate to Translation Rules** section
2. **Click "Create New Rule"** button
3. **Enter rule title** and detailed description
4. **Provide examples** of good and bad translations
5. **Save and activate** the rule

### Rule Types

**Tone and Voice**

* Control formality levels (formal vs casual)
* Define brand personality in translations
* Specify addressing conventions (tu/vous, Sie/du)

**Formatting Guidelines**

* Number formats (1,000 vs 1.000)
* Date formats (DD/MM/YYYY vs MM/DD/YYYY)
* Currency display (€100 vs 100€)
* Time formats (24-hour vs 12-hour)

**Language Structure**

* Prefer present tense and active voice
* Avoid complex sentence structures
* Use consistent terminology across translations

## Rule Examples

### Formal Tone Rule

```
Title: French Formal Address
Description: Always use "vous" form when addressing users in French
Example: "Connectez-vous" not "Connecte-toi"
```

### Currency Format Rule

```
Title: Euro Display Format
Description: Place euro symbol after amount with space
Example: "100 €" not "€100"
```

### Voice and Tone Rule

```
Title: Brand Voice
Description: Use "nous" when speaking as the company, "vous" when addressing users
Example: "Nous recommandons" not "On recommande"
```

## Managing Rules

### Rule Organization

* **Search rules** by title or description
* **Edit existing rules** to refine guidelines
* **Delete outdated rules** that no longer apply
* **View rule usage** in translations

### Rule Application

* **Automatic application** to new translations
* **Retroactive effects** may apply to existing content
* **Rule conflicts** resolved by priority order
* **Rule testing** with sample translations

## Best Practices

### Effective Rule Writing

* **Be specific** - provide clear, actionable guidance
* **Include examples** - show correct and incorrect usage
* **Consider context** - account for different content types
* **Keep updated** - regularly review and refine rules

### Rule Management

* **Start simple** - begin with basic tone and formatting rules
* **Add gradually** - introduce new rules based on observed needs
* **Test thoroughly** - verify rules produce expected results
* **Team alignment** - ensure rules reflect team consensus

### Common Rule Categories

* **Formality levels** for different languages
* **Brand voice consistency** across all content
* **Technical terminology** standardization
* **Cultural adaptation** for regional markets