I have another example of glossary terms being placed in the wrong spot in the sentence.
It's on this page: hidden link
This time the issue only happens with the German translation and not with the English translation.
Here is a Screen recording: hidden link
In this video I also mention two other issues:
1) I prefer bigger segments keeps on getting enabled automatically. I had disabled that when I made the previous screen recording, but today it was enabled again. One of your colleagues has said before that when you disable it, it will remain disabled for that site and all other sites that are connected to the same credits account. But that doesn't seem to be the case. It looks like I have to disable it all the time over and over again.
» is this a bug?
» why is this setting in the ATE and not in the plugin settings? I mean, if you don't want bigger segments, it needs to be disabled before translation. That's impossible now, because once you go to the ATE it starts translating immediately. Same if you have automatic translation enabled.
» shall I create a separate ticket for that?
2) Date & time format. The is a British/European format (day, month, year, 24h clock) is different from the American format (month, day, year, 12 clock am/pm). DeepL supports both, but WPML always assumes American English, even when the local is set to en_GB.
» already reported before.
Also, saving of #tag and mailto: segments is still not fixed.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
1)
One of your colleagues has said before that when you disable it, it will remain disabled for that site and all other sites that are connected to the same credits account.
They will be disabled for that site, not all the other sites. However, this applies to the new jobs, not the old ones.
These are the steps to keep it disabled:
- Open a new job in ATE (so send it from WPML > Translation Management)
- Now disable the bigger segments through the settings.
- Save the changes on the page, click complete, etc.
- Now send another page to translation as you did with this previous job.
- It should appear with the shorter segments.
The entire workflow is being refined, so it's possible that eventually you'll have a global setting option (that's not possible at the moment). When the page is translated automatically for the first time, you can "undo" the changes, so you can then switch the settings as you like.
2) For the mailto and #tag, if they are translated in the same way, meaning that you're copying it, then yes it's not saved on the next job. that is already fixed in our staging site but it's not deployed to production. that applies to links as well. if the problem is a bit different, then please let me know the URL where I could see the Issue or the ticket where you reported it in the past so I can investigate further.
Do you have a page with the formatting issue you mention? please share the URL so I can ask our devs about it.
1) It's actually better to have that setting per site, although I believe it should be in the plugin settings so you can specify what you want before something is sent to translation, instead of translate as big sentence by default, then undo, change setting and retranslate.
2) ok, I just mentioned it again because you expected it to be released around the 15th.
3) this page hidden link
Zet deze data alvast in je agenda:
📅 Opening nieuw Steakhuis: 28 februari 2025
📅 Grand opening Drinkhuis: 30 januari 2025
-- hidden link
Please mark these dates in your calendar:
Opening new Steakhouse: Feb. 28, 2025
Grand opening Drinkhouse: Jan. 30, 2025
* just noticed it didn't pick up the emoji with the 'Translate Everything Automatically - active' setting. When I edit the translation and click the [Translate automatically] button, it does add it though (I just did that with English, but if you check German the emoji are still missing).
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
I asked our Devs about all these issues and they told me they will look into the dates situation, however it's a holiday season so things are a bit slow.
The emoji issue is already known and will be fixed soon in one of our next deployments.
