Chapter 1 looks fine, but I have now updated the template again. I had
failed to put the latest iteration of the cover graphic into the
template. I've now replaced both the chapter and book templates on the
website. These updated templates include the latest graphic and the
addition of visible URLS in the Copyright section.

I had some other changes to make in Chapter 1, so I have inserted the
updated graphic at the same time. My revised chapter is here:
http://www.oooauthors.org/english/userguide3/gs3/feedback-on-3.2/0101GS3-IntroducingOOo_JS_JHW_20100728.odt/view
I have submitted it for further review. Changed are tracked.

Do carry on with the other chapters!

--Jean

On Tue, 2010-07-27 at 22:15 +0100, Joe Sellman wrote:
> Hi Jean,
> 
> Chapter one is in the [correct] feedback folder, hopefully all is ok,
> 
> Thanks for the heads up on the template - that was a lot easier than how I
> was going to do it,
> 
> Regards
> Joe
> 
> On Tue, Jul 27, 2010 at 10:38 AM, Jean Hollis Weber 
> <[email protected]>wrote:
> 
> > Joe,
> > No one has taken this on yet. For your trial chapter, you might as well
> > do Chapter 1.
> >
> > Do you know how to apply a revised template? Basically, you download the
> > new version of the template and replace the old version with the new one
> > in your templates folder. If you don't have the old version, then simply
> > save the revised template anywhere on your computer and then import it
> > into the templates folder. After that is done, then when you open a user
> > guide chapter, it should ask you if you want to update styles. Choose
> > Yes, and it's done. All that's left is to manually change the cover
> > graphics. If the chapter does NOT ask about updating styles, then you'll
> > have to go to Plan B: using the Template Changer extension.
> >
> > BTW, amended chapters should go here:
> > http://www.oooauthors.org/english/userguide3/gs3/feedback-on-3.2
> >
> > I moved the chapter you uploaded from where you put it to there. Sorry
> > about the two feedback folders; I wasn't specific enough in my previous
> > note. You did what I said, not what I meant.
> >
> > When naming files, please do not have any blank spaces in the filename.
> > Use an underscore or hyphen if you wish. Also please include the date,
> > for example: 0105GS3-GettingStartedWithCalc_JS_20100727.odt
> >
> > --Jean
> >
> > On Tue, 2010-07-27 at 09:30 +0100, Joe Sellman wrote:
> > > Hi Jean,
> > >
> > > I notice this email didnt get any responses, does this still need to be
> > > done?
> > >
> > > If so, let me know (and specify a chapter),
> > >
> > > Regards,
> > > Joe
> > >
> > > On Sat, Jul 17, 2010 at 1:57 AM, Jean Hollis Weber <[email protected]
> > >wrote:
> > >
> > > > We need someone (or several people) to do some maintenance on the
> > > > Getting Started book (other than the chapters on Calc and Draw, which
> > > > are being done by Joe and Bhagyashree, respectively).
> > > >
> > > > Here is what needs to be done in each of the chapter files:
> > > >
> > > > * Apply revised template and title page graphics.
> > > > * Update email address for OOoAuthors on title page.
> > > >
> > > > Please take the files from this folder:
> > > > http://www.oooauthors.org/english/userguide3/gs3/V32_published
> > > >
> > > > Do NOT retract the files while you are working on them. Just take a
> > > > copy, amend it, and put it into the Feedback folder for the book.
> > > >
> > > > Whoever takes this on, please do ONE chapter and let me check it to
> > make
> > > > sure there are no problems, before you do all of them.
> > > >
> > > > After all the chapters have been done, I'll pick someone (from those
> > who
> > > > said they wanted to be book compilers) to put together the full book.
> > In
> > > > the meantime, I'll keep going through my notes to see if any chapters
> > > > need updates to their contents as well.
> > > >
> > > > Jean
> > > > --
> > > > Jean Hollis Weber
> > > > Co-Lead, OpenOffice.org Documentation Project
> > > 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to