Hub: Building a custom system using a dictionary only

You may build a custom system without using parallel documents by using a dictionary only, no other files needed.
This will work for projects in language pairs with a fully supported Microsoft translation system behind it (see below), not for any other language pairs.

A dictionary is an Excel file containing the language code as column header in row 1, and the values of phrases you want translated the exact specified way in the subsequent rows. You specify "Do not translate" by entering the same phrase twice. You may enter as many languages as you like in the same file, and the columns can be in any order. 

Then you select this file in the “Dictionary” tab.

If there are less than 2000 sentences available, there is no point choosing anything in the “Training” tab. Unselect any files in the Training tab that may have been automatically selected.
You are now ready to train and deploy a system. You will not get a test report. The training in this case will only extract your dictionary, and deployment will publish the dictionary as part of the Microsoft Translator service.

Language pairs with a fully supported Microsoft translation system behind it

English (en) from and to any of the following:

af Afrikaans
ar Arabic
bg Bulgarian
bn Bengali
bs-Latn Bosnian – Latin
ca Catalan
cs Czech
cy Welsh
da Danish
de German
el Greek
es Spanish
et Estonian
fa Persian
fi Finnish
fil Filipino
fj Fijian
fr French
he Hebrew
hi Hindi
hr Croatian
ht Haitian Creole
hu Hungarian
id Indonesian
it Italian
ja Japanese
ko Korean
lt Lithuanian
lv Latvian
mg Malagasy
ms Malaysian
mt Maltese
mww Hmong (White)
nl Dutch
no Norwegian
otq Querétaro Otomi
pl Polish
pt Portuguese
ro Romanian
ru Russian
sk Slovak
sl Slovenian
sm Samoan
sr-Cyrl Serbian (Cyrillic)
sr-Latn Serbian (Latin)
sv Swedish
sw Kiswahili
th Thai
tlh Klingon
tlh-Qaak Klingon (pIqaD)
to Tongan
tr Turkish
ty Tahitian
uk Ukrainian
ur Urdu
vi Vietnamese
yua Yucatec Maya
zh-HanS Simplified Chinese

Japanese (ja) from and to Korean (ko)

Edited on May 3, 2017


  1. Announcement: Changes to the Collaborative Translation functions
  2. Translator Hub replaces the Collaborative Translation Framework (CTF)
  3. Microsoft Translator Moves to the Azure portal
  4. API - Translator datacenters
  5. API and Hub: Confidentiality
  6. API - Translator Speech: Microsoft Translator Speech API references
  7. API - Translator Text: How to report an issue with the API
  8. API - Translator Text / Speech: Microsoft Translator with IP filtered firewalls
  9. API - Translator Text / Speech: Get a report of your consumption
  10. API - Translator Text / Speech: Using the API key directly in the call. No more token.
  11. API - Translator Text / Speech: Why are there two keys for my API subscription?
  12. API - Translator Text: Hybrid Neural Machine Translation
  13. API - Translator Text: Using Neural MT Systems
  14. API- Translator Text: Standard category languages
  15. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  16. API - Translator Text: Limits
  17. API - Translator Text: How Microsoft Translator counts characters
  18. API - Translator Text: Gender selection in the Speak() method
  19. API - Translator Text: Trados plugin for Microsoft Translator
  20. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  21. API - Translator Text: European datacenter
  22. API - Translator Text: Languages detected by the Detect() method
  23. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  24. API - Translator Text: Profanity filtering in the TranslateArray() method
  25. API - Translator Speech: Signal the end of the utterance
  26. Hub: API available
  27. Hub: Translator Hub Resource Guide
  28. Hub: August 2016 Release notes
  29. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  30. Hub: Capacity of custom Microsoft Translator Hub systems
  31. Hub: Building a custom system using a dictionary only
  32. Business Applications: Security and Privacy in Microsoft Office Products

Feedback and Knowledge Base