Not strictly a Tridion problem I know, but I'm reaching out to those who might have experience with encoding problems and SI4T.


Basically my Spanish text is appearing in Elasticsearch as double-encoded - I'm using the JEST library to index my documents and every log I've looked at my text looks ok.

The impact is I have to convert the UTF-8 text before rendering it back out. I just can't track down where its being double encoded.

1 Answer 1


You mention in your comment on stackoverflow that the JEST client log shows everything correctly. This tells us that the sending side has it right before firing off the request with the data. So this leaves the http request itself (perhaps the client has an encoding setting?) and the encoding config on the receiving side.

Take a snoop at the Request data being sent across the network via a tool like Fiddler and see if it is double-encoded. If it is, then it's the sending side that is packaging the data into the request that's doing it. Otherwise, there has to be some encoding mismatch on the ElasticSearch side. So look at the search configs there and also the settings of the web server that hosts the engine.

  • Any tips on how to get Fiddler picking up networks made by Java as part of the deployer process?
    – Neil
    Jan 26, 2015 at 16:17
  • 1
    It's just a proxy. It shouldn't matter whether Java or other technology. You point the Deployer's JRE to the machine running Fiddler so Fiddler can sniff out the network packets. Here is a link to the docs: JRE settings for Java: docs.telerik.com/fiddler/Configure-Fiddler/Tasks/… Jan 26, 2015 at 20:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.