This is an issue with the old TextNative text framework. In 6000.0 we moved everything to the newer TextCore framework which seems to have also fixed this issue. We cannot backport this move back to 2022 or older, nor can we risk making core changes in 2022 or older on TextNative.