Disclaimer

[julkue]

@mir3z Could you please explain why this repository isn't maintained anymore?

[mir3z]

Unfortunetely I have limited free time and issues reported here suggest that some aspects of highlighting and serialization need to be rethinked carefully in order to fix these issues. Beside that I'm contributing to other projects which are more important to me. So I decided to stop maintaining this project but I believe the biggest advantage of github in this case is that anyone can fork the project and continue work.

[jtsternberg]

Would love to know if anyone officially adopts this project. @mir3z Can you update this thread if a new maintainer steps up?

[jtsternberg]

Just as a heads up, I've forked this repo, and will maintain until another steps up, or I can't afford to do so.

[julkue]

Basically I think we should work out the advantages of texthighlighter in comparison to e.g. rangy first to see if it is worthwhile to continue maintaining.

[jtsternberg]

Rangy looks pretty good. Are you using it @julmot?

[julkue]

@jtsternberg No, neither one.

[mir3z]

One thing I know is that rangy has a lot better serialization feature than texthighlighter.

On the other hand, rangy provides kind of a DOM Level 2 Range polyfill and is heavier than texthighlighter.

[jtsternberg]

I've played with both quite a bit so far. I like texthighlighter a bit more, but decided to use Rangy since it's being supported. So far, in my experience, the serialization/deserialization is a bit brittle. the DOM needs to be the exact shape it was when the serialization was created. I'm not sure if texthighlighter was the same way, but it's making things a bit difficult for a dynamic site. sigh

[mir3z]

To be host - serialization is very buggy in texthighlighter.