It's all about the answers!

Ask a question

[closed] RQM - Can encoding of CSV file be changed? Broken Double byte character issue

DH Lee (25784446) | asked May 27 '13, 1:24 a.m.
closed Dec 17 '16, 2:13 p.m. by Ralph Schoon (63.3k33646)
I am working with customer who is experiencing broken double byte character issue when CSV file is generated from Test case list. Customer had been creating test cases using JKE Banking project.

I attempted to replicate customer's issue in similar environment, however I could not reproduce customer's garbled double byte issue.

Below is environment used
- Windows Server 2008 R2 local locale
- CLM 4.0.1
- JKE Banking project
- FF 13.0.1, IE 8, Chrome

I had customer change charset for generated CSV file, then customer did not see any broken double byte character issue. Initially CSV file was usign UTF-8 encoding.

My question is
- "Is it possible to change charset of CSV file so double byte characters are not broken in UTF-8 encoding format?"
- Alternatively, is there any preventive process to avoid double byte character issue?

The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Dec 17 '16, 2:13 p.m.

Accepted answer

permanent link
Paul Slauenwhite (8.4k12) | answered May 28 '13, 11:05 a.m.
The encoding of the exported CSV file is UTF-8 and cannot be changed.  I would suggest open a PMR since this appears to be a product defect.
Ralph Schoon selected this answer as the correct answer

One other answer

permanent link
Setembrino Lusa (514) | answered Dec 16 '16, 12:58 p.m.
 @paules Hi, see my question here