Comments on: Quick Note on Sparkle 1.5b1 Localizations

By: David M

David M — Fri, 20 Jun 2008 04:40:56 +0000

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

By: Andy Matuschak

Andy Matuschak — Wed, 18 Jun 2008 04:13:37 +0000

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-.

By: Chris

Chris — Wed, 18 Jun 2008 01:41:53 +0000

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?

By: Maarten Van Coile

Maarten Van Coile — Mon, 02 Jun 2008 15:23:09 +0000

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)