Jaguar Developers Documentation <-- thinking about converting it

[disjaukifa]

Hey Guys,

 

I just download the information for the Jaguar Developers Guide, and I am one of those people like to have stuff printed. I can't tell you how nice it is to have Official Documentation, however I was thinking about re-typing into a standard text file so that you could print it easier.

 

This is one I was going to do Jaguar Dev Docs

 

If I am going to be the only that is going to use this, then I'm not going to bother, however if ya'll would like a copy please let me know, it will take a while. I am going to do it in sections and release it in sections as it is with the downloaded developer Documents.

 

Let me know

 

Thanks

Disjaukifa

 

PS this also forces me to get my butt to read the whole thing

[Mord]

Hey Guys,

 

I just download the information for the Jaguar Developers Guide, and I am one of those people like to have stuff printed. I can't tell you how nice it is to have Official Documentation, however I was thinking about re-typing into a standard text file so that you could print it easier.

 

This is one I was going to do Jaguar Dev Docs

 

If I am going to be the only that is going to use this, then I'm not going to bother, however if ya'll would like a copy please let me know, it will take a while. I am going to do it in sections and release it in sections as it is with the downloaded developer Documents.

 

Let me know

 

Thanks

Disjaukifa

 

PS this also forces me to get my butt to read the whole thing

 

I'd likely make use of it if/when I get around to jaguar stuff. Even if a nice officialish printed copy is nice to have, at times having a standard text file format is pretty convenient for doing quick searches to find specific info you want to double check while at the computer. No reaching for a manual that way.

 

For my 2600 coding, I have a nice printed version with diagrams etc, as well as text-only files for just this purpose. The printed version goes to work with me when I want to spend a little time on my break reading/reviewing material, but most of the time while doing actual work on the computer I'll just load up the txt file and skim for what I want.

 

So there is a benefit to having it done up beyond forcing you to read it.

[+sgrddy]

Wow. That seems like a monumental task. I am actually fine with the current format of the docs myself.

[JagChris]

Hey Guys,

 

I just download the information for the Jaguar Developers Guide, and I am one of those people like to have stuff printed. I can't tell you how nice it is to have Official Documentation, however I was thinking about re-typing into a standard text file so that you could print it easier.

 

This is one I was going to do Jaguar Dev Docs

 

If I am going to be the only that is going to use this, then I'm not going to bother, however if ya'll would like a copy please let me know, it will take a while. I am going to do it in sections and release it in sections as it is with the downloaded developer Documents.

 

Let me know

 

Thanks

Disjaukifa

 

PS this also forces me to get my butt to read the whole thing

 

I'll take a copy of that. I hate reading books and docs off the internet. I like a hard copy. I printed out the entire v8 manual in book form and put it in a binder. It looks nice. The only way to go.

[+selgus]

I still have my original Jaguar printed documentation, with my developer number watermarked over every page. Having electronic searchable docs come in handy when doing development.

--Selgus

[Tyrant]

I still have my original Jaguar printed documentation, with my developer number watermarked over every page. Having electronic searchable docs come in handy when doing development.

--Selgus

You do?! What are the dates on the bottom? If you have newer versions of anything from the scanned pdf's I think I can speak for everyone when I say we would all be in your debt if you could scan and release them.

[Zerosquare]

I agree with Selgus, but the amount of work needed (typing and proofreading - which is very important for a technical document) would be positively huge. I'd have suggested using OCR software, but I doubt it would work considering the quality of the scans. And TechRef v8, which covers a lot of useful things, is already text-searchable.

 

I'd advise saving your time and motivation for something more useful

Edited October 4, 2009 by Zerosquare

[Tyrant]

If I am going to be the only that is going to use this, then I'm not going to bother, however if ya'll would like a copy please let me know, it will take a while. I am going to do it in sections and release it in sections as it is with the downloaded developer Documents.

 

Well, I just printed out the key bits of the scanned pdf's (softref, appendices, etc) and keep them in a binder, I actually find them easier to refer to on paper than as a pdf, but I suppose a machine readable version would be of benefit for many people. It would also form a nice base for an updated set of documentation, including the things the community has discovered post-Atari, so I say go for it.

 

What format were you thinking of? You would want it to be fairly accessible, but also be able to manage large documents and support nice formatting (and diagrams)... micros~1 word would be one choice, but LaTeX would be my suggestion for a document that size.

[disjaukifa]

I still have my original Jaguar printed documentation, with my developer number watermarked over every page. Having electronic searchable docs come in handy when doing development.

--Selgus

You do?! What are the dates on the bottom? If you have newer versions of anything from the scanned pdf's I think I can speak for everyone when I say we would all be in your debt if you could scan and release them.

 

Yeah I think we would all be happy to do so, heck I could even scan them and do all the work for you and put them in a nice pdf. I just wanted to make a nice set of Developer Documents that would look better printed. Heck, I'm thinking about just cleaning up the current documents, and making them look better.

 

-Disjaukifa

[Atari_Owl]

Hey Guys,

 

I just download the information for the Jaguar Developers Guide, and I am one of those people like to have stuff printed. I can't tell you how nice it is to have Official Documentation, however I was thinking about re-typing into a standard text file so that you could print it easier.

 

This is one I was going to do Jaguar Dev Docs

 

If I am going to be the only that is going to use this, then I'm not going to bother, however if ya'll would like a copy please let me know, it will take a while. I am going to do it in sections and release it in sections as it is with the downloaded developer Documents.

 

Let me know

 

Thanks

Disjaukifa

 

PS this also forces me to get my butt to read the whole thing

 

A BIg job - but would certainly be useful for many i think

[+selgus]

I still have my original Jaguar printed documentation, with my developer number watermarked over every page. Having electronic searchable docs come in handy when doing development.

--Selgus

You do?! What are the dates on the bottom? If you have newer versions of anything from the scanned pdf's I think I can speak for everyone when I say we would all be in your debt if you could scan and release them.

Mine say July 11, 1994 on most of the pages.

--Selgus

[+GroovyBee]

Mine say July 11, 1994 on most of the pages.

The stuff publicly available is from mid 1995 or so.

[Tyrant]

Mine say July 11, 1994 on most of the pages.

The stuff publicly available is from mid 1995 or so.

I've clearly got too much time on my hands, as I just went through and checked all the docs for their dates:

 

00 index		11 nov 1994 	copyright 1994 atari corp
01 getting started 	5 june 1995 	copyright 1995 atari corp
02 tech overview 	10 april 1995 	copyright 1995 atari corp
03 soft ref		7 june 1995 	copyright 1992-95 atari corp 	"version 2.4"
04 tech ref 		26 april 1995 	copyright 1995 atari corp
05 hardware bugs 	26 april 1995 	copyright 1994 atari corp
06 cd-rom 		16 may 1995 	copyright 1995 atari corp
07 modem 		26 april 1995 	copyright 1995 atari corp
08 workshop series 	8 nov 1994 	copyright 1994 atari corp
09 samples 		16 may 1995 	copyright 1005 atari corp
10 libraries 		26 april 1995 	copyright 1995 atari corp
11 qsound 		25 april 1995 	copyright 1995 qsound labs
12 cinepak 		16 june 1995 	copyright 1995 radius inc and atari corp
13 tools 		5 june 1995 	copyright 1995 atari corp
14 apendices 		26 april 1995 	copyright 1994 atari corp
15 madmac 		8 nov 1994 	copyright 1994 atari corp
16 linker 		5 june 1995 	copyright 1995 atari corp
17 debugger 		93/11/15	no copyright notice

[+Stephen Moss]

I suppose a machine readable version would be of benefit for many people. It would also form a nice base for an updated set of documentation, including the things the community has discovered post-Atari, so I say go for it.

 

I have been thinking about doing that for a couple of years and compiling it as a more readable PDF (like Techref V8) if I can scan prints of the documentation to obtain the text, having to retype it all would be a serious drag and very time consuming unless you can touch type and have a two monitor set up so you have the existing DOCs displayed on one screen and your re-write on the other.

Edited October 5, 2009 by Stephen Moss

[Gorf]

V8 works well. It does the trick. You wont miss much of anything in the other version other than stuff not implemented in the

Jaguar anyway There are a few pieces of docs like the 6D controllers and analog controls, but you could always add that on.

Though I baught several 6D Space Ball type controls for very cheap, they are hardly commonplace and not all Jags have analog.

Use the ZeroSquare add on if you MUST have analog...its a job well done by ZS. I still say encoders work just as well but at

leat ZS has a good means of using analogs. Genlock on Jag? For what?