Did any one used translation implementation in AEM 6.1. I came across some sort of limitation.
In most of the cases composite multi field dialog implementations create data in JSON formats inside properties (there are widgets which can store data in nodes and properties). Especially composite multi fields. When we generate XML using AEM 6.1 translation we will get JSON strings as is in the XML output. Translation rules also not applied if the data is stored as JSON. Did any one solved this by extending or overriding translation framework.Is there any enhancement around this?