RSS/Atom feed Twitter
Site is read-only, email is disabled

autogen.sh [Was: Updating POT's]

This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

7 of 7 messages available
Toggle history

Please log in to manage your subscriptions.

Updating POT's julien 27 Dec 08:34
Updating POT's Ulf-D. Ehlert 28 Dec 12:09
  Updating POT's julien 28 Dec 17:57
   Updating POT's Ulf-D. Ehlert 28 Dec 21:07
    Updating POT's Marco Ciampa 29 Dec 03:05
     Updating POT's Ulf-D. Ehlert 29 Dec 18:09
    autogen.sh [Was: Updating POT's] Ulf-D. Ehlert 31 Dec 12:27
julien
2008-12-27 08:34:54 UTC (over 16 years ago)

Updating POT's

Hi Ulf,

I saw that you can update the english part of every languages po at the same time. How do you do that?
It seems that no "fuzzy" comment is created. I can do this for one language with msgmerge, getting "fuzzy" comments.

Probably I cant use your method to update to v2.6 and translators will have to use msmerge on every po file before translating.

All the best,

Julien

Ulf-D. Ehlert
2008-12-28 12:09:03 UTC (over 16 years ago)

Updating POT's

Hi Julien,

julien (Samstag, 27. Dezember 2008, 08:34):

I saw that you can update the english part of every languages po at the same time. How do you do that?

I edited the orginal multi-lang files causing problems and applied the migrate script to those files.

It seems that no "fuzzy" comment is created.

xml2po produces no "fuzzy" comments when initializing po files.

I can do this for one language with msgmerge, getting "fuzzy" comments.

Why did you use "msgmerge"? Everything should be done with "make".

Probably I cant use your method to update to v2.6 and translators will have to use msmerge on every po file before translating.

If you have an old patch which has to be applied to the old multi-lang files, you can mail it to me and I try to integrate it.

Otherwise you just have to commit the changed src files and the updated French po files. The remaining po files should be updated by the respective translators.

Bye,
Ulf

julien
2008-12-28 17:57:52 UTC (over 16 years ago)

Updating POT's

Hi,

I can do this for one language with msgmerge, getting "fuzzy" comments.

Why did you use "msgmerge"? Everything should be done with "make".

Because I didn't know that Makefile was done for that. I opened the Makefile (Why Make and Makefile.GNU?) but I don't understand it.
Do I must do a ./autogen.sh or a ./configure before using it? Please give an example: the menus/edit-cut.xml is updated. I want to create (update?) the POT file and the po/fr/edit-cut.po file. How can I do that with "make"?

Cheers,

Julien

Ulf-D. Ehlert
2008-12-28 21:07:51 UTC (over 16 years ago)

Updating POT's

Hi,

julien (Sonntag, 28. Dezember 2008, 17:57): [...]

Why Make and Makefile.GNU?

[...]

The default build system uses autoconf and automake. You have to run "autogen.sh" once and then later configure (this is also done automatically by autogen.sh), e.g. to set ALL_LINGUAS.

The (default) Makefile is generated by "configure". This is the same as before, except that the Makefile targets and/or commands had to be changed, of course.

"Makefile.GNU" is meant to be used without any autogen or configure scripts (maybe a very simple configure script later). I still think we don't need the autotools (autoconf, automake, configure.ac, Makefile.am, autogen.sh) and just started to try it...

For now, both Makfile and Makefile.GNU should behave the same. Ok, sometimes I use Makefile.GNU for testing - e.g. try make -f Makefile.GNU status-fr

Do I must do a ./autogen.sh or a ./configure before using it?

Yes, run ./autogen.sh [--without-gimp] [LINGUAS="en fr"] to initialize the default build system.
Note that you have to re-run autogen.sh if you install new software like "dblatex" or "docbook2odf" -- using Makefile.GNU this shouldn't be necessary.

Please give an example: the menus/edit-cut.xml is updated. I want to create (update?) the POT file and the po/fr/edit-cut.po file. How can I do that with "make"?

make po/fr/edit-cut.po (or make po-fr).

Bye, Ulf

Marco Ciampa
2008-12-29 03:05:28 UTC (over 16 years ago)

Updating POT's

On Sun, Dec 28, 2008 at 09:07:51PM +0100, Ulf-D. Ehlert wrote:

Yes, run ./autogen.sh [--without-gimp] [LINGUAS="en fr"] to initialize

^^^^^^^^
I think you meant:

./autogen.sh [--without-gimp] [ALL_LINGUAS="en fr"]

or

export ALL_LINGUAS="en fr"

./autogen.sh --prefix=/usr --without-gimp

bye

Ulf-D. Ehlert
2008-12-29 18:09:09 UTC (over 16 years ago)

Updating POT's

Marco Ciampa (Montag, 29. Dezember 2008, 03:05):

I think you meant:

./autogen.sh [--without-gimp] [ALL_LINGUAS="en fr"]

or

export ALL_LINGUAS="en fr"

./autogen.sh --prefix=/usr --without-gimp

Oops, you are right.

BTW, I think "ALL_LINGUAS" is a bad name, pretending there's a "LINGUAS" variable too containing a subset of "ALL_LINGUAS".

Bye, Ulf

Ulf-D. Ehlert
2008-12-31 12:27:14 UTC (over 16 years ago)

autogen.sh [Was: Updating POT's]

Ulf-D. Ehlert (Sonntag, 28. Dezember 2008, 21:07):

The default build system uses autoconf and automake. You have to run "autogen.sh" once and then later configure (this is also done automatically by autogen.sh), e.g. to set ALL_LINGUAS.

I have to correct myself: Since (while) we are using a trick in Makefile.am and autogen.sh, you'll have to run "autogen.sh" whenever Makefile.am has been changed. This is not the default autotools behaviour, though.

Ulf