Multiple issues with fields

[NoSync]

I'm currently testing out the plugin on a couple projects, and I ran into a few issues:

• Some fields are not completely translated. In particular, when a field contains multiple paragraphs separated by two carriage returns, only the first paragraph is translated.
• Sometimes the output doesn't contain the plain translation, but begins with "It can be translated with" and similar terms. I am using gpt-4o, for reference.
• Some read-only fields are sometimes also translated, which is very odd. In this example, Box type is translated, which breaks the website:

[velomovies]

Hi @NoSync thanks for raising these issues.

Some fields are not completely translated. In particular, when a field contains multiple paragraphs separated by two carriage returns, only the first paragraph is translated.

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? What fields are you using, what translation service and which text?

Sometimes the output doesn't contain the plain translation, but begins with "It can be translated with" and similar terms. I am using gpt-4o, for reference.

This could maybe be solved by adding a translation context for chatGPT. See https://github.com/voorhoede/datocms-plugin-translate-fields/issues/44. Feel free to make a PR for that.

Some read-only fields are sometimes also translated, which is very odd. In this example, Box type is translated, which breaks the website

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!

[NoSync]

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? What fields are you using, what translation service and which text?

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.

This could maybe be solved by adding a translation context for chatGPT. See #44. Feel free to make a PR for that.

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.