This article was published on Sunday, June 01st, 2008 at 10:05 am.
For those wonderful prospective localizers, you should know that I’ve actually already changed a few strings since 1.5b1 (doh!). One of my localizers pointed out some flaws.
Anyway, here’s a new English strings file and test app to use to test with: Sparkle 1.5b1 Localization Pack.
I may need to update things some more if there are more problems; I’ll update this entry if that happens. Alternately, you can keep abreast of changes in a much easier (for me, at least) way using Bazaar.
Hi there. I'm Andy Matuschak, a computer science student at Caltech, but a software engineer at heart. I'm a long-time Cocoa programmer and a user experience nutcase and all that—you can read about what I've done or what I'm working on elsewhere.
I do have an untechy side, too. I'm a singer first and foremost, a passable pianist, and a okay-maybe-needs-more-experience actor. I love to teach. I love to write. But most of all, I'm quite helplessly in love with life.
Questions? Comments? Feel free to reach me by email or by AIM. I'll do my best to get back to you rapidly, but Caltech is a cruel mistress.
If you're looking for something specific then give the search form below a try:
The Conversation {4 comments}
A quick note: The en.lproj in the source contains some extra .string files that were probably left there by someone. Since these are copies of what needs to be translated in the nibs and you should check the layout anyway, you better just ignore them.
I’m talking about these: SUUpdateAlert.strings, SUAutomaticUpdateAlert.strings and SUStatus.strings
You DO need to translate Sparkle.strings though.
Cheers,
Maarten (Dutch localizer)
I think you should make it a priority to get out a Sparkle with a working GC version. As you know, the current GC one wasn’t compiled for GC.
In fact, why do you even need two versions? If you enable GC it should work for GC and non-GC shouldn’t it?
If you get the latest from bzr, GC works. There do have to be two versions (not 100%, but fairly sure) because supporting GC involves a bunch of calls like objc_assign_pointer which don’t exist on 10.4-.
Building with GC on Leopard has three possible settings. Required, supported, and not-supported. Required means that the codes requires GC, supported means that it uses retain/release but doesn’t rely on it so much that GC won’t work.
I’m not aware of unique calls needed to make it support GC.
A reference doc is http://developer.apple.com/documentation/Cocoa/Conceptual/GarbageCollection/Articles/gcEssentials.html
Leave a Comment
You can follow any responses to this entry via its RSS comments feed. You can also leave a trackback if the inclination is there.