It is not a perfect solution, but effective for the problem we are facing.
Ideally, components using tCenter can still be "classic" components, but in the designspace/ufo backend, these are treated as variable components, because else the tCenter values get lost. As a proactical solution, we now decompose components that have non-zero values for tCenterX or tCenterY, to make sure they are not stored as variable components in the UFOs.
This fixes #1396.
It is not a perfect solution, but effective for the problem we are facing.
Ideally, components using tCenter can still be "classic" components, but in the designspace/ufo backend, these are treated as variable components, because else the tCenter values get lost. As a proactical solution, we now decompose components that have non-zero values for tCenterX or tCenterY, to make sure they are not stored as variable components in the UFOs.