AI Assisted Translations group_work

Using glossaries (terminology consistency)

Glossaries make sure brand names, product names, and specific terms are always translated the same way.

What you need to do

1. Prepare a CSV file with your terminology. The file needs at minimum a key column and one column per language (e.g. en, fr_FR, el_GR).

   Example:

   key	en	fr_FR	el_GR	ms_MY
   oyster_sauce	Lee Kum Kee Oyster Sauce	Sauce aux huîtres Lee Kum Kee	Σαλτσα Στρειδιων Lee Kum Kee	Sos Tiram Lee Kum Kee
   stir_fry	stir-fry	sauter au wok	τηγανισμα στο γουοκ	tumis

2. Upload the CSV file to your site's glossary folder in Jahia (your administrator can tell you the exact path — by default it is /files/glossaries under your site).

3. That's it. The next translation request will automatically pick up the glossary and apply it.

Tip: You can have multiple CSV files in the glossary folder (one per topic, brand, or domain). They are all loaded and merged automatically.

Frequently asked questions

Do I have to configure anything? No — setup is handled by your Jahia administrator (API keys, provider selection, glossary folder path). You just use the buttons.

Which AI provider is being used? Either DeepL or OpenAI, depending on your organisation's configuration. The experience is the same from jContent regardless of the provider.

Can I translate into multiple languages at once? From the page-level action you can trigger one target language per run. Run the action again and switch the UI language to translate into additional languages.

Will translation overwrite my existing content? For the Edit / Translate screen flow, suggested values are filled into the form but not saved until you click Save — you can discard any field you disagree with. For the page-level flow, the translation is applied directly. Make sure to review the result afterwards.

My glossary terms are not being applied — what should I check?

• Make sure the CSV file is saved in the correct folder.
• Make sure the column headers match the language codes used by your site.
• Ask your administrator to verify the glossary folder path in the module configuration.

1. In Jahia, go to Administration -> Server settings -> System components -> Modules.
2. Upload ai-assisted-translations-X.X.X.jar.
3. Ensure the module is started.
4. Update the file org.jahia.community.translation.assisted.cfg with the needed API keys
5. Activate the module on the websites where you want to use it.

MIT License

Copyright (c) 2022 - present Jahia

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.