Table of Contents
- Introduction
- Installation
- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags
- Graphics

  | · Introduction · Fonts · Image File Formats · Graphical Text · Business Graphics · Pike Image Module

- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting
- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

Graphical Text
This module defines the `<gtext>` tag that renders text into GIF images. For more information see the gtext page in the User manual.

`Cache directory for gtext images`
  Where to save the generated images. All generated images are saved for a while since they will usually be referred to more than once.

`Default number of colors per image`
  The default number of colors to use, 16 is usually sufficient. The size of the image will depend on the number of colors.

`Normalize colors in parsed tags`
  Challenger can handle colors in many different formats, RGB (#rrggbb), CMYK (@c,m,y,k) and as English words (black). Not all versions of browsers support those color formats. If this variable is set the gtext module will convert the colors in the HTML tags specified in the Tags to parse for color variable to the RGB format (#rrggbb).

`Tags to parse for color`
  When rendering an image it is important to know the background color. The gtext module can try to find out the background color by parsing HTML tags where you can set background color. This way the user does not have to explicitly set the background in the `<gtext>` tag. On the other hand, parsing all those tags will use quite a lot of CPU. Often more CPU than the actual image generation, since every one of these tags will be parsed for every RXML page, regardless of whether there are any `<gtext>` tags on the page or not.

  If you later decide to change this variable to be more restrictive, some pages that rely on this feature might stop working. If you are concerned about CPU usage you should be restrictive from day one.

  You will have to reload this module or restart Challenger to make changes to this variable take effect.

Example