| Summary: | Transmission of special characters like Umlaute | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Sebastian von Klinski <sebastian.vonklinski> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | ||||||
| Version: | 2.0 | ||||||
| Target Milestone: | 2.0 M3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sebastian von Klinski
Change priority to P1 as this is a regression. I don't see any encoding issues. Can you reproduce it, Ivan? Created attachment 223040 [details]
Snippet to reproduce it
Yes. I can. The "source" text field contains cyrilic characters. Add some more text to it and hit copy button. The text into the "target" text field contains garbage.
The problem is in the ProtocolUtil#getClientMessage where the request input stream is read without encoding. Fixed with commit cf0f49f428749b4ed0d9e82ff802246746311074. |