Regex examples

[Mister L]

Originally Posted by Tex2002ans

Definitely don't ever do a Replace All with something like that though, you won't know what sort of rogue madness might happen. (And I didn't test on an odd number of en dashes.)

Just the thought of the chaos if I did replace all makes my hair stand on end.

Originally Posted by Tex2002ans

Find: – (\w*[^\.\?!]+?) –
Replace: – \1 –

Hopefully it works, and it will at least save you a lot of time. The rest can probably then be found with a simple:

Find: – <--- Put a space before or after the en dash

[/QUOTE]
Yes that is my method although I am making epub3 so my replace is
– \1 –

Previously I was searching for
– (.*) –
but very often you can have several dashes in the same paragraph but not the same sentence and as I said, I frequently work on books with hundreds of dashes so the more efficient and refined my search is the better.

I search first for a complete set followed by a comma, then complete set no comma, then one dash + comma and then one dash alone. I might be able to combine some of those steps now that I have the more refined search, we'll see.

[Mister L]

Originally Posted by Mister L

...I am making epub3 so my replace is
–*\1*–

Oops, just noticed that my code got eaten... my replace is –# 160 ;\1# 160 ;– only without the spaces, obviously.

Just did a book today with 2313 dashes in it (x_x) so the new and improved regex was greatly appreciated.

[doubleshuffle]

Originally Posted by Mister L

Oops, just noticed that my code got eaten...

Hey, we've got code tags!!

[Tex2002ans]

Originally Posted by Mister L

Just did a book today with 2313 dashes in it (x_x) so the new and improved regex was greatly appreciated.

Originally Posted by Mister L

Oops, just noticed that my code got eaten... my replace is –# 160 ;\1# 160 ;– only without the spaces, obviously.

You can get around this restriction by using the [ noparse] [/noparse] tag, but you have to "break" the entity in the middle (I usually shove it right after the ampersand):

–&[ noparse]#160;[/noparse]\1&[ noparse]#160;[/noparse]–

which will get you this:

–&#160;\1&#160;–

The forum "helpfully" decides to substitute characters, but in this case, we don't want them, so we tell it "not to parse".

[doubleshuffle]

Jeez, even the code tag eats stuff. Wasn't aware of that. It shouldn't, should it?

[DiapDealer]

Originally Posted by doubleshuffle

Jeez, even the code tag eats stuff. Wasn't aware of that. It shouldn't, should it?

When it comes to certain entities, yes. They will always require noparse tags to properly render them as entities. Even within code tags.

[estevam]

Hi!

I have 200 ".xhtml" files inside an epub and I need to delete the line 14 of each one of them.

Is it possible to do this with Regex?

[Doitsu]

Originally Posted by estevam

I have 200 ".xhtml" files inside an epub and I need to delete the line 14 of each one of them.Is it possible to do this with Regex?

That depends on the contents of line 14. If it follows a predictable pattern, someone might suggest a regex for it.

[theducks]

Originally Posted by estevam

Hi!

I have 200 ".xhtml" files inside an epub and I need to delete the line 14 of each one of them.

Is it possible to do this with Regex?

REGEX is about Patterns, not line numbers.

The simplest is select by the text and replace with 'x' ('x' can be nil )
Can you post the offending line?
Is it always the same? If not, what part is different?

[wrCisco]

If "line 14" means the fourteenth line of code (as opposed to the book's textual content), the regex could be:

Find: ((?:.*?\R){13}).*?\R
Replace: \1

(The search must be executed WITHOUT the DotAll option selected and must start at the beginning of each file).

That's a risky operation, since newlines can be easily added or removed by many automatic formatting processes, but if one is absolutely certain that the text between the thirteenth and the fourteenth newline in the code must be deleted (along with the fourteenth newline), that's one way to do it.

If, instead, "line 14" is not a reference to the lines of xhtml code, you can ignore this contribution and should provide some meaningful pattern as the others already said.

[estevam]

This is what I want to delete (marked as red):



As you can see I have a duplicate title in every file, so what I want is to delete that specific line (14) in all of my xhtml files.

[theducks]

you can delete the (</h1>)\s+<p>.+?</p>
replace just with the \1 <<I never perfected the use without capture. I just put back the trigger.

You can replace the .+? with precise text

[estevam]

Originally Posted by theducks

you can delete the (</h1>)\s+<p>.+?</p>
replace just with the \1 <<I never perfected the use without capture. I just put back the trigger.

You can replace the .+? with precise text

Thank you!!! It worked really well

[d351r3d]

I want to be able to copy and replace with saved text kond of like how (\d+) saves the number or more than 1 number in a row and then you can output it with \1,\2, etc. Is there a way to do this with all text in between tags. An example would be:

<p><b>20</b> Words and stuff. Why are there words?<br/><b>20</b> Words and stuff. Why are there words?</p>

I realize that I can (\d+) the numbers and replace them elsewhere with \1.

Find

<p><b>(\d+)</b>\s … <br/><b>\d+</b>\s … </p>

Replace

<h4>\1</h4></br><p> … </p><p> … </p>

I figured it out.

Find

<p><b>(\d+)</b>\s(.*?)<br/><b>\d+</b>\s(.*?)</p>

Replace

<h4>50:\1</h4><p>\2</p><p>\3</p>

[Mister L]

Is it possible to make a regex to turn a phrase with "fake small caps" into a sentence-case phrase, whilst also handling the occasional capitalised proper name in the middle? It must:
1. remove the spans;
2. put all the text between the spans into lower case, leaving the letters outside the spans in upper case;
3. (this is the tricky part) there may be one span on the whole phrase OR there may be several on different parts of the phrase, so it may be necessary to do a multi-part regex.

Example:
Find this:

<span class="Cap">F</span><span class="SmallCap">IRST WORD OF THE SENTENCE IS ALWAYS CAPITALISED,</span> <span class="Cap">O</span><span class="SmallCap">OTHER</span> <span class="Cap">W</span><span class="SmallCap">WORDS IN THE SENTENCE MAY OR MAY NOT BE CAPITALISED</span>

Turn it into this:
First word of the sentence is always capitalised, Other Words in the sentence may or may not be capitalised


If there is just one span I can manage it but since there can be two or three (or potentially more) spans I am not sure how to manage those possibilities.