Alejandro
WPML Supporter since 02/2018
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Rome (GMT+02:00)
|
Hello,
The retranslation was done again, but I just checked the engines available for the maltese language and I see only Google and Microsoft allow it, Meaning Deepl and PTC doesn't, thus, the glossary will not be applied to those languages.
Remember the glossary is only applied to languages that use DeepL and PTC alone (improvements for this specific notice UI is coming up, probably by mid october).
For other languages that do use DeepL and PTC, it should show the glossaries applied.
Regards,
|
Jasper
|
Hi Alejandro,
Sorry - I did not realize/remember this.
So if I understand correctly if I would use the PCT for this language it will use the glossary in Maltese?
|
Alejandro
WPML Supporter since 02/2018
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Rome (GMT+02:00)
|
If you use PTC or DeepL for the languages, the glossaries will be applied but Maltese is currently not available in neither of them, only in Google and Microsoft which currently do not accept Glossaries.
Regards,
|
Jasper
|
Understood… going manual 😊
|
Jasper
|
Hi Alejandro,
Thank you. I will look at the update and PTC shortly.
I have another question that I try to grasp/report.
During the checking of our Norwegian language we found that a word we use very often (500+) is often capitalized mid sentence.
I first checked if we used that word in our glossary, and this was the case. In the glossary the word was capitalized. I changed this because I thought this might deliver confusion with the (soon disappearing) 'name' column.
After that I had the system scan for updates. WPML went to work and found a lot of changes, including languages I did not change recently. What it did it a block box for me, so I am hoping nothing broke.
The whole process took about 24 hours to complete. However when I checked the original issue was still there.
I switched to manual and openend every occurrence in the ATE editor. I did not manually change the word but used automatic translation within the ATE editor. When I do this it correctly changes the capitalization of the word.
My question is why it does work correctly when using the ATE automatic translations. But not when I have the glossary scan? Or is this ignored and should I have retranslated the posts?
As mentioned earlier. I fixed this but I am trying to understand. I this is a issue you would like to investigate, I can give you a staging with a earlier backup.
Regards,
|
Jasper
|
Also I have jobs in progress that don't seem to finish. Even when I clear all jobs from the support page and resent them.
|
Alejandro
WPML Supporter since 02/2018
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Rome (GMT+02:00)
|
Hello,
Can you confirm you are in WPML 4.8.1 already? if not, please do so because we found some bugs about this while we were about to release V 4.8 that we fixed in version 4.8.1. there are still a few known issues about this that will probably be in 4.8.2 but those are still not confirmed.
However i'm confident the issues will go once you follow these steps:
- Update to version 4.8.1 and all the related versions for the add-on plugins
- Go to WPML > Support > Troubleshooting
- Almost at the end of the page there will be an option "cancel and retry all 'in progress' jobs"
- Click it
- Check if the jobs are either gone or appear as translated.
If they are still there, please check which jobs are in progress and for which language pair and send some of them to me so I can check if the problem is something technical like the file size or something similar.
---------------
About the first issue. would you kindly expand on "After that I had the system scan for updates", where did you do that? in theme and plugins localization (that's only for strings so I don't think that was it, right?) ? I actually think you meant the retranslate feature but that feature will likely not work for you because if the content is a lot, then it will definitely not make any change. We're working on a "global retranslation" feature which should address the issue that I believe you're mentioning and reapply the changes in the glossary entries.
Regards,
|
Jasper
|
I meant the 'update existing translations' under Glossary.
Anyway I will try to setup the update now on staging and see if this solves it.
t.b.c
|
Alejandro
WPML Supporter since 02/2018
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Rome (GMT+02:00)
|
Ok so it's the retranslate feature that you're talking about. That scan will only work for the last 2000 jobs sent in the last 30 days so it won't be applied to all of them.
The thing is that in your case you have many languages and that means that 1 page is more than one job since it's one for each language so 2000 jobs is not that many.
Plus If you have less than 2000 jobs sent in the last 30 days then it will be even less content that will have the glossary applied to.
That's what I mentioned that we're working on, because those features work better on smaller sites or sites without that many languages, at the moment.
Anyways, let me know what you get in the staging and I'll try to see how we can help you out.
|
Jasper
|
Morning Alejandro,
Oké thanks. Because of the behavior of WPML I mistakenly assumed the feature was all ready active.
I updated WPML after some tries. I needed to delete the plugin folders to achieve this. This worked and I pushed everything back to production. For now everything looks stable. I can test further when new input from my partners arrives.
Thank you.
|
Jasper
|
Hi Alejandro,
I will close this topic because the basic issues seem to be resolved. If I encounter a new one I will report back.
Thank you so much for your help.
Best regards
|
