On July 7, 2008 at 11:43, Barry Warsaw wrote:
Actually RFC 3548 defines a "url safe" base64 alphabet which substitutes -
and _ for + and /. Python's base64 library supports this and I propose
using this alternative alphabet if we go with base64.
I did not know there was an RFC for this.
The RFC is marked as "Informational", so how widely used is
the URL-safe base64 encoding used?
Nothing is currently listed in the IETF assignments for this
type of encoding:
http://www.iana.org/assignments/transfer-encodings
I have no problems going with it, as long as it is documented.
However, from a usability perspective (possibly), the use
of understrike can be a problem.
For example, links are normally rendered with an underline, and
this rendering behavior can "hide" an understrike character, making
the URL appear to have a space in it.
--ewh
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV
