# Translations

### Theme Translations

To translate theme stings please use **Multi-language Content Filter.**

{% hint style="warning" %}
**Multi-language Content Filter Documentation**

<https://docs.moodle.org/400/en/Multi-language_content_filter>
{% endhint %}

{% hint style="success" %}
**Theme Language Pack**

If you're interested in collaborating and contributing a translation pack to the theme, kindly reach out to me. [via the support page.](https://roseathemes.ticksy.com/)

File to translate you can find in *space/lang/en/theme\_space.php*
{% endhint %}

### **Adding a new language to Moodle**

1. **Go to:** `Dashboard → Site administration → Language → Language packs`
2. **Select** Available language packs (on the right)
3. **Install** selected language pack(s)

### **What can I do with untranslated Moodle elements?**

1. **Go to:** `Dashboard → Site administration → Language → Language customization`
2. **Select** the language to add a translation.
3. **Click:** Open language pack for editing
4. Show strings of these components: Select all (`Ctrl + A` or `CMD + A`)
5. Only strings containing: e.g **`Sample non-translated string`**
6. **Click:** Show strings
7. Add translation and Save


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rosea.gitbook.io/space-moodle-theme/getting-started/translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.