> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/tag-extensions/rich-text-fields.md).

# Manage "Rich Text" fields

By default, the Salesforce formatting is applied to the content of a rich text field placed in a Word document at generation. Add one or more tag extensions to change these settings.

By default, the formatting chosen in the Salesforce field is applied at generation: size, color, indentation... To override this formatting and apply the format defined in Word, use a tag extension that lets you choose exactly the right format.

**Formats you can change**

* **"f"** for "font"
* **"s"** for "size"
* **"c"** for "color"
* **"t"** for "type form" = character style
* **"i"** for "indentation"

1. From the assistant, go to the Rich Text tag you want to change
2. Click the 3 small dots on the right
3. Click "Format rich text"
4. Select the formatting to take from Word
5. Your tag is copied and can be pasted into your template where you want it

{% hint style="danger" %}
**Warning**

If indentation is not handled correctly, use the **i** extension to make the display consistent, with a tag such as `{!Account|Description(HTML,i)}`
{% endhint %}

{% hint style="success" %}
**Example**

`{!Account|Description(HTML,f,s)}` if you want to apply the font and size of the Word tag defined in the template. The result will be consistent with the Word layout.
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/tag-extensions/rich-text-fields.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.