RELATED IDEAS
Add glossary support for dynamic knowledge base translations
What is the challenge? |
The new on-the-fly LLM translation is handy, but it can’t handle specialized terminology. Since translations only exist on the front end, we can’t edit or correct terms that are wrong or inconsistent. |
What is the impact? |
Logistics terms, brand names, and industry jargon might get mistranslated. |
Describe your idea |
Let us upload a glossary (source/target terms) per language. The LLM should always use these glossary terms when translating KB pages live. This would make dynamic translation much more reliable for specialized content. Example:
|
© 2025 Aha! Labs Inc.•All rights reserved
Multilingual documentation that features product-specific terminology, tone and style would be extremely helpful! To support this, it would be great to have something like a "Configure AI Translations" section in the knowledge base settings. This would allow us to "guide" AI-generated translations. Ideally, we could define terminology directly in the KB settings in a field. For example like this for English <> German:
"Accounting Export" ⇔ "Buchhaltungsexport"
"Reporting" ⇔ "Berichte"
"AHA Knowledge" ⇔ "AHA Knowledge"
Another example would be to give instructions on how to address the customer; such as in a formal or informal tone, where necessary based on target language and audience.
There are many things we could configure if we had a configurable field to customize AI-generated translations.
Thanks @Guest , overriding and customizing translations is an important option! Would you want a single glossary across your entire account, or would they be specific to each knowledge base?
This is super important for a professional customer experience - currently the translation for example sometimes translates the name of the product and we have no way to influence that. AI translation is a lot better than it was years ago, but it is not yet there to replace humans entirely, so please allow humans to be part of the process.