View Issue Details

Related ChangesetsJump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
09266Bug reportsTranslationpublic2014-09-30 08:412014-10-20 13:49
Reporteranurag Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.05+ 
Fixed in Version2.05+ 
Summary09266: Chinese and Japanese characters support in case of MS SQL Server
Description

Limesurvey has this peculiar issue with SQL Server databases. When Chinese or Japanese language is added to a survey, upon saving basic information, questions or answers, the characters are not stored properly in database and displayed in a funny way (see attachment) when a user opens the survey.

This has been the case since, at least, v1.92+ where I fixed the issue by converting many text/varchar columns in database into their N-datatypes (Nvarchar, Ntext, etc.) for getting Unicode support. I also had to "hack" a lot of core files and replace datatypes to match the N-datatypes.

Now we have upgraded to v2.05, but the issue still exists. We cannot imagine doing all that dirty hacking all over again. Is there an easy way to get Limesurvey plus SQL Server to support Chinese/Japanese characters?

Steps To Reproduce
  1. Create a survey in English.
  2. Add an additional language, say Japanese.
  3. Populate Survey Basic Properties for Japanese.
  4. Create a few questions with both English and Japanese text.
  5. Test the survey.
  6. Japanese characters appear like random ASCII characters (screenshot attached), for both basic survey info (welcome text, instructions, etc.), and question text.
TagsNo tags attached.
Attached Files
ScreenShot2014-09-29at3.17.08pm.png (239,026 bytes)
Bug heat6
Complete LimeSurvey version number (& build)Build 148011
I will donate to the project if issue is resolvedNo
BrowserAll
Database type & versionSQL Server 2008 R2
Server OS (if known)Windows Server 2008
Webserver software & version (if known)IIS 7.5
PHP VersionPHP 5.4

Users monitoring this issue

anurag

Activities

c_schmitz

c_schmitz

2014-10-14 00:06

administrator   ~30791

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14560
c_schmitz

c_schmitz

2014-10-14 00:10

administrator   ~30792

For the patch to work you will need to re-create your LimeSurvey database using the LimeSurvey installer with this patch applied. Don't re-use an existing database. The problem is that certain columns in the database need to be created as nvarchar instead of varchar in the MSSQL tables. There is no easy way to convert existing columns, so a re-install is necessary. Please give feedback how it worked out.
anurag

anurag

2014-10-14 06:44

reporter   ~30795

Wow! Thanks. I will try and come back with how it goes.

Btw, is there an easy way to export/import Limesurvey DB data? We have a 500 MB (and growing) database :p
c_schmitz

c_schmitz

2014-10-14 21:30

administrator   ~30797

Sorry, no experience with that - usually with MSSQL it is more complicated than with other DBs.
c_schmitz

c_schmitz

2014-10-20 13:49

administrator   ~30826

Version 2.05+ Build 141020 released

Related Changesets

LimeSurvey: master 1e883c5b

2014-10-13 22:06:18

c_schmitz

Details Diff 		Fixed issue 09266: Chinese and Japanese characters not suppoerted when using MS SQL Server Affected Issues
09266
mod - application/helpers/admin/activate_helper.php Diff File
mod - application/helpers/admin/token_helper.php Diff File
mod - installer/sql/create-mssql.sql Diff File

Issue History

Date Modified Username Field Change
2014-09-30 08:41 anurag New Issue
2014-09-30 08:41 anurag File Added: ScreenShot2014-09-29at3.17.08pm.png
2014-09-30 08:45 anurag Issue Monitored: anurag
2014-10-13 23:08 c_schmitz Assigned To => c_schmitz
2014-10-13 23:08 c_schmitz Status new => assigned
2014-10-14 00:06 c_schmitz Changeset attached => LimeSurvey master 1e883c5b
2014-10-14 00:06 c_schmitz Note Added: 30791
2014-10-14 00:06 c_schmitz Resolution open => fixed
2014-10-14 00:10 c_schmitz Note Added: 30792
2014-10-14 00:10 c_schmitz Status assigned => feedback
2014-10-14 06:44 anurag Note Added: 30795
2014-10-14 06:44 anurag Status feedback => assigned
2014-10-14 21:30 c_schmitz Note Added: 30797
2014-10-14 21:30 c_schmitz Status assigned => resolved
2014-10-14 21:30 c_schmitz Fixed in Version => 2.05+
2014-10-20 13:49 c_schmitz Note Added: 30826
2014-10-20 13:49 c_schmitz Status resolved => closed
2021-08-02 19:35 guest Bug heat 4 => 6