-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple issues with fields #51
Comments
Hi @NoSync thanks for raising these issues.
This is something we have to look in to. My first thought is that it has probably something to do with the maximum number of characters that can be translated. Can you share a specific use case where the text is not translated correctly?
This could maybe be solved by adding a translation context for chatGPT. See #44. Feel free to make a PR for that.
This issue is actually a known but really difficult issue. We don't have direct access to metadata of a field and therefore we have no context of what that field is, which type or which settings it has. This is certainly an issue we can look into, but is not that easily solved. Feel free to help, we hope to get some of the issues fixed in the future! |
gpt-4o in all cases. Whenever there are carriage returns fields are consistently not translated, regardless of the type of field and number of characters.
Indeed I added some more instructions to the local fork I use (alongside "just translate the text 1 to 1, never add any explanations") and the issue disappeared. #44 is probably a better solution though. Thank you. |
I'm currently testing out the plugin on a couple projects, and I ran into a few issues:
The text was updated successfully, but these errors were encountered: