Custom dictionary examples
Requirements: Enterprise, Pro Pack bolt-on
CaptionHub will do its best to match words in the custom dictionary to the audio it’s examining, but there can be instances where there’s ambiguity.
Here are a few examples:
Phrase | Ambiguity | Suggested “Sounds like” field | Further options |
.NET | Could be “dot-net” or “dot-N-E-T” | dot-net | |
Porsche 911 | Could be “Porsche nine one one” or “Porsche nine eleven” | porsche-nine-eleven | |
EMEA | Could be “emea” or “E-M-E-A” | emea | amia |
NATO | Could be “Nato” or “N-A-T-O” | nato | |
FYI | Could be “fyi” or “F-Y-I” | F.Y.I. | f-y-i |
CEO | Could be “ceo” or “C-E-O” | C.E.O. | c-e-o |
gnocchi | Could sound like “nyohki” or “nokey”, depending on the speaker | nyohki | nokey |
Please note that you can have multiple entries in a custom dictionary for the same term.
Did this answer your question?
😞
😐
🤩