We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
Look at my profile name. It's time for globalization, add support for text encoding decoding methods, add official tutorials for dealing with text encodings, and possibly fix the database encoding (such as UTF-8 ).
@è严 å¨ I've got information that the issue was fixed and the user's name should be fixed the next time they log on. Could you please log on to Ideas Portal to check that your username is ok now? We tested this approach with several other users, and it works ok now. Please let me know if your user's name doesn't encode correctly.
Support for UTF8 4 bytes is a must in IRIS. Currently it's impossible to store an emoticon in IRIS as a character. When a user enters a text in a form containing an emoticon, it's fun to find the cause of the error is an emoticon ;-)
@è严 å¨ I've got information that the issue was fixed and the user's name should be fixed the next time they log on. Could you please log on to Ideas Portal to check that your username is ok now? We tested this approach with several other users, and it works ok now. Please let me know if your user's name doesn't encode correctly.
Ward, I can store emoticon in my IRIS:
USER>set ^x = $WC(128053,32,128584,32,128585,32,128586)
USER>zw ^x
^x="🐵 🙈 🙉 🙊"
USER>zzdump ^x
0000: D83D DC35 0020 D83D DE48 0020 D83D DE49 🐵 🙈 🙉
0008: 0020 D83D DE4A 🙊
Support for UTF8 4 bytes is a must in IRIS. Currently it's impossible to store an emoticon in IRIS as a character. When a user enters a text in a form containing an emoticon, it's fun to find the cause of the error is an emoticon ;-)