I confirm the main issue has now been resolved. I have switched all my products to use the advanced translation editor and the glossary is now being applied properly.
However, we have run into another issue. Are you able to please advise on this urgently?
*The issue now is a certain phrase has random capitalization. How can we fis this?
The glossary entry is translated as: cored wire > arame tubular
See example:
1. hidden link VS
2. hidden link
- See attached screenshot. According to the client, this should have been 'A'rame 'T'ubular para 'R'evestimento.
*The same applies to all the products..the capitalization of this phrase is inconsistent.
Please advise.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Hi,
I see you mentioned an attached screenshot, but I don’t see it on our side — could you please resend it?
Just to clarify what we currently see in the translation editor: the glossary entry is set as “cored wire” → “arame tubular” (lowercase), and it is being applied consistently wherever that term appears. The editor inserts the glossary term exactly as defined, while the overall capitalization of the sentence follows the source text. hidden link
On the pages we’re viewing, both the English and Portuguese versions are displayed in sentence case, so the Portuguese rendering matches what we would expect from the glossary setup.
If you’re seeing different capitalization on your side, a screenshot and the exact page URL will help us confirm whether this is coming from a different content field, template, or cached version.
1. See screenshot of en.png based on: hidden link
VS.
See screenshot of pt-br.png based on: hidden link
2. The correct translation should be "Arame tubular para revestimento".
Example:
See HARDFACE BUF-S on the pt-br.png screenshot which is capitalized correctly (Arame tubular para revestimento)
VS.
HARDFACE BUF-S on the pt-br.png screenshot which is capitalized incorrectly (arame tubular para Revestimento)
Just an additional note on this Capitalization issue to please investigate it on Translations/Glossary Translations as whole, not just this one phrase. This one phrase is the only one we have picked up for now.
So, we are just trying to ensure we don't have a similar issue now or in future.
Could you please provide an urgent update on the progress of this ticket. The client is waiting to finalise the translations on their site, and this issue is now holding up the completion of all other language translations.
Your prompt feedback would be greatly appreciated as this has become time-sensitive.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
We checked this internally with our 2nd-tier support and the ATE (advanced translation editor) team, and based on their review, this behavior appears to be expected.
What’s happening is related to how the AI handles capitalization within the context of a full sentence. In the original source content, the term appears at the beginning of a sentence and is therefore capitalized (“Cored wire”). To preserve natural sentence structure in Portuguese, the AI applies the same capitalization and outputs “Arame tubular.”
If the glossary term were enforced strictly in lowercase (“arame tubular”) at the start of a sentence, it could look inconsistent or unnatural in Portuguese. Because of this, the AI applies contextual capitalization while still respecting the glossary term itself.
Based on what we’re seeing and the discussion with the ATE team, this is expected behavior rather than an issue with glossary application.
Please let us know if you’d like us to explore any configuration or workaround options.
The issue you have just explained is exactly what's happening (The natural sentence structure is NOT being preserved - it is random. Sometimes it is Sentence case, sometimes it is lower case):
-In the beginning of the sentence, in EN, I have Sentence case: Cored wire but sometimes it is Arame tubular, other times it is arame tubular. See example below:
hidden link vs hidden link
Can you please assist with the following:
1. Ensure a Sentence always starts with Sentence case, preserving the language structure as you have mentioned. *This will solve the first issue.
2. We have additional logical issues we need to flag. It might be possible to tweak this based on the configurations you have avialable. Can you please create a separate ticket for "Logical Glossary Translations"? AND if possible, can we do this over a LIVE call, where we are able to share screen and explain the issues exactly?
