KWIC display does not space words properly.

Craig Berry

The problem with spaces next to highlighted matches that have adjacent punctuation is the difference between the following axis (which we can't use for performance reasons) and following-sibling, which we are currently using. For example, the highlighted word "iron" comes through looking like this:

<tei-w>iron</tei-w>

so that element that indicates the highlight puts the content at a different level in the hierarchy than any adjacent <pc> element. They aren't siblings, so the space processing that depends on following-sibling doesn't work. It's the exact same problem we have elsewhere with <hi> surrounding a word but not its adjacent punctuation.

2018-03-29T19:06:58+00:00

Comments (2)

Craig Berry
The problem with spaces next to highlighted matches that have adjacent punctuation is the difference between the following axis (which we can't use for performance reasons) and following-sibling, which we are currently using. For example, the highlighted word "iron" comes through looking like this:

<tei-w>iron</tei-w>

so that element that indicates the highlight puts the content at a different level in the hierarchy than any adjacent <pc> element. They aren't siblings, so the space processing that depends on following-sibling doesn't work. It's the exact same problem we have elsewhere with <hi> surrounding a word but not its adjacent punctuation.
- 2018-03-29T19:06:58+00:00
Craig Berry
- changed status to resolved
We are now using BlackLab for search, so the problem with the eXist-based KWIC results is no longer relevant.
- 2023-06-03T18:08:43+00:00
Log in to comment