Re: [libreoffice-documentation] Weird stuff department: Why everything needs last-minute checking

[Tom Davies <tomdavies04@yahoo.co.uk>]

Hi :)
A lot of this could be picked up by anyone, however new to the team.  It just needs someone other than the author (or whoever has just done a lot of work on the chapter/guide).  Hazel is brilliant and goes into a LOT of detail but perhaps we need a more informal "quick squint test" or something.  

I think this team does usually do this anyway.  Usually when chapters or books get uploaded to the wiki i make a point of telling the Users List and Tim of KrackedPress fame so that they can have a quick look or come back with problems they spot.  They hardly ever grumble about any of the documentation tho so i got lazy and  didn't do this with Draw or Impress.  

Someone had a brilliant idea of making an announcement to the entire community and it might be a good idea to do that when guides are uploaded to the wiki?  It still might be  good idea to let soem of the lists know when individual chapters are released but when guides are uploaded an community wide announcement would be great.  
Apols and regards from
Tom :)


--- On Mon, 4/6/12, Jean Weber <jeanweber@gmail.com> wrote:

From: Jean Weber <jeanweber@gmail.com>
Subject: [libreoffice-documentation] Weird stuff department: Why everything needs last-minute checking
To: Documentation@global.libreoffice.org
Date: Monday, 4 June, 2012, 1:40

The ToC in the Draw 3.4 Guide is missing the Preface and hence has
wrong page numbers for the rest of the book, but the really weird bit
is that the page numbering restarts in Chapter 3. The actual page
numbers in the document are correct. I'm not sure what caused that
weirdness (other than the ToC not being updated before the PDF was
created), but I certainly should have noticed it. And I probably
should have put the "release candidate" out for others to check, but I
didn't...

This is not a big deal, but it does point out the need for us to have
more quality assurance on our books... but that QA needs to be on a
fast turnaround as well as thorough. I wonder who might have noticed
the ToC was wrong? (Hazel, probably.) Does anyone else actually look
through a ToC when final-proofing a book? I usually do, when it's
someone else's book; but when it's a book I've done, I just don't
notice things.

When I get a chance, I'll regenerate the ToC and the PDF and hope
nothing else goes weird. ;-)

--Jean

-- 
Unsubscribe instructions: E-mail to documentation+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted


-- 
Unsubscribe instructions: E-mail to documentation+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted