On 07/04/13 09:34, Kornel Benko wrote:
> Am Sonntag, 7. April 2013 um 01:36:52, schrieb Tommaso Cucinotta
>
>> I came up with this trivial patch for the kind of scenario you proposed.
>> Simply,
>> export an regexp inset using the text, rather than math, "encoding" rules.
>> AFAICS, one might us
Am Sonntag, 7. April 2013 um 01:36:52, schrieb Tommaso Cucinotta
> So,
>
> I came up with this trivial patch for the kind of scenario you proposed.
> Simply,
> export an regexp inset using the text, rather than math, "encoding" rules.
> AFAICS, one might usefully be willing to write text (and s
On 06/04/13 20:04, Kornel Benko wrote:
>> However, when the regexp contains non-ASCII chars, then it's misinterpreted
>> in the text conversion. I suspect it's due to the fact that the regexp inset
>> has been essentially derived from a math inset, so it's not expecting any
>> non-ASCII stuff there
Am Samstag, 6. April 2013 um 19:32:58, schrieb Tommaso Cucinotta
> On 03/04/13 22:40, Kornel Benko wrote:
> > I want to find (as regular expression) the string "použiť". In tex, it looks
> > "použi\v{t}".
> > But the searched string (as it is diplayed while filling the search form)
> > it is
> >
On 03/04/13 22:40, Kornel Benko wrote:
> I want to find (as regular expression) the string "použiť". In tex, it looks
> "použi\v{t}".
> But the searched string (as it is diplayed while filling the search form) it
> is
> "\regexp{pou\check{z} it\mkern-5mu\mathchar19\endregexp{}}".
Ok, I could repr
I cannot enter those chars on my keyboard. Can u provide a sample lyx file
where I can search and see the problem ?
T.
On 03/04/13 22:40, Kornel Benko wrote:
> Am Mittwoch, 3. April 2013 um 20:28:59, schrieb Tommaso Cucinotta
>
>
>> On 02/04/13 10:28, Jean-Marc Lasgouttes wrote:
>
>>
Am Mittwoch, 3. April 2013 um 20:28:59, schrieb Tommaso Cucinotta
> On 02/04/13 10:28, Jean-Marc Lasgouttes wrote:
> >> I am not sure if it has anything to do with utf8. The expanded string looks
> >> like it is expanded for LaTeX. This looks quite wrong to me in context of
> >> searching. Why is
On 02/04/13 10:28, Jean-Marc Lasgouttes wrote:
>> I am not sure if it has anything to do with utf8. The expanded string looks
>> like it is expanded for LaTeX. This looks quite wrong to me in context of
>> searching. Why is this done?
>
> This is how advanced search works.
Confirm. This is how th
31/03/2013 21:35, Georg Baum:
I believe this happens because the "ž" is encoded as two bytes when
using UTF-8. And I guess the regexp matching software in use works on
"bytes", not "characters". So, you are forced to use two periods to
match the two bytes in "ž". And more, if you want to match Ch
Helge Hafting wrote:
> On 29. mars 2013 13:38, Kornel Benko wrote:
>> I seem unable to find strings using non ascii chars (e.g. latin2)
>>
>> (Please try to use UTF-8 encoding to read this mail)
>>
>> The regex search string may be "pou.i.", so I was expecting to find
>>
>> e.g. "použiť". I have t
On 29. mars 2013 13:38, Kornel Benko wrote:
I seem unable to find strings using non ascii chars (e.g. latin2)
(Please try to use UTF-8 encoding to read this mail)
The regex search string may be "pou.i.", so I was expecting to find
e.g. "použiť". I have to use '..' to find this single chars. ("
11 matches
Mail list logo
