Some of my client's paragraphs have double carriage returns creating spaces between them. They indicate a new section in the narrative.
How can I have InDesign ignore an empty line whenever a paragraph is at the top of a new page? So the paragrph lines up with the top of the page frame.
NB. I realise that I could a special paragraph style on the preceding paragraph with that extra bottom space built-in, but that seems quite laborious if there is an automatic way for ID to handle this.
InDesign can't ignore an empty paragraph returns at the top of the page. Your realization is correct: let paragraph styles do the work for you. Use Find/Change to quickly get to the double returns and reduce them to a single return.
Thanks. I'll get re-formatting.
maybe I didn't understand good your issue.
but you could find triple returns
and change with a single return + space after
Thanks. I am constantly re-flowing the text during my layout design stage, so I needed a solution that does not involve deleting the line returns for those special cases, because with each layout change, the line returns may need to be put back in. I think the special paragraph style is the most flexible, thank-you. And also layout changes may also occur after proof-reading by the author.
It is essentially a challenge of re-training old typing habits, whether you own or your boss!
Well, the writer knows where the double spaces go – I do not. So I think that he has to provide the copy with those spaces, so I know where they go. I will then need to remove them by hand and apply the special end-of-section extra line paragraph style before the section break.
Or, just use the Query that ships with InDesign in Edit > Find/Change:
This will remove all of the extra returns, of course, but spacing should be handled with InDesign spacing and keep commands, and not with extra ¶s.
I was going to recommend the built-in script named FindChangeByList.jsx, which does a more thorough job than the single pre-set query you cited above. But when I looked at it in a text editor to see if it matched your GREP query (~b~b+), I noticed that the whole series of GREP searches within it was written incorrectly. That means the built-in FindChangeByList.jsx will actually fail to do a complete cleanup. It won't give any summary indication of what it did or did not do. My re-written version on my website works more reliably, and also will protect existing paragraph styles. It also does roughly twice as many text cleanups as the built-in FindChangeByList.jsx.
Hi Simon, as you can see in my short video above, replacing double return with "space after" the spacing between paragraphs never change.
The space "disappears" only if at the top of the page (as on the second page in my video)
Vlad. Thank-you. I don't think I quite understood what you were saying. It sounds good and I will try that first.
you can take a look here about paragraph spacing
if you need further informations about paragraph spacing just ask
some of us will give you precise instructions
with each layout change the line returns may need to be put back in.
See #1 in this list: https://www.thebookdesigner.com/2011/03/4-top-book-formatting-mistakes-to-avoid/.
I work primarily in long document publishing. In that environment, every extra click adds up, so I am micro-focused on streamlining my workflow. The first thing I do when I receive a document from a client is run a series of find/change queries to clean up the mess, like the extra returns, spaces, etc. Then I design paragraph styles that control the spacing between paragraphs and force top-level heads to the top of the next pages, automatically. This approach allows the document to reflow after edits. I won't do anything that requires manual updates after edits. Those minutes can add up to lost weekends.
Wise words. Thank-you.
But, if the client uses the double carriage return consistently to indicate a new section, you might want to change that double carriage (or triple or whatever quantity) for a jump to new column character or a jump to new frame or to new page (depending on the format), wouldn't you?
Always looking to avoid extra hand work, of course.
I think Simon doesn't want to start these sections to a new page (or to new frame) but he wants to eliminate spaces above if they are at the top of a new page