[bksvol-discuss] Re: Ok, I'm confused! What's next?

  • From: Gmail For Deb <djoutland@xxxxxxxxx>
  • To: "bksvol-discuss@xxxxxxxxxxxxx" <bksvol-discuss@xxxxxxxxxxxxx>
  • Date: Thu, 26 Jun 2014 23:44:52 -0400

And thank you both!

Deb Outland
Lexington, Kentucky

> On Jun 26, 2014, at 9:48 PM, "Kim Friedman" <kimfri11@xxxxxxxxxxx> wrote:
> 
> Hi Judy, thank you, thank you, thank you. Regards, Kim Friedman.
>  
> From: bksvol-discuss-bounce@xxxxxxxxxxxxx 
> [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Judy s.
> Sent: Thursday, June 26, 2014 6:44 PM
> To: bksvol-discuss@xxxxxxxxxxxxx
> Subject: [bksvol-discuss] Re: Ok, I'm confused! What's next?
>  
> Hi Deb, Kim's suggestion regarding sidebars is great.  I've done many books 
> with sidebars and I do the following in addition to what Kim said.
> 
> Separate the text of the book from the text of the sidebar by putting three 
> asterisks on a line by themself, one set before the text contained within the 
> sidebar, one set after.  Then, on the line of text where the sidebar begins, 
> put the word Sidebar in as Kim suggests, but put that word inside of square 
> brackets. Also, keep the text that's in the sidebar on the actual page of 
> text where it appears, but it's perfectly reasonable to move where it falls 
> within that page so that it doesn't break up a paragraph.  Sidebars rarely 
> are embedded into the middle of a paragraph in the original printed text. 
> That's why they're called "sidebars" -- they are a column of text or box of 
> text that appears to one side or the other of the normal printed text for a 
> page. smile. The way they get embedded in an OCRed scan is usually an 
> artifact of how OCRing and scanning works.
> 
> Here's an example then of what you want the page to be:
> 
> paragraph of text
> paragraph of text
> ***
> [sidebar:] text from sidebar
> ***
> paragraph of text
> 
> I hope that makes sense. smile.
> 
> In regards to working with the file in .rtf format, that definitely makes 
> sense.  Whatever editor you use (Kurzweil and Microsoft Word are the two that 
> most volunteers use if they are working on a windows system), though, make 
> certain that it retains the page breaks that Omnipage has preserved in your 
> scanned files. Some editors that can work with .rtf files (like Wordpad) 
> strip out the hard page breaks, which you don't want an editor to do.
> 
> Judy s. 
> Follow me on Twitter at QuackersNCheese
> 
> On 6/26/2014 8:24 PM, Kim Friedman wrote:
> Hi Deb, with regard to sidebars, I can't advise you since I have proofread
> fiction and not non-fiction. I've dealt with appendices, footnotes, casts of
> characters, but not sidebars. Probably what you'd do is write Sidebar with a
> colon after it and proceed to make sure what's in the sidebar. I personally
> think if sidebars are located within a paragraph of text, I probably would
> prefer to read the whole paragraph of the text, then read the sidebar
> connected to it. I do not know what other submitters would say, but the
> question arises   about whether sidebars are located in such a way as to
> make sense. Again, I don't know what other submitters will say. With regard
> to working the format in .rtf, it sounds like a good idea, especially if
> you're saving your file as an .rtf file. As for me, I generally open the
> file and proofread it in Word, but I have used Kurzweil when Word was being
> squirrelly. Regards, Kim Friedman.
>  
> -----Original Message-----
> From: bksvol-discuss-bounce@xxxxxxxxxxxxx
> [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Gmail For Deb
> Sent: Thursday, June 26, 2014 5:18 PM
> To: bksvol-discuss@xxxxxxxxxxxxx
> Subject: [bksvol-discuss] Re: Ok, I'm confused! What's next?
>  
> Thanks, Kim!
>  
> Yes it gives me some parts to work on tomorrow.  Do you typically work in
> word, or some other text editor?  OmniPage has a text editor, but I'd
> rather not  rely on the export of the book into rtf to just work without
> more tweaking afterwards.  It seems like  it would be better to do
> manipulation of the file in actual rtf format in an editor that plays nicely
> with it.
>  
> The one other item that would be helpful to know before I start is how to
> treat those boxed sections that are kind of like sidebars.  They are at
> least sometimes guided meditations that fit the general section of the book,
> but are placed (I believe) right out in the middle of the main flow of the
> book.  Any suggestions?
>  
> Again, thanks!
> Deb Outland
> Lexington, Kentucky
>  
> On Jun 26, 2014, at 7:59 PM, "Kim Friedman" <kimfri11@xxxxxxxxxxx> wrote:
>  
> Hi Deb, sometimes headers and footers are either the book title and 
> the author's name. If you see those, you can strip them. If you see a 
> chapter number or title, then you only want those on the actual first 
> page of a chapter. Subsequent pages don't need them. I'd also think if 
> the chapter has sections in them, then you only want a particular 
> section title to occur on the first page of the section and not on 
> another page which is in the same section (do you follow me?). With 
> regard to font, you want to make sure you have a font which is 
> readable for the whole book (Bookshare likes Times New Roman with 
> titles at 20-point, Parts at 18-point, Chapter titles at 16-point, 
> sub-sections or sections at 14-point, actual body of the whole text at 
> 12-point, Author's name at 20-point. (With regard to font, the real 
> consideration is that it be readable so Times New Roman or Arial, or 
> anything which is really clear to read is important.) Page setup should be
> legal or custom size, margins (I'd go for narrow (1.0 or 1.25 all round).
> Paragraph setup for the body of the text is generally on the left. I 
> know what I used to do for paragraphs with regard to proofreading a 
> document and I can send you my procedure for it, but I think other 
> submitters will be better at giving you more specific information 
> about what to do about paragraphs in your text. I hope what I've mentioned
> so far helps you out.
> Regards, Kim Friedman.
>  To unsubscribe from this list send a blank Email to
> bksvol-discuss-request@xxxxxxxxxxxxx
> put the word 'unsubscribe' by itself in the subject line.  To get a list of
> available commands, put the word 'help' by itself in the subject line.
>  
>  To unsubscribe from this list send a blank Email to
> bksvol-discuss-request@xxxxxxxxxxxxx
> put the word 'unsubscribe' by itself in the subject line.  To get a list of 
> available commands, put the word 'help' by itself in the subject line.
>  
>

Other related posts:

  1. Home
  2. bksvol-discuss
  3. Archive
  4. 06-2014