> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/gauge-chart/labels.md). # Labels The **Labels** tab controls the visible text shown on each gauge. #### Font settings * **Font Size - Dimension**: scales the dimension label size * **Font Family**: uses the workbook font from Tableau #### Gauge Label Enable **Gauge Label** to show the category or dimension label. Available shortcodes: * `` * `` Example: ``` ``` #### Gauge Value Label Enable **Gauge Value Label** to show the main value and optional status information. Available shortcodes: * `` * `` * `` * `` * `` * `` * `` * `` Example: ```
``` #### HTML support Labels support basic HTML formatting, including: * headings such as `H1` * images such as `IMG` * line breaks using `
`
--- # 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.infotopics.com/showmemore/features/gauge-chart/labels.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.