This also occurs if someone answers in Japanese. So the results are not usable :(

Have you used the language before with this installation of LimeSurvey?
Or is this the first time you use Japanese characters in this LimeSurvey installation?

Did I get it right. The Umfragetitel is always shown correctly? Any other fields, which are showing the correct content after saving the form?

Apache and PHP are running on Windows, right?

No it was the first time we tried Japanese characters.
The survey title works fine, the questions are also shown in Japanese correctly.
But if I save the fields mentioned above and if someone answers the questions and I check the answers I see a lot of "?"

Maybe some probem with mssql? I had no chance to test it with mysql, sorry :(

Can you check what admin theme is set? Configuration -> Themes -> Admin themes.

There is a admin theme
"Default LimeSurvey admin interface template with NOTO font. NOTO font is will provide a correct display for any existing language."

To me it looks more like an issue which LS only has when interacting with MS SQL.
But would be nice if you could try the NOTO theme with a few browsers and check if you sense a difference.

I will try.
Default installation of V 2.62.2 is working on the same database

No change when switching to the NOTO default template.

Version 2.62.2+170203 is working perfect in the same database. Even with the SeaGreen template. Maybe this helps.

markus, I'd like your point of view on this problem

anything I could do to help here?

still nothing? I searched a lot, compared it with 2.62.2 but I did not find the solution :(

Surely related to DB (MS SQL Server 2016) and maybe Server OS (Windows Server 2012 R2 64Bit)

We already use nvarchar and ntext for MSSQL :https://stackoverflow.com/a/22955415/2239406

About the "how to find when this issue happen"
With a working 2.62 version, update to a https://github.com/LimeSurvey/LimeSurvey/releases/tag/2.72.3%2B171020 and see if you have same issue.
If yes, come back to 2.62 and go to https://github.com/LimeSurvey/LimeSurvey/releases/tag/2.63.0%2B170304 , if OK : https://github.com/LimeSurvey/LimeSurvey/releases/tag/2.63.1%2B170305 etc …

Until find the broken release.

Hi, and thanks for the reply.
Currently we are using 3.13 and the issue appears. In the database I see that the data is stored in 'text', not in ntext

Just to clarify: I should set up a secound system again (2.62) and upgrade it step by step? Then I will try it :)

Can not reproduce on 3.15.5 version on Windows server 2016 (IIS) + php 7.2.9 + sqlsrv + msodbcsql17.dll + SQLServer 12.00.5590
With firefox on windows

I will try this asap :)

stil the same :(

japanese.png (60,928 bytes)

It is working in 2.27.3, but not in 3.x

Difference I found in application\core\db\MssqlSchema,php
beginning from line 50 it is different between ls version 2. and 3.
could it be, that there is something wrong? I'm honest, I did not take a deeper look yet

Both versions have the line: $this->columnTypes['text'] = 'nvarchar(max)';
But in 3.X the columns are still created as text and not as nvarchar

This part : https://github.com/LimeSurvey/LimeSurvey/blob/master/application/core/db/MssqlSchema.php#L50-L66

Here is the same function used in 2.73 : https://github.com/SondagesPro/LimeSurvey-SondagesPro/blob/2.73/framework/db/schema/CDbSchema.php#L371-L383

It's seems to update ONLY for pk, then in think it's a difference in your MSSQL server

hmm true. Can't find a difference.

I'm using the same databse for the two versions, also the same settings.

Is the database collation the same?
Typically Limesurvey tries to use UTF8 as much as possible.

@markusfluer : mssql issue somewhere
It's the reason of nvarchar : https://www.mssqltips.com/sqlservertip/4322/sql-server-differences-of-char-nchar-varchar-and-nvarchar-data-types/

And this line : https://github.com/LimeSurvey/LimeSurvey/blob/b96ff7cba0ecff5b80a912f762903bc12c6c4ce0/application/core/db/MssqlSchema.php#L19 or https://github.com/LimeSurvey/LimeSurvey/blob/b96ff7cba0ecff5b80a912f762903bc12c6c4ce0/application/core/db/MssqlSchema.php#L11

@markusfluer everything is the same but the LS Version, and the table prefix, lime26 and lime3, so there shouldn't be the problem.

it is a MS SQL Server 2012, can't change it in the Bug report