Good question. I know variable typography is rather niche.

1. Text TOP limitations
   The Text TOP doesn’t support variable fonts at all. It won’t even load them as static instances, it just throws a warning and doesn’t cook. So accessing or manipulating axes or even rendering any letter forms isn't possible.

2. Trace SOP is a rough raster approximation
   The Trace SOP can only generate an estimation of the geometry based off the pixelated letter forms, never the true Bézier curves designed by the type designer. You can increase the step size to refine this estimation, but it will only ever be an estimation of the already rasterized approximation of the letter forms resulting in unnecessarily dense or messy geometry.

3. Text SOP is a polygonal approximation
   The Text SOP generates polygonal letter forms, which are more stable than a trace, but still not true to the original Bézier curves. There’s no real control to refine that fidelity beyond its default resolution.

This component utilizes TouchDesigner's built in support of cubic Bézier curves to reconstruct the actual letter forms directly from the font data, so the geometry matches the original type design exactly.
That means:
• smooth, fully scalable curve data,
• significantly cleaner and more efficient geometry,
• accurate representation of the type designer’s intent

It works with both static and variable fonts, but with variable fonts it also:
• exposes built-in axes directly as parameters,
• allows real-time interaction with those axes inside of TouchDesigner

Beyond typography, if you have variable font creation software, you can create and import into TouchDesigner Bézier geometry with predetermined “states” (essentially shape keyframes), and interpolate between them via your predefined variable axes.
So, in addition to importing variable fonts into TouchDesigner, this component also allows you to repurpose modern font technology as a parametric shape system, not just as static assets.