[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR inconsistencies
From: |
Sebastiano Vigna |
Subject: |
Re: LSR inconsistencies |
Date: |
Sat, 12 Oct 2019 18:18:05 +0200 |
> On 12 Oct 2019, at 12:08, Werner LEMBERG <address@hidden> wrote:
>
>> Template: integrating \startTextSpan and \stopTextSpan in a customized
>> TextSpanner
>>
>> then click "Enable filter". Nothing returns.
>
> Indeed. Here, the *second* backslash in the title prevents results in
> the filter. This looks like a bug in the LSR search engine.
> Sebastiano?
Mmmmhhhh... there's some weird escaping sorcery going on. If you look for
\\startTextSpan it'll work. But yes, it should work with a single slash.
Actually, not. The indexed token is starttextspan. So the engine should
tokenize '\' 'startTextSpan' and do its job. It's not. I'll have a look into it.
Ciao,
seba
- LSR inconsistencies, Werner LEMBERG, 2019/10/05
- Re: LSR inconsistencies, Thomas Morley, 2019/10/05
- Re: LSR inconsistencies, Werner LEMBERG, 2019/10/07
- Re: LSR inconsistencies, Thomas Morley, 2019/10/11
- Re: LSR inconsistencies, Werner LEMBERG, 2019/10/12
- Re: LSR inconsistencies, Thomas Morley, 2019/10/12
- Re: LSR inconsistencies, Werner LEMBERG, 2019/10/12
- Re: LSR inconsistencies, Thomas Morley, 2019/10/12
- Re: LSR inconsistencies,
Sebastiano Vigna <=
- Re: LSR inconsistencies, Wols Lists, 2019/10/13