Erm, but there is no rule that the wdx full text search applies to "office style" files only.Lefteous wrote:It somehow must be 'combined' with 'Office xml'.
It was intended to filter ANY file type, for example, I use the full text search for my APK-wdx plug-in to search in the app string pool.
So it wouldn't make any sense if you can only choose a plug-in field when you "activated" Office/XML search.
What I meant is:
Showing all wdx full text fields (dropdown list etc.) in any case, so that users don't need to navigate to the plugin tab and enter a term there.
TC can use a raw content search, either by looking for ANSI/OEM text, UTF-8 text, UTF-16 text, or by gracefully unpacking XML-style office files and searching in it.
Offering a plug-in search in that same dialog location greatly advertises an alternative search engine, no matter the file type.
Exactly.Lefteous wrote:...you have to define if you want to use the internal mechanism or for example using the "TextSearch" plugin
That's why we'd need the usual checkbox, so that you can combine all search mechanism as you like.
The point was that the plug-in search needs to be independent from the internal Office/XML search.