Strict/Lax Considerations

strict mode:
- should avoid undocumented assumptions about internal encoding,
- should reject or warn about string/character edge cases whose behavior is known to vary across Unicode modes or host versions,
- should prefer explicitly encoded text I/O where supported.
lax mode:
- may accept broader compatibility behavior for legacy text handling,
- may emulate legacy ASCII/MBCS behavior when targeting pre-2021 Autodesk semantics or equivalent host profiles.