(Split out from #245082: Advanced search functions)

Use cases:

Sometimes, we borrow words from English. In some cases, we later find a better word in our own language to replace the borrowed word with. For instance, for a long time we translated "feed" with "feed", until we managed to agree on a Norwegian word to use instead.

Some English words are spelled the same way as a different word in another language. For instance, in Norwegian, "the list" can be translated as either "lista" or "listen". We've decided to use a lingustic style where "lista" should be used instead of the more conservative "listen". But when I search for this word, I get quite a lot of hits for the English verb "listen".

Related issues: #691786: Advanced search: Search for complete words and #691790: Advanced search: Case sensitive search. These options should probably be hidden behind an "Advanced search" link normally, to prevent the interface from being to cluttered.

Comments

gábor hojtsy’s picture

Added #1118430: Set up the filtering/display setting UI for future growth to set us up for filter extensions like this.

Sahin’s picture

Title: Advanced search: Search only in translation, not in source strings » Separate the source and target strings for "search string"

The input/search string should be searchable in source or target strings, or in both. We need this for different use cases.
A dropdown selection list with options
* source
* target
* both [default]
located to the right of the "Contains" box can resolve this issue.