The shared Template class has constructors to auto-assign US-ASCII as the character encoding and most if not all of the call sites creating them are using that shortcut.
We need to expose encoding options in the schemas and the objects and pass that through. We probably need to default to ASCII for the time being for compatibility.
The shared Template class has constructors to auto-assign US-ASCII as the character encoding and most if not all of the call sites creating them are using that shortcut.
We need to expose encoding options in the schemas and the objects and pass that through. We probably need to default to ASCII for the time being for compatibility.