GNOME.org
 

Re: docs qs (was: Re: Release notes translated to VI

Thankyou again for your help, Murray. :)

Ccing this to cvsmaster, who have always been very helpful, and have a lot of experience in the CVS area. There's a clue in the name, somewhere... ;)

On 05/09/2005, at 10:42 PM, Murray Cumming wrote:

If you have checked the source out then, wherever, or however, you have
checked it out, you can just change the file and do a cvs commit.

Ah. I'd thought where they were mattered. Maybe that's just keeping them organized for yourself? I thought a working copy should mirror the on-server structure?

Do I edit a changelog?

With a text editor. 

The question was, "Do I do it?" Not "How do I do it?" ;)

Some commits don't require changelogs, e.g. the debian installer Level 1 via SVN, so I'm learning to check if a changelog edit is required. Working in several different projects can be confusing. :S

I don't think we can assume that everyone is experienced in CVS. 

But you need to learn that sometime. I recommend this:
http://developer.gnome.org/tools/cvs.html

Thankyou. What I was trying to say, is that there's a distinct gap between "I know nothing" and "I am experienced", and it helps if people take that into account. A bit more information can save questions afterward. 

If you have checked out
gnomeweb-wml/www.gnome.org/start/2.12/


Yay, it worked. :D

I didn't know I needed to checkout all that first. No wonder I didn't know what to work with. :S

or you are somehow in the 2.12/ directory, then do
$ cd press_release
$ gedit ChangeLog

Thankyou, I just needed to know where to start. I know where the po application files fit in the structure; I didn't know where the docs fit, and I found that confusing. A visual map of the structure helps me a lot, since my processing capacity has been damaged. [In any case, presenting information from different sensory points of view (visual, aural, touch etc.) is generally more effective than only one method.]

If you are not starting in exactly the same directory then you will need
to understand how to cd into the correct directory. I am quite confident
that you can do that.

My solemn thanks for that vote of confidence. ;)

What do you mean by "your locale name"?

"vi" is a locale name, I think.

Then I add that.

There are already several translations, so you should already be able to
guess how your files and directories should look.

Create the figures directory. For instance, in your docbook/vi directory,
$ mkdir figures
$ cvs add figures
$ cd figures
$ cp yourdirectorysomewhere/figure-somethingorother.png .
$ cp yourdirectorysomewhere/figure-somethingorother.png .
(The filenames must be the same as the filenames in the original
docbook/C/figures/) 

yes, having the directory contents checked out will help a lot here.

$ cvs add -kb *.png
(The -kb is for binary files in cvs. Try to remember it, though it is
annoying.)


definitely not intuitive mnemonics.

$ cvs commit -m "Added vi figures."

Thankyou. I'll get started on that right away, now I know where to start. :) 

I know. However, I can't track build errors, since I don't know what
they are. What am I supposed to look for? When I find it, what am I
supposed to do?


If it doesn't look wrong then don't worry. If it looks wrong and/or
mentions "error" somewhere, then ask here or on irc.

"Error" is fairly intuitive in this context. Thankyou. I'll do that. :)

_Another_ mailing list? Where do I find it, please?

http://mail.gnome.org/archives/gnome-doc-list/

I've just joined. That's <counts> 24 mailing lists for i18n projects. <frustrated sigh>

I'll see you there. I'm currently cursing a lot about the shouted copyright messages in the bug-buddy docs... I'd be muttering into my beard â if I had a beard.

[Note: get a beard first. Then mutter into it.]

from Clytie (vi-VN, Vietnamese free-software translation team / nhÃm Viát hÃa phán mám tá do)
http://groups-beta.google.com/group/vi-VN


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]