Hi,
I have an output that has Chinese characters but when I write back to sql (generate a new table
MSSQL_ADO) the characters are lost. The data comes from SQL and FME handles the characters correctly up to the point the writer is used any suggestions? Thanks.
Best answer by lenaatsafe
Hi @denby
you have Chinese characters in attribute values (not in attribute names), am I correct?
Is your SQL Server default language English? You can check this through Microsoft SQL Server Management Studio > Server Properties > Advanced > Default Language. You can set the default language to Chinese (either Simplified or Traditional) and this will probably fix the problem. However, this is not the easiest option.
You are probably writing the Chinese values into char or varchar columns. Both - char and varchar - support values in server default language encoding (which should be Win-1252 in case of English). Instead of char/varchar you can use nchar/nvarchar that by default store Unicode values - this should solve the problem without affecting all your SQL Server databases/users.
+19
+19works fine on English characters as I have processed various countries?
In fact, there are potential issues on internationalization. I've experienced many issues on Japanese characters, reported everything to Safe support, and many have been resolved but there still are outstanding issues unfortunately.
+43Is it attribute names or values? Names are always a bit harder to do, and I would recommend updating to the latest FME version if necessary (you don't say which you are using).
As Takashi says, this is probably one to take up with our support team. I did a quick look for existing reports and can't find any, so either it should work, or no-one has ever asked for this before. I suspect it should work, but the ADO writer might be different. Could you try the JDBC non-spatial writer to see if the result is the same? Or maybe even try the Spatial version, just ignoring geometry.
Sorry I can't be much more help but I hope either a different writer or the support team will be able to get you going
Hi @denby
you have Chinese characters in attribute values (not in attribute names), am I correct?
Is your SQL Server default language English? You can check this through Microsoft SQL Server Management Studio > Server Properties > Advanced > Default Language. You can set the default language to Chinese (either Simplified or Traditional) and this will probably fix the problem. However, this is not the easiest option.
You are probably writing the Chinese values into char or varchar columns. Both - char and varchar - support values in server default language encoding (which should be Win-1252 in case of English). Instead of char/varchar you can use nchar/nvarchar that by default store Unicode values - this should solve the problem without affecting all your SQL Server databases/users.
Hi @denby
you have Chinese characters in attribute values (not in attribute names), am I correct?
Is your SQL Server default language English? You can check this through Microsoft SQL Server Management Studio > Server Properties > Advanced > Default Language. You can set the default language to Chinese (either Simplified or Traditional) and this will probably fix the problem. However, this is not the easiest option.
You are probably writing the Chinese values into char or varchar columns. Both - char and varchar - support values in server default language encoding (which should be Win-1252 in case of English). Instead of char/varchar you can use nchar/nvarchar that by default store Unicode values - this should solve the problem without affecting all your SQL Server databases/users.
Great thankyou, its fixed using nvarchar instead of varchar
+43Hi @denby
you have Chinese characters in attribute values (not in attribute names), am I correct?
Is your SQL Server default language English? You can check this through Microsoft SQL Server Management Studio > Server Properties > Advanced > Default Language. You can set the default language to Chinese (either Simplified or Traditional) and this will probably fix the problem. However, this is not the easiest option.
You are probably writing the Chinese values into char or varchar columns. Both - char and varchar - support values in server default language encoding (which should be Win-1252 in case of English). Instead of char/varchar you can use nchar/nvarchar that by default store Unicode values - this should solve the problem without affecting all your SQL Server databases/users.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
