> For the complete documentation index, see [llms.txt](https://lewe.gitbook.io/teamcal-neo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lewe.gitbook.io/teamcal-neo/administration/language-classic.md).

# Language (classic)

## Classic Structure

TeamCal Neo comes with two languages, English and German. In the classic structure, the language terms are saved in four files per language in the `languages` folder:

| File                 | Content                                      |
| -------------------- | -------------------------------------------- |
| \[language].php      | Strings related to the application framework |
| \[language].app.php  | Strings related to the calendar application  |
| \[language].gdpr.php | Strings related to the GDPR page             |
| \[language].log.php  | Strings related to the system log            |

If you want to create your custom language, copy those four files and replace the \[language] part with your language name. TeamCal Neo will automatically scan them and allow to switch to them. Of course, you need to translate all the srtings in those files too.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://lewe.gitbook.io/teamcal-neo/administration/language-classic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.