[betabookcourier] Re: little bug in k1000 transfers

  • From: M Kilburn <mkilburn@xxxxxxxxxxx>
  • To: betabookcourier@xxxxxxxxxxxxx
  • Date: Fri, 28 Oct 2005 21:54:15 -0300

Hi Katie: 

When I was able to transfer KES files, I never found they navigated well
in BC. Also, I believe they are larger files than the text format. 

Mike 

-----Original Message-----
From: betabookcourier-bounce@xxxxxxxxxxxxx
[mailto:betabookcourier-bounce@xxxxxxxxxxxxx] On Behalf Of Katie Walker
Sent: October 28, 2005 6:44 PM
To: betabookcourier@xxxxxxxxxxxxx
Subject: [betabookcourier] Re: little bug in k1000 transfers


Hi Mike,

Using an API we gave them, Kurzweil developed the software that
transfers 
files from K1000 to BC. I believe they initially wrote the software to 
transfer KES files because that's their main file format. Then, because 
they could and it was fairly straightforward, they included the ability
to 
transfer text files as well. We don't know exactly how each transfer
works 
since we didn't do the software. Steve is planning to do some detailed 
testing in the next couple of days to get a better idea of what's going
on. 
We'll let you know what we find out.

Katie

At 01:20 PM 10/27/2005, you wrote:
>Hi John - Katie - anyone:
>
>I need to know if there is some particular advantage to transfering KES

>versus text format out of K1000 into BC. Is the navigation better with 
>BC for one over the other? If not, why have the 2 formats to choose 
>from.
>
>Mike
>
>-----Original Message-----
>From: betabookcourier-bounce@xxxxxxxxxxxxx
>[mailto:betabookcourier-bounce@xxxxxxxxxxxxx] On Behalf Of john riehl
>Sent: October 26, 2005 11:13 PM
>To: beta book courier list
>Subject: [betabookcourier] little bug in k1000 transfers
>
>
>I've transferred several K1000 files to the beta bc using .kes format. 
>each time I do, K1000 adds a 22 to the end of the file. For
>example:
>"Eugenic Wars volume 3 22" I can't tell if there'a  a period before the

>22 but it's deffinitely there each time.

Katie Walker
Springer Design, Inc.
katie@xxxxxxxxxxxxxxxxxxx 

Other related posts: