Field-level translations not recommended for content using PortableText in Sanity.io

Hello! I am reading that the

field-level translations

is not recommended for content using

PortableText

. Has anyone tried / knows why this is the case?Source:
https://www.sanity.io/plugins/document-internationalization

That would be because it creates a massive number of attributes and will cause you issues as you generate content.

Thanks , so would it then follow that if a majority of a project’s components include the need for Rich Text with Portable Text, document level translation is really the best/only way forward?

Correct. I’d only ever use field level translation if there were one or two fields needing translation. Document level is the way to go.

Always helpful to get it validated from the source, thanks so much !

You’re very welcome!

Hopefully a quick follow up — is there a way to provide documents for translation to a third party? I was reading about the Transifex plugin (my client uses TransPerfect so this won’t work).

Yes, but we don’t currently have a plugin for TransPerfect. You could take a look at the existing plugins and use them as guidance for building out your own, though.

Got it — so by plugin only, at the moment?

You could also create a document action or anything that sends the JSON of a document to whatever service you’re using. Your service would need to to be configured to write content back to your dataset as well.

Ahh right right. THANK YOU! Appreciate your time.