>Here are my thoughts and Justin perhaps can comment as well.
>
>Firstly, the apostrophe IS being treated like a character as it
>should be - if it were a separator it would always be ignored and I
>don't think that is the intention and would not provide the result
>because in many cases in French a single character exists before the
>apostrophe.
Actually if the apostrophe was treated like a separotor, it would be just perfect IMHO.
In french, you just find single "d" or "l" or "s" before it, which are absolutely useless in terms of search/find functionalies (these are not terms)... But maybe this is not the case in english? Don't know...
>You can't search for just the apostrophe in the boolean parser (main
>find box) because boolean search routines look for 'terms'. 'Fond
>d'air' is set of terms while a single apostrophe is NOT. If you
>search for "fond AND air" it must find those exact terms or a
>wildcard of them which "d'air" with the apostrophe in front of it is
>NOT thus the result. If you search for "fon *air" you should find it
>as I have told the boolean parser to look for a contains search(slower).
>
>Similarly, if you want to search for "fond air" then use the
>iterative routines like SEARCH IN FIELD and ADVANCED SEARCH which are
>VERY different routine that do not look for terms but anything that
>contains those characters - this is a much slower way of searching
>but provides an alternative to the boolean parser.
>This is the design of BOOLEAN engines. If you want "fond AND air to
>find "fond d'air" then in your thesaurus you have to tell the boolean
>engine that "air" is the same as "d'air" and now you have created a
>synonym "term".
Sure we can do that, but it's quite constricting...
>In either case, you have several features in V4pro that allow you to
>work in many different ways provided you understand the engines.
Sure, but the main search field is THE way to go in a day to day workflow. Do we (french users) have to adapt to the way Soundminer searches, or the invert? That is the question
.
If results won't appear just because of a "useless" apostrophe present in the description, it's really a shame IMHO.
Just FYI, the search function in the Pro Tools's Workspace treats the apostrophe like a separator, so this specific problem is not present...
Bye.
PS: BTW, you didn't answer concerning FLAC and Ambisonic / multichannel VST, is it a "no, no"?