> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/standards/edit-standards/alternate-language.md).

# Manually enter alternate language text

Contact your system administrator to set the secondary languages available for translation.

Contact your system administrator to set the secondary languages available for translation. Available options are:

*French, German, Italian, Japanese, Portuguese, Russian, Spanish, Ukrainian*

Currently, translated content may only be entered for fields shown in the Content ribbon when editing a Standard. These fields are:

*Title, Summary, Description, Feature, Body, Statements*

**Step 1** Find and edit the standard.

**Step 2** Open the Content ribbon, and click the pencil icon.

**Step 3** To enter French text, click the FR link.

**Step 4** Enter the French text directly in the Edit box.

**Step 5** Save

*Helpful tip: You can edit multiple fields within the Content ribbon without losing your data, but you must save before you navigate away from the Content ribbon.*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shiftiq.com/help/standards/edit-standards/alternate-language.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.