Is there a database to store posts in any national language?

Quote:

Originally Posted by Nιgнтмαяε Why do you keep making the same post over and over with different topic names? No one is going to help you convert the shit to Chinese.

Quote:

Originally Posted by ディオニュソス Delete all databases - > recreate them using a Chinese collation -> change your applications codepages to a Chinese one. Thats most likely all you have to do

Quote:

Originally Posted by xTwiLightx He wants to support multiple languages, so only changing the collation won't do the trick. Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made): [Only registered and activated users can see links. Click Here To Register...] As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode. When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

Quote:

Originally Posted by ディオニュソス Delete all databases - > recreate them using a Chinese collation -> change your applications codepages to a Chinese one. Thats most likely all you have to do

Quote:

Originally Posted by xTwiLightx He wants to support multiple languages, so only changing the collation won't do the trick. Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made): [Only registered and activated users can see links. Click Here To Register...] As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode. When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

Quote:

Originally Posted by ディオニュソス I very much doubt that's what he wants, all he wants is store chinese characters, he just has his speech upped to 100 so nobody understands him unless they have reached the same level of eloquence.

Quote:

Originally Posted by xTwiLightx He wants to support multiple languages, so only changing the collation won't do the trick. Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made): [Only registered and activated users can see links. Click Here To Register...] As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode. When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

Quote:

Originally Posted by ディオニュソス I very much doubt that's what he wants, all he wants is store chinese characters, he just has his speech upped to 100 so nobody understands him unless they have reached the same level of eloquence.

Quote:

Originally Posted by mobai520 [Only registered and activated users can see links. Click Here To Register...] This is the name I created in Chinese, click on it and click here.

select * from sys.fn_helpcollations()
where [name] like 'Chinese%'

Quote:

Originally Posted by xTwiLightx The thread title even says "ANY national lanuage" :thinking: If you just want chinese, go on and set the collation to a chinese one on database or server level and re-create the databases. To see what collations are available on your server, execute the following query: Code: select * from sys.fn_helpcollations() where [name] like 'Chinese%' For me, the results look like that: [Only registered and activated users can see links. Click Here To Register...] See what fits your requirements, the collation is mainly for the sort order of characters. But that could be different for a complex language like chinese. Set your codepage everywhere to the one used for chinese - see [Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by mobai520 Thank you, the main thing is that I won't [Only registered and activated users can see links. Click Here To Register...] [Only registered and activated users can see links. Click Here To Register...] Use this to use this

Quote:

Originally Posted by xTwiLightx Our results don't have to be the same - you have to decide what collation you need. I am not into the chinese language, so you'll have to go trough that list and choose the one that fits your requirements. After that, you can check this site which covers a few scenarios when changing the collation: [Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by xTwiLightx It seems you'll have to re-create the database and execute the scripts to create the tables and procedures after that.

Quote:

Originally Posted by mobai520 It should be re-established. Can you help me? Thank you.