> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/aac-speak-helper-tool/writing-with-languages.md).

# Writing with languages

So we are not providing here software Gridsets/Pagesets of Keyboards for different languages.&#x20;

If you want a client to write in the language of this TTS system (not use translate) You have to

* Find a keyboard layout the client is familar with in the correct **script**.

{% hint style="info" %}
This part is **KEY.** Many TTS systesm will not respond or act strangely if you present the wrong script (eg. latin script as in English, French, German when a TTS is needing arabic). You can get lucky but technically the system may be doing transliteration without you realising it
{% endhint %}

* Copy and paste the characters needed into a Gridset/Pageset that you need. Remember to not put spaces behind the characters&#x20;
* This is painstaking. Please consider sharing your work so others can benefit.&#x20;


---

# 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://docs.acecentre.org.uk/products/aac-speak-helper-tool/writing-with-languages.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.
