Merge lp:~dpm/quickshot/enable-translations into lp:quickshot

Note that for Quickshot for be properly translatable constructions of this kind should be avoided:

                self.usersetup.label.set_label(''.join((
                 "<b>Save all your work</b> and click the \"Login\" button to ",
                 "logout and login to this new user to start taking ",
                 "screenshots or, if you want to begin at a later time, ",
                 "click \"Close\".",
                )))

That's just one of the several examples in bin/quickshot. For translators to be able to do their work, these strings should be not truncated (and then they should be surrounded by _() to make them translatable).

This looks good to me, thanks a lot dpm!

Thank you for your patch, David.

However, the entire GUI design is set for a rebuild, now that we know what works and what doesn't (a three-week development cycle kinda leads to lots of kludges, like using .join() as a compromise between having super-long strings and developer-side readability). As such, we'll be able to avoid inconsistencies in how we define strings and where we store literal data in the codebase (it'll be a highly modular design, with an emphasis on making it easy to find the right code to change to alter behaviour).

Unfortunately, your contribution likely won't be preserved as we move forward, since we're tearing things down to do them right, but we will be certain to study what you have changed and apply your enhancements throughout every new piece of code that we write.

When we're ready to begin accepting translations in a couple of months, we would greatly appreciate your input on anything we can do better with the new infrastructure, to make the process as easy as possible for would-be contributors.

El dt 18 de 05 de 2010 a les 20:05 +0000, en/na Neil Tallim va escriure:
> Thank you for your patch, David.
>
> However, the entire GUI design is set for a rebuild, now that we know
> what works and what doesn't (a three-week development cycle kinda
> leads to lots of kludges, like using .join() as a compromise between
> having super-long strings and developer-side readability). As such,
> we'll be able to avoid inconsistencies in how we define strings and
> where we store literal data in the codebase (it'll be a highly modular
> design, with an emphasis on making it easy to find the right code to
> change to alter behaviour).
>
> Unfortunately, your contribution likely won't be preserved as we move
> forward, since we're tearing things down to do them right, but we will
> be certain to study what you have changed and apply your enhancements
> throughout every new piece of code that we write.
>

That's absolutely fine. However, the basic steps for a localizable
application will remain:

* Initialize gettext (the bindtextdomain stuff)
* Mark strings for translation (generally surrounding them with _() or
using ngettext for plurals)

> When we're ready to begin accepting translations in a couple of
> months, we would greatly appreciate your input on anything we can do
> better with the new infrastructure, to make the process as easy as
> possible for would-be contributors.

Sure, feel free to ping me any time and I'll be glad to help in what I
can.

--
David Planella
Ubuntu Translations Coordinator
david(dot)planella(at)ubuntu(dot)com
www.ubuntu.com