diff options
author | gdt <gdt> | 2010-07-24 17:56:26 +0000 |
---|---|---|
committer | gdt <gdt> | 2010-07-24 17:56:26 +0000 |
commit | 1d9ab56f6bb6a5d3b803960d632b5f7ad0732bce (patch) | |
tree | 9053800d904735224954f8e985c06f32110ec1c1 /devel/rdp | |
parent | a9624c4afac08867d39f89f510c4ac7d209a2866 (diff) | |
download | pkgsrc-1d9ab56f6bb6a5d3b803960d632b5f7ad0732bce.tar.gz |
Import py26-zbase32-1.1.2 as converters/py-zbase32.
An alternate base32 encoder (not RFC 3548 compliant).
The rationale for base-32 encoding in RFC 3548 [1] is as written therein: "The
Base 32 encoding is designed to represent arbitrary sequences of octets in a
form that needs to be case insensitive but need not be humanly readable.".
The rationale for our encoding is different -- it is to represent arbitrary
sequences of octets in a form that is as convenient as possible for human
users to manipulate. In particular, z-base-32 was created in order to serve
the Mnet project [3], where 30-octet cryptographic values are encoded into
URIs for humans to manipulate. Anticipated uses of these URIs include cut-
and-paste, text editing (e.g. in HTML files), manual transcription via a
keyboard, manual transcription via pen-and-paper, vocal transcription over
phone or radio, etc.
The desiderata for such an encoding are:
* minimizing transcription errors -- e.g. the well-known problem of confusing
`0' with `O'
* embedding into other structures -- e.g. search engines, structured or
marked-up text, file systems, command shells
* brevity -- Shorter URLs are better than longer ones.
* ergonomics -- Human users (especially non-technical ones) should find the
URIs as easy and pleasant as possible. The uglier the URI looks, the worse.
Diffstat (limited to 'devel/rdp')
0 files changed, 0 insertions, 0 deletions