QTR-Quadtone RIP

Looking over many inquiries written by posters, I'm inclined to think that I'm not the only one 
who feels that the QTR Manual is poorly written. For those of us who aren't and don't claim to 
be tech-centric, would be helped a bunch if someone, who understands the p's and q's of 
this "system", would kindly take the time to create a glossary of terms that would explain 
what it means when dragging and dropping files (.txt) and error messages pop up as such:
"Printer not defined" or "The Lab values are not in order. Cannot be linearized." If not, why 
not? And what does the user do to define the printer and put the Lab values in order? 
These are just a couple of examples in what I think are several gaps in information that 
would help many to make sense of the how's and why's of QTR.

Hi,
While I'm sure it would be useful to nearly everyone beyond the
experts in the field, it is worth considering how those experts got to
be that way. They did not have such a glossary either.

It was mentioned in Joost's recent post that RIPs generally cost a
good deal more than QTR does. He did not offer a comparison price but
it should be mentioned that in many cases it runs from hundreds US$ to
thousands. What you are asking is for someone to make it all "plug and
play" for you. That sort of software has a history of coming with a
perpetual price that continues on and on, as witness a popular
operating system we all know of. I can't speak for Roy but I suspect
that he needs, like most of us, to make a living, and it is Not from
QTR that he does that. He simply made it available to us and continues
to update and improve it. All for a one time measly little price that
he likely doesn't even see from many who actually use his software.

The extra documentation that does exist has for the most part been
donated by users of QTR. Spend some time becoming an expert yourself
and help add to those efforts if you feel it to be so crucial.
Understanding will never come without some effort :-)

Consider also that this group has been set up to help in the very
areas you are requesting. Ask your questions and they will usually be
answered by someone. Just be patient and understand that no one is
getting rich from this. The truth is that you are getting a real deal.
The catch is that you have to earn it.

Regards
Duane


--- In QuadtoneRIP@yahoogroups.com, "cmndcntrl" <cmndcntrl@...> wrote:
>
> Looking over many inquiries written by posters, I'm inclined to
think that I'm not the only one 
> who feels that the QTR Manual is poorly written. For those of us who
aren't and don't claim to 
> be tech-centric, would be helped a bunch if someone, who understands
the p's and q's of 
> this "system", would kindly take the time to create a glossary of
terms that would explain 
> what it means when dragging and dropping files (.txt) and error
messages pop up as such:
> "Printer not defined" or "The Lab values are not in order. Cannot be
linearized." If not, why 
> not? And what does the user do to define the printer and put the Lab
values in order? 
> These are just a couple of examples in what I think are several gaps
in information that 
> would help many to make sense of the how's and why's of QTR.
>

I am going to have to strongly disagree with the last post--and I 
have written a couple of computer books, including the first book on 
how to do research on the Internet back in 95. I have also written  
internal tip sheets at the company where I work.

For someone who has worked with computers since 81, unfortunately, I 
found some parts of the documentation cnfusing. For me, as new user, 
there was too much concentration on creating new curves and not 
enough on helping the newbie get the system up and running.

And the search function here on Yahoo Groups is not that good, if you 
are searching for specific hints.

I also understand that this a part time effort.

The solution is  to turn the documentation into open source...I have 
seen open source manuals that work well for other sofeware.

Those people with experience with the software rather than dismissing 
new users could take the time to write a few paragraphs on a section 
where they have a lot of experience or  have special hints and upload 
them to the file folders.  Then after a check by other users, the 
information can bue used to update the documentation.

Robin

--- In QuadtoneRIP@yahoogroups.com, "dlruckus" <dlruckus@...> wrote:
>
> Hi,
> While I'm sure it would be useful to nearly everyone beyond the
> experts in the field, it is worth considering how those experts got 
to
> be that way. They did not have such a glossary either.
> 
> It was mentioned in Joost's recent post that RIPs generally cost a
> good deal more than QTR does. He did not offer a comparison price 
but
> it should be mentioned that in many cases it runs from hundreds US$ 
to
> thousands. What you are asking is for someone to make it all "plug 
and
> play" for you. That sort of software has a history of coming with a
> perpetual price that continues on and on, as witness a popular
> operating system we all know of. I can't speak for Roy but I suspect
> that he needs, like most of us, to make a living, and it is Not from
> QTR that he does that. He simply made it available to us and 
continues
> to update and improve it. All for a one time measly little price 
that
> he likely doesn't even see from many who actually use his software.
> 
> The extra documentation that does exist has for the most part been
> donated by users of QTR. Spend some time becoming an expert yourself
> and help add to those efforts if you feel it to be so crucial.
> Understanding will never come without some effort :-)
> 
> Consider also that this group has been set up to help in the very
> areas you are requesting. Ask your questions and they will usually 
be
> answered by someone. Just be patient and understand that no one is
> getting rich from this. The truth is that you are getting a real 
deal.

> The catch is that you have to earn it.
> 
> Regards
> Duane
>

Duane,

I couldn't agree more. 

Having said that, I understand the need for an update of the user 
manual, especially on the workflow part. And hereby I offer my help 
to do so. I clearly don't feel competent enough to do that alone, so 
I'd rather share the burden with one or two others.

Any volunteers?

Joost


--- In QuadtoneRIP@yahoogroups.com, "dlruckus" <dlruckus@...> wrote:
>
> Hi,
> While I'm sure it would be useful to nearly everyone beyond the
> experts in the field, it is worth considering how those experts got 
to
> be that way. They did not have such a glossary either.
> 
> It was mentioned in Joost's recent post that RIPs generally cost a
> good deal more than QTR does. He did not offer a comparison price 
but
> it should be mentioned that in many cases it runs from hundreds US$ 
to
> thousands. What you are asking is for someone to make it all "plug 
and
> play" for you. That sort of software has a history of coming with a
> perpetual price that continues on and on, as witness a popular
> operating system we all know of. I can't speak for Roy but I suspect
> that he needs, like most of us, to make a living, and it is Not from
> QTR that he does that. He simply made it available to us and 
continues
> to update and improve it. All for a one time measly little price 
that
> he likely doesn't even see from many who actually use his software.
> 
> The extra documentation that does exist has for the most part been
> donated by users of QTR. Spend some time becoming an expert yourself
> and help add to those efforts if you feel it to be so crucial.
> Understanding will never come without some effort :-)
> 
> Consider also that this group has been set up to help in the very
> areas you are requesting. Ask your questions and they will usually 
be
> answered by someone. Just be patient and understand that no one is
> getting rich from this. The truth is that you are getting a real 
deal.
> The catch is that you have to earn it.
> 
> Regards
> Duane
> 
> 
> --- In QuadtoneRIP@yahoogroups.com, "cmndcntrl" <cmndcntrl@> wrote:
> >
> > Looking over many inquiries written by posters, I'm inclined to
> think that I'm not the only one 
> > who feels that the QTR Manual is poorly written. For those of us 
who
> aren't and don't claim to 
> > be tech-centric, would be helped a bunch if someone, who 
understands
> the p's and q's of 
> > this "system", would kindly take the time to create a glossary of
> terms that would explain 
> > what it means when dragging and dropping files (.txt) and error
> messages pop up as such:
> > "Printer not defined" or "The Lab values are not in order. Cannot 
be
> linearized." If not, why 
> > not? And what does the user do to define the printer and put the 
Lab
> values in order? 
> > These are just a couple of examples in what I think are several 
gaps

> in information that 
> > would help many to make sense of the how's and why's of QTR.
> >
>

My interest is in archival black and white; 30 years ago I was spending 
hours in the darkroom using high-end fiber-based paper and selenium 
toned my prints. I am looking for a digital equivalent.

I haven't yet used QTR or any other RIP: I have been lurking for a while 
trying to decide whether I want to get a supported Epson printer (I 
currently have an HP), Piezography inks and a RIP. The RIP that Jon Cone 
apparently recommends for professional use with his Piezography inks is 
Studioprint. If I remember correctly, Studioprint costs US$1300. QTR 
costs US$50. Typically a US$50 shareware program is a small and focussed 
utility that fills a small gap in the market. Even from my reading of 
the list over the last few months it is obvious that QTR does very 
complicated things and the program has to adapt to new inks and new 
printers. This is way beyond what programmers of typical US$50 programs 
have to keep up with. So, expecting a US$500 or more level of support is 
unreasonable in my view. I also have seldom, if ever, come across a 
US$500+ program where the users can actually communicate with the 
programmers, and I seem to remember that QTRGui, which as a Windows user 
I would need, is a freebie. If I were pricing QTRGui, it alone would be 
US$50 or more and QTR would be about US$150-US$300, about 1/3 or 1/4 of 
the commercial-channel price, which is a common ratio for shareware 
versus commercial-channel.


dlruckus wrote:

>
> Hi,
> While I'm sure it would be useful to nearly everyone beyond the
> experts in the field, it is worth considering how those experts got to
> be that way. They did not have such a glossary either.
>
> It was mentioned in Joost's recent post that RIPs generally cost a
> good deal more than QTR does. He did not offer a comparison price but
> it should be mentioned that in many cases it runs from hundreds US$ to
> thousands. What you are asking is for someone to make it all "plug and
> play" for you. That sort of software has a history of coming with a
> perpetual price that continues on and on, as witness a popular
> operating system we all know of. I can't speak for Roy but I suspect
> that he needs, like most of us, to make a living, and it is Not from
> QTR that he does that. He simply made it available to us and continues
> to update and improve it. All for a one time measly little price that
> he likely doesn't even see from many who actually use his software.
>
> The extra documentation that does exist has for the most part been
> donated by users of QTR. Spend some time becoming an expert yourself
> and help add to those efforts if you feel it to be so crucial.
> Understanding will never come without some effort :-)
>
> Consider also that this group has been set up to help in the very
> areas you are requesting. Ask your questions and they will usually be
> answered by someone. Just be patient and understand that no one is
> getting rich from this. The truth is that you are getting a real deal.
> The catch is that you have to earn it.
>
> Regards
> Duane
>
> --- In QuadtoneRIP@yahoogroups.com 
> <mailto:QuadtoneRIP%40yahoogroups.com>, "cmndcntrl" <cmndcntrl@...> wrote:
> >
> > Looking over many inquiries written by posters, I'm inclined to
> think that I'm not the only one
> > who feels that the QTR Manual is poorly written. For those of us who
> aren't and don't claim to
> > be tech-centric, would be helped a bunch if someone, who understands
> the p's and q's of
> > this "system", would kindly take the time to create a glossary of
> terms that would explain
> > what it means when dragging and dropping files (.txt) and error
> messages pop up as such:
> > "Printer not defined" or "The Lab values are not in order. Cannot be
> linearized." If not, why
> > not? And what does the user do to define the printer and put the Lab
> values in order?
> > These are just a couple of examples in what I think are several gaps
> in information that
> > would help many to make sense of the how's and why's of QTR.
> >
>
>

[rest of original comments edited to shorten thread. btw, if my comment comes across as 
unkind or rude please pardon. it's not intended to come across this way. besides, text 
communication is one lowest form of communication.]

i agree with robin. although it's true that other experienced QTR users did begin without 
much resources, but in all fairness all the frequently-asked-questions could've been 
spared from this forum had we have a cohesive manual and a glossary. much of the 
information is availabe in the manuals, but they're not presented cohesively. the user often 
have to connect the dots to make some sense of what the programmer is describing in the 
manual. 

i've written small manuals for a small company, and it's not an easy task. it's a challenge to 
take several sentences to describe a procedure and condense it down to a few steps 
without loosing the user. it's very easy to assume that the user understands your 
description and instructions because you already have in your mind how the product 
works. this is always easily overlooked when creating a manual for a product. if you've 
done technical writing for a product, i think you can sympathize with Roy and other 
programmers. it's not just step one, step two, and then step three. it's just as time 
consuming to design a program as it is to write a good manual. it's like an art, and so is 
writing a good program like QTR. with this said, i think a cohesive manual can become a 
reality when it's given fresh eyes from a user's perspective. i think this is what it needs.

i'm a new user to QTR and i've toyed with the idea of writing a manual but backed-out. 
there are many other details about QTR that i don't understand yet. for me to try to write a 
manual may be counter productive because i may inadvertently misuse terminologies or 
describe procedures that contradicts Roy's original procedures. little details but important. 
so if anyone wants to improve on the manual, we'll have to put our heads together and 
agree on the terminologies and procedures. this way we can avoid any confusion which 
could trigger another mass of frequently-asked-questions populating this forum.

i hope my comment made sense.

regards,
daniel

--- In QuadtoneRIP@yahoogroups.com, "Rob" <robin@...> wrote:

>
> 
> I am going to have to strongly disagree with the last post--and I 
> have written a couple of computer books, including the first book on 
> how to do research on the Internet back in 95. I have also written  
> internal tip sheets at the company where I work.
> 
> Those people with experience with the software rather than dismissing 
> new users could take the time to write a few paragraphs on a section 
> where they have a lot of experience or  have special hints and upload 
> them to the file folders.  Then after a check by other users, the 
> information can bue used to update the documentation.
> 
> --- In QuadtoneRIP@yahoogroups.com, "dlruckus" <dlruckus@> wrote:
> >
> > Hi,
> > While I'm sure it would be useful to nearly everyone beyond the
> > experts in the field, it is worth considering how those experts got 
> to
> > be that way. They did not have such a glossary either.

But, the documentation is essentially open source. It was not written by Roy,
but by a QTR user. It is published as a PDF for convenience, but I am sure Tom
Moore would be more than happy to provide the original MS Word document to any
and all who would wish to improve it.

I will certainly make the same offer for the QTRgui help. It is in HTML. Who is
volunteering? 

By the way, I have been in computers since 1962 (and photography since the
1950's). I don't understand how the time in service has anything to do with
ability to write or communicate. 


-Stephen
 www.sbillard.org/Stephen

-----Original Message-----
From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On Behalf
Of Rob
Sent: Friday, March 09, 2007 5:41 AM
To: QuadtoneRIP@yahoogroups.com
Subject: [QuadtoneRIP] Re: A Glossary Would Be Helpful


I am going to have to strongly disagree with the last post--and I have written a
couple of computer books, including the first book on how to do research on the
Internet back in 95. I have also written internal tip sheets at the company
where I work.

For someone who has worked with computers since 81, unfortunately, I found some
parts of the documentation cnfusing. For me, as new user, there was too much
concentration on creating new curves and not enough on helping the newbie get
the system up and running.

And the search function here on Yahoo Groups is not that good, if you are
searching for specific hints.

I also understand that this a part time effort.

The solution is  to turn the documentation into open source...I have seen open
source manuals that work well for other sofeware.

Those people with experience with the software rather than dismissing new users
could take the time to write a few paragraphs on a section where they have a lot
of experience or  have special hints and upload them to the file folders.  Then
after a check by other users, the information can bue used to update the
documentation.

Robin

One of the best approaches to writing a manual is to organize all the questions
you would like answered into a coherent flow. I am sure if you did so, others on
this group would help fill out the detail. Your experience in writing manuals
should be of great help in this endeavor, just put in place marks for the things
you don't know.


-Stephen
 www.sbillard.org/Stephen

-----Original Message-----
From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On Behalf
Of Daniel
Sent: Friday, March 09, 2007 10:45 AM
To: QuadtoneRIP@yahoogroups.com
Subject: [QuadtoneRIP] Re: A Glossary Would Be Helpful

[rest of original comments edited to shorten thread. btw, if my comment comes
across as unkind or rude please pardon. it's not intended to come across this
way. besides, text communication is one lowest form of communication.]

i agree with robin. although it's true that other experienced QTR users did
begin without much resources, but in all fairness all the
frequently-asked-questions could've been spared from this forum had we have a
cohesive manual and a glossary. much of the information is availabe in the
manuals, but they're not presented cohesively. the user often have to connect
the dots to make some sense of what the programmer is describing in the manual. 

i've written small manuals for a small company, and it's not an easy task. it's
a challenge to take several sentences to describe a procedure and condense it
down to a few steps without loosing the user. it's very easy to assume that the
user understands your description and instructions because you already have in
your mind how the product works. this is always easily overlooked when creating
a manual for a product. if you've done technical writing for a product, i think
you can sympathize with Roy and other programmers. it's not just step one, step
two, and then step three. it's just as time consuming to design a program as it
is to write a good manual. it's like an art, and so is writing a good program
like QTR. with this said, i think a cohesive manual can become a reality when
it's given fresh eyes from a user's perspective. i think this is what it needs.

i'm a new user to QTR and i've toyed with the idea of writing a manual but
backed-out. 
there are many other details about QTR that i don't understand yet. for me to
try to write a manual may be counter productive because i may inadvertently
misuse terminologies or describe procedures that contradicts Roy's original
procedures. little details but important. 
so if anyone wants to improve on the manual, we'll have to put our heads
together and agree on the terminologies and procedures. this way we can avoid
any confusion which could trigger another mass of frequently-asked-questions
populating this forum.

i hope my comment made sense.

regards,
daniel

Judging from the forum posts here and my own experiences sofar with 
QTR, there is a lot of confusion about what QTR does and how to use 
it, so any improvements in the Help guide or user manual would be 
very helpful. However just not anybody will have the knowledge to 
make those improvements. I myself have significant experience in 
writing and editing highly technical manuals, but would be the 
absolutely wrong person to get involved here because of my lack of 
knowledge about QTR. Let's not get all excited and do the wrong thing!

Frans Waterlander

--- In QuadtoneRIP@yahoogroups.com, "Stephen Billard" <stephen@...> 
wrote:
>
> But, the documentation is essentially open source. It was not 
written by Roy,
> but by a QTR user. It is published as a PDF for convenience, but I 
am sure Tom
> Moore would be more than happy to provide the original MS Word 
document to any
> and all who would wish to improve it.
> 
> I will certainly make the same offer for the QTRgui help. It is in 
HTML. Who is
> volunteering? 
> 
> By the way, I have been in computers since 1962 (and photography 
since the
> 1950's). I don't understand how the time in service has anything to 
do with
> ability to write or communicate. 
> 
> 
> -Stephen
>  www.sbillard.org/Stephen
> 
> -----Original Message-----
> From: QuadtoneRIP@yahoogroups.com 
[mailto:QuadtoneRIP@yahoogroups.com] On Behalf
> Of Rob
> Sent: Friday, March 09, 2007 5:41 AM
> To: QuadtoneRIP@yahoogroups.com
> Subject: [QuadtoneRIP] Re: A Glossary Would Be Helpful
> 
> 
> I am going to have to strongly disagree with the last post--and I 
have written a
> couple of computer books, including the first book on how to do 
research on the
> Internet back in 95. I have also written internal tip sheets at the 
company
> where I work.
> 
> For someone who has worked with computers since 81, unfortunately, 
I found some
> parts of the documentation cnfusing. For me, as new user, there was 
too much
> concentration on creating new curves and not enough on helping the 
newbie get
> the system up and running.
> 
> And the search function here on Yahoo Groups is not that good, if 
you are
> searching for specific hints.
> 
> I also understand that this a part time effort.
> 
> The solution is  to turn the documentation into open source...I 
have seen open
> source manuals that work well for other sofeware.
> 
> Those people with experience with the software rather than 
dismissing new users
> could take the time to write a few paragraphs on a section where 
they have a lot
> of experience or  have special hints and upload them to the file 
folders.  Then
> after a check by other users, the information can bue used to 
update the

> documentation.
> 
> Robin
>

I have uploaded the QTRgui help files for any and all who wish to help improve
them. Look in the Docs section of the forum files. 


-Stephen
 www.sbillard.org/Stephen

-----Original Message-----
From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On Behalf
Of Stephen Billard
Sent: Friday, March 09, 2007 11:12 AM
To: QuadtoneRIP@yahoogroups.com
Subject: RE: [QuadtoneRIP] Re: A Glossary Would Be Helpful

One of the best approaches to writing a manual is to organize all the questions
you would like answered into a coherent flow. I am sure if you did so, others on
this group would help fill out the detail. Your experience in writing manuals
should be of great help in this endeavor, just put in place marks for the things
you don't know.


-Stephen
 www.sbillard.org/Stephen

-----Original Message-----
From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On Behalf
Of Daniel
Sent: Friday, March 09, 2007 10:45 AM
To: QuadtoneRIP@yahoogroups.com
Subject: [QuadtoneRIP] Re: A Glossary Would Be Helpful

[rest of original comments edited to shorten thread. btw, if my comment comes
across as unkind or rude please pardon. it's not intended to come across this
way. besides, text communication is one lowest form of communication.]

i agree with robin. although it's true that other experienced QTR users did
begin without much resources, but in all fairness all the
frequently-asked-questions could've been spared from this forum had we have a
cohesive manual and a glossary. much of the information is availabe in the
manuals, but they're not presented cohesively. the user often have to connect
the dots to make some sense of what the programmer is describing in the manual. 

i've written small manuals for a small company, and it's not an easy task. it's
a challenge to take several sentences to describe a procedure and condense it
down to a few steps without loosing the user. it's very easy to assume that the
user understands your description and instructions because you already have in
your mind how the product works. this is always easily overlooked when creating
a manual for a product. if you've done technical writing for a product, i think
you can sympathize with Roy and other programmers. it's not just step one, step
two, and then step three. it's just as time consuming to design a program as it
is to write a good manual. it's like an art, and so is writing a good program
like QTR. with this said, i think a cohesive manual can become a reality when
it's given fresh eyes from a user's perspective. i think this is what it needs.

i'm a new user to QTR and i've toyed with the idea of writing a manual but
backed-out. 
there are many other details about QTR that i don't understand yet. for me to
try to write a manual may be counter productive because i may inadvertently
misuse terminologies or describe procedures that contradicts Roy's original
procedures. little details but important. 
so if anyone wants to improve on the manual, we'll have to put our heads
together and agree on the terminologies and procedures. this way we can avoid
any confusion which could trigger another mass of frequently-asked-questions
populating this forum.

i hope my comment made sense.

regards,
daniel

by the way, just a reminder for eveyone else who might not know, there are two versions 
of QTR -- one for mac os x and the other for windows (QTRgui) -- so there will be some 
differences in procedures in reaching the same goal. here is probably one of the 
confusions when users (i.e. myself) posts questions and forgetting to make it clear that 
the question is for QTR for mac os x, and then become confused with the answer because 
the answer is, for example, refering to QTRgui instead of QTR.

--- In QuadtoneRIP@yahoogroups.com, "Stephen Billard" <stephen@...> wrote:
>
> I have uploaded the QTRgui help files for any and all who wish to help improve
> them. Look in the Docs section of the forum files. 
> 
> 
> -----Original Message-----
> From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On 
Behalf

> Of Stephen Billard
> Sent: Friday, March 09, 2007 11:12 AM
> To: QuadtoneRIP@yahoogroups.com
> Subject: RE: [QuadtoneRIP] Re: A Glossary Would Be Helpful
> 
> One of the best approaches to writing a manual is to organize all the questions
> you would like answered into a coherent flow. I am sure if you did so, others on
> this group would help fill out the detail. Your experience in writing manuals
> should be of great help in this endeavor, just put in place marks for the things
> you don't know.

Hi Stephen

The QTR User Guide certainly needs some work. For the next month or so
I will be too busy curling to get to it. Later in April I plan to work
on a revision.

I'm not convinced that just posting the MS Word document would be a
useful thing to do. However, if there are people who are interested in
contributing to the document, that would be great once I revise the
table of contents and determine the objectives of each section.
However, I think that someone (or a small group) has to maintain
editorial control of the document. It seems to me that just throwing
the document out into the "wild" would make that too difficult.

One of the (many) glaring deficiencies of the User Guide, is that it
is oriented toward the PC user environment. Since I'm not a Mac user,
I have no plans to address this this need. If someone wants to create
a Mac version, I would be quite willing to provide the source of my
document as a starting point (or better yet, to exchange material). If
someone wishes to incorporate Mac relevant content for the existing 
User Guide, I would be willing to incorporate it and to cooperate in
developing a joint table of contents.

With respect to a glossary, I would certainly be willing to
incorporate an expanded one into the revised document. If someone
wanted to act as a coordinator for construction of a glossary, that
would be useful and could start now. It's construction might also
serve as an example for how we could improve the User Guide cooperatively.

Another item than might be useful (but hasn't been mentioned, I think)
is a FAQ List. Again, volunteers to prepare one of these (even just
the questions to start) would be useful. A good one would be a great
resource for new users and would augment Yahoo's limited search
facilities. However, FAQ Lists take significant work to prepare and
keep current.

As a final thought, one of the current interesting means of
cooperative development of information is the Wiki (as in Wikipedia).
However, I have no interest in setting up a Wiki and I have know idea
what resources (knowledge, software etc.) one needs to maintain one.
However, you, Roy (or someone else)were willing to set up and host a
QuadtoneRIP Wiki, that might be a good means for cooperatively
developing a document.

Tom Moore

--- In QuadtoneRIP@...m, "Stephen Billard" <stephen@...> wrote:
>
> But, the documentation is essentially open source. It was not
written by Roy,
> but by a QTR user. It is published as a PDF for convenience, but I
am sure Tom
> Moore would be more than happy to provide the original MS Word
document to any
> and all who would wish to improve it.
> 
> I will certainly make the same offer for the QTRgui help. It is in
HTML. Who is
> volunteering? 
> 
> By the way, I have been in computers since 1962 (and photography
since the
> 1950's). I don't understand how the time in service has anything to
do with
> ability to write or communicate. 
> 
> 
> -Stephen
>  www.sbillard.org/Stephen

...