Installation manual
There is a reference to some material which is only in the German version,
which needs to be integrated back into the others (starting with English,
presumably). It would be great to have that reverse translation, if the
material is still current.
I think I will have time this weekend to work on the English version of the
docs. I set up anonymous cvs to the archive for my machine last night. I
was not planning on committing anything myself. Adam, please let me know
how you'd like me to proceed if I do get to it.
> -----Original Message-----
> From: apharris@burrito.onshore.com
> [mailto:apharris@burrito.onshore.com]On Behalf Of Adam Di Carlo
> Sent: Monday, March 27, 2000 8:56 PM
> To: Sebastian.Leske@bigfoot.de
> Cc: debian-boot@lists.debian.org
> Subject: 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.
>
> Great.
>
> >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
> personallly. <debian-boot@lists.debian.org>.
>
> 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
> CVS/pserver?
>
> 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
> username/password.
>
> 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-----
> Version: 2.6.3a
> Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface
>
> mQCNAzAqrA0AAAEEAOiRAUILsvbbeYBh5SxUqgbG1saOny/WK0PDzaq8k36LIg29
> PJg/binO7JphJF3RzpyWFGWrFFNQ2E+GMzYUxBZi6pATSELwE8DjucmJPm6pXlLJ
> 9vZbb5ndZPz1UgsPMLwCULyCA1uoUIoXk4oJI4hjAUJhP5B26o/8QF79WmfNAAUR
> tCBBZGFtIERpIENhcmxvIDxhZGFtQG9uc2hvcmUuY29tPokAlQMFEDaKg0+P/EBe
> /VpnzQEBw04EANtb/6uDcCcVDdZcUX85UXc3h/mZnv8o/VwRm9dX0YK4+cJfh/NP
> 7j6BRbCIYRj87Y3Kv6RQiCog5y1uGc0mAs9LeHcRhNFiPGQqlHh4osZi046gxYWo
> h98iYSvQgdpaudse4IFaKhOBePA5xRt1afJDP+1C+GnlqBpzPtjYvbqdtCNBLiBQ
> LiBIYXJyaXMgPGFwaGFycmlzQG9uU2hvcmUuY29tPokAlQMFEDSQaAKaa/nJd0Bw
> nQEBtvMEAKjGydAjAu7lJZn1FjF64xFoBxVF2zepbDAabCfzyg5V20/DYwSFrivu
> nO3clw9f8vzMTM8MeF3hmcDyuaL58crtmXb8M63bQ3N7dGl6wUTMSMJLrMRyUC7+
> GRLX9xNRlE3INxD1AeMNl86Bl18U5DBYEgtFcVg9FVEg9aYknzvFiQCVAwUQMYmW
> yyQekuOetIzJAQGgvAQAv/vaoJKyMXYg7HB97MqMRJP3WwL0u4Cxm7AS/ryQ+G7c
> RNnwkqRd2NIPPIUVvaIg7vEREJnB9J498IjaLXnv4IIpnPuqTN3st1bumyW1c6sB
> ljcFpIXC3yeRDgByzBExrsClF8/ILK18ejlMEqkOYqgiZofdy308DxVwqQCy2oSJ
> AJUDBRAwQY3Fj/xAXv1aZ80BASrjA/9O50bYY3FJ7xeyjunmksm98+Nw3kwJ2eap
> 3ZFGrmAuLow5LsxwPfcY5XI3sv3iBqmRxfA5Ml4s26gqLfwq4WhVKJC1KESMLg6K
> Typ/mrmOyGqz7cTmDrnN9eOimQ+7TmaYGg7lnk7pmVxYeaHKgbbrwaRIETOpmAiZ
> s2o+JgKWtLQfQS4gUC4gSGFycmlzIDxhZGFtQG9uU2hvcmUuY29tPokAlQMFEDZk
> Ve1dZWD4XzDwBQEBizQD/3Rh1PHnfZUegCXt2Q6QzzVjOEUw93PyUqxF+ExhhdFk
> VrpfG4jlJ/KWChNqrrGc1ssQfq7B85Ukpaa9gEzVWJc92H6USbnzwx0e2Gg8Spbh
> c0hN8L3IUnLyiTUdWV3+pDQu+T/1f1D4My00Ct8hblDD2hQ1BR/h/qEH3ikwFExI
> iQCVAwUQNh5LM2njSQSFnViJAQGfvgQAo+3870xryTfSMh+7hIdO/e6NKdFvCUdA
> m1vCox+heVAmEkacPI1LfskcD75rS/zqhVofQX6L0USvq03+Q69fVQ/uA04QmU/i
> 1p5+7iVjDYebkuf209T/S8cFmOyDK8x2MO2iOcp8ASggBbYP/IQo3xe/g2utQbjg
> UeYKMLPcP9uJAJUDBRA1CdJrj/xAXv1aZ80BAQEwA/4nhmjvSlkhN5RTQR975/9W
> 5hnGp/XKtTiJDtOOS6f1ALXO1v/OEbSMcQDRKk3sRP0JHM28UzbzivVQnvWuOrhI
> SSlq/epbYcMn4dwS9xCYOn6cIkNQHMXFs7GvF4MN6ZwOooEQMG6rTl5EpLgcHQde
> ylyCvyKD2cdyl/ROPJ6aELQfQWRhbSBQLiBIYXJyaXMgPGFwaEBkZWJpYW4ub3Jn
> PokAlQMFEDTfYH2P/EBe/VpnzQEB7UsD/i4lfrk24+UfnX+bqD9Js1rke3WJ1YHF
> fLkRABoyhWyDFiq66Jbp33UWV3GPYGhzubOCO2gytVUUo4/tDtXudYGKchrO7jeG
> GW1xbuTCv3yr9KIw/0GTCcEdpf+vIeKXgASOfKHIe4GRn7GZqxKlnM4H1anH3QES
> Yo7lAcKNLekFtB5BZGFtIERpIENhcmxvIDxhcGhAZGViaWFuLm9yZz6JAJUDBRA2
> T6oTj/xAXv1aZ80BAVEeBAC3m2RHKpYsJv+iLcDz6YH1FAsMPLiCMk/A/qDCSjrD
> LXWEnaoqt1qn2a3QKbMQ9jOG0eYVb2ODzAqNGRADgRNoHhotQrBNT5VBWfkFslw3
> Uo9pHLU9amfpU74ePoJMIjnqYmOooOcUkaIgYDNJ0BDsJCQ60uN1HM6PISDDWFN4
> GQ==
> =PpN8
> -----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
> identically.
>
> 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:
> <URL:http://cvs.debian.org/cgi-bin/cvsweb>.
>
> 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
> type those.
>
> # If you are logged into to cvs.debian.org (CNAME va.debian.org):
> export CVSROOT=/cvs/debian-boot
>
> # If you are using `ssh' to access the area, and you have an
> # account on cvs.debian.org -- this is the recommended method:
> export CVS_RSH=ssh
> export CVSROOT=:ext:<MY-USERNAME>@cvs.debian.org:/cvs/debian-boot
>
> # If you are using anonymous (readonly) access:
> export CVSROOT=:pserver:anonymous@cvs.debian.org:/cvs/debian-boot
> cvs login
> # 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):
> export CVSROOT=:pserver:<USERNAME>@cvs.debian.org:/cvs/debian-boot
> cvs login
> # 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
> <debian-boot@lists.debian.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
> required reading.
>
>
> --
> To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
Reply to: