You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After creating a glossary and running a test translation, the glossary entry provided was partially translated and the source entry is sometimes included in the translation.
To Reproduce
Steps to reproduce the behavior:
I have created a glossary from EN to DE
I have added some entries to test the functionality
Results as seen in the screenshot below are not sticking to the terms set in the glossary.
This is the code I'm calling the translations with:
Expected behavior
I'm uncertain if I misunderstood how glossaries work, but I thought they would always take precedence over default translations. Also, the source language string should never show up in the translation.
The text was updated successfully, but these errors were encountered:
I have experienced the same behaviour and just tried with a normal fetch with the same test glossary_id of a glossary I created. It seems to be related to the package as the vanilla fetch call behaves as expected with the glossary.
As a workaround for now the vanilla fetch call will have to suffice.
Describe the bug
After creating a glossary and running a test translation, the glossary entry provided was partially translated and the source entry is sometimes included in the translation.
To Reproduce
Steps to reproduce the behavior:
This is the code I'm calling the translations with:
Expected behavior
I'm uncertain if I misunderstood how glossaries work, but I thought they would always take precedence over default translations. Also, the source language string should never show up in the translation.
The text was updated successfully, but these errors were encountered: