On 05/11/10 21:22, Marc Paré wrote:
Le 2010-11-05 17:03, Jean Hollis Weber a écrit :
On Fri, 2010-11-05 at 16:52 -0400, Marc Paré wrote:
Le 2010-11-05 16:12, Jean Hollis Weber a écrit :
On Fri, 2010-11-05, Marc Paré wrote:

From the perspective of the "outside world" the public face of the
LibO
documents section, it would seem to make sense that documents be
provided in the first place in our native ODT formats. This should be
trumpeted as our success in document achievement. I think that this is
an expectation that we all share.

Also, if we are going to keep advertising the virtues of the ODF
files.
It would seem to make sense that we find ways to make the ODF files
system "play nice" with the internal document flow. What better
occasion
would we get than having the use of a corporate-like structure such as
the "TDF/LibreOffice document team division" use the ODF files
internally at developing documents from start to end. We have our devs
on-side for the development of an Office Suite championing the use of
ODF, would it not make sense that we would try to make the
creation/editing of internal ODF documents part of the internal
process?
The devs could could help in making this work. We could then, without
any doubt, suggest and prove that using the ODF in creating
documents in
a corporate structure, from start to end production, is entirely and
assuredly possible.

If so, as a group of committed document editing professionals, as you
all are, you could use this occasion to streamline the ODF
documents to
work in such a process.

This would certainly help in marketing our LibO Suite as a viable
office
suite for the corporate/enterprise world.

Just my thoughts.

Marc

Marc, you have expressed my opinion on this subject better than I can.
Thank you.

--Jean




Sorry to the documentation team if this seemed a negative comment on
your production process. I think that most members who have taken the
time to read your posts have come to the same conclusion as I, in that
you are very professional in your approach to documentation as well as
in respecting the production flow.

In some ways I feel apprehensive to thank you because I don't think that
any of you would be anything else than this in any other comparable
tasks. Thank you and my respects.

But in the same breath ... I will still add my opinions when and where I
can. :-)

Marc

Marc, please do! And I, at least, did not take your comments negatively.
I agree with all you said, and you said it well.

--Jean


Thanks.

Marc




Hello,

I must confess that I read the thread fairly quickly so I may have missed some points, but here we go with my observations.

Language
It has to be en-US since, at least for OOo, this is the default language and the one you get in addition to the localized version. Though I would like to see colour, metre, centre written correctly ;-) I think you can live with this choice.

File format
My preference is to use ODF.
No doubt that the wiki version is much more dynamic and better suited for a collaborative environment, but it also has drawbacks (review of entries, printing, tracking of the program version)

Workflow
There is another thread on this so to keep it short, I think we should stay with something similar to OOoAuthors based on
draft --> review --> publish
What is missing in OOoAuthors is a definition of the role of publisher / "editor in chief" that is the person(s) that decide when to pull the trigger and publish. At present Jean takes care of this (and does a great job) but if it wasn't for her dedication I do not know how a document would be deemed ready for publishing.
So some work to do there.

Template
I guess it does not make much sense to depart from the template used by OOoAuthors that over time has been refined and improved. You may want to consider making better use of colours, adding heading numbers, make it more modern-looking but I am not sure that should be a priority unless you want to give the LibO guides their own identity from the start.

Cheers,

Michele

--
E-mail to [email protected] for instructions on how to 
unsubscribe
List archives are available at http://www.libreoffice.org/lists/documentation/
All messages you send to this list will be publicly archived and cannot be 
deleted

Reply via email to