Of your list of components, I'm done with Writer, Calc, and Impress.  Will
continue till I've finished the list.

Re: the question of a glossary, I think I need to make clear why I put
forward suggestions like that out there.  My background was in humanities;
I came to tech well into my working life, with as much anxiety as the
average user.  Then, when I began to teach, I saw my students going through
the same apprehensiveness.

To folks with your background, terms like GNOME and KDE (see p. 123) don't
need to be explained.  But to folks like (some of) my students, and even me
at one point, terms like these can induce cold feet.  I'd be willing to bet
a few $$ on the idea that there are at least a few who don't understand
what an operating system (see p. 124) is.

My "mixed background" makes me all the more impressed with open source of
any kind.  I think cultivating audiences like those I've described is very
effective in promoting open source products.  In such contexts, relying on
styles internal to a document as a way to explain or convey meaning may not
suffice.  I did find one example of using less formal language to make an
important point - this statement on p. 144 (italics mine):

*Paste the text in the desired position. Do not worry if it does not look
right; it will in a minute.*

I'm going to proceed with my proofreading; hope to have Draw, Math, and
Base done in another few days.

On Mon, May 29, 2023 at 2:44 PM Keith N. McKenna <keith.mcke...@comcast.net>
wrote:

> Michele Petrovsky wrote:
> > Keith, as is the case with all of Open Office's  documentation, the
> > discussion of  tracking changes is very well done.  I'm particularly
> > impressed with the clarity with which screen shots are used to
> illustrate a
> > point or a set of steps.
> >
> > I'll continue to plug away at proofreading.  I hope to have a (fairly)
> > complete set of suggestions in each of two categories (glossary, and
> > smoother flow of language) ready in another couple of weeks.
> >
> >
>
> I look forward to seeing those suggestions, but understand that the
> chapter files have been published and that only the compiled book is
> still waiting, and that there are 5 (possibly 6) individual manuals to
> be completed.
>
> The priorities are:
> 1) Writer
> 2) Calc
> 3) Impress
> 4) Draw
> 5) Math
> 6) Base
>
> Because of this, some or all of the information may be entered into
> Bugzilla, our issue tracking database, for future action.As far as a
> glossary is concerned, you may have noted that much of that has been
> done internal to the documents by use of styles. All recommendations
> will however be considered though possibly acted upon in different ways.
>
> Regards
> Keith
>
> > On Fri, May 26, 2023 at 10:24 AM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> Michele Petrovsky wrote:
> >>> Hope this finds everyone well...
> >>>
> >>> Re: *Getting Started*, I'm continuing my proofreading; averaging 50 or
> so
> >>> pages a day.  So far, no obvious spelling / punctuation / other
> >>> proofreading-type errors.  There are a few word choices that could be
> >>> improved, I think.  But other than that nothing needs corrected; it's
> >> very
> >>> nicely done.
> >>>
> >>> I'm going to continue with this practice, put together a set of
> >> suggestions
> >>> for wording, and also possibilities for entries in a glossary.  Will
> keep
> >>> you posted.
> >>>
> >>> *Michele*
> >>>
> >> Michele;
> >>
> >> Thank you so much for your help with this. I look forward to seeing your
> >> list of suggestions.
> >>
> >> For future reference, Writer, the word processing component of
> >> OpenOffice, has a feature to record and show changes that we make use of
> >> in the documentation. It is turned on until the document is ready to be
> >> published. and all changes are marked with a color unique to each
> person.
> >>
> >> If you look closely at the Writer chapter in the Getting Started Guide,
> >> and also in the Writer Guide you should get a better understanding of
> >> the particulars of the program. Also if you have any questions on
> >> OpenOffice or on how we use Git, ask them here and we will be ore than
> >> happy to give you any help that we can.
> >>
> >> Regards
> >> Keith
> >>
> >>>
> >>> On Sun, May 21, 2023 at 2:07 PM Keith N. McKenna <
> >> keith.mcke...@comcast.net>
> >>> wrote:
> >>>
> >>>> F Campos Costero wrote:
> >>>>> I do see problems with the figures when I use the menu Insert -> File
> >> on
> >>>> a
> >>>>> blank document to insert AOO41GS2.odt. Instead of a problem with one
> >>>>> figure, I saw problems with figures 2,4,11,12, and 17. The document
> >>>> showed
> >>>>> a placedholder rather than the actual figure. I could delete the
> >>>>> placeholder and copy and paste the figures from the chapter file in
> >> most
> >>>> of
> >>>>> the cases. For figures 12 and 17, I had to delete the frame intended
> to
> >>>>> hold the figure, delete the placeholder (which was somehow not in the
> >>>>> frame), insert a new frame, and then copy over the figure from the
> >>>> chapter
> >>>>> file.
> >>>>> If you turn on View -> Nonprinting Characters, you can see that
> figures
> >>>> 12
> >>>>> and 17 are unusual. The figure caption is preceded by several empty
> >>>>> paragraphs. I bet I did something wrong when I inserted those figures
> >>>> long
> >>>>> ago.
> >>>>> I inserted AOO41GS3.odt without any problems.
> >>>>>
> >>>>> Regards,
> >>>>> Francis
> >>>>>
> >>>>> On Wed, May 17, 2023 at 11:21 AM F Campos Costero <
> >> fjcc.apa...@gmail.com
> >>>>>
> >>>>> wrote:
> >>>>>
> >>>>
> >>>> Hi Francis;
> >>>>
> >>>> Thank you for looking into this. The files to be used are all at the
> top
> >>>> level. The ones in ForWiki, already have all the front matter in them
> >>>> and are strictly to create the PDFs and chapter files for distribution
> >>>> on the mwiki.
> >>>>
> >>>> The problem was with figure 4 in AOO41GS2, which would be figure 5 in
> >>>> the complete book.
> >>>>
> >>>> If you can correct whatever you find and finish compiling the book it
> >>>> would be greatly appreciated.
> >>>>
> >>>> Regards
> >>>> Keith
> >>>>
> >>>> was
> >>>>>> I'll try to compile the complete book later today. To make sure we
> are
> >>>>>> working with the same files, please confirm that:
> >>>>>> 1. You are using the template file AOOdoc.ott from the Templates
> >> branch
> >>>>>> 2. The odt chapter files are in the Getting-Sarted-Guide branch in
> the
> >>>>>> ForWiki folder
> >>>>>> 3. The Aoo41GSFrontMatter.odt file is the one at the top level of
> the
> >>>>>> Getting-sarted-Guide branch.
> >>>>>>
> >>>>>> Which figure in chapter 1 is causing problems?
> >>>>>>
> >>>>>> Regards,
> >>>>>> Francis
> >>>>>>
> >>>>>> On Wed, May 17, 2023 at 9:47 AM Keith N. McKenna <
> >>>>>> keith.mcke...@comcast.net> wrote:
> >>>>>>
> >>>>>>> I am having difficulty compiling the Complete book for the Getting
> >>>>>>> Started Guide. All the chapters  except Chapter 1 (AOO41GS2)
> Compile
> >>>>>>> perfectly. There is one figure in chapter 1 that does not come
> >> through
> >>>>>>> properly. It is there in the Chapter file, but not the the complete
> >>>>>>> book. If one of you could try to compile it and see if there is
> >> still a
> >>>>>>> problem it would be greatly appreciated.
> >>>>>>>
> >>>>>>> The way I have been doing it is to create a blank writer file from
> >> the
> >>>>>>> AOO Template and then insert the chapters along with any manual
> >> breaks
> >>>>>>> as needed, then at the top insert Aoo41GSFrontMatter.odt which
> >> contains
> >>>>>>> the Tittle Page, Copyright Page and a blank TOC.
> >>>>>>>
> >>>>>>> Thank a lot for the help
> >>>>>>>
> >>>>>>> Regards
> >>>>>>> Keith
> >>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >>>>>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Reply via email to