Ah, this would be because I haven't added "，" as a character that gets an auto-delay by default... This system has two caveats that I need to reprogram so hopefully I get time to do that soon...
Basically, for autodelays, it's using the standard delay data scriptableobject to determine what characters are getting delays. These delay datas have special names used by the "SpecialKeyToName()" method inside of SuperTextMesh.cs. So... the ones that don't have names there won't work as it stands.
The second issue is what you pointed out, the autodelay system will only care about what it calls "free" characters, characters with a space afterwards. A friend had some concerns about this system too, so what I want to do is...
1) Make a new, separate type of data for autodelays that instead of relying on the scriptableobject name, has a field for a char, and uses that.
2) This new type can also determine the behaviour. So "." might only come into effect if the next character is a space, while "，" will always cause a delay no matter what.
Different options: Always Delay, Only if followed by space, Only if followed by different character, Only if followed by same character or a space
Hopefully I can have this implemented soon, I think this will solve the issue...?