[ https://jira.jboss.org/jira/browse/JBPORTAL-2163?page=com.atlassian.jira.... ] Sohil Shah commented on JBPORTAL-2163: -------------------------------------- So I have researched this a lot and bottomline is, Java treats ZipEntries as UTF-8 names and international characters are treated just fine. However, the Zip Spec and hence thirdparty archiving tools don't see eye-to-eye on this issue. Not all tools treat Zip Entry names in UTF-8 mode. Hence, an archive produced by a Java Program with international characters seems like the characters have been garbaged, when in fact its the third party unzipper that is not processing international characters properly. This cannot be helped by the Java Program like our CMS that produced the archive. This is an interoperability issue here is a decent more detailed explanation of this issue: http://www.oreillynet.com/xml/blog/2008/03/reaping_what_you_sow_how_a_sta... Hence, for interoperability, you need to make sure CMS resource names don't contain international characters if you want the Export feature to produce archives that play nicely with their thirdparty archiving tools Stressing that its just the resource *names* that should not contain international characters. The content with international characters is fine. In fact if the content cannot be internationalized, that would suck real real bad ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira