Thank you very much for taking on the glossary issues.
I published a new article on June 5 hidden link
I also added the new glossary entries that are referenced in this Support issue on the same day. The issues are described below and also in the screenshot, hidden link
1. 'Quick WO' in the glossary, but not recognised correctly.
2. 'Quick IDT' in the glossary (similar type of wording), which is recognised correctly
3. 'Stages' in the glossary, but not recognised; instead, auto-translation shows in the article. I used the ATE to correct this content.
Please let me know if you require additional information.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
A few questions about this:
1) when did you add the glossary? Before sending the job to translate or after (but before actually translating it)
2) did you translate this page automatically without accessing the editor at all?
3) if you create a new page with a different text containing the glossary term, does it work in that new page?
See, if you had translated a segment containing the phrase or term from the glossary, then the glossary term would not be applied since it would be using the translation from the translation memory, thus, would not search the entry for any glossary entries
Thank you for responding. Here is the sequence of steps that I followed:
1. Created the article in English hidden link
2. Updated the glossary with correct translations
3. Ran the article through automatic translation
4. Viewed the ATE when I noticed certain glossary entries were not recognised correctly
Could the issue be that WPML is not recognising the variation of a glossary entry? For example, in earlier articles, 'WO' is recognised correctly as 'OR'. In the latest article, we need to use an entry, 'Quick WO'. WPML only recognises 'WO' and shows the translation as 'Quick OR'. The correct translation in the glossary for 'Quick WO' is 'OR Rapide'.
I created another test article and tried a variation of wording around the topic of 'Quick WO'. It is still incorrectly recognised. hidden link
Please let me know if this helps clarify the issue.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hi there! i'm running a few tests on my own, because what you mentioned used to be a bg but was fixed a while ago. i'll let you know as soon as i have more info.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Interesting, i'm not sure why is it happening with this specific glossary entry, because i tested it with another 2 ("house" and "my nice house") and it worked correctly then.
I have tested them both here: hidden link
and you can play around with it if you want too.
However, i asked our developers to take a look at this one because i suspect this could be some sort of edge case or untested scenario.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
This is indeed a bug and is already being taken care of. We are actually updating a few things about the glossary on our end and for this issue to be fixed, we first have to implement another internal feature for the glossary that is being in the works already.
We don't have a workaround for it at the moment but it won't happen to all the glossary terms, only the ones that contain 2 entries: a partial one and a constructed one from the partial entry, it will always take the one starting with the "highest" letter or character ( WO will be used instead of Quick WO because "W" comes later on the alphabet than "Q" from Quick).
I'll keep you updated on the development of this issue.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
- The ticket will remain open so we can let you know when this happens. i can't give you an ETA because before this ticket can be fixed another few things need to be done on our site (we're doing a major technical overhaul to the glossary and we have been doing this for a while already, so i guess we're nearly there, though).
- If you will only use the special characters, then it's likely you may run into problems but in very specific scenarios, not all the time, however they are permitted. please note, though that sometimes your write a single quote and wordpress could try to encode it, so for the system there could be 2 different types of single quotes and that means that you may not be able to see the content correctly picked up and translated from the glossary.
I can delete the translation memory of the staging site, that's not a problem but please know you will lose the translation of the ENTIRE SITE, for all the languages if we do so. at the same time that will not return the credits used
if you want to delete the translation memory for specific pages, let us know which ones and we can do that instead 🙂
Do you have any updates/estimated completion date on the revisions to the glossary? We are preparing to go live with our French translations and want to do our planning with the WPML updates in mind.
Also, I have a quick question. Is there any mechanism in WPML to flag certain phrases/words that the automatic translations bypass? In other words, we want to keep the English text untranslated, e.g. field names in the database (there are a large number).
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
It seems the fix for this was in the process of being addressed but it's still not in production yet. i asked our devs about a possible ETA and i'll let you know as soon as they get back to me.
About the mechanism you mention, there isn't anything like that and i'm not sure it's a "simple" feature request, but i'll ask our devs if it could be considered.
The entire glossary feature is about to have a few major changes so features for them are not going to be developed soon (but they could still be accepted for a future development cycle).
