Community
Participate
Working Groups
Build Identifier: It would be really helpful to have the possibility to export the tests as UTF-8 encoded XML instead of UTF-16. 2 Options: 1. make UTF-8 the default encoding and/or 2. provide a choice in the export dialog to select the desired encoding. Reproducible: Always Steps to Reproduce: 1. export your tests to xml 2. check the encoding 3. it's UTF-16
Agreed - I am about to implement option 1 with backwards compatibility for 'old' UTF-16 encoded project files.
The necessary modifications have been made with changeset http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=29770fa5c157db3b24e777674fb2db793ebc5445 From now on all newly written project XML files should be encoded with UTF-8 (see [1]) which should in most cases significantly reduce the file size for exported project XML files as well as significantly increase the interoperability of those files with other tools / platforms / OS. [1] http://en.wikipedia.org/wiki/UTF-8
Fix verified. I tested this issue by exporting a project with GD 7.0 and checked its encoding with PSPad which says that this UTF8 encoded. Also the content is written in one long string without any breaks. I crosschecked this by exporting a project using GD 6.1 and opened this one again with PSPad and this time the encoding was displayed as UTF16 BE and included breaks. I imported this UTF16 encoded project using GD 7.0 and was able to open it to check if it is backwards compatible. Closing this ticket.
