TotalFinder 0.9.5 is here. This release added localization support and a few fixes.
Translate TotalFinder and get a free license
I’m pretty sure that you understand that translation must be an ongoing process. TotalFinder will be getting new features over time and of course I want to be free to tweak and possibly change anything. I don’t want to spend my time swapping text files in emails and micro-managing translators. Instead I want to focus on TotalFinder improvements and features. That’s why I’m looking for a good solution to this localization problem.
You know that already, the guys behind the GitHub are my rock stars. Quite frankly, if I were a young lady I would want to have babies with all of them.
Ehmm, all right, I’m a big believer in the GitHub concept. The transparency it offers when looking at versioning and collaboration is breath-taking. I didn’t even announce localization support here on the blog and some folks already ‘got it’ and have forked my repo. I understand that not everyone is familiar with git and other tools I’m forcing you into, but if you are a techie I guarantee you learning git and GitHub is damn well invested time. Take it as a good opportunity to learn something new. Now you have a reason and my full support.
For your information, this is my experience when collecting localizations, easy as pie! :-)
Please look at this repo and read the instructions: http://github.com/binaryage/totalfinder-i18n
I will be improving those instructions over time by answering your actual questions. There is a sample Czech translation. All I needed to provide was translations of several string files.
Headaches solved with switching exotic keyboard layouts
Some Asian guys got into big troubles when they updated to 0.9.3. Switching complex keyboard layouts might cause the whole Mac to hang for a few seconds.
This wasn’t quite my bug but some hidden problem in the ShortcutRecorder library. All has been solved now and the world is better by one patch.
My fight for pixel perfection
You might remember that I slaughtered the Google Chrome codebase and extracted the tabs implementation out of it. Some pixels got lost during this dirty process and some eagle-eyed UI designers are poking me to fix it (thanks Steve!).
Now I’m slowly learning how rendering the tabs really works and trying to tame Cocoa rendering on the pixel level. This version made pretty good progress on this.
Other news is that Google is (probably!) planning a slightly different tab look in an upcoming version. It looks gorgeous in my opinion. TotalFinder will definitely keep up and I want to know every pixel by name.
Also one of the most requested features is Safari-style tabs. I hear you! I will put these newly acquired skills towards this ultimate goal (sometime after the 1.0 release).