Does anyone have a tutorial to create a role that can support any country whose language is not an NPC name?
Does anyone have a tutorial to create a role that can support any country whose langu
03/26/2019 17:52
mobai520#1
03/26/2019 22:07
xTwiLightx#2
One thread is enough, seriously.
Change all Neides columns (m_szName and m_szGuild to name the most important) to support any unicode characters (utf-16 support) - that means nvarchar and a proper collation.
Change all variables in stored procedures that affect those columns to also support all unicode characters - so nvarchar. Also the N' prefix has to be used when nvarchar values are inserted/updated to nvarchar columns.
I guess that UNICODE has to be defined so that those characters are properly handled in the code. It could be that some changes in the CQuery class have to be made, but I could be wrong.
Also, the proper codepage has to be set in all files (UTF-16 Little Endian [1200] might be the right one).
Change all Neides columns (m_szName and m_szGuild to name the most important) to support any unicode characters (utf-16 support) - that means nvarchar and a proper collation.
Change all variables in stored procedures that affect those columns to also support all unicode characters - so nvarchar. Also the N' prefix has to be used when nvarchar values are inserted/updated to nvarchar columns.
I guess that UNICODE has to be defined so that those characters are properly handled in the code. It could be that some changes in the CQuery class have to be made, but I could be wrong.
Also, the proper codepage has to be set in all files (UTF-16 Little Endian [1200] might be the right one).
03/28/2019 14:45
mobai520#3
I can't do it, have you tried itQuote:
One thread is enough, seriously.
Change all Neides columns (m_szName and m_szGuild to name the most important) to support any unicode characters (utf-16 support) - that means nvarchar and a proper collation.
Change all variables in stored procedures that affect those columns to also support all unicode characters - so nvarchar. Also the N' prefix has to be used when nvarchar values are inserted/updated to nvarchar columns.
I guess that UNICODE has to be defined so that those characters are properly handled in the code. It could be that some changes in the CQuery class have to be made, but I could be wrong.
Also, the proper codepage has to be set in all files (UTF-16 Little Endian [1200] might be the right one).
I can add you Discord, can you give me a try?
03/30/2019 23:41
xTwiLightx#4
Since I am not using any asian language in any kind: No - I haven't tried it.Quote:
I can add you Discord, can you give me a try?
I am not interested on any contact - this board is for sharing information.
If you can't do that work, then you'd better learn it or leave it. If you're really looking for help in supporting asian languages, you should better be looking on other websites that are consisting of non-latin members. This community consists of people that speak english, german, french and spanish. There will be no one really helping you when it's about foreign languages like chinese.
03/31/2019 12:25
mobai520#5
Thank you, but I can't find other websites.Quote:
I am not interested on any contact - this board is for sharing information.
If you can't do that work, then you'd better learn it or leave it. If you're really looking for help in supporting asian languages, you should better be looking on other websites that are consisting of non-latin members. This community consists of people that speak english, german, french and spanish. There will be no one really helping you when it's about foreign languages like chinese.