We are migrating our Tridion platform from Tridion 2011 SP1 HR2 to Tridion 2013 SP1 HR1. The Content Delivery (Deployer, Web Service, etc...) is installed as a Java Web Application.
With Tridion 2011, we had to configure the Tomcat server with the following java parameter "-Dfile.encoding=UTF8" to make the deployer able to process UTF-8 encoded files during the publication (Chinese characters for ex).
But with Tridion 2013 SP1 it seems that the default encoding of Component Presentations in the Broker db has changed to UTF-16 (See Component Presentations in SQL 2012 DB shows up as a different encoding with 2013)
My question : Is this parameter still needed ? Do we have to update it to "UTF16" with Tridion 2013 SP1 ?
EDIT: Yes I know UTF8 is enough for Chinese or other languages. It was working well on our Tridion 2011 SP1 env and I know how to set the encoding on the publication target. My question is more linked to the migration it-self. When I have a look at CPs in the DB, "original" one's are still in a "readable" format. But those I've republished since Tridion 2013 migration are now in a "weird chinese like" format.