View Single Post
Old 03-08-2023, 11:08 AM   #11
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,079
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by Jaws View Post
I was afraid of that.

The only other option I can see is to manually drop fake-code markers like

<p class="splitbabyhere"></p>

into the index.xhtml file at the desired split points -- but then I still can't be sure that an xpath statement would work correctly. Since I don't use xpath for anything else, I'd almost certainly screw it up even if that's the right approach, especially working on a new machine with an oversensitive touchpad.
Hey I use <div class="splithere"> </div>

It works just fine
Just do whatever to place the split point markers.

The Right-click in the code:split at multiple locations:
Code:
//h:div[re:test(@class, "split_here", "i")]
After the split, you will need to bulk remove the 'marker'
theducks is offline   Reply With Quote