As not everybody will want to do that, generation of the index files is optional. This means that for quite a small amount of data (about 4MB) you’ll put a lot of junk on your hard drive (over 35000 files using about 150MB of space) – which in my opinion is neither elegant nor good style… but if Apple can do it, so can we. Unfortunately, Spotlight isn’t able to just index a whole database you throw at it, but to get meaningful information from it (in a documented way) requires you to use a single file for every character you want indexed. The latest step along this path is to provide a similar solution for Spotlight, which more people should be able to use. The next step was rough AppleScript support for that feature so we could integrate with applications like LaunchBar which gave us system wide access to Unicode characters by their name. By now, a similar feature is available in Apple’s character palette as well. Good for finding the checkmark character or ☃. The evolution of this is as follows: First there was the find sheet in UnicodeChecker which lets you find the Unicode character you’re interested in by its name. I’ve been nagging Steffen about this for… well, almost as long as Spotlight had been announced. The new version reads the Unicode data even more quickly and is reasonably fast when starting up with the huge Unihan file, and speedy even when starting up in its default setup. We already had significant speed improvements in the update to version 1.6, some of which vanished again in version 1.7 for people who installed the huge Unihan data file. The biggest universal change to Unicode Checker in this revision is once more its faster startup speed. I am very happy with what Steffen did in this version… partly because quite a few parts were positive responses to feature requests and nagging I did. Ranging all the way from significant speed improvements to the ability to abuse Spotlight on X.4 systems. And this update by a tenth of a version number has quite a few new and improved features in it. Re: 23.0.An updated version of UnicodeChecker is coming your way. Re: Fwd: Compilation mode does not properly handle MSFT Re: 23.0.60 describe-char gives wrong information,.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 6.Re: 23.0.60 describe-char gives wrong information, Kenichi Handa, 6.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 1.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 0.Re: 23.0.60 describe-char gives wrong information, Kenichi Handa, 0.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 8.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 5.Re: 23.0.60 describe-char gives wrong information, Kenichi Handa, 5.Re: 23.0.60 describe-char gives wrong information, Peter Dyballa, 4.Re: 23.0.60 describe-char gives wrong information, (continued). The GNU Emacs with PID 839 is running since a few days, the otherīehold the warranty. The character info returned looks also strange. With this enabled the HELLO looks a bit alien (left with font-īackend, in the middle GNU Emacs 23.0.60 from ten days ago, rightĪnd here is the start when the glyphs are not lined up correctly andĭo not seem to be the right ones (left window is from UnicodeChecker It's definitely the enabled font-backend that consumes so much CPU MUTT-ClearlyU-Medium-R-Normal-17-120-100-100-P-123-ISO10646-1Ĭharacter code properties are not shown: customize what to show Many open boxes appear, the size of the glyphs found Not configuring with font-backend seems to make GNU Emacs behave asįast as usual. I also installed a feature to use the specified font for all Re: 23.0.60 describe-char gives wrong information Re: 23.0.60 describe-char gives wrong information emacs-devel
0 Comments
Leave a Reply. |