Thanks Troy, The precise /flavour/ of *regex* supported by diatheke search really needs to be properly documented.
Expecting the *dot* to be a byte when we're handling Unicode is just not on at all. I'm struggling more because I'm on Windows, where the UTF-16 verse UTF-8 disparity affects everything outside ANSI, but even the friends using diatheke in Linux are having no success with the dot. The character class *[.,;:]* treats it as just a full-stop punctuation mark. cf. I'm so used to having to escape the full-stop in most other contexts. (e.g. Notepad++ search, TextPipe replace filters, etc). If *regex* is to be of any real use, we shouldn't leave users to resort to trial and error to see what works. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656900.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
