


For those who import Classifications with Chinese/Japanese/Korean characters in the “Key” column, how do you do so?
This is what I did:
After waiting for 2 days, my Chinese keys are still unclassified :weary:
When I export my classifications again — even with “<Default>” encoding, I can see that my Chinese keys have the expected English classifications.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Ouch... I haven't had to deal with those types of characters.. but that sounds horrible that the rules aren't working for you...
It sounds like the export is converting to UTF-16 but when the rules are re-imported, they go back to UTF-8?
Have you tried getting client care to open a ticket with the engineering team? This sounds like it might be a rather large issue / lack of support for the asian customers.....
Views
Replies
Total Likes
Hello, it needs to be UTF-8 with no BOM character encoding.
I can confirm this as I have worked with Korean customers.
Always good to have someone with real-world experience! 🙂
Views
Replies
Total Likes