Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
@è严 å¨ 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 ;-)