D*** it, I used to know that! Great catch. Rewind all that about CC=1. In *this* case, purely from a technical POV.
On Tue, Oct 10, 2017 at 3:14 PM, Tony Harminc <[email protected]> wrote: > On 10 October 2017 at 14:18, Ed Jaffe <[email protected]> wrote: >> On 10/10/2017 10:47 AM, Tony Harminc wrote: > ... > So it's the table *output* characters that are matched against the > character in R0 - not the input. For TROT that character is a 16-bit > one, and your hex table is only 512 bytes long, is sparse, and is not > going to contain 0000 or any of the other 65279 values you could > choose arbitrarily to avoid ending prematurely with CC=1. > > Tony H. -- sas
