Empty fields in nested content - Translation manager v2.2.3
Is there a setting to avoid sending empty fields for translation in the Translation settings or Set?
Fields within nested content are being sent for translation even though they are empty.
Also, is there a way to exclude specific Leblender grid content properties from being sent for translation?
I think at the moment blank values will be sent if they are nested inside another property editor (e.g a value inside a LeBlender field)
Mainly because for some things (for example in the Grid) the ordering of the values can be critical. Not sending a blank item could change how things serialized back in and you could end up with items in different places on your target language.
In terms of excluding specific types, we have had this on the list for a while, but it can get quite complex especially in how the settings are made and stored.
If you know exactly what you want you can hook into the events generated by Translation Manager and remove properties from the translated value
This will fire whenever a translated node is created and you could reach in and get change the values you want to remove.
your other option (depending on what the field in LeBlender is) would be to create a custom property editor that then wouldn't be recognised by translation manager and wouldn't go into the final translation.
Empty fields in nested content - Translation manager v2.2.3
Is there a setting to avoid sending empty fields for translation in the Translation settings or Set? Fields within nested content are being sent for translation even though they are empty.
Also, is there a way to exclude specific Leblender grid content properties from being sent for translation?
Using Translation Manager 2.2.3
Thanks!
Hi,
I think at the moment blank values will be sent if they are nested inside another property editor (e.g a value inside a LeBlender field)
Mainly because for some things (for example in the Grid) the ordering of the values can be critical. Not sending a blank item could change how things serialized back in and you could end up with items in different places on your target language.
In terms of excluding specific types, we have had this on the list for a while, but it can get quite complex especially in how the settings are made and stored.
If you know exactly what you want you can hook into the events generated by Translation Manager and remove properties from the translated value
This will fire whenever a translated node is created and you could reach in and get change the values you want to remove.
your other option (depending on what the field in LeBlender is) would be to create a custom property editor that then wouldn't be recognised by translation manager and wouldn't go into the final translation.
Thanks for the quick response again!
is working on a reply...