> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-universal-printing-best-practices/v19/parallels-ras-universal-printing-best-practices/fonts-and-font-caching.md).
# Fonts and font caching
One of the common printing issues for all universal printing solutions is to create an identical fonts environment for the server and the client.
For the EMF format (Windows only) Parallels RAS Universal Printing is able to extract embedded fonts (or fonts used in a particular document) automatically and then transfer them to Parallels Client allowing it to print documents using the same exact fonts.
Parallels Client can cache fonts installed on a local computer, so it does not have to extract and transfer this data over network on subsequent printouts.
## **Parallels recommends**
Exclude standard operating system fonts (Arial, Times New Roman, etc.). Also exclude fonts that are already present on RD Session Hosts according to the **Fonts Management** settings in the RAS console. To view and modify the settings, open the RAS console and navigate to **Universal Printing** > **Fonts**.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.parallels.com/landing/ras-universal-printing-best-practices/v19/parallels-ras-universal-printing-best-practices/fonts-and-font-caching.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
