View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
05834Bug reportsTranslationpublic2012-02-20 09:352012-03-11 16:35
Reportertacman1123 Assigned ToTMSWhite  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version1.92RC3 
Fixed in Version1.92 
Summary05834: Moving a Vietnamese Survey breaks character set
Description

The utf8 characters are not preserved when moving a Vietnamese survey.

Steps To Reproduce

Create a survey in Vietnamese.
Export the survey as a .lss file
Import the survey.
Compare the character sets.

TagsNo tags attached.
Attached Files
vi_only_bug.lss (27,023 bytes)
vi_import_overview.png (18,539 bytes)   
vi_import_overview.png (18,539 bytes)   
Bug heat4
Complete LimeSurvey version number (& build)155
I will donate to the project if issue is resolvedNo
Browser
Database type & versionmysql 5
Server OS (if known)all
Webserver software & version (if known)Apache 2.2
PHP Version5.3

Relationships

Relationship GraphDependency Graph
related to 05833 closedTMSWhite Non-english language surveys don't consistently publish 
related to 05827 closedc_schmitz Encoding problem at Label Set import (former: "Statistics Show Wrong Results") 

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2012-02-22 14:39

updater   ~17542

Last edited: 2012-02-22 15:12

There is another issue: After having imported the attached survey, parts (or everything and some strings are just not translated) of the admin interface switch to Vietnamese language (see attached screen shot).
Once you click the "go to this survey" link at the bottom of the import overview, the admin interface switches back to the correct language.

Update 1: This problem does not show up at LS 1.91 and 2.0alpha.

Update 2: The same language switch at the admin interface happens when activating a survey.
TMSWhite

TMSWhite

2012-02-22 22:36

reporter   ~17571

Is the character set within the sample survey correct? If not, sounds like export of UTF-8 surveys might also have trouble.

Also, if not, I have no way of comparing whether the load was correct, other than getting a database dump of the original survey.
Mazi

Mazi

2012-02-23 09:25

updater   ~17578

I opened the attached .LSS file in Notepad++ which tells me that the current encoding of that file is "UTF-8 without BOM" which looks correct to me.

Strings with special characters such as "Thông tin" are shown correctly at that file.
TMSWhite

TMSWhite

2012-02-23 15:12

reporter   ~17581

Imports work correctly in RC4 and RC5

Issue History

Date Modified Username Field Change
2012-02-20 09:35 tacman1123 New Issue
2012-02-20 09:35 tacman1123 File Added: vi_only_bug.lss
2012-02-21 16:44 Mazi Relationship added related to 05833
2012-02-22 14:37 Mazi Assigned To => TMSWhite
2012-02-22 14:37 Mazi Status new => assigned
2012-02-22 14:39 Mazi Note Added: 17542
2012-02-22 14:40 Mazi File Added: vi_import_overview.png
2012-02-22 14:45 Mazi Note Edited: 17542
2012-02-22 15:12 Mazi Note Edited: 17542
2012-02-22 15:25 Mazi Relationship added related to 05827
2012-02-22 22:36 TMSWhite Note Added: 17571
2012-02-23 09:25 Mazi Note Added: 17578
2012-02-23 15:12 TMSWhite Note Added: 17581
2012-02-23 15:12 TMSWhite Status assigned => resolved
2012-02-23 15:12 TMSWhite Fixed in Version => 1.92RC4
2012-02-23 15:12 TMSWhite Resolution open => fixed
2012-03-11 16:35 c_schmitz Status resolved => closed
2012-03-11 16:35 c_schmitz Fixed in Version 1.92RC4 => 1.92