Add regexp into pdfsnip rule to remove extraspaces and linebreaks from snips from pdfs

[arunnbabu81]

I use this editor-toolbar button shared by etardiff in the talk tiddlywiki forum to remove extraspaces and linebreaks between the snips taken from some pdfs.

Before removing the extraspaces and linebreaks it looks like this.

After removing the extraspaces and linebreaks using the editor toolbar button, it looks like this.

Is there any way to add this regex pattern to remove extraspaces and linebreaks into the pdfsnip rule

[buggyj]

Try this macro, like: ((*@reduceLines(@text)*))

reduceLines.js.json.zip

[arunnbabu81]

Try this macro, like: ((*@reduceLines(@text)*))

reduceLines.js.json.zip

Thanks @buggyj for this. I am traveling now. Will check and respond tomorrow.

[arunnbabu81]

Before removing the extraspaces and linebreaks it looks like this.

I am not able to reproduce behaviour shown in the picture above.
What I get on snip from pdf now is like given below

But after adding the reduceLines json to my wiki and changing the pdf rule to this

What I get on pdf snip is

What I actaully want is add a line break after each punctuation mark or full-stop like shown in the image below.

If I go further, is it possible to add a bullet formatting to each sentence like shown below on snip.

Is it possible to do this as two separate rules so that I can use them as I need.

[buggyj]

you can try this:

#extraInsert=*
@text=((*#extraInsert*))((*@removelf(@text)*))
#rule=/(\.)/g
#term=$1\n((*#extraInsert*))
@text=((*@text/#rule/#term*))
$text=((*@text*))\n\n

[arunnbabu81]

you can try this:

#extraInsert=*
@text=((*#extraInsert*))((*@removelf(@text)*))
#rule=/(\.)/g
#term=$1\n((*#extraInsert*))
@text=((*@text/#rule/#term*))
$text=((*@text*))\n\n

This one works.
How to modify this code to get each sentence limited by full stop as separate lines without adding the bullet formatting as shown below.

[buggyj]

change #extraInsert=

…

On Wed, 24 May 2023 at 20:53, arunnbabu81 ***@***.***> wrote: you can try this: #extraInsert=* @***@***.******@***.***)*)) #rule=/(\.)/g #term=$1\n((*#extraInsert*)) @***@***.***/#rule/#term*)) ***@***.****))\n\n This one works. How to modify this code to get each sentence limited by full stop as separate lines without adding the bullet formatting as shown below. [image: image] <https://user-images.githubusercontent.com/67494083/239698396-ea8f233b-3c5b-47c0-976b-9f9b7a0c0c22.png> — Reply to this email directly, view it on GitHub <#121 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVZG457MSMV5XTYPSBFBPDXHZKL3ANCNFSM6AAAAAAYG5DVIQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[arunnbabu81]

#extraInsert=((*@userstring*))
@text=((*#extraInsert*))((*@removelf(@text)*))
#rule=/(\.)/g
#term=$1\n((*#extraInsert*))
@text=((*@text/#rule/#term*))
$text=((*$text*))\n\n((*@text*))\n\n

This is the rule I am using now. I added #extraInsert=((*@userstring*)) which is more flexible and can be changed at the time of the clipping. Also I modified the last line as $text=((*$text*))\n\n((*@text*))\n\n so that the subsequent clips are not getting deleted (based on your old suggestion).

I have one doubt. If I keep the userstring as empty, I get this result

How to get an extra line break after each sentence as shown in the image below using userstring input with the abovementioned rule.

Is that possible ? It's not an urgent need. Just a doubt.

[buggyj]

try entering \n

[arunnbabu81]

Did you meant using \n as userstring as shown in the image above. If yes, it's not working

[buggyj]

it needs converting to a 'linefeed'

try

#nl=\n
#n=n
#nlescaped=\((*#n*))
@userstring=((*#nlescaped==@userstring*??*#nl*??*@userstring*))

[arunnbabu81]

That was awesome. It works perfectly. Note taking has become so easy with all these new additions to tiddlyclip. Whenever I ask some doubts you come up with new tricks.

I have seen that you have updated the tiddlyclip demo page with new contents. Should I share some of the rules which I use (obviously based on your advice and suggestions) to be added to the demo page ?

[buggyj]

It is difficult to write good documentation. I think the first contact needs to be very simple and then slowly get more complicated. For the more complex stuff (the interesting stuff) maybe a separate TW is needed.

There will be a new version of the plugin soon (version 3.0.x).