Bug overview description.
If you use "~" to search multiple metatags of different types, no results will ever be returned, even if the search is otherwise a valid one.
You can search for, say, posts that have both a width of 1200 and a height of 1200, but you can't perform an "or" search for those.

What part(s) of the site page(s) are affected?
Posts page.

What is the expected behavior?
Posts that match at least one of the metatags prefixed with "~" will be returned.

What actual behavior is given instead?
No posts are returned, even if they match at least one of the metatags given.

Time of incident (if applicable).
Can you reproduce the bug every time?
What steps did you take to replicate this bug?
Tested with ~height:1200 ~width:1200, as well as "~notes:translat ~desc:translat". Neither produce any results, even though all of these tags return results separately.

Errors or other messages returned (if any).
"No posts matched your search."

This is definitely a well-known bug. Unfortunately the way searches are coded makes this basically impossible to do without a significant overhaul.

You can't use ~ or - with metatags at all. ~height:1200 ~width:1200 is querying for posts that have the ordinary tag named "height:1200" or the tag named "width:1200", and is not querying for any metatags at all.

As I understand it metatag terms are parsed completely separately from ordinary tag terms (ie. any advanced features like ~ and - have to be implemented specifically in the metatag parser if you want to be able to use them with metatags.). Since metatag terms cannot currently begin with ~ or -, the result mentioned above occurs: the term beginning with ~ or - is necessarily treated as an ordinary tag.

The lack of - is regarded as more of a problem than the lack of ~ IIRC.

Meta-tags don't really play well with other meta-tags, specially with operators.

If you're trying to get squared images width:1200 ratio:1 does the trick (actually ratio:1 does the work and the other just limits the size). As for searching in notes/description you'll have to do that separately