How to use format-patch?
I want the "format-patch" to react on my translated po files only, not on the whole catalog. What exactly do I have to write? Do I have to run "diff" or something like this before format-patch? In case yes, how to avoid diff reacting on changes in dates etc.?

I am working on a copy of the gimp-help-2 created by "git clone". After translating my po files I run the usual make xml-nn, validate etc. and then "format-patch". (The new programs from Ulf-D works fine).

Validate error: $ make validate-nn
[SRC] src/preface/authors.xml
-:35445: element para: validity error : Element shortcut is not declared in para list of possible children
[...] F1.

Do I have to update my docbook or something else?

Kolbjoern

Ulf-D. Ehlert skreiv:

Kolbjørn Stuestøl (Wednesday, 30. December 2009)

How to use format-patch?
I want the "format-patch" to react on my translated po files only, not on the whole catalog. What exactly do I have to write? Do I have to run "diff" or something like this before format-patch? In case yes, how to avoid diff reacting on changes in dates etc.?

1. Commit your changes.
2. For making n patch files from the last n commits, use git format-patch HEAD~n.
You can also make patches from a range of commits, e.g. git format-patch HEAD~12..HEAD~11,
or you can specify any single commit with git format-patch -1 .

I am not able to commit and do not know how to (no password or whatsoever). May I send my po and image files to you as before, Ulf? Some few details remaining so perhaps next year ;-)

Validate error:
$ make validate-nn
[SRC] src/preface/authors.xml
-:35445: element para: validity error : Element shortcut is not declared in para list of possible children [...] F1.

is only valid as child of .

Tip: Install a local copy of "DocBook: The Definitive Guide" (see http://www.docbook.org/), then you can simply lookup DocBook elements under
/path/to/local/copy/of/docbook-tdg/.html

Ulf

I'll do and have a look.

Thank you to you and all others for good help during 2009 and previous years.

Kolbjoern

Ulf-D. Ehlert skreiv:

Kolbjørn Stuestøl (Thursday, 31. December 2009)

I am not able to commit and do not know how to (no password or whatsoever).

You don't need a password for a commit; you commit your changes to your *local* branch "master" ("git commit" does not correspond to "svn commit"). Without account to gnome.org you are just not able to *push* your changes to the remote repository.

See: "Everyday GIT With 20 Commands Or So" (http://www.kernel.org/pub/software/scm/git/docs/everyday.html), section "Individual Developer (Participant)"

Wasn't aware of this difference and therefore never tried to commit. I'll give the site a look. Perhaps I find out some day how to do the format-patch.

May I send my po and image files to you as before, Ulf? Some few details remaining so perhaps next year ;-)

No problem (but check if a simple diff file would be smaller!). If you find out how to commit and how to use 'format-patch', you will probably feel better, though. ;-)

Ulf

Yes, I'll work further on this tomorrow. (No time left today). Thank you a lot.
Kolbjoern