You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/robertknight/approx-string-match-js#readme returns {start: 19933, end: 20035, errors: 21}, which corresponds to "33) And you think that kind of empathy that you referred to, that requires moral courage?' when it should be possible for this quotation to match the text with fewer errors:
Lex Fridman
(00:21:33)
And you think that kind of empathy that you referred to, that requires moral courage?
At the least it could match more of the timestamp and have an equal number of edits with a larger match.
The problem may be the leading whitespace. We could probably remove this for approx-string-match-js, but we'd need to figure out how to accommodate that in dom-anchor-text-positiontoRange.
The text was updated successfully, but these errors were encountered:
Sometimes our approximate string search library can't find a more complete match, even though it seems like it should be possible with fewer errors.
E.g. for the quotation
(from https://lexfridman.com/robert-f-kennedy-jr-transcript/)
https://github.com/robertknight/approx-string-match-js#readme returns
{start: 19933, end: 20035, errors: 21}
, which corresponds to "33) And you think that kind of empathy that you referred to, that requires moral courage?' when it should be possible for this quotation to match the text with fewer errors:At the least it could match more of the timestamp and have an equal number of edits with a larger match.
The problem may be the leading whitespace. We could probably remove this for
approx-string-match-js
, but we'd need to figure out how to accommodate that indom-anchor-text-position
toRange
.The text was updated successfully, but these errors were encountered: