It sounds like a good spot, though. Thanks.
Other languages: It already came up, earlier today. That would be interesting!
Fetch the two lists: I just make them EXPORT_OK and documented global lists. If there are selectible word lists, then maybe it shouldn't be under EN but can choose language at run-time?
This is the code, BTW, starting on line 528 in the file after the word lists.
Good point about having an inverse function! The principle use is to compare two lists, not copy a list (I use the NATO alphabet for the latter). I figured a useful "inverse" would be heavy on the user interface. E.g. start typing the first few letters and it jumps to the right spot in a scrolling list.sub _mapone { my ($code, $counter)= @_; my $list= (($counter&1) == 0) ? \@two_syllable_words : \@three_syllab +le_words; my $result= $$list[$code]; die unless defined $result; # internal error -- can't happen. return $result; } sub list { my $x= shift; # delete leading zeros $x =~ s/^\0+//; my $counter= 0; return map { _mapone ($_, $counter++) } (unpack ("C*", $x)); }
Interesting game re constructing sentences. I put in the zipcode at work, as a 4-byte long, and thought I got an error since the output started with "absurd...". The zipcode is "absurd cellulose assume". I put those into Google and eyeball one that's in the right order. So... find existing text that encodes the message, and then refer to it?!
You also might like regional variations on the word lists, not just whole different languages. Here in Texas, some words have 3 syllables when in other parts of the country they only have 1 or 2.
In reply to Re: (tye)Re: Biometric Word List -- in a pm file
by John M. Dlugosz
in thread Biometric Word List -- in a pm file
by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |