We have reported multiple issues with the glossary. We were informed about a patch update from WPML and re-tested the issues we found. Subash Chandra Poutel was handling the ticket titled Glossary Issues with German Site.
Subash closed the ticket, so I am submitting a new one with the remaining issues described below. Screenshots and links to articles are included.
Issue 1 - French article – “Important” in the Heading block is not translated (see screenshot). hidden link hidden link
Issue 2 – German article – Words next to glossary entries are dropped. This a NEW issue that should be escalated to second-tier Support/Development. Two examples are highlighted in the screenshot. hidden link hidden link
Issue 3 – Space added when the glossary entry is at the end of the sentence. This is a NEW issue that should be escalated to second-tier Support/Development. Two examples are highlighted in the screenshot. hidden link hidden link
Issue 4 - Glossary entry not recognised in H2 block. You can see that ‘Purchase Orders’ is in the glossary and is correctly translated in the Paragraph block. The screenshot shows this. The article link is also included. hidden link hidden link
Please let me know if you need additional information
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
1) does this segment has a glossary? it doesn't seem that way. it seems here that in another page you had the same segment translated as "important" so it took the value and added it from the translation memory.
2) There are limitations in the glossary based on semantics and words structures. if you have a glossary entry for "management" and one for "content management", then the glossary will pick up the shorter one, not the entire one as a glossary entry and that is not a bug (technically), there's always a decision that the system needs to make and it takes the shorter version because it's statisctically more likely to be used than the long one.
The solution would be to remove the glossary entries that are too shot in favor of longer terms.
3) Can you see if this happens on other languages as well? we've had similar issues and they are really not coming from our end, but from translation engines based on rules they have on specific languages grammar. we've seen this quite often in German and French. are you also using the translation engines to translate this content, by any chance?
4) I'll check this one out and send it to our developers. it's happening only on heading blocks and it happens with any term from a glossary that belongs to a gutenberg native H tag paragraph, correct? or does it only happen with "Purchase Orders"?
For Issue 2, words not in the glossary are dropped in the translation when they are next to a word in the glossary. This is happening for German only. I included examples above showing this.
For issue 3, the extra space at the end of a sentence happens for German and French when there is a glossary entry at the end of a sentence.
The issues with heading blocks occur intermittently where the glossary entry is not recognised. In most cases, glossary entries in heading blocks are recognised.
Please let me know if you need additional information.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Thank you very much, i'm trying to recreate the problem from scratch with the help of a developer (from this and the other ticket) and i'll get back to you as soon as we have a way to fix them.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
I haven't forgotten you. i'm still running a few tests to see if we can find a solution for at least some of the issues you have and i'm also documenting everything for our devs.
