From: Ian Sparkes <isparkes@q9f47.dmst02.telekom.de>
Date: Tue, 12 Aug 1997 00:07:01 +0800
To: Adam Back <mark@unicorn.com
Subject: Re: Comments on PGP5.0 OCR (was Re: fyi, pgp source now available , internationally)
In-Reply-To: <Pine.LNX.3.91.970811105552.3203A-100000@cowboy.dev.madge.com>
Message-ID: <3.0.2.32.19970811174614.0068a410@q9f47.dmst02.telekom.de>
MIME-Version: 1.0
Content-Type: text/plain



At 15:32 11.08.97 +0100, Adam Back wrote:
>
>Mark Grant <mark@unicorn.com> writes:
>> 
>> I just wanted to make a few comments on the proofreading, in case anyone
>> feels like releasing software in a similar manner in future:
>> 
>> [...] the OCR-ed pages at HIP included a per-line
>> checksum. This was good... but... it also checksummed the whitespace. 
>> This wasn't a problem in theory, because tabs were indicated by a special
>> character. However, most lines had both tabs *and* spaces and there was no
>> way to see where the spaces were because they were overrriden by the tab
>> (e.g. "mov<sp><tab>ax,23<sp><sp><tab><sp><tab>; Stuff"). 
>
>How about a book full of 2D barcodes?  
>
>As a plus perhaps the book would be more compact, as you could gzip it
>first -- the full source tree looks to be over a foot of doublesided
>paper!
>

How about importing the scanned in source (in electronic form) back into
the States and doing a 'diff' there. This could produce an electronic
patchfile to repair the mistakes in the scanned in code, meaning that the
whole of the code could be cleaned up in one go. This patchfile could then
be exported as it holds no crypto source code. (Somehow this seems *too*
simple. Would this perhaps get up the US gubmint's nose? Have I missed some
nuance or implicit limitation?)


>Adam
>-- 
>Have *you* exported RSA today? --> http://www.dcs.ex.ac.uk/~aba/rsa/
>
>print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
>)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`
>
>