Re-evaluate usage of encoding throughout the package #103
Labels
area: api 🤖
issue: planned ⌚
Assigned to a specific version's milestone
topic: encodings ↔️
type: question ❔
Something to investigate
Milestone
Right now many things internally are coerced to using UTF-8. This may be fine! Occurrences of encoding collisions may be infrequent enough that it might as well be a YAGNI to do this.
But, it would be a good opportunity to strengthen understanding of when to handle encodings in which way(s).
The text was updated successfully, but these errors were encountered: