Asked by:
Problem of using Microsoft.VisualBasic.Strings.StrConv() to convert Chinese

Question
All replies
-
I use Microsoft.VisualBasic.Strings.StrConv() to convert traditional Chinese to simplified Chinese. I found a error conversion.
瞭 should be converted to 瞭. But it's converted to 了.
Your problem is in my perception comprehensive described in the documentation on MSDN
https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.strings.strconv(v=vs.110).aspx
Success
Cor- Edited by Cor Ligthert Friday, March 24, 2017 12:00 PM
-
I use Microsoft.VisualBasic.Strings.StrConv() to convert traditional Chinese to simplified Chinese. I found a error conversion.
瞭 should be converted to 瞭. But it's converted to 了.
Your problem is in my perception comprehensive described in the documentation on MSDN
https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.strings.strconv(v=vs.110).aspx
Success
Cor
-
There is stated:
The constants VbStrConv.Wide, VbStrConv.Narrow, VbStrConv.SimplifiedChinese, VbStrConv.TraditionalChinese, VbStrConv.Katakana, and VbStrConv.Hiragana can cause run-time errors when used in locales where they do not apply
Probably only local Chinese persons can help you. I see the Chinese MSFT's passes always questions as it is about Chinese, I don't know why.
However, you can try to do this. You have yourself to find the correct parameters (like in English en-US) for those Chinese culture dependend languages.
http://www.vb-tips.com/Cultures_Simple_Example.aspx
I won't say it helps, but in your case I would give it a try with all possibilities.
Success
Cor -
Hi niexuchina,
I have try to serval methods to convert 瞭 to 瞭, but I fail. I saw that some people said 瞭 is the 了 traditional Chinese, so it is converted to 了.
Best Regards,
Cherry Bu
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.- Proposed as answer by Cor Ligthert Monday, March 27, 2017 10:46 AM