[Shotwell] Bug fixes (Was: Shotwell - Thoughts on work-flow and extensions)

[Bruno Girin]

On Mon, 2010-05-31 at 10:45 -0700, Lucas Beeler wrote:
> Hi Bruno,
> 
>    The GNU gettext suite (see http://www.gnu.org/software/gettext/ for
> more information), provides the standard mechanism for
> internationalization support on Linux platforms and defines the PO
> file format. The suite contains about 15 command line tools, a dynamic
> library for runtime support, and headers and stub libraries for
> development. At Yorba, we've done a considerable amount of work to
> make the gettext tool suite work with the Vala language and to develop
> an internationalization workflow. What's more, we've done all of these
> things with the aim of the making internationalization as painless and
> transparent as possible for developers like you.
> 
>    Essentially, the only thing you need to do to as a developer to
> plug into the Yorba internationalization workflow is to enclose all of
> your translatable strings in gettext markup, which is simply an
> underscore and a pair of parentheses. For example, if you'd normally
> set the caption text of an on-screen widget by making a method call
> like:
> 
>     widget.set_caption_text("Publish");
> 
> you'd simply alter your code to look like:
> 
>     widget.set_caption_text(_("Publish"));

Yes, I did that, the string I use is properly enclosed in a _( ) call.


> 
> marking up the string "Publish" to let gettext know that it's
> translatable. The gettext suite then handles string extraction and POT
> template file generation automatically.

OK so does it mean I should re-generate the .pot file or will that be
done automatically once the patch is merged in? If I need to re-generate
it, is there a preferred command to use or a make target? I tried this
from the top level directory:

xgettext -d shotwell -p ./po src/*.vala

but I end up with too many differences between the original and the new
file for me to be confident that this is the correct way to do it.

Best regards,

Bruno