← Back to team overview

launchpad-translators team mailing list archive

Re: qshutdown release coming soon (1.6.4)


Hi Christian,

The French translation is (nearly) done.
(the .po is in the import queue)

Here are some tips for the next release...

- When you ask translators to translate an app, the relative app should be in a
kind of "string freeze". You should not change the .pot, except to fix typos.
This is to prevent translators to go mad when they notice that what they
translated yesterday no longer exist.

- You should avoid at any cost this kind of strings:

Because, you know what? There is (at least) a typo in it.
"configurationfile" should be "configuration file".
So, when you will correct this, translations of this whole and huge string will
be invalidated for all languages. I hope you see the problem...
(that's why I did not translate this string yet)

- Some strings are strange. For example:

Why couldn't you just use something like
"The file "%s" is not writeable"
(but, please, don't change it now. These kind of changes should be for the next
release, see my first point)

- I don't know if this is qshutdown-specific, but nothing is displayed when a
string is not translated. I mean, usually the English string is used when the
translation is not available. This is not the case in qshutdown: a blank is
displayed. So, because of this, you can't include nearly-done translations.
So there is a bug somewhere here...

About qshutdown iself:

A checkbox to set if another checkbox should be checked by default? Really?
Well, I'm not a designer but is this necessary? You could just save the last
state of the checkbox.

The same goes for the "Keep proportions" and the "Logfile" options in the
menubar. Put them in the settings, it should be enough.

More generally, the UI seems quite complicated for such a simple app...
(well, ok, this is out of topic ;))


Follow ups