On Mon, Feb 15, 2010 at 3:35 AM, Byung-Hee HWANG wrote:

So how can i help this for gimp? Espeically i like to work for docs of gimp -- just translation, i'm not professional speaker for English. OK any advice comment welcome!

Welcome, Byung-Hee.
I think I could give you some infos.

In fact, there was a wiki page for new participants, but now it's not available. Here is short instructions about that.

1. Get the source files. (on command line)
git clone git://git.gnome.org/gimp-help-2

2. Make pot (on command line, in gimp-help-2 folder) ./autogen.sh --without-gimp
make pot

** Memo : You need some packages to compile gimp-help-2. (linux or cygwin both) However, I don't have the full list now.

3. Update each po files of your language. (I'm sorry, I don't know how to automatically.)

4. Edit po files. You can use one of po file editors.

5. Update your local resource. git pull

6. Check validation
make validate-ko

7. if you want to make html files make html-ko

8. If there's no error, make a patch for it. git diff > korean_translation_2010_xxxx.patch (anyname you want)

9. Send the patch file to this mailing list and ask to commint Then, someone will commit your work.

10. Special comment for Korean Translation. There are a lot of fuzzy strings. I've translated about a year ago, but they're not
updated. Most of them don't need to edit or re-translate, just check and update small changes.

If you need more information, feel free to ask me and other members on this list.
Thank you for your participation.

On Mon, Feb 15, 2010 at 8:01 AM, Byung-Hee HWANG wrote:

And don't forget it, don't
change your email address unless i die.

Ok, I'll not change my e-mail address unless I change my name. ;)

Hi,

With careful i read and read your guidance. And i realized that i need some homework for git usage.

No need of git if you are only translating. Go to http://l10n.gnome.org/module/gimp-help-2/ There, you will find Japanese files to edit.

I started summarizing my experience there: http://gimp-help-how-to-contribute.rendez-vous-wiki.com/gimp-help-how-to-contribute

Julien

On Mon, Feb 15, 2010 at 4:13 PM, jm.hard wrote:

Hi,

With careful i read and read your guidance. And i realized that i need some homework for git usage.

No need of git if you are only translating. Go to http://l10n.gnome.org/module/gimp-help-2/ There, you will find Japanese files to edit.

Hi, Julien.
You're right. He doesn't need to learn howto use git. Just download korean files from there.
However, he might need to git and some other packages.

To translate all strings in order, just download po files and translate them, but it's not easy to do by one person in his rest time. I've translated about 200 pages for a year and more than are untranslated.

Therefore, I'd like to recommend him to compile gimp-help-2 and make html files for checking what he did or what he have to. Of course he could see gimp-help-2 online version, though.

Anyhow, in my experience, strings in po files of gimp-help-2 are not independent. To know some connections between paragraphs or to understand flow of contexts are needed, since it is a document. That's why I told him to get files from git. :)

??????? ???? ?????!
I welcome you.
My name is ????, I'm a translator for Japanese.

I read your web page and knew you use FreeBSD. I was a FreeBSD user too. As you know, the port of the GIMP Help stick on the version 2.4.2 yet. If you have more spare time, please do send-pr to update it to the version 2.6.0. The current official packages only need to be extracted under the directory /usr/local/share/gimp/, but do not require any other document-building system around XML like for the older version (2.4.x).

Occasionally I don't use FreeBSD but Cygwin now because my own PC is broken on its disk crash. Someday I will come back to my favorite OS, and check your work on fortune-mod-the-godfather.

Something I know about Makefile on this system: This system use GNU make, so I recommend you to type the commands (with a target) as follows: MAKE=gmake gmake target
The 'find' command on the top Makfile is expected to be run on BASH shell internally, like $(find_l) images/{common,C}
, but it does not work on genuine SH shell. If you get trouble on it, edit these command lines as $(find_l) images/common images/C

Cheers, -=-=-=-=-=
SimaMoto,Ry?Ta
http://code.google.com/p/gimp-doc-ja/

Hello, Ry?Ta SimaMoto.
I'm Jihui Choi, an ex-translator for Korean. ;) In fact, I can't translate for a while, so Byung-Hee volunteer to translate gimp ui and gimp-help-2 instead of me or with me. :)

By the way, I'm really surprised of your work. A year ago, there was no Japanese translation for gimp-help-2, but one day you've translated all documents. How did you do that? Did you do only by yourself or with someone?

As my known, translating work is very active in Japan. I believe we can learn something from your experience and knowledge about translating. If you don't mid, would you give us some advice? If you do that, I'll really appreciate to you and all Japanese translators.

2010/2/16 Byung-Hee HWANG :

After i read above thing, i think that you have professional skill about C programing. That's good. By the way, i have to study more more more about that to make/edit something under C area.

No, I'm not an expert on C, but a long-years novice. :) Actually once I wrote a configure.ac file and some Makefile.am files for producing a toy application on KDE2/Qt2 (C++). It is very short skill.

The building system on the GIMP Help is very useful. I can't write such a perfect makefiles. There are many user-friendly functions, like the validation command which find errors on all XML tags, and on path and name of image files, and various utility commands for counting the current progress statistics on PO files, or for quick test in short draft output from one XML file, and so on. Try to call the usage list as:
gmake help

-=-=-=-=-=
SimaMoto,Ry?Ta
http://code.google.com/p/gimp-doc-ja/

Ry?Ta SimaMoto (Monday, 15. February 2010)

The 'find' command on the top Makfile is expected to be run on BASH shell internally, like $(find_l) images/{common,C}
, but it does not work on genuine SH shell.

'find' doesn't work?

If you get trouble on it, edit these command lines as $(find_l) images/common images/C

"find_l" is defined as "find -L", and you can always override it on the command-line with
make ... find_l=/what/ever/you/want If the '-L' option is not supported by your system [*] we can add a test to check this and set find_l to "find" if necessary.

Just report if something doesn't work, I'm (a) a Linux-only user and (b) no clairvoyant ... ;-)

Ulf

[*] The '-L' option "shall be supported" according to POSIX.1-2008, AFAIK.

Hi, Ulf

2010/2/16 Ulf-D. Ehlert :

Ry?Ta SimaMoto (Monday, 15. February 2010)

The 'find' command on the top Makfile is expected to be run on BASH shell internally, like   $(find_l) images/{common,C}
, but it does not work on genuine SH shell.

'find' doesn't work?

If you get trouble on it, edit these command lines as   $(find_l) images/common images/C

"find_l" is defined as "find -L", and you can always override it on the command-line with
       make ... find_l=/what/ever/you/want If the '-L' option is not supported by your system [*] we can add a test to check this and set find_l to "find" if necessary.

Just report if something doesn't work, I'm (a) a Linux-only user and (b) no clairvoyant ... ;-)

I must say "because SH shell cannot expand this abridgment with brackets to the correct directories." This is not a matter on the 'find' command but the shell.

Though FreeBSD offers just two shells, the old standard shell /usr/bin/sh and the C Shell /usr/bin/csh, users can install the Bourne Again Shell /usr/local/bin/bash through the BSD port system, and almost desktop users do so. (Other users use the C shell.) But this powerful one does not override (overwrite) the older standard one, so sometimes user needs to know which one runs.

The Makefile contains "images/{C, common}". This shorthand is not allowed on the old /usr/bin/sh shell. Actually, I installed bash too, and this shorthand is expanded properly as I expect. I run this 'make' action on the 'bash' environment, but the 'find' command was called internally with the old 'sh', then this shell warned and did not work correctly.

Almost platform-depend problems caused by features and definitions on Linux products are avoided on *BSD operating systems by using some tricks and/or patch files. I think there should be also some useful hacks on this issue, because it seems typical, but I did not know any essential solution for this.

-=-=-=-=-= SimaMoto,Ry?Ta
http://code.google.com/p/gimp-doc-ja/