> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/readme/reset-font-properties.md).
# Reset font properties
### Resetting font properties
Most font properties in Vitara Charts’ Property editor are set to ‘Auto’ by default. Let’s look at how to reset the font settings to ‘Auto’ after manually providing them in this document. Font features such as ‘font-family’ and ‘font-size’ are particularly important.
#### 1. Font family
Font family can be applied to Axes, Data labels, Tooltip text, Legend labels, and other elements. Assume we change the font family of some text in a chart to ‘Times New Roman’, as shown in the screenshot below:
Now to set back this font family property to ‘Auto’, then just set it to Select from the Labels dropdown as shown in the screenshot below:
2\. Font size
Almost all labels in a chart, including axes, data labels, tooltip text, legend labels, and series width, can have the font size property set. Assume we set the Data labels size in a chart to ‘14’, as shown in the screenshot below:
Now to reset the data labels size to ‘Auto’, just make the font size textbox empty\[select and clear the font size number using backspace]. See the screenshot below:
---
# 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.vitaracharts.com/readme/reset-font-properties.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 `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.
