Anchor pairs
Start with high-confidence language pairs where terminology, examples, and reviewers already exist.
Languages
A wider multilingual layer.
Idanium extends the original Sozleralemi language focus into a network for European, Middle Eastern, and global language pairs with domain-specific confidence.
Core
Starting from strong language pairs.
Turkish, German, and English remain natural anchors, with expansion into nearby professional translation markets and institutional language needs.
TurkishGermanEnglishFrenchSpanishArabicItalianDutchPolishPortugueseUkrainianChineseGreekRussianPersianKurdishHebrewJapanese
Expansion strategy
Language growth should follow domain evidence.
Idanium can add new languages more responsibly when each language is connected to sources, reviewers, terminology owners, and real use cases.
Concept transfer
Use reviewed concepts to support additional language directions even before direct translation memory is deep.
Reviewer network
Add native and domain-specific reviewers so each language has accountability, not only machine coverage.
Scripts
Different scripts, different translation problems.
Latin, Cyrillic, Arabic, Hebrew, Greek, and CJK scripts create search, transliteration, name matching, typography, and citation challenges that a simple dictionary cannot solve well.
Transliteration
Track original script, accepted transliteration, local spelling, and citation form for names and terms.
Name matching
Connect variants of personal names, institutions, places, historical names, and administrative entities.
Directionality
Support right-to-left and mixed-script cases where layout and punctuation affect readability.
Search normalization
Find related terms across diacritics, spelling variants, scripts, and transliteration systems.
Language metadata
Every language needs its own context.
Equivalents are only useful when the system knows how and where they should be used.
Register
Formal, official, professional, neutral, public, learner-friendly, or child-oriented usage.
Stored per equivalentRegion
Country, jurisdiction, institution, community, or market-specific usage differences.
Stored per termReview
Native reviewer, domain reviewer, approval date, confidence, and unresolved questions.
Stored per language