> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v8/report-model/miscellaneous/microsoft-word-and-rich-text-format-support.md).

# Microsoft Word and Rich Text Format Support

## **Microsoft Word (.doc and .docx extension)**

The .doc file extension was proprietary to Microsoft and is still one of the most popular file formats existing today. Software from other types of word processing products had trouble reading files with a .doc extension. As a result, Microsoft created a newer file format called the .docx extension. This signifies the Office Open XML international standard for Office documents. .Docx is supported by a growing number of applications from Microsoft and Apple, as well as open-source word processing programs and other vendors.

## **Rich Text Format (.rtf extension)**

The .rtf file format was developed by Microsoft Corporation for cross-platform document interchange with Microsoft products.

Most word processing software supports RTF format importing/exporting/editing, etc. The RTF Specification uses the ANSI file format. RTF supports generic font family names and also supports the inclusion of image file formats such as JPEG and PNG.

Astera now includes support for Microsoft Word and RTF formats: enjoy efficient and easy information extraction from more source files than ever before. Now you can process invoices, purchase orders, receipts, forms, and other Word/RTF-formatted files with Astera.

The screenshots below illustrate .docx extension support in Astera.

1. Select *File > New > Report Model* and choose your source document.

![](https://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2F2eKwgaSL8Y9UwhfFT8h2%2F0.png?alt=media)

As seen in the screenshot below, the .docx file opens and is ready for processing.

![](https://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2FeEiW6VJdTo6WswMbMb7r%2F1.png?alt=media)

2. You can now continue to create your report model.

![](https://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2Fn77tFTnxoDRf5g1T9Izv%2F2.png?alt=media)


---

# 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://documentation.astera.com/astera-data-stack-v8/report-model/miscellaneous/microsoft-word-and-rich-text-format-support.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.