Summary

Most modern scientific desktop applications support Unicode. This allows them to store and display Cyrillic characters if the operating system and fonts also support them. Limitations usually relate to formatting, sorting, analytics, or clipboard handling — not to basic character display.

Below is a practical overview by product applicable to the current version (2026).

Benefits

• Store and display Cyrillic author names, titles, annotations, and data
• Work with multilingual research materials
• Avoid third-party character conversion tools
• Maintain compatibility across modern Windows systems

EndNote

Support level: Yes (Unicode supported)

• EndNote stores records using Unicode.
• Cyrillic characters can be used in author names, titles, and notes.
• Output styles may require adjustment for correct formatting.
• Sorting may not follow native Cyrillic publishing rules.

Root cause of limitations: Output style configuration, not encoding.

NVivo

Support level: Yes (full Unicode support)

• NVivo allows import, coding, and analysis of Cyrillic text.
• Text search and queries work with Cyrillic characters.
• Built-in language dictionaries and stop-word lists may not include all Cyrillic languages.
• Custom language settings and stop-word lists are required for lexical queries.

Root cause of limitations: Language resources, not character encoding.

XLSTAT

Support level: Depends on Microsoft Excel configuration

• XLSTAT runs inside Microsoft Excel.
• If Excel displays Cyrillic correctly, XLSTAT outputs will also display correctly.
• XLSTAT does not manage text encoding independently.

Root cause of limitations: Excel, Windows locale, and installed fonts.

MathType

Support level: Yes, with context limitations

• MathType supports Unicode input.
• Cyrillic characters can be inserted alongside mathematical symbols.
• Display depends on the host application (for example, Word) and installed fonts.
• The editor is optimised for equations, not long-form multilingual text.

Root cause of limitations: Host application and font support.

ChemDraw

Support level: Yes for labels and annotations

• ChemDraw uses system Unicode support for text labels.
• Cyrillic text can be typed or pasted into annotations.
• No Cyrillic-specific sorting or spell checking.
• Text extraction or search behaviour may vary depending on export format.

Root cause of limitations: Font support and lack of language-specific tools.

PTC Mathcad Prime

Support level: Yes (Russian UI supported; worksheet text dependent on system settings)

• Russian is listed as a supported interface language.
• This indicates built-in Cyrillic support in menus, dialogs, and documentation.
• Text regions in worksheets can display Cyrillic if the system locale and font support it.
• No explicit vendor documentation confirms full character-set coverage for arbitrary worksheet content.

Root cause of limitations: System font and locale configuration rather than core application encoding.

SigmaPlot

Support level: Yes (explicit Unicode support)

• Documentation states support for Unicode characters in worksheets, graphs, and reports.
• Cyrillic text can be displayed if the selected font includes Cyrillic glyphs.
• Works similarly to other Windows applications with Unicode support.
• When copying from Excel or other sources, ensure Unicode text formats are preserved to avoid character loss.

Root cause of limitations: Clipboard format handling or font selection, not lack of Unicode capability.

@RISK (Palisade)

Support level: Yes in modern versions (7.5 and later)

• Older versions relied on legacy code pages, which could prevent the correct display of non-Latin text such as Cyrillic.
• From version 7.5 onwards, Unicode handling was improved, and code pages are no longer a concern.
• @RISK runs as an add-in for Microsoft Excel.
• If Excel displays Cyrillic correctly, @RISK will inherit that behaviour in simulations, outputs, and reports.

Root cause of past limitations: Legacy internal encoding in older versions.

Current limitation scope: Dependent on Excel configuration and installed fonts.

ABBYY FineReader

Support level: Yes (explicit and documented)

• FineReader PDF 16 supports 198 recognition languages in all combinations.
• The supported list includes multiple Cyrillic-script languages such as Azeri (Cyrillic), Belarusian and Bulgarian.
• Multi-language OCR is supported in a single recognition process.
• Russian is available as a selectable interface language, meaning menus and dialogues can be displayed in Cyrillic.

Practical implications:

• Scanned Cyrillic documents can be converted into editable text.
• Mixed-language documents are supported.
• The user interface can operate in Cyrillic (Russian).

Root cause of limitations (if encountered): Incorrect OCR language selection rather than a lack of script support.

How Unicode support works

If an application supports Unicode, it can display any script defined in the Unicode standard, including:

• Cyrillic
• Arabic
• Japanese
• Greek

For correct display:

1. Install a font that includes Cyrillic characters.
2. Ensure Windows language and regional settings allow Cyrillic input.
3. Confirm the host application supports Unicode text handling.

When these conditions are met, the application can render Cyrillic text correctly.

Important notes

• Character display support is different from language-specific behaviour.
• Sorting, spell checking, and analytics may not fully support all Cyrillic languages.
• Most issues are configuration-related rather than software defects.

Disclaimer

The information in this article reflects the most accurate and up-to-date details available for the current versions of the software at the time of writing. Vendor capabilities, language support, and technical specifications may change between releases.

If Cyrillic or Unicode support is critical for your workflow, we recommend contacting us directly before purchase. This allows us to confirm current behaviour, version-specific limitations, and any configuration requirements relevant to your environment.