Skip to content

Consider base16k #11

Closed
Closed
@sffc

Description

@sffc

My colleague @markusicu has proposed Base16k as an alternative to Base64 that is more compact when the resulting text is stored as UTF-16. This could be useful when storing byte arrays in JSON, for example.

https://sites.google.com/site/markusicu/unicode/base16k

If we're going to be opinionated enough to add Base64 to the standard library, then perhaps we should explore some competitors on their own merits.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions