Hello,

I downloaded the new SVN in a new folder.

No problem to work on po and pot files with kate or KBabel : a lot of work in almost all files...
Makefile.GNU must be renamed to Makefile before running "make xml-fr".

My problem: I have some xml files in an "old" SVN copy that were ready for committing before the migration. For instance, I completely rebuilt the menus/file-open.xml file (en;fr).
How to extract the english xml file in order to create the corresponding pot file (not with copy-paste of course)?

Greetings

Julien

Roman Joost (Sonntag, 21. Dezember 2008, 19:08):

Ulf will probably reply to my mail and talk about his future plans.

Hmm, I thought of having some nice days without working on anything, of course... ;-)

There is a Makefile.GNU in the root of the module. It's his playground of an automake-free gimp-help-2 module. If you want to try out the Makefile, just rename it to 'Makefile' and *don't* run ./autogen.sh or configure afterwards.

Some additional notes (I've just spent some hours updating my local working copy and did not check anything):

Don't expect anything to work, we just have a starting point, not more.

We tried to save as many translations as possible, but there was no chance to save them all.

Some of the xml or po files may be totally useless, and some of the useless files may be fixed by editing the original multi-language xml file and applying the migrating script to the changed files, so tell us when you find such files.

For using "Makefile.GNU" instead of the autotools-generated "Makefile", make -f Makefile.GNU ...
should work ("-f" is not GNU-specific).

You may alway try make -n [-f Makefile.GNU] ...
to see what "make" *would* do (without really executing it), e.g. make -n pot
make -n po-de
make -n xml-de
make -n html-de

If something doesn't work (and this *will* happen) don't panic until Roman tells you so. ;-)

I don't have any fixed plans for the future, but I think the next steps should be
- changing the image directories structure so that we can use localized images again,
- merge po files, e.g. one po file per subdirectory.

Your ideas are always welcome...

Ulf

julien (Montag, 22. Dezember 2008, 15:28):

No problem to work on po and pot files with kate or KBabel : a lot of work in almost all files...
Makefile.GNU must be renamed to Makefile before running "make xml-fr".

Try "make -f Makefile.GNU" ...

My problem:
I have some xml files in an "old" SVN copy that were ready for committing before the migration. For instance, I completely rebuilt the menus/file-open.xml file (en;fr). How to extract the english xml file in order to create the corresponding pot file (not with copy-paste of course)?

Work in a temporary directory where you can test anything, e.g.

mkdir -v /tmp/gimp-help && cd /tmp/gimp-help

Copy tools and stylesheets as well as your changed old-style sourcefile(s), e.g.:

cp -ai /path/to/svn/files/{tools,stylesheets} . # note the "." mkdir -vp src/menus
cp /path/to/changed/xml/files/src/menus/file-open.xml src/menus/

Then try to invoke the migrating script:

LINGUAS="fr" tools/migrate.sh

and ignore any complaints about missing glossary etc.

Then you should have a new directory "oldsrc" containing your edited xml files and new directories "src", "pot", "po" (and "xml").

Try find scr pot po -type f
and compare these files with the corresponding SVN files.

HTH, Ulf

? ???, 21/12/2008 ? 19:08 +0100, Roman Joost ?????:

Hi folks,

I merged the xml2po branch and migrated the content. I hope I squeezed most translations out of the xml files thanks to Ulfs astonishing work. He worked most of the time on the migration and content splitting scripts (check the tools directory).

That means from now on new documentation is written in English *only*. Translations go in their designated po directories. With everything new and shiny, there are of course some downsides. There is currently no way of creating HTML files or validating. That's what need to be revamped, because the whole workflow of creating HTML (or other formats) has changed now.

I hope the work on this will be more transparent now and errors can be faster spotted. Please let us now what your first impressions are. Don't hesitate to ask questions.

Speaking of first impressions: You may find po files, with incorrect translations. That's where you come in to fix that. Every author can create new po files for it's language with the following makefile target:

make po-[language code]

example (creating po files for German): make po-de

The creation of po files are dependant on pot files, so they should be created automatically.

Similar to this way, you're also able to create (translated) XML files. Just type (make xml-de for example) to get the DocBook/XML files (for German) created. I think it's just a snap from being able to create HTML files.

Ulf will probably reply to my mail and talk about his future plans. There is a Makefile.GNU in the root of the module. It's his playground of an automake-free gimp-help-2 module. If you want to try out the Makefile, just rename it to 'Makefile' and *don't* run ./autogen.sh or configure afterwards.

That's currently all I have to say :)

Looks great, congratulations.

Is there any particular reason it uses so small po for a single file? Having a single catalog would be more correct:

1. It's easier for translator to work with it. 2. Many translations are joined thus providing a basis for translation consistency.
3. It's easier to get statistics :)

Currently it looks a bit complicated.

2008/12/23 Nickolay V. Shmyrev wrote:

Looks great, congratulations.

Is there any particular reason it uses so small po for a single file? Having a single catalog would be more correct:

A single catalog for the whole translation? Please no :)

1. It's easier for translator to work with it.

If you have a Core2 Quad or Xeon based workstation... :)

2. Many translations are joined thus providing a basis for translation consistency.

Not sure if it really helps :)

Alexandre

23.12.08, 17:41, "Alexandre Prokoudine" :

2008/12/23 Nickolay V. Shmyrev wrote:

Looks great, congratulations.

Is there any particular reason it uses so small po for a single file? Having a single catalog would be more correct:

A single catalog for the whole translation? Please no :)

It can be a single file for a folder.

1. It's easier for translator to work with it.

If you have a Core2 Quad or Xeon based workstation... :)

Problems with text editor :) Choose the different one. The total size of joined ru catalog is around 4 Mb, when everything will be translated it will be about 7 Mb.

2. Many translations are joined thus providing a basis for translation consistency.

Not sure if it really helps :)
Alexandre

Ok, then it's up to you to open each po file and fix a header there.

2008/12/23 Nickolay V. Shmyrev wrote:

A single catalog for the whole translation? Please no :)

It can be a single file for a folder.

A single file for a folder isn't so bad already :)

1. It's easier for translator to work with it.

If you have a Core2 Quad or Xeon based workstation... :)

Problems with text editor :) Choose the different one. The total size of joined ru catalog is around 4 Mb, when everything will be translated it will be about 7 Mb.

In Inkscape project we have a couple of people for who their UI translation file is too large :) And it's around 600Kbyte, mind you :) Even for me just loading it into poEdit takes quite a while.

Alexandre