[bksvol-discuss] Re: Paragraph breaks

  • From: "Sue Stevens" <siss52@xxxxxxxxxxxx>
  • To: <bksvol-discuss@xxxxxxxxxxxxx>
  • Date: Tue, 12 Mar 2013 17:54:15 -0500

Hi Christina,

I followed the instructions and it just found 4, but Madeleine found 36. So I 
tried to use ^p, but got the error message that something was wrong in the 
“find what” box. So I guess ^p would require a different search string pattern. 
Madeleine called them paragraph breaks, but they appeared where they shouldn’t. 
I was using my practice file.

Sue S.


From: Christina 
Sent: Monday, March 11, 2013 10:44 AM
To: bksvol-discuss@xxxxxxxxxxxxx 
Subject: [bksvol-discuss] Re: Paragraph breaks

Hi, Sue.

I've pasted the below instructions that I got from Judy years ago.  If it 
doesn't work with ^l, try ^p instead.  You don't need to see the paragraph 
breaks, just be able to get rid of them with a search and replace.  Don't 
forget to save a copy of the book before you try this, just in case.

 

Exclusions with Wild Cards

It takes three steps.  What you'll do is first protect all the

instances where a page number is followed by a line break. That

will work as the way to exclude those line breaks from getting eaten.

 

Then, you'll do your step that you already know how to do to

remove all the line breaks followed by a lower case letter.

 

Finally, you'll put back in all the line breaks that follow a

page number.

 

First, though, save a copy of your file just in case this does

something unexpected or plain wrong.

 

Step 1: Protect the line break that follows a page number

 

In Word's search and replace, make sure you have the option to

"use wildcards" checked.

 

Find: ([0-9])^l

 

that is, left-parentheses left-square-bracket zero hyphen nine

right-square-bracket right-parentheses caret one

 

Replace: \1###

 

that is backslash one pound-sign pound-sign pound-sign

 

Replace all

 

step 2: Remove all the line breaks followed by a lower case letter

 

Find: ^l([a-z])

 

that is caret lower-case-l left-parentheses left-square-bracket

lower-case-a hyphen lower-case-z right-square-bracket

right-parentheses

 

Replace:  \1

 

that is space backslash one

 

Replace all

 

Step 3: Put back in your line breaks after each page number

 

unclick the "use wildcards"

 

Find: ###

 

that is pound-sign pound-sign pound-sign

 

Replace: ^l

 

that is caret lower-case-l

 

 

 

 

From: bksvol-discuss-bounce@xxxxxxxxxxxxx 
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Sue Stevens
Sent: Monday, March 11, 2013 11:11 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Paragraph breaks

 

 

Hi Christina,

Yes, I am using Word 2010, and so far the suggestions haven’t worked because 
the paragraph marks won’t show up on my Braille display.

 

Sue S.

 

 

From: Christina 

Sent: Monday, March 11, 2013 9:33 AM

To: bksvol-discuss@xxxxxxxxxxxxx 

Subject: [bksvol-discuss] Re: Paragraph breaks

 

Hi, Sue.

Are you using Microsoft Word to edit the document?  If so, I can tell you how 
to get rid of the extra paragraph breaks.

Christina

 

 

From: bksvol-discuss-bounce@xxxxxxxxxxxxx 
[mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx] On Behalf Of Sue Stevens
Sent: Monday, March 11, 2013 8:06 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Paragraph breaks

 

 

Hi all,

 

I have a proposition for someone who might want it. As you know, I had a book 
returned for more editing due to inappropriate paragraph breaks. I can’t get 
them to show up on my Braille display. So, if someone would take it and do 
this, he/she can have the proofing credit. Madeleine sent me a list of the 
pages where the unwanted paragraph breaks are, and I would email this list to 
the person. The book is called A Matter of Character: Bethlehem Springs Book 3. 
It is Christian fiction, so you wouldn’t want it if you do not proof Christian 
fiction. There isn’t any violence in it though.

 

Please email me offlist if you would do this, so I can upload it again and tell 
Madeleine what is planned. My email address is siss52@xxxxxxxxxxxx.

 

Thanks,

 

Sue S.

 

Other related posts: