David, I'm not sure if you just missed my
previous post or didn't want to address it (which would also be fine).
To add on to my previous post, I feel somewhat confident that once I've located it, I can contribute code to fix the problem I mentioned, but due to all the moving parts involved between different source formats being delivered to the device as KEPUBs via the KoboTouch Extended driver and this plugin reading the location of a highlight, it'd be massively helpful if someone with previous knowledge of the code involved could point me towards likely culprits. Even knowing whether it makes more sense to start my search with the driver or this plugin (let alone specific scripts) helps.