Mantis Bugtracker 

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008076TestLinkExport/Importpublic2017-09-14 07:482017-09-14 07:48
Assigned To 
PlatformLinux on Virtual MachineOSLinux (Red Hat family)OS VersionRH5, CentOS 7.3
Product Version1.9.14 (2015 Q3) 
Fixed in Version 
Summary0008076: Wrong charset in export of custom fields
DescriptionExporting the custom fields in UTF-8 machines results in an ISO-nnnn-n declared XML file.

When the file is imported back into TestLink, non-ASCII characters (spanish tilded vocals, etc) are imported back incorrectly.
Steps To Reproduce1) Create a custom field named with non-ASCII characters (tilded vocals in our case).
2) Export custom fields.
3) Import the exported custom fields.

The non-ASCII characters are retrived incorrectly with other characters replacing the non-ASCII ones.
The original custom fields named with non-ASCII characters get a twin (duplicated) with almost the same name but different non-ASCII characters.
Additional InformationThis bug affects only export of custom fields:
Export of test cases and other items works well, generating UTF-8 encoded and so declared xml, and thus non-ASCII characters are retrieved correctly.

It only affects plain text fields:
Enriched text (HTML) fields encode these characters like in URLS (tilded A as "Á" a.s.o) and get retrieved correctly at import time.

Since 1.9.8 and still in 1.9.16.
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL, but most probably irrelevant.
BrowserMozilla's FireFox and Microsoft's Internet Explorer. Most probably irrelevant.
PHP Version5.4 with TestLink 1.9.8 and 7.0 with TestLink 1.9.16.
QA Team - Task Workflow Status
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-09-14 07:48 izubiaurre New Issue

Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker