Defines options for reading, displaying, and writing the svg.
The most important option as far as compatibility is the soUseFillText option. When this option is present, the RSCL uses FillText calls to directly render the text to the canvas. When this option is not present (default), the RSCL converts text into paths that are then filled and stroked. Converting text to paths provides the highest compatibility but slower performance. If you use the FMX GPU Canvas (FMX.Types.GlobalUseGPUCanvas), text is always filled and not converted to paths.
The following differences exist between the two text rendering paths:
• Fill Text does not use the Pen and so cannot both fill and stroke text
• Fill Text cannot use gradients for filling (FMX)
•ShapeRendering affects the smoothness of text when filling path-based text (as text are shapes); TextRendering affects the smoothness of text when filling text
• Fill Text uses less memory
• Fill Text generates better text at small sizes
• Path-based text caches its shapes so subsequent draw calls are faster, even faster than fill text calls in many cases
• Path-based text allows pixel level selection of text; Fill Text can only be selected as a text bounding box
• Path-based text renders decorative fonts (underline, overline, and strike-out) using an extra path for the decoration (FMX will not generate paths with the decoration when converting text to paths). Surprisingly, this means that compatibility is higher with path-based text as the decoration gets its rendering configuration from the parent text element (e.g., strike-out text should use the parent text's font size and not vary as the size of child text span's font size changes).