[ http://issues.apache.org/jira/browse/BEEHIVE-1032?page=comments#action_12361255 ]
Jin Kudo commented on BEEHIVE-1032: ----------------------------------- "Use platform encoding" is not good solution. There are many cases to use different encoding between platform encoding (or file encoding) and request encoding. And current testrecorde xml file are defined as UTF-8, so it causes to change it to this encoding. And generally XML file should be UTF-8 encoding. So the better solution is the data should not convert to unicode string and compare the data as binary. But in case of this test tool, xml format file is used as the data storage, so it should use base64 encoding and so on for store the binary data to xml file. So possible solutions are follows. Current: Use ISO-8859-1 encoding. Cannot use any out of ISO-8859-1 encoding characters. Solution 1: Use UTF-8 encoding. The request encoding have to be UTF-8 encoding. The test recorder xml file are defined as UTF-8, so the xml file always readable xml file. Solution 2: Test Recorder encode the data using base64 without character set conversion and store it to xml file. > TestRecorder handle request encoding > ------------------------------------ > > Key: BEEHIVE-1032 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1032 > Project: Beehive > Type: Test > Components: NetUI > Versions: V1 > Reporter: Jin Kudo > > Currently the test recorder always handle the request encoding as ISO-8859-1. > That is cause to none ASCII characters can't be stored in the recording data > file correctly. Request encoding determination is not so easy, but I suggest > as the reasonable solution testrecorder use the platform encoding as request > encoding rather than fixed ISO-8859-1 value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
