Service Desk Practitioners Forum
cancel

sun.io.CharToByteUTF8

Highlighted
Sergey Kalinin
Contributor.

sun.io.CharToByteUTF8

Hi.
There was a problem of interaction of post program "WebMail" and Service Desk 4.5
It was tested on SP20 and SP30
This post system sends letters strictly in coding UTF-8.
Service Desk accepts the references created by means of given post system, all is good... BUT if to send the letter with an investment named in Russian, problems here begin...

Servicecall it is successfully created, but with an investment named, for example "content.msword" instead of the "Russian text.doc"
here log part:

Чт, 02/07/2009 12:48:16 Characterset: windows-1251

Чт, 02/07/2009 12:48:20 Ended parsing duration: 10953 ms

Чт, 02/07/2009 13:01:59 Started parsing E-mail

Чт, 02/07/2009 13:01:59 Converter class not found (sun.io.CharToByteUTF8)

Continuing without characterset conversion.

Чт, 02/07/2009 13:01:59 Attachments: [(content.msword : C:\Program Files\Hewlett-Packard\OpenView\service desk 4.5\server\tmp\28-content.msword!#! : application/msword;charset=UTF-8;name=ТерриториР.doc)]


How to force Service Desk to understand investments in Russian in coding UTF-8?

Any decision is welcomed!