Forum: CAT Tools Technical Help
Topic: TMLookup
Poster: FarkasAndras
Post title: filter
[quote]Meta Arkadia wrote:
[quote]Michael Beijer wrote:
895 hits is great, and just what I want in such a case.
However, sometimes, it would be useful to be able to filter on individual TMXs, and thus narrow down the results.[/quote]
That's one thing, the other would be to repeatedly filter on things like "target language not like CONSUMER INTEREST" (don't know how to do this in TMLookup) to see alternatives. Can still be a lot of work, especially with 895 hits.
Cheers,
Hans [/quote]
This post only showed up for me now. As I said before, current program versions can't do this unless you also enter a positive target language search term.
I.e. you can do
consumer NOT "consumer interest"
to get hits that contain consumer but not consumer interest, or even
consumer interest NOT "consumer interest"
to get hits that contain both terms but not as one phrase. Due to a limitation in sqlite, you can't do
NOT "consumer interest"
BTW I would be very surprised if db viewer for sqlite (or whatever the name is) had this functionality, as it is a limitation of the underlying SQLite code. They would have had to add their own secret sauce to make it work.
But fear not! Here is a new version with filter buttons:
[url removed]
If you enter consumer interest in the highlight field and click -Filter, it will hide every hit that contains the phrase (in any column). BTW the highlight box is a regex field, while the main search boxes use boolean expressions, so the two work differently. In the highlight box, " NOT and - are taken literally, . is an any-character wildcard, [] is for character sets etc. I will add a syntax description to the readme. (Interestingly /for a regex nerd/, the regex mode in the main search boxes also works slightly differently from the regex mode of the highlight field. The former is parsed by SQLite while the latter is parsed in my own perl code. SQLite's regex parser doesn't recognize characters like á as letters, so some expressions don't work properly. The highlight box has better non-ascii support.)
I'm still not sure if I will leave the filter buttons in, especially if FTS5 adds support for single negative search expressions.
I also added sorting options to the View menu.
[Edited at 2016-01-06 13:04 GMT]
Topic: TMLookup
Poster: FarkasAndras
Post title: filter
[quote]Meta Arkadia wrote:
[quote]Michael Beijer wrote:
895 hits is great, and just what I want in such a case.
However, sometimes, it would be useful to be able to filter on individual TMXs, and thus narrow down the results.[/quote]
That's one thing, the other would be to repeatedly filter on things like "target language not like CONSUMER INTEREST" (don't know how to do this in TMLookup) to see alternatives. Can still be a lot of work, especially with 895 hits.
Cheers,
Hans [/quote]
This post only showed up for me now. As I said before, current program versions can't do this unless you also enter a positive target language search term.
I.e. you can do
consumer NOT "consumer interest"
to get hits that contain consumer but not consumer interest, or even
consumer interest NOT "consumer interest"
to get hits that contain both terms but not as one phrase. Due to a limitation in sqlite, you can't do
NOT "consumer interest"
BTW I would be very surprised if db viewer for sqlite (or whatever the name is) had this functionality, as it is a limitation of the underlying SQLite code. They would have had to add their own secret sauce to make it work.
But fear not! Here is a new version with filter buttons:
[url removed]
If you enter consumer interest in the highlight field and click -Filter, it will hide every hit that contains the phrase (in any column). BTW the highlight box is a regex field, while the main search boxes use boolean expressions, so the two work differently. In the highlight box, " NOT and - are taken literally, . is an any-character wildcard, [] is for character sets etc. I will add a syntax description to the readme. (Interestingly /for a regex nerd/, the regex mode in the main search boxes also works slightly differently from the regex mode of the highlight field. The former is parsed by SQLite while the latter is parsed in my own perl code. SQLite's regex parser doesn't recognize characters like á as letters, so some expressions don't work properly. The highlight box has better non-ascii support.)
I'm still not sure if I will leave the filter buttons in, especially if FTS5 adds support for single negative search expressions.
I also added sorting options to the View menu.
[Edited at 2016-01-06 13:04 GMT]