Re: Installation Manual Translations -- we need help
>I happen to be German, and I'like to help with the German translation.
>While I have not done translation work for Debian before, I have some
>experience with translating and interpreting in general and a reasonable
>amount of Linux/Debian knowledge.
>If you could tell me what to do, or point me at some address where I can
>apply, I'd be glad to help and to do some translating.
Well, first off, please correspond to the list rather than to me
If you have an account on va you can use that without further ado. If
you do not, I can create one for you -- are you familiar with
Attached is instructions for how to access the CVS narea.
Attached also is my public key. You can send me, crypted with the
attached public PGP key (pgp 2.x only please!), a requested
Please be careful in what you commit and be sure that the SGML is
valid ('make LINGUA=de lint') prior to making any commits.
Please let us know if there are things which should be added to the
defaults.ent or urls.ent -- editing in there directly is ok too.
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface
-----END PGP PUBLIC KEY BLOCK-----
CVS and boot-floppies Sources
You can access the boot-floppies using CVS; this is particularly
useful if you are actively working on the package.
CVS comes with excellent documentation; in particular, see the `cvs'
info pages, and "Open Source Development with CVS", a GPL book freely
available online, at <URL:http://cvsbook.red-bean.com/>. (There is a
Debian package of it, called "cvsbook".)
There are various ways to access the CVS repository for boot-floppies,
depending on your circumstances. However, once you've set up your
CVSROOT variable properly, all the access methods behave almost much
There is a `cvsweb' interface, which is great for browsing the commit
logs, pulling diffs from the repository, and getting a good look at
the layout of the module. It can be accessed via:
The following are POSIX bourne shell commands you can run to get the
CVS area; other shell users should be able to translate to their shell
language easily. Commands with a `#' are comments; you don't have to
# If you are logged into to cvs.debian.org (CNAME va.debian.org):
# If you are using `ssh' to access the area, and you have an
# account on cvs.debian.org -- this is the recommended method:
# If you are using anonymous (readonly) access:
# You will be prompted for a password -- just hit `Enter'.
# If you are using a pserver account (i.e., you need write access
# but do not have a login account, and you have been given a
# pserver username and password):
# Enter the password you have been given.
After that, all techniques are the same. Simply check out the
sources. For the lastest (possibly unstable) version, do:
cvs co boot-floppies
For the slink CVS branch, which is probably what you are using if you
are working on translating slink documentation:
cvs co -r adam-boot-floppies_2-1_branch boot-floppies
>From there, you can use `cvs update', `cvs commit', `cvs diff', and
`cvs status' -- see the info pages. If you do not have write access
to the repository, and have made modifications that you would like us
to incorporate, please mail the `cvs diff -u' output along with a
brief description of what the patch does to
<firstname.lastname@example.org>. It is helpful if you put "[patch]" in
the subject line.
Please try to make meaningful commit log entries that describe
something fairly specific about what changes you have made. It is
best to commit one file at a time, or group them logically, so that
modifications to several files that pertain to fixing one particular
bug or add a certain feature contain a log message that is relevant
for that file, without cruft about unrelated changes to unrelated
files. A massive commit of 15 files with a common log entry that
says "blah changes that fix bugs, C-u M-! fortune" are not very
useful later on when you are trying to find out when a certain change
happened. The log entry should describe what's been changed, so that
later on maintainers do not have to parse every single diff to find
one simple modification. You should be able to scan the log and
narrow down the search based on what's written there. There is a
good discussion of this in the GNU `Standards' info document, under
"Documenting Programs", "Change Logs". `Standards' is considered