Good job. Simply, please, place your 'ko' in alphabetical order, in principal between 'it' and 'nl'

I'm trying to translate GUM from English to Korean. but I faced some problems.

1. someone change cvs files while I work. when I made patch file, I just recognized at that time. (added some italian translations)

If you only add 'ko' text and if you don't modify the existing text or the XML structure, there is no problem: your 'ko' text will simply be added to CVS when committing.

2. how do I do to ask to commit?
As far as I know, there's no korean who has the commit authority.

3. I translated just a little bit. Of course I'm doing, and will go on. but now I have very small part. Can I ask to add my works on CVS files? (If can't, how can I do? day after day.. cvs files will change

again and again..)

Roman, romanofskiATgimpPOINTorg,is the Gimp help maintainer. He is charge of committing patches for doc writers who have not access to CVS. Unfortunately, he is very busy: I sent him two patches since 06-03-22 and they are not committed yet...:-(

someone told me.
IF you want to add korean translation, at least, you have to have the 100% translation scripts.(though that's not perfect translation. it means, just quantity, not quality.)

Is it true? do I need 100% translation script?

I have no idea about this

please, tell and help me.
(I don't know about gimp, linux, cvs, and xml. and I don't have good english, either.

XML files must be validated before committing and this is only possible under Linux...

But because of those, I'll never givp up. -_-;)

thanks

p.s. my patch file : http://mr-dust.pe.kr/gimp/gimp-help-2.patch my works : http://mr-dust.pe.kr/gimp/gimp.zip

------------------------------------------------------------------------ ??? ?? ??? ??, ???
http://happybean.naver.com

------------------------------------------------------------------------

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

Am 01.05.2006 um 06:21 schrieb Dust:

hello..

I'm trying to translate GUM from English to Korean. but I faced some problems.

1. someone change cvs files while I work. when I made patch file, I just recognized at that time. (added some italian translations)

That happens all the time and cvs is designed to handle this. As long as the changes are not in the same line of a file both changes (yours the the remote ones) get merged in the file automatically. Just make sure that while you are working on the translation you update your files often through cvs

2. how do I do to ask to commit?
As far as I know, there's no korean who has the commit authority.

That is not a problem either. There are some people (including myself) which can do this for you. Just make sure to mail a diff to the most recent version of the files in the cvs and attach additional files as images.
The head of the documentation project is Roman, he's usually the one who does most of the patch handling.

3. I translated just a little bit. Of course I'm doing, and will go on.
but now I have very small part. Can I ask to add my works on CVS files?
(If can't, how can I do? day after day.. cvs files will change again and again..)

yes, of course. Just start with a small portion and let it grow. Just make sure that the edge you start of with makes sense and fits into the docs structure. Do you know how working with a project in cvs works? You actually do work on the files from the cvs, you should update them very regular. Updating means you merge the changes that other people commited to the cvs repository with your local copy. After you did some work to your local files, you have to maks sure that everything is valid (also but not only in the meaning of xml docbook validity). If that is done you can create a patch by making a diff to the files you changed and send that diff to somebody (e.g. Romanofski).

someone told me.
IF you want to add korean translation, at least, you have to have the 100% translation scripts.(though that's not perfect translation. it means, just quantity, not quality.)

Is it true? do I need 100% translation script?

what ist the 100% translation script. Sorry no idea what you mean here.

please, tell and help me.
(I don't know about gimp, linux, cvs, and xml. and I don't have good english, either.

Well if writing a manual some knowledge about gimp _might_ help.

But because of those, I'll never givp up. -_-;)

thanks

p.s. my patch file : http://mr-dust.pe.kr/gimp/gimp-help-2.patch my works : http://mr-dust.pe.kr/gimp/gimp.zip

I'll have a look into that patch and let you know.

greetings, lexA

--------------------------------------------------------------------

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Julien,

Roman, romanofskiATgimpPOINTorg,is the Gimp help maintainer. He is charge of committing patches for doc writers who have not access to CVS. Unfortunately, he is very busy: I sent him two patches since 06-03-22 and they are not committed yet...:-(

make sure that the patch works with the current cvs content or just create a new one and send it to me. Roman is on vacation for the next two weeks, so it might be helpful if I have a look into this.

Just hurry up, I have 6h left and will be offline for the rest of the week.

greetings,

lexA

- --- Live is like a chocolate box, you never know what you wanna get... GPG Signatur auf http://wernicke-online.net/Impressum/ pr?fen

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEVcYzR9mXLVsAbiQRAlrZAJsEgAf0bkla5Y7iAVOaHlejaorwkgCfcslN 50ewXvzBNserI23lMAedO/s=
=i/xK
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,
Am 01.05.2006 um 06:21 schrieb Dust:

p.s. my patch file : http://mr-dust.pe.kr/gimp/gimp-help-2.patch my works : http://mr-dust.pe.kr/gimp/gimp.zip

OK,

I had a look into your patch. It looks pretty good. I merged it and it will be commited in a couple of minutes (Please note, that due to some caching it might take up to 24h until you see the changes in the public cvs server).

I'd just like to have some minor suggestions, which by the way should be interesting for every author:

- - please stick to the alphabetical order for the different languages: --> en;cs;de;fr;it;ko;nl;zh_CN
note: since en is the "leading" language, it is mostly put in front of everything else

- - use " to embrace attributes in xml tags -> lang="ko" instead of lang='ko'

- - you have lots of dead references in your text. Please do not enable references to other chapters as long as they are not translated to you language yet. It's good to do something like:

This way you can later search for "PENDING: ko" and enable the links very fast after the chapters are translated. DEAD REFERENCES ARE ERRORS THAT USUALLY PROHIBIT COMMITING A PATCH (big exception from that rule for you for this time only!)

- - you should zip the patch and attach all changed or new images to the zip as well. It is impossible for the commiter to search for missing images in time.

- - please set the print resolution for screenshots and large examples to 144dpi - This is necessary to produce good looking pdf files that can be printed.

All in all just minor issues! Please keep up the good work!

Greetings, lexA

--------------------------------------------------------------------

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

Am 01.05.2006 um 06:21 schrieb Dust:

p.s. my patch file : http://mr-dust.pe.kr/gimp/gimp-help-2.patch my works : http://mr-dust.pe.kr/gimp/gimp.zip

patch approved and commited.

I've no clue how the ALL_LINGUAS comes into the Makefile - can somebody (neo?!) please add "ko" to the list of languages to be build?

Thanks a lot, lexA

--------------------------------------------------------------------