The result is that I need to re-request all the translations in order to make a new, and stable, but localized version of iShowU.
I’ll be putting up some help (another movie!) on this shortly, but I intend to use Localization Manager (click the image to visit the site that provides the tool) to manage the process. This will allow me to maintain an English version of the UI, plus a number of translation files. I can simply give the translation files to the translators, who use the wonderful Localizer (part of the suite) to edit them. The nice translator people then send them back to me, and I merge the whole lot back to create the end result.
Amazing, great,
wonderful. Cool.
I’ll be posting something on the forum when
I’m ready to proceed.

Here’s the result so far! This release
(1.1a) contains :
* A funky new level meter,
* Presets
* A slight (but unfortunately not perfect) fix for
the sprite black cursor problem.
* Quite importantly - I’ve fixed the jumpy
capture that sometimes occurred when using larger
capture rectangles.
CoreData is actually OK. Coming from a Java/Hibernate
background, it’s a little odd, but I think if
you put on the ‘it’s Apple, do it their
way and it should work’ hat, then it does work
well. Having to manually override an object so that
you can have statically typed accessors is a bit of a
pain (and really, I do want those when using these
object within code and not via bindings). Overall
I’m pleased with the result. Would I use them
again? Yes, I think so, now that I’m more
familiar with management of the object life cycles.
I’ve still to work out a nice way to share
managed object contexts across nib files, but
I’ve only worked with CoreData about 3 days, so
I shouldn’t expect too much of myself just yet.
Go to the downloads page to get the 1.1a
build.