The issue is fixed permanently in WorldServer 11.3.3.
There are 2 workarounds for earlier versions:
- change tomcat's server.xml file. Add URIEncoding="ISO-8859-1" as follows (make sure you restart WorldServer after this change):
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"
URIEncoding="ISO-8859-1"/>
If you are using the
SSL protocol, make sure to add it to the corresponding connector as well, where the port can be either 443 or the default tomcat 8443. Here is an example:
<Connector
protocol="org.apache.coyote.http11.Http11NioProtocol"
port="443" maxThreads="200"
URIEncoding="ISO-8859-1"
scheme="https" secure="true" SSLEnabled="true"
keystoreFile="C:\keystore\ssl-sdl-test-2018-2019.pfx" keystorePass="nopasswd"
clientAuth="false" sslProtocol="TLS"/>
- or set the strict servlet complicance property. See reference page on the Tomcat Apache page.
The
server.xml file can be found on the server where WorldServer is installed and under this directory:
<WS_Home>\ tomcat\conf\ server.xml
If you cannot apply the solution about, the current workaround is to rename the file name to avoid these special characters
Ü
Ä
ß
Ó
òinclined apostrophe such as
’ .Example: "I’m a file.txt". This could be renamed using a strainght apostrophe such as
' instead.
To be able to download file despite the error using Chrome (it might work also with Firefox):
- find the file in the target folder in Explorer
- right click on it and select View
- the download of the file will start. The file is slightly renamed which is why it can be downloaded.
- save the file locally and open it in its native application to check that it is translated.
