> 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/pasco/tips-n-tricks/editing-with-texteditor.md).

# Using a text editor to make your language tree

Before you edit the raw language file you must remember some rules!

1. Use a **Plain Text editor**. **Don't use Microsoft Word, Wordpad, Apple Pages or similar**. When you have a plain text editor - no fancy formatting like bolding text or underlining is possible. Which is great for pasco - as it will mess with its head!. The only formatting you can use is a tab to indent the text (or use spaces). For example:

   ```
    Chat
    	Social Chat
    		Alright Mate
    		How's things?
    	Polite Chat
    		Good morning
    		How are you?
    		Anything I can do for you today
    Care Messages
    	Body Parts
    	Medical equipment
    		Chair
    		Bed
    I'll spell it
   ```
2. **Tabs and Spaces don't mix!** Each line can start with either spaces OR tabs. Not both

So you cannot do this:

```
[space-space]I'll spell it
```

i.e. here the file has started with a space - but then given a tab. The next line has two spaces. In many text editors this is difficult to see - but effectively we have messed up pasco. Does it look at spaces or tabs?

1. **Cues can be put in brackets**

for example if you wanted the person to be able to say "Hello World" (Main Voice) but a cue to be "Hello" we could do this:

```
Hello World(hello)
```

## Editing with Notes on iOS

Unless you have a fancy iPad Pro - or are using an external keyboard you cant use tabs on the iPad - so you will **have** to use spaces instead. Where you would use one tab to indent - do the same with a space. Keep the number of spaces the same so your file looks nice and neat.

## Editing with Notepad on Windows


---

# 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/pasco/tips-n-tricks/editing-with-texteditor.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.