[Sparkle] development and localization

[Jonas Witt]

It would fall back to en.lproj/file or file if <locale>.lproj/file is
not *existant* at all. If it exists, however, NSBundle will locate it
and NSNib will try to load it and then it doesn't structurally match
what the code expects (from the english nib) - I don't think there's a
fallback in that case since NSNib doesn't actually fail to load the
nib. On solution would be to remove all non-english files until they
are completely localized (have some kind of english-only target in
XCode).

Jonas


On Thu, May 8, 2008 at 7:47 PM, Andy Matuschak <andy at andymatuschak.org> wrote:
> But I'm a little confused about ticket 190. Why doesn't it just fall back to
> the English NIB? Am I missing something about how the NSBundle APIs work?