Hi,
I am wondering if QL version of an Epub text reader is possible.
Epub uses Zip hold all the files with the config files.
A HTML Reader is required, maybe using Prowess HTML Reader or Lynx...
Or maybe write fro scratch in SBASIC which should be fast enough.
Regards,
Derek
On 13/05/15 09:49, Derek Stewart wrote:
Hi,
I have just tried unzipping the epub file to a directory, all the HTML
linked pages seem to link crrectly in a web browser (Firefox)
So when all the correction have been made a WIKI version could be produced.
I have converted all the TRAP and Vector Tables to HTML tables, which
size is depentan on the scree. Assuming viewing the manual on a mobile
phone with small screen area may still format correctly, though I have
to test this, I ideally wanted on a Kindle.
Regards,
Derek
On 13/05/15 09:12, Derek Stewart wrote:
Hi Wolfgang,
I am really only putting the manual into epub/mobi format so that I can
have it on a ereader for reference when trying to problem in assembley
language.
I have already produced a ODT version in Libre Office, but does not have
the corrections, format changes to the Trap listing into tables and
interlinking of the sections.
It possible to make the corrections to the manual and convert it to HTML
and put online as a WIKI file for users to update and correct.
Would this contravene any copyright?
Regards,
Derek
On 13/05/15 07:00, Wolf wrote:
Hi,
I'm pretty sure that Marcel is right here (as usual).
IOB.TEST makes no sense, this just checks whether there is still some
input, not whether i/o/ operations are complete, so this must be
IOF.CHEK.
However, I had a (very quick, sorry) look at the sources and you can
find the following in iod_iox_vector_asm
;+++
; Directory Device check slave blocks
;
; d6 c p drive / file number
; a0 c p channel block
; a3 c p linkage block
; a4 c s definition block
;
; status return standard
;---
iox_chek
jmp iox_flsh ; just flush
So at least here, test just calls flush....
AFAIK, though, noting actually uses that.
OTOH, not all drivers will implement this trap (I *** believe*** this
might be the case, e.g. for ram disks where this will just go to a moveq
0,d0 and an rts)
since you're redrafting the manual, you might want to add a little rider
in this respect.
Wolfgang
On 05/12/2015 09:52 PM, Marcel Kilgus wrote:
derek wrote:
Hi,
I just looked in the SMSQ/E sources and can not fond IOF.TEST.
Is the statement in Section 5.3 correct?
If not how should read.
As I wrote I'm pretty sure they meant to write IOF.CHEK
Marcel
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
