Jeff Prater wrote:
In my opinion, we should only have a single version of documentation for
both web, print, and the built-in help.
I agree with what Andrea says.
In addition, the help file is supposed to explain the product screen-by-screen
and control-by-control.
The reason is the user
-
Jeff Prater
On Fri, Dec 3, 2010 at 11:30 PM, Jean Hollis Weber jeanwe...@gmail.com wrote:
Just to be clear: I don't think ODT is the best medium for providing
docs to users, but I do think it is the best medium to use as the source
documents from which a variety of outputs (PDF, wiki,
Hi Jeff,
Am Sat, 4 Dec 2010 11:49:40 -0500
schrieb Jeff Prater j...@thoughtreactor.com:
-
Jeff Prater
On Fri, Dec 3, 2010 at 11:30 PM, Jean Hollis Weber
jeanwe...@gmail.com wrote:
[...]
I never thought about people with limited bandwidth--I guess I don't
have to worry about
On Sat, 2010-12-04 at 13:59 +1000, Jean Hollis Weber wrote:
On Sat, 2010-12-04 at 08:40 +0530, Narayan Aras wrote:
prediapress is running a successful Print-on-Demand business out of
printing books from wikis.
...
Each book is nothing but an exported pdf from wiki
So
On Fri, 2010-12-03 at 20:53 +0530, Narayan Aras wrote:
Hi all,
I do not know if this is the right forum (and the right time) to put this
idea, but why are we circulating odt/pdf files for proofreading?
I have written a 380-page user manual in odt; and also written several help
docs in
Hello Narayan,
Op 3/12/2010 16:23, Narayan Aras schreef:
Hi all,
I do not know if this is the right forum (and the right time) to put this idea,
but why are we circulating odt/pdf files for proofreading?
I have written a 380-page user manual in odt; and also written several help
docs in
I'm probably the only other person here to say this, but I agree with
Narayan on how initial documentation should be developed. I work for a
rather large county government and all of our documentation is developed and
maintained on our intranet website. All of our documentation is web-based,
and
On Fri, 2010-12-03 at 20:07 -0500, Jeff Prater wrote:
... I agree with
Narayan on how initial documentation should be developed...
I understand the desire to create these ODT files since it's an intuitive
method to showcase the capabilities of LibreOffice, but I believe our time
could be
IMO for the first release of LibO, ideally we would have PDFs and
printed books available, as well as info on the wiki. Started from the
ODTs is the fastest way to do all of that. For future releases, the
method could be quite different.
--Jean
Thanks Jean for bringing out this
I think the best way to start the process would be to copy the completed,
published LibO documents. I wouldn't start from scratch since all of the
work has already been compiled and only minor changes are required to
convert the documents from OOo to LibO. But I wouldn't start the transition
until
On Sat, 2010-12-04 at 09:17 +0530, Narayan Aras wrote:
IMO for the first release of LibO, ideally we would have PDFs and
printed books available, as well as info on the wiki. Started from the
ODTs is the fastest way to do all of that. For future releases, the
method could be quite
Jeff, thanks for that clarification. Some comments interleaved below.
--Jean
On Fri, 2010-12-03 at 23:10 -0500, Jeff Prater wrote:
I think the best way to start the process would be to copy the completed,
published LibO documents. I wouldn't start from scratch since all of the
work has already
12 matches
Mail list logo
