110 words
on
earthlingsoft
Thanks to Steffen’s efforts – there’s finally an update to the codepoint geek’s favourite UnicodeChecker again!
The update includes support for Unicode 7 as well as a powerful advanced search window:
Little improvements I particularly like are those to the Utility window’s Split Up tool. It will now display each codepoint’s offset in the string and display each selected codepoint to the main window.
To keep up with Apple’s pace in backwards incompatibility and style, support for OS X versions older than X.7 has been dropped and the icon has been flattened. In addition to that, Growl support has been removed in favour of OS X’s Notification Center.
Enjoy!
February 19, 2015, 0:17
Tagged as
earthlingsoft, UnicodeChecker.
Nice job indeed, the new search feature seems very interesting.
However there are some glitches.
In the Unicode point list on the left the font is not aliased and the appearance is very poor.
It’s impossible to download the Unihan files; the dialog box that appears at the first start is stuck and doesn’t answer requests. The same happens when the “Download and install Unihan data” is chosen. Whether I click on “Cancel” or “Move to Trash”, the dialog box is stuck and the only way out is quitting the application.
February 19, 2015, 17:27
You guys rock! As a programmer working with text, this has been an incredibly useful tool over the years. Thank you.
February 24, 2015, 2:00
You should release a version with updated Sparkle:
http://arstechnica.com/security/2016/02/huge-number-of-mac-apps-vulnerable-to-hijacking-and-a-fix-is-elusive/
The app is wonderful, thank you very much.
March 7, 2016, 19:12
Would it be possible to include in the information for a symbol what Alt keystroke would produce that character, if any do? I suspect that this is different for different keyboards, so might be difficult prospect. But it would be a nice addition.
April 5, 2017, 19:05
Thanks for the suggestion Bitt.
As you guess this seems to be a tricky issue. Personally I wouldn’t even know how to determine the specific key combination needed with a user’s current keyboard layout. (And seeing that even Apple’s own character palette does not seem to provide this information, makes me think it may not even be possible to do this properly.)
April 5, 2017, 23:28
