Text content language is the language of the files that you import or work with in NVivo. You can work with your NVivo interface in one language and your source files in another. For example, you may work with the interface in English, but you are analyzing interviews that are transcribed in French.

The text content language and stop word lists are managed via project properties. Project property settings apply to every user who accesses the project.

For the lexical queries (text search and word frequency query) you can customize the language settings so that NVivo detects the words in the correct language and excludes words based on the stop-word list.

Supported languages

NVivo supports several text content languages, and has pre-defined stop-words lists for those.

NVivo provides the following text content languages: Chinese, English (UK), English (US), French, German, Japanese, Portuguese and Spanish.

Each text content language has an associated dictionary that is used for:

Spell checking.
Finding words with the same stem or similar meanings when you run Text Search and Word Frequency queries.
Including words with the same stem when you autocode based on existing coding patterns. (This feature is only available in NVivo installations with coding enhancements enabled.)

Each text content language also has an associated 'stop word' list. The words in the stop word list are filtered out (removed) when you:

Run a Word Frequency or Text Search query
Generate a cluster analysis diagram comparing words in files or codes

Other languages

Make sure that the text content language is set to match the language of your files. If the language of your files is not available as a text content language, you should set the text content language to 'Other'. When the text content language is set to 'Other', you cannot look for similar words when you run a Text Search query or Word Frequency query.

If you are working with data in a different language, you will have to define the text content language as "Other" and customize your settings, prior to running any lexical queries. Therefore, in your open project go to “File”, choose “project properties” and switch the “text content language” to “Other” (the default option is “English (US)”. Then, if you run a text search (in which you can also choose which sources/cases to include in the search, in case you work with multiple languages) you can search for different terms and put the slider on “exact matches”. In the project properties next to "text content language" you will also find a button to open the stop-words list which you can customize for every project.

More information

Please find more information HERE.

and for special text search queries here:
http://help-nv11.qsrinternational.com/desktop/deep_concepts/special_characters_and_operators.htm