View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
03547Bug reportsOtherpublic2009-08-09 00:55
Reporteruser4494Assigned Touser372 
PrioritynormalSeverityminor 
Status closedResolutionduplicate 
Product Version1.85 
Summary03547: Single quotes in description/welcome/end message
Description

As described in bug <a href="http://bugs.limesurvey.org/view.php?id=3385">3385</a> it is not possible to use single quotes in the description/welcome/end message of a survey.

I'm trying to do a survey in French. As in French language single quotes are very common (grammatically even necessary), it is almost impossible to write reasonable texts without them. Thus it would be good to have a way to write descriptions and welcome/goodbye texts even WITH single quotes.

Unluckily I'm not programmer at all, so I have no idea on how to deal with this, and since it is not really a bug, I thought I'd just submit this as a feature request.

Simon

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)
I will donate to the project if issue is resolved
Browser
Database type & version
Server OS (if known)
Webserver software & version (if known)
PHP Version

Users monitoring this issue

There are no users monitoring this issue.

Activities

user372

2009-08-08 18:33

  ~09061

Last edited: 2009-08-08 18:33

Please upgrade to the latest stable plus version ==> LimeSurvey 1.85+ build 7394 ==> IMHO all these problems have already been fixed ==> if NOT, please attach a sample survey (survey structure as .csv-file), where we can reproduce the issue - THX!

If all youor problems are resolved at the latest version, please leave a short note too!

user4494

2009-08-09 00:50

  ~09062

I've installed limesurvey via Simplescript, so if I install a newer version, I brake the possibility to easy upgrade.

I can not upload a cvs file since the problem prevents the creation of a survey. But if you can create a survey and put the sentence "mieux cerner les besoins d'un Hub" in the "description" field, and it works, then the problem is indeed solved in the newer version.

user372

2009-08-09 00:55

  ~09063

Tested with your example sentence ==> everyathing is working fine ==> problem has already been fixed in v1.85+

Issue History

Date Modified Username Field Change
2009-08-08 13:14 user4494 New Issue
2009-08-08 18:30 user372 Project @2@ => Bug reports
2009-08-08 18:31 user372 Status new => assigned
2009-08-08 18:31 user372 Assigned To => user372
2009-08-08 18:33 user372 Note Added: 09061
2009-08-08 18:33 user372 Note Edited: 09061
2009-08-08 18:33 user372 Status assigned => feedback
2009-08-09 00:50 user4494 Note Added: 09062
2009-08-09 00:55 user372 Note Added: 09063
2009-08-09 00:55 user372 Status feedback => closed
2009-08-09 00:55 user372 Resolution open => duplicate
2010-05-06 10:26 c_schmitz Category Data entry (non-public) => (No Category)