Skip Menu |
 

This queue is for tickets about the Number-RecordLocator CPAN distribution.

Report information
The Basics
Id: 36294
Status: rejected
Priority: 0/
Queue: Number-RecordLocator

People
Owner: Nobody in particular
Requestors: MichaelRWolf [...] att.net
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Better algorithm documentation
Download (untitled) / with headers
text/plain 236b
It's not clear why you use a 32 character alphabet, and why you choose to map the characters that you did. What's so special about them that they need to be special-cased? What criteria was used to define "easy to read and pronounce"?
Subject: Re: [rt.cpan.org #36294] Better algorithm documentation
Date: Fri, 30 May 2008 11:01:39 -0400
To: bug-Number-RecordLocator [...] rt.cpan.org
From: Jesse Vincent <jesse [...] fsck.com>
Download (untitled) / with headers
text/plain 802b
On May 30, 2008, at 3:44 AM, Michael R. Wolf via RT wrote: Show quoted text
> > Fri May 30 03:44:19 2008: Request 36294 was acted upon. > Transaction: Ticket created by MichaelRWolf@att.net > Queue: Number-RecordLocator > Subject: Better algorithm documentation > Broken in: (no value) > Severity: Wishlist > Owner: Nobody > Requestors: MichaelRWolf@att.net > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=36294 > > > > It's not clear why you use a 32 character alphabet,
Base 32 is convenient to work in. Show quoted text
> and why you choose > to map the characters that you did. What's so special about them that > they need to be special-cased? What criteria was used to define "easy > to read and pronounce"?
Ad-hoc user testing and experience with other similar system.
Download PGP.sig
application/pgp-signature 186b

Message body not shown because it is not plain text.



This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.