> For the complete documentation index, see [llms.txt](https://docs.gooey.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gooey.ai/speech-and-language/how-to-use-compare-ai-translations/google-translate-glossary.md).

# Google Translate Glossary

These sheets contain the glossary information for Google Translate translations on gooey.ai. Please be careful when updating the sheets since it is possible to break translations with incorrect syntax. It is best to copy and paste complete changes into Glossary.sheets (i.e. one row/column at a time). See an example glossary [here](https://docs.google.com/spreadsheets/d/1IRHKcOC86oZXwMB0hR7eej7YVg5kUHpriZymwYQcQX4/edit#gid=0).

### Glossary.sheet <a href="#ggm07dbcp5ot" id="ggm07dbcp5ot"></a>

This sheet contains the glossary terms. The first row should be [ISO-639](https://wikipedia.org/wiki/ISO_639) or [BCP-47](https://tools.ietf.org/html/bcp47) language codes. Two extra columns are allowed: “pos” to specify part of speech and “description” (these columns are currently ignored by the Google Translate API but may be used in the future):

<figure><img src="/files/uWHFUnaQDYOgSiYq1T0y" alt=""><figcaption></figcaption></figure>

Each subsequent row is then one glossary term in multiple languages. Read more [here](https://cloud.google.com/translate/docs/advanced/glossary#translate_v3_translate_text_with_glossary-drest). Changes made to this file are automatically uploaded to a Google Cloud Bucket to be used as a translation Glossary in gooey-server Google Translate requests.

**Notes**:

* By default, each glossary term is not case-sensitive. This parameter can be changed in the gooey-server code.
* Glossary entries for stopwords are[ignored by the Google Translate API](https://cloud.google.com/translate/docs/advanced/stopwords)


---

# 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.gooey.ai/speech-and-language/how-to-use-compare-ai-translations/google-translate-glossary.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.