Custom dictionary examples
Requirements: Professional or Enterprise plan
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 |
frontend | front end | ||
frontend | front-end |
Please note that it is acceptable and encouraged to have multiple entries for the same term. Each entry can represent a different variation, such as the example with "frontend" above, to ensure consistency across all possible uses.
Did this answer your question?
😞
😐
🤩