> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-work-with-right-to-left-languages.md).

# How To: Work with Right-to-Left Languages

Format templates for right-to-left languages like Hebrew and Arabic.

Use RTL options when document text must render correctly for right-to-left languages.

### Problem

You need to generate documents in Hebrew, Arabic, or other right-to-left languages.

### Solution 1: RTL for Merge Fields

**Reverse a single field:**

```
{{!Account.Greeting__c RTL="true"}}
```

**Input:** `שלום`\
**Output:** `םולש`

### Solution 2: RTL for Entire Sections

**Reverse a section with static text:**

```
<rtl>reverse</rtl>
<p>Welcome to our company, {{!Account.Name}}!</p>
<p>Your account number is: {{!Account.AccountNumber}}</p>
```

Both static text and merge field data reverse.

### Solution 3: Multi-Line RTL

**Use separate tags for each line:**

```
<rtl>reverse</rtl>
<p>First line of text with {{!Field1}}</p>

<rtl>reverse</rtl>
<p>Second line of text with {{!Field2}}</p>
```

RTL tags do not work well when text wraps across multiple lines.

### Complete RTL Document Example

```
<html dir="rtl">
<head>
  <style>
    body {
      direction: rtl;
      text-align: right;
      font-family: Arial, sans-serif;
    }
  </style>
</head>
<body>
  <rtl>reverse</rtl>
  <h1>{{!Account.Name}}</h1>

  <rtl>reverse</rtl>
  <p>Account ID: {{!Account.AccountNumber}}</p>

  <rtl>reverse</rtl>
  <p>{{!Account.Description__c}}</p>
</body>
</html>
```

### Tips

* `RTL="true"` affects merge field data only.
* `<rtl>` affects static text and merge fields.
* Do not combine both on the same field.
* Use separate `<rtl>` tags for each line.
* Test with real RTL content before rollout.


---

# 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://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-work-with-right-to-left-languages.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.