# translation of cervisia.po to 
# translation of cervisia.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: cervisia\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:35+0200\n"
"Last-Translator: Lwandle Mgidlana <lwandle@translate.org.za>\n"
"Language-Team:  <xh@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.0beta2\n"

#: index.docbook:15
#, no-c-format
msgid "&cervisia; Manual"
msgstr ""

#: index.docbook:17
#, no-c-format
msgid ""
"<firstname>Bernd</firstname><surname>Gehrmann</surname> "
"<affiliation><address><email>bernd@mail.berlios.de</email></address>"
"</affiliation>"
msgstr ""

#: index.docbook:22
#, no-c-format
msgid "ROLES_OF_TRANSLATORS"
msgstr ""
"<othercredit role=\"translator\"><firstname>Antoinette</firstname> "
"<surname>Dekeni</surname><affiliation><address><email>"
"antoinette@translate.org.za</email></address></affiliation><contrib>"
"Translation</contrib></othercredit> "

#: index.docbook:31
#, no-c-format
msgid "Bernd Gehrmann"
msgstr ""

#: index.docbook:35
#, no-c-format
msgid ""
"This program may be distributed under the terms of the Q Public License as "
"defined by Trolltech AS of Norway and appearing in the file LICENSE.QPL "
"included in the packaging of this file."
msgstr ""

#: index.docbook:39
#, no-c-format
msgid ""
"This program is distributed in the hope that it will be useful, but WITHOUT "
"ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or "
"FITNESS FOR A PARTICULAR PURPOSE."
msgstr ""

#: index.docbook:50
#, no-c-format
msgid "&cervisia; provides a graphical view of &CVS;."
msgstr ""

#: index.docbook:54
#, no-c-format
msgid "<keyword>KDE</keyword>"
msgstr "<keyword>KDE</keyword>"

#: index.docbook:55
#, no-c-format
msgid "kdesdk"
msgstr ""

#: index.docbook:56
#, no-c-format
msgid "Cervisia"
msgstr "Cervisia"

#: index.docbook:57
#, no-c-format
msgid "<keyword>CVS</keyword>"
msgstr ""

#: index.docbook:58
#, no-c-format
msgid "version control"
msgstr ""

#: index.docbook:59
#, no-c-format
msgid "revision control"
msgstr ""

#: index.docbook:65
#, no-c-format
msgid "Getting Started"
msgstr "Iyaqala"

#: index.docbook:68
#, no-c-format
msgid "Accessing The Repository"
msgstr ""

#: index.docbook:70
#, no-c-format
msgid ""
"In this section we assume that you are using &CVS; only on the client side. "
"That means, someone (probably the administrator of the &CVS; repository) "
"gave you an account on the server machine, and it's your job to checkout "
"modules from the repository and work with them."
msgstr ""

#: index.docbook:77
#, no-c-format
msgid ""
"&CVS; supports several methods of accessing the repository, which can be "
"categorized as follows:"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "Local"
msgstr "Ubulali"

#: index.docbook:82
#, no-c-format
msgid ""
"The repository is something like <filename "
"class=\"directory\">/home/cvs</filename>"
" and is simply stored in a directory which is accessible from your computer. "
"It may physically be on a disk which is mounted via <acronym>NFS</acronym>, "
"but this is an irrelevant detail. If you often use a certain local "
"repository, you will want to tell &cervisia; about it."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "Adding A Local Repository"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"Open the Repositories dialog by choosing "
"<menuchoice><guimenu>Repository</guimenu> "
"<guimenuitem>Repositories...</guimenuitem></menuchoice>."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "Press the <guibutton>Add...</guibutton> button."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "Enter the details of the repository in the dialog box that displays."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "Confirm by pressing the <guibutton>OK</guibutton> button."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"In the future, whenever you use &cervisia; to check out a new module, "
"&cervisia; will present you the repositories you have added here."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "<term>rsh</term>"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"The repository name is something like "
"<literal>:ext:bernd@cvs.cervisia.sourceforge.net:/cvsroot/cervisia</literal>."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"This method requires that you have a user account on the server machine (in "
"this case, <systemitem class=\"systemname\">cvs.sourceforge.net</systemitem>"
" and use a remote shell for communication. By default, &CVS; uses &rsh; for "
"this purpose, however, &rsh; is long considered to be insecure, and is "
"widely replaced by &ssh;."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"If you must use &ssh;, you must set the environment variable "
"$<envar>CVS_RSH</envar> to &ssh; when using the <command>cvs</command> "
"client. &cervisia; supports this easily."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"Open the repositories dialog again, and press the "
"<guibutton>Add...</guibutton> button. Now enter the name of the repository "
"in the first line and the remote shell (&eg; &ssh;) in the second line. If "
"you now confirm with the <guibutton>OK</guibutton> button, &cervisia; "
"memorizes these settings."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"Note that &cervisia; can not answer possible password requests from the "
"server machine. You must make sure that a remote login works without "
"requiring you to enter the password. With plain vanilla &rsh;, this can be "
"achieved for example by creating a "
"<filename>$<envar>HOME</envar>/.rhosts</filename> file with a list of "
"trusted hosts (see the &rsh; manpage)."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"With &ssh;, it can be achieved by copying your public key "
"<filename>$<envar>HOME</envar>/.ssh/identity.pub</filename> to the server. "
"In this case, the key must not be encrypted with a passphrase (see the "
"&ssh;> manpage and the &CVS;/<acronym>SSH</acronym> <acronym>FAQ</acronym> "
"on SourceForge). If you are unsure about these issues, ask your system "
"administrator."
msgstr ""

#: index.docbook:82
#, no-c-format
msgid "pserver"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"The repository name looks like "
"<filename>:pserver:gehrmab@cvs.kde.org:/home/kde</filename>"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"This method accesses the server via a special protocol with a relatively "
"weak authentication (<literal>pserver</literal> stands for password "
"authentication). Before you can use such a server, you have to login. As "
"this is not directly supported by &cervisia;, enter on the command line"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"<prompt>%</prompt><userinput><command>cvs</command> <option>-d</option> "
"<parameter>:pserver:joe@cvs.kde.org:/home/kde login</parameter></userinput>"
msgstr ""

#: index.docbook:82
#, no-c-format
msgid ""
"(of course, with your repository substituted). &CVS; will prompt you for "
"your password and check with the server. If the password is ok, the "
"repository name, together with the (slightly scrambled) password, will be "
"appended to the file <filename>$<envar>HOME</envar>/.cvspass</filename>. "
"Whenever &CVS; accesses the repository, it will silently send the password "
"to the server, so you do not have to take care of that once you have logged "
"in. As everybody who knows your password can work with the repository in "
"your name (and even do major damage to it), you should keep the "
"<filename>$<envar>HOME</envar>/.cvspass</filename> secret and non-readable "
"for others."
msgstr ""

#: index.docbook:206
#, no-c-format
msgid "Importing a module into the repository"
msgstr ""

#: index.docbook:208
#, no-c-format
msgid ""
"In this section, we discuss how you put a new project into the &CVS; "
"repository. If you just want to work with an existing project which is "
"already in a repository, you may skip this section."
msgstr ""

#: index.docbook:215 index.docbook:216
#, no-c-format
msgid "A screenshot of &cervisia;'s import dialog"
msgstr ""

#: index.docbook:222
#, no-c-format
msgid ""
"In <xref linkend=\"screenshot-import\"/> you can see the dialog which helps "
"you to <emphasis>import</emphasis> a project as a module. After you have "
"filled out this form and confirmed by <guibutton>OK</guibutton>, the "
"following &CVS; command is used:"
msgstr ""

#: index.docbook:229
#, no-c-format
msgid ""
"<command>cvs</command> -d <co "
"id=\"co-repository\"></co><replaceable>repository</replaceable> import -m "
"\"\" <co id=\"co-module\"></co><replaceable>module</replaceable> <co "
"id=\"co-vendortag\"></co><replaceable>vendortag</replaceable> <co "
"id=\"co-releasetag\"></co><replaceable>releasetag</replaceable>"
msgstr ""

#: index.docbook:231
#, no-c-format
msgid ""
"The name of the &CVS; repository, also known as $<envar>CVSROOT</envar>"
". You must have write access to it, and the repository must be properly "
"initialized. If the repository does not yet exist, initialize it with the "
"command <userinput><command>cvs</command> <option>-d</option> "
"<replaceable>repository</replaceable> <command>init</command></userinput>."
msgstr ""

#: index.docbook:231
#, no-c-format
msgid ""
"If the repository is remote, make sure that authentication works (see <xref "
"linkend=\"accessing-repository\"/>)."
msgstr ""

#: index.docbook:231
#, no-c-format
msgid ""
"The name of the module under which the project will be stored. After the "
"import, the project can be checked out under this name. See <xref "
"linkend=\"checkingout\"/>"
" for more information. This is also the name of the corresponding directory "
"in the repository."
msgstr ""

#: index.docbook:231
#, no-c-format
msgid ""
"The vendor tag is historically used for tracking third-party sources. Just "
"use your user name if you have no better idea. It does not matter much what "
"you enter here."
msgstr ""

#: index.docbook:231
#, no-c-format
msgid ""
"This tag is also historically used for importing different versions of "
"third-party software. If you are not doing this, use the word "
"<literal>start</literal> or a string <literal>FOO_1_0</literal> where "
"<literal>FOO</literal> is the name of your project and "
"<literal>1.0</literal> is the version number of the imported release."
msgstr ""

#: index.docbook:277 index.docbook:349
#, no-c-format
msgid "Working directory"
msgstr ""

#: index.docbook:278
#, no-c-format
msgid ""
"This is the toplevel directory of the project you want to import. The import "
"starts from this directory and goes down recursively."
msgstr ""

#: index.docbook:285
#, no-c-format
msgid "Ignore files"
msgstr ""

#: index.docbook:286
#, no-c-format
msgid ""
"If you fill out this field, an additional <option>-I "
"<replaceable>filenames</replaceable></option> option is given go the "
"<command>cvs import</command> command. This entry is interpreted as a "
"whitespace-separated list of file name patterns which are ignored. In "
"general, a cleaner and less error-prone way to control which files go into "
"the repository is to create a directory with only the files which you want "
"to import and start from that. Nevertheless, this entry may be useful if the "
"project contains files which are by default ignored by &CVS;, e.g. files "
"with the name <filename>core</filename>. In such a case, simply enter the "
"character <literal>!</literal> in this field. This overrules &CVS;'s scheme "
"of ignored files, see <xref linkend=\"ignoredfiles\"/>."
msgstr ""

#: index.docbook:301
#, no-c-format
msgid "Import as binaries"
msgstr ""

#: index.docbook:302
#, no-c-format
msgid ""
"If you check this box, all files are imported in binary mode, i.e. an "
"argument <option>-kb</option> is given to <command>cvs import</command>."
msgstr ""

#: index.docbook:312
#, no-c-format
msgid "Checkout a module from the repository"
msgstr ""

#: index.docbook:313
#, no-c-format
msgid ""
"Before you work on a project under revision control, you must check out a "
"<emphasis>working copy</emphasis>."
msgstr ""

#: index.docbook:319 index.docbook:320
#, no-c-format
msgid "A screenshot of &cervisia;'s checkout dialog"
msgstr ""

#: index.docbook:327
#, no-c-format
msgid "Repository"
msgstr "Indawo yokugcina"

#: index.docbook:328
#, no-c-format
msgid ""
"The name of the &CVS; repository, also known as "
"<filename><envar>$CVSROOT</envar></filename>. If the repository is remote, "
"make sure that authentication works, see <xref "
"linkend=\"accessing-repository\"/>."
msgstr ""

#: index.docbook:337
#, no-c-format
msgid "Module"
msgstr "Umnqongo"

#: index.docbook:338
#, no-c-format
msgid ""
"The name of the module to be checked out. If you are working with an "
"existing repository, you have probably got this name from the administrator. "
"Alternatively, if the repository has a "
"<filename><envar>$CVSROOT</envar>/modules</filename> file, you can retrieve "
"a list of available modules by clicking on the <guibutton>Fetch "
"list</guibutton> button."
msgstr ""

#: index.docbook:350
#, no-c-format
msgid ""
"The directory under which the module should be checked out. Note that the "
"toplevel directory of the working copy is always created as a directory with "
"the name as the module under the directory given here."
msgstr ""

#: index.docbook:361
#, no-c-format
msgid "The main screen"
msgstr ""

#: index.docbook:362
#, no-c-format
msgid ""
"When you start &cervisia;, and open a working copy by choosing "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Open "
"Sandbox...</guimenuitem></menuchoice> you see a hierarchical view of the "
"current directory. According to the settings in your "
"<filename>.cvsignore</filename> files, the files you usually do not want to "
"include into the repository - like e.g. object files - are not shown. For "
"each file, you see its corresponding status. In the default setting, this is "
"\"Unknown\" because &cervisia; delays the fetching of information until you "
"choose <guimenuitem>Update</guimenuitem> or "
"<guimenuitem>Status</guimenuitem> from the <guimenu>File</guimenu> menu. "
"With this approach, you have a minimal amount of functionality available "
"even if you do not have a permanent connection to the &CVS; server."
msgstr ""

#: index.docbook:378 index.docbook:379
#, no-c-format
msgid "A screenshot of &cervisia;'s main view"
msgstr ""

#: index.docbook:385
#, no-c-format
msgid ""
"The commands in the File menu usually act only on the files which you have "
"marked. You may also mark directories. Now choose "
"<guimenuitem>Update</guimenuitem> from the <guimenu>File</guimenu> menu. "
"&cervisia; issues a"
msgstr ""

#: index.docbook:391
#, no-c-format
msgid "cvs update -n <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:395
#, no-c-format
msgid ""
"command to get status information for the marked files. Note that &cervisia; "
"goes recursively into subdirectories. only if you have the according option "
"in the <guimenu>Settings</guimenu> menu set. According to the respective "
"file's status, you now see an entry in the <guilabel>Status</guilabel> "
"column:"
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Locally Modified - This means you have modified the file compared to the "
"version in the repository."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Locally Added - This means the file does not exist in the repository, but in "
"your working directory and you have scheduled it for addition. The actual "
"insertion into the repository only happens after a commit."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Locally Removed - This means you have scheduled the file for removal, but it "
"still exists in the repository. The actual removal happens only after a "
"commit."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Needs Update - This is shown if a newer version of the file exists in the "
"repository, e.g. because someone commited a modification. Normally, you want "
"to update this file so you have an up-to-date version in your directory."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Needs Patch - This is essentially the same as before. The difference is only "
"the hint that in case of an update, the &CVS; server transfers only a patch "
"instead of the whole file to you."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Needs Merge - Indicates that a merge of the revision of this file in your "
"working directory with the version in the repository is necessary. This "
"typically happens if you have made modifications to the file file while "
"someone else has commited his modifications. If you choose to update, the "
"modifications in the repository are merged into your file. In case of a "
"conflict (i.e. if someone else has changed some of the same lines like you) "
"the new status is then \"Conflict\"."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Up to Date - Indicates that the file is identical with the version in the "
"repository."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Conflict - This is shown if this file still has conflict markers in it. "
"Maybe you have previously updated the file and not resolved the conflicts."
msgstr ""

#: index.docbook:402
#, no-c-format
msgid ""
"Not In CVS - Indicates that the file is not registered in the &CVS; "
"repository. If you want it to available for others, you should add it to the "
"repository. If not, you may consider adding it to your "
"<filename>.cvsignore</filename> file."
msgstr ""

#: index.docbook:462
#, no-c-format
msgid ""
"Now that you have got an overview of the current status of the CVS, you may "
"want to do an update. Mark some files (or the root of the directory tree "
"which is equivalent to marking all files in this directory). Now choose "
"<guimenuitem>Update</guimenuitem> from the <guimenu>File</guimenu>"
" menu. (Of course, you could have chosen this at the beginning of the "
"session). For some of the files the status may change now. Typically, files "
"which had \"Needs Patch\" or \"Needs Update\" are updated. So the following "
"new items are possible in the status column:"
msgstr ""

#: index.docbook:473
#, no-c-format
msgid "Updated - Shown if the file was updated from the repository."
msgstr ""

#: index.docbook:473
#, no-c-format
msgid ""
"Patched - Indicates that the &CVS; server has sent a patch for this file and "
"the patch has been sucessfully applied. If the patch was not successfull "
"because there was a conflict between your modifications and those someone "
"else commited to the repository, the status is now \"Conflict\"."
msgstr ""

#: index.docbook:488
#, no-c-format
msgid ""
"You may have noticed that according to the status of the file, its row has a "
"different color. The colors are chosen to somehow reflect the priority of "
"the status. For example, a file with a conflict is marked red to show you "
"that you have to resolve a conflict before you can continue working with the "
"file. If your directory contains a high number of files, you may "
"nevertheless lose the overview. To get more concise information about which "
"files have an unusual status, simply click on the header of the "
"<guilabel>Status</guilabel> column. The file list is then sorted by "
"priority, so you have all important information at the top of the list. To "
"get back to the alphabetically sorted view, click on the header of the "
"<guilabel>File name</guilabel> column."
msgstr ""

#: index.docbook:506
#, no-c-format
msgid "Working with files"
msgstr ""

#: index.docbook:508
#, no-c-format
msgid ""
"All commonly used &CVS; functionality is directly available in &cervisia;'s "
"main view. Commands usually act on several files at once, namely all which "
"currently selected. If the selection includes directories, its "
"interpretation depends on the settings made under the "
"<guimenu>Settings</guimenu> menu. For example, if "
"<menuchoice><guimenu>Settings</guimenu><guimenuitem>Commit and remove "
"recursively</guimenuitem></menuchoice> is checked and you choose "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Commit...</guimenuitem>"
"</menuchoice> while a directory is selected, then all files in the tree "
"under that directory are commited. Otherwise, only the regular files in the "
"directory itself are affected."
msgstr ""

#: index.docbook:521
#, no-c-format
msgid ""
"You can simply edit a file by double-clicking on it or pressing "
"<keycap>Return</keycap>. This starts the editor configured under "
"<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure "
"Cervisia...</guimenuitem></menuchoice> with the file name as argument."
msgstr ""

#: index.docbook:529
#, no-c-format
msgid "Adding files"
msgstr ""

#: index.docbook:531
#, no-c-format
msgid ""
"Adding files to a project requires two steps: First, the files must be "
"registered with &CVS;. To this end, mark all files to be added in "
"&cervisia;'s main view. Then, choose "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Add to "
"repository</guimenuitem></menuchoice>. &cervisia; issues a command"
msgstr ""

#: index.docbook:537
#, no-c-format
msgid "cvs add <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:541
#, no-c-format
msgid ""
"If the operation was successful, the status column should have \"Added to "
"repository\" for the added files."
msgstr ""

#: index.docbook:546
#, no-c-format
msgid ""
"In order to actually put the files into the repository, you must commit "
"them. This procedure has an important advantage: You can commit the files "
"together with modifications to other parts of the project. When doing this, "
"one can easily see (e.g. in commit emails) that all these changes are part "
"of a whole."
msgstr ""

#: index.docbook:554
#, no-c-format
msgid ""
"&CVS; is not designed to provide meaningful revision control for binary "
"files. For example, merging binary files normally does not make sense. "
"Furthermore, by default &CVS; performs keyword expansion (&eg; on the string "
"<literal>&dollar;Revision: 1.6 &dollar;</literal>) when a file is commited. "
"In binary files, such replacements may corrupt the file and make it "
"completely unusable. In order to switch this behavior off, you should commit "
"binary files (or other files, like Postscript) with a command line"
msgstr ""

#: index.docbook:564
#, no-c-format
msgid "cvs add -kb <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:568
#, no-c-format
msgid ""
"In &cervisia;, this is achieved by choosing "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Add "
"binary...</guimenuitem></menuchoice>"
msgstr ""

#: index.docbook:577
#, no-c-format
msgid "Removing files"
msgstr ""

#: index.docbook:579
#, no-c-format
msgid ""
"Like adding files, removing files is done in two steps: First, the files "
"have to be registered as removed by choosing "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Remove from "
"repository</guimenuitem></menuchoice> which issues the command"
msgstr ""

#: index.docbook:585
#, no-c-format
msgid "cvs remove -f <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:589
#, no-c-format
msgid ""
"After that, this modification to the sandbox has to be commited, possibly "
"together with other modifications to the project."
msgstr ""

#: index.docbook:594
#, no-c-format
msgid ""
"The above command only works if the file is up-to-date. Otherwise, you get "
"an error message. This behavior is sensible: If you have modified the file "
"compared to the version in the repository, or if someone else has made any "
"modifications, you will first want to check if you really want to discard "
"them."
msgstr ""

#: index.docbook:606
#, no-c-format
msgid "Adding and removing directories"
msgstr ""

#: index.docbook:608
#, no-c-format
msgid ""
"Directories are handled fundamentally different from ordinary files by "
"&CVS;. They are not under revision control, i.e. you cannot tell which "
"directories existed in the project at a certain time. Furthermore, "
"directories can never be explicitly removed (expect by removing them "
"directly in the repository)."
msgstr ""

#: index.docbook:616
#, no-c-format
msgid ""
"As a substitute, &CVS; follows the convention that a directory is \"not "
"existent\" in a version of the project if is is empty. This convention can "
"be enforced by using the option <option>-P</option> to <command>cvs "
"update</command> and <command>cvs checkout</command>"
". This option can be set in the menu "
"<menuchoice><guimenu>Settings</guimenu><guimenuitem>Prune Empty Directories "
"On Update</guimenuitem></menuchoice>."
msgstr ""

#: index.docbook:625
#, no-c-format
msgid "A directory can be added to the repository with the command"
msgstr ""

#: index.docbook:629
#, no-c-format
msgid "cvs add <replaceable>dirname</replaceable>"
msgstr ""

#: index.docbook:633
#, no-c-format
msgid ""
"which is implied by the menu item "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Add to "
"repository</guimenuitem></menuchoice>. Note that in contrast to adding "
"files, adding directories does not require a commit afterwards."
msgstr ""

#: index.docbook:644
#, no-c-format
msgid "Commiting files"
msgstr ""

#: index.docbook:646
#, no-c-format
msgid ""
"When you have made a certain amount of changes to your working copy, and you "
"want other developers to have access to them, you 'commit' them. With a "
"commit, you place your versions of the modified files as new revisions into "
"the repository. A subsequent update by another developer will bring your "
"modifications into his working copy."
msgstr ""

#: index.docbook:654
#, no-c-format
msgid ""
"In order to commit a couple of files, select them in &cervisia;'s main view "
"and choose "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Commit...</guimenuitem>"
"</menuchoice>."
msgstr ""

#: index.docbook:661
#, no-c-format
msgid "A screenshot of &cervisia;'s commit dialog"
msgstr ""

#: index.docbook:667
#, no-c-format
msgid ""
"You get a dialog that shows you on the top a list of the selected files and "
"on the bottom a log message for your changes. When you have finished the "
"dialog, the command"
msgstr ""

#: index.docbook:672
#, no-c-format
msgid ""
"cvs commit -m <replaceable>message</replaceable> "
"<replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:676
#, no-c-format
msgid ""
"is used. &cervisia; helps you in several ways to find a meaningful log "
"message: First, in the file list you can double-click a file or press "
"<keycap>Return</keycap> in order to see the changes you have made to the "
"file. Second, it gives you a list of log messages you have previously used "
"in a combo box. Third, this dialog is integrated with &cervisia;'s changelog "
"editor described below."
msgstr ""

#: index.docbook:685
#, no-c-format
msgid ""
"A common error you may encounter when commiting is <errorname>Up-to-date "
"check failed</errorname>. This indicates that someone has commited changes "
"to the repository since you last updated. Or more technically, that your "
"<literal>BASE</literal> revision is not the newest on its branch. In such a "
"case, &CVS; refuses to merge your modifications into the repository. The "
"solution is to update, resolve any conflicts and commit again. Of course, if "
"you are working on a software project, it is normally good style to check if "
"the program still works after you have updated - after all, there could be "
"bad interactions between your modifications and the other modifications "
"which break the code."
msgstr ""

#: index.docbook:698
#, no-c-format
msgid ""
"Another popular mistake results in the error message <errorname>Sticky tag "
"'X' for file 'X' is not a branch</errorname>. This happens if you try to "
"commit a file which you have previously brought to a certain revision or tag "
"with the command"
msgstr ""

#: index.docbook:698
#, no-c-format
msgid "<prompt>%</prompt><userinput>cvs update -r X</userinput>"
msgstr ""

#: index.docbook:698
#, no-c-format
msgid ""
"(which is &eg; used by the menu item "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Update to "
"Tag/Date...</guimenuitem></menuchoice>"
"). In such a case, the tag on the file gets sticky, i.e. further updates do "
"not bring you to the newest revision on the branch. If you want to commit "
"further revisions to the branch, you have to update to the branch tag before "
"you do further commits."
msgstr ""

#: index.docbook:717
#, no-c-format
msgid ""
"With &cervisia;, it is quite easy to maintain a ChangeLog file that is "
"compliant with the format layed out in the GNU coding guidelines. To use it, "
"choose <menuchoice><guimenu>File</guimenu><guimenuitem>Insert ChangeLog "
"entry...</guimenuitem></menuchoice>. If a file with the name "
"<filename>ChangeLog</filename> exists in the toplevel directory of your "
"sandbox, this file will be loaded and you have the possibility to edit it. "
"To this end, at the top of the file, an entry with the current date and your "
"user name (which can be configured as described in <xref "
"linkend=\"customize-general\"/>) is inserted. When you finish the dialog "
"this dialog by clicking <guibutton>OK</guibutton>, the next commit dialog "
"you open will have the log message set to the message you last entered in "
"the change log."
msgstr ""

#: index.docbook:736
#, no-c-format
msgid "Resolving conflicts"
msgstr ""

#: index.docbook:738
#, no-c-format
msgid ""
"Conflicts may occur whenever you have made changes to a file which was also "
"modified by another developer. The conflict is detected by &CVS; when you "
"update the modified file. &CVS; then tries to merge the modifications "
"commited by the other developer into your working copy. The merge fails if "
"both your and his modifications are in overlapping parts of the file, and "
"the &CVS; server issues and error message."
msgstr ""

#: index.docbook:747
#, no-c-format
msgid ""
"It is your job now to resolve these conflicts before you commit the file. "
"&CVS; will refuse to commit any files with conflicts until they have been "
"edited. Of course, you have a great amount of freedom when resolving a set "
"of conflicts: you can for each conflict decide to take one of the two "
"alternative versions. You can also decide that both approaches are are "
"broken and rewrite a whole routine or the complete file from scratch."
msgstr ""

#: index.docbook:756
#, no-c-format
msgid ""
"In &cervisia;'s main view, files with conflicts are indicated with "
"\"Conflict\" in the status column and with a red color. From the main view, "
"you can of course resolve conflicts the traditional way: just double-click "
"the file in question and edit it with your favourite editor. But you can "
"also choose to use the dialog available via "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Resolve...</guimenuitem>"
"</menuchoice>."
msgstr ""

#: index.docbook:766 index.docbook:767
#, no-c-format
msgid "A screenshot of &cervisia;'s resolve dialog"
msgstr ""

#: index.docbook:773
#, no-c-format
msgid ""
"On the top of the dialog, you see your version the file on the left hand "
"side and the version in the repository on the right hand side. The "
"differences between them are marked in red color. Below these two versions, "
"you can see the merged version which will be saved as soon as you click the "
"<guibutton>Save</guibutton> button."
msgstr ""

#: index.docbook:781
#, no-c-format
msgid ""
"You can switch between the differing sections by pressing "
"<guibutton>&lt;&lt;</guibutton> and <guibutton>&gt;&gt;</guibutton>. In the "
"lower middle of the dialog you can see which section is currently marked. "
"For example, <literal>2 of 8</literal> means that you are currently at the "
"second differing section of 8 total. Now can can decide section by section "
"which of the both versions you want to have in the merged file. By pressing "
"<guibutton>A</guibutton>, you take over the version you edited. By pressing "
"<guibutton>B</guibutton>, you take over the version from the repository."
msgstr ""

#: index.docbook:798
#, no-c-format
msgid "Obtaining information about files"
msgstr ""

#: index.docbook:801
#, no-c-format
msgid "Browsing cvs logs"
msgstr ""

#: index.docbook:803
#, no-c-format
msgid ""
"When you mark a file in the main view and choose <guimenuitem>Browse "
"log</guimenuitem> from the <guimenu>View</guimenu> menu, a"
msgstr ""

#: index.docbook:808
#, no-c-format
msgid "cvs log <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:812
#, no-c-format
msgid ""
"command is issued and a dialog is shown which reflects the version history "
"of the marked file."
msgstr ""

#: index.docbook:818 index.docbook:819
#, no-c-format
msgid "A screenshot of &cervisia;'s browse logs dialog"
msgstr ""

#: index.docbook:825
#, no-c-format
msgid ""
"You can choose to see the history as a tree or in list form. What you prefer "
"is of course a matter of taste and it depends on what information you are "
"interested in. The tree is an intuitive representation of what has been done "
"on different branches by which authors. As tooltips, you can see the "
"according log messages. The list is by its nature linear and therefore does "
"not give an immediate view of branches. On the other hand, it concentrates "
"more otherwise relevant information on less screen estate, namely the time "
"of each change of the file and the first part of the log message."
msgstr ""

#: index.docbook:836
#, no-c-format
msgid ""
"To obtain more information about a certain revision, you can click on it "
"either in the list or the tree view. The fields in the middle of the dialog "
"are then filled with the complete information provided by <command>cvs "
"log</command>. You can mark two revisions, called 'A' and 'B', which are "
"relevant if you make use of further features provided by the push buttons. "
"Revision 'A' can be chosen with the left mouse button, revision 'B' with the "
"middle one. In the list view, you can also navigate with with your cursor "
"keys. In order to mark revisions 'A' and 'B', use the keybindings "
"<keycombo><keycap>Ctrl</keycap><keycap>A</keycap></keycombo>, "
"<keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo>, resp."
msgstr ""

#: index.docbook:849
#, no-c-format
msgid ""
"If you press the button <guibutton>Annotate</guibutton>, you get a dialog "
"showing the text of file belonging to the revision marked as 'A'. Every line "
"is prefixed with the information about who edited this last time, and at "
"which revision this happened."
msgstr ""

#: index.docbook:856
#, no-c-format
msgid ""
"If you press the button <guibutton>Diff</guibutton>, a <command>cvs "
"diff</command> call is issued and you get a dialog in which all the "
"modifications between the two marked revisions are shown. To make it easy to "
"see the changes, different colors are used to mark lines which have been "
"added, removed or simply changed."
msgstr ""

#: index.docbook:867
#, no-c-format
msgid "Browsing the history"
msgstr ""

#: index.docbook:869
#, no-c-format
msgid ""
"If the used repository has logging enabled, &cervisia; can present you a "
"history of certain events like checkouts, commits, rtags, updates and "
"releases. Choose <guimenuitem>History</guimenuitem> from the "
"<guimenu>View</guimenu> menu, and &cervisia; will issue the command"
msgstr ""

#: index.docbook:876
#, no-c-format
msgid "cvs history -e -a"
msgstr ""

#: index.docbook:880
#, no-c-format
msgid ""
"This fetches the complete logging file from the server, i.e. a list of the "
"events for all users and all modules. This can be a huge amount of data!"
msgstr ""

#: index.docbook:885
#, no-c-format
msgid ""
"Now you can see the list of events, sorted by date. In the second column, "
"the type of the event is shown:"
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Checkout - The user who is displayed in the 'Author' column has checked out "
"a module"
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Tag - A user has used the command <command>cvs rtag</command>"
". Note that the usage of <command>cvs tag</command>"
" (as done by &cervisia;'s "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>"
"Tag/Branch...</guimenuitem></menuchoice> command) is not recorded in the "
"history database. This has historical reasons (see the &CVS; "
"<acronym>FAQ</acronym>)."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Release - A user has released a module. Actually, this command is rarely "
"used and not of much value."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Update, Deleted - A user has made an update on a file which was deleted in "
"the repository. As a consequence, the file was deleted in his working copy."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Update, Copied - A user has made an update on a file. A new version was "
"copied into working directory."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Update, Merged - A user has made an update on a file. The modifications in "
"the repository version on the file were merged into his working copy."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid ""
"Update, Conflict - A user has made an update on a file, and a conflict with "
"his own modifications was detected."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid "Commit, Modified - A user commited a modified file."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid "Commit, Added - A user added a file and commited it."
msgstr ""

#: index.docbook:890
#, no-c-format
msgid "Commit, Removed - A user removed a file and commited it."
msgstr ""

#: index.docbook:945 index.docbook:946
#, no-c-format
msgid "A screenshot of &cervisia;'s history dialog"
msgstr ""

#: index.docbook:952
#, no-c-format
msgid ""
"You can sort the list by other criteria simply by clicking on the respective "
"column header. In order to sort out the history entries you are interested "
"in, there are various filter options activated by check boxes:"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Show commit events - shows commits"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Show checkout events - shows checkouts"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Show tag events - shows taggings"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Show other events - shows events not included in the above"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Only user - shows only events caused by a certain usere"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Only filenames matching - filters file names by a regular expression"
msgstr ""

#: index.docbook:958
#, no-c-format
msgid "Only dirnames matching - filters directory names by a regular expression"
msgstr ""

#: index.docbook:968
#, no-c-format
msgid "Special characters recognized by the regular expression matcher are:"
msgstr ""

#: index.docbook:972
#, no-c-format
msgid ""
"<literal>x*</literal> matches any number of occurences of the character "
"<literal>x</literal>."
msgstr ""

#: index.docbook:972
#, no-c-format
msgid ""
"<literal>x+</literal> matches one or more of occurences of the character "
"<literal>x</literal>."
msgstr ""

#: index.docbook:972
#, no-c-format
msgid ""
"<literal>x?</literal> matches zero or one occurences of the character "
"<literal>x</literal>."
msgstr ""

#: index.docbook:972
#, no-c-format
msgid "<literal>^</literal> matches the start of the string."
msgstr ""

#: index.docbook:972
#, no-c-format
msgid "<literal>$</literal> matches the end of the string."
msgstr ""

#: index.docbook:972
#, no-c-format
msgid ""
"<literal>[a-cx-z]</literal> matches a set of characters, &eg; here the set "
"consisting of a,b,c,x,y,z."
msgstr ""

#: index.docbook:1008
#, no-c-format
msgid "Watching differences between revisions"
msgstr ""

#: index.docbook:1010
#, no-c-format
msgid ""
"There are several places in &cervisia; where you can ask for a window "
"showing the differences between revisions of a file:"
msgstr ""

#: index.docbook:1015
#, no-c-format
msgid ""
"In the main view, you can choose "
"<menuchoice><guimenu>View</guimenu><guimenuitem>Difference to "
"repository...</guimenuitem></menuchoice>. This is based on the command "
"<command>cvs diff</command> and shows you the differences between the "
"version in your sandbox and the version to which you last updated (also "
"known as <literal>BASE</literal>). This is in particular useful just before "
"you commit a file, so you can find an appropriate log message."
msgstr ""

#: index.docbook:1015
#, no-c-format
msgid ""
"In the dialog that is shown when a you commit a set of files, you can "
"request a difference window by selecting a file name in the selection list, "
"either by double-clicking it or by pressing <keycap>Return</keycap>"
". This is quite similar to using "
"<menuchoice><guimenu>View</guimenu><guimenuitem>Difference to "
"repository...</guimenuitem></menuchoice> with the respective file in the "
"main view."
msgstr ""

#: index.docbook:1015
#, no-c-format
msgid ""
"In the Browse logs dialog, you can mark two revisions of a file and request "
"a dialog showing the differences between them (see the section <xref "
"linkend=\"browsinglogs\"/>)."
msgstr ""

#: index.docbook:1043
#, no-c-format
msgid ""
"As you may have expected, &cervisia; does not just dump the output of the "
"<command>diff</command> command into your terminal, but shows you a "
"graphical view as seen in <xref linkend=\"screenshot-log\"/>."
msgstr ""

#: index.docbook:1050 index.docbook:1051
#, no-c-format
msgid "A screenshot of &cervisia;'s diff dialog"
msgstr ""

#: index.docbook:1057
#, no-c-format
msgid ""
"The text in the dialog is an improved variant of the text given by the diff "
"command with the <option>-u</option> option. You can see the differing "
"versions in two windows, with lines arranged such that you can do a "
"side-by-side comparison. That means, where text has been added or deleted, "
"the respective window shows empty lines with the marker "
"<literal>+++++</literal> at the left hand side. Elsewhere, you can see the "
"running number of each line in the left column."
msgstr ""

#: index.docbook:1066
#, no-c-format
msgid ""
"In the second column in the right window, you can see which kind of change "
"has been made. Possible types are <literal>Add</literal>, "
"<literal>Delete</literal> and <literal>Change</literal>. The respective "
"lines are marked in blue, green and red color. In the middle of the dialog a "
"compressed image of the color markers is shown. In this way, you can get a "
"quick overview of the overall changes to the file. You can also use the "
"position of the colored regions in the compressed image as an orientation "
"when you using the scroll bars."
msgstr ""

#: index.docbook:1077
#, no-c-format
msgid ""
"Normally, the scrollbars at the left and the right window are synchronized, "
"i.e. if you scroll on the left hand side, the right hand side is scrolled by "
"the same amount. You can change this by checking the box "
"<guibutton>Synchronize scroll bars</guibutton>."
msgstr ""

#: index.docbook:1084
#, no-c-format
msgid ""
"For information about how to customize the diff dialog, see <xref "
"linkend=\"customize-commands\"/>."
msgstr ""

#: index.docbook:1092
#, no-c-format
msgid "Watching an annotated view of a file"
msgstr ""

#: index.docbook:1094
#, no-c-format
msgid ""
"With the command <command>cvs annotate</command>, &CVS; offers the "
"possibility to see - for each line in a file - who has modified a line the "
"most recently. This view may be helpful in order to find out who has "
"introduced a change in the behavior of a program or who should be asked "
"about some change or bug in the code."
msgstr ""

#: index.docbook:1102
#, no-c-format
msgid ""
"&cervisia; gives you to access to this feature, but it further enriches the "
"information in an interactive way. You obtain an annotate view by choosing "
"<menuchoice><guimenu>View</guimenu><guimenuitem>Annotate...</guimenuitem>"
"</menuchoice>. Another possibility is to press the button "
"<guilabel>Annotate</guilabel> in the Browse log dialog. In <xref "
"linkend=\"screenshot-annotate\"/> you can see a screenshot of the dialog."
msgstr ""

#: index.docbook:1113
#, no-c-format
msgid "A screenshot of &cervisia;'s annotate dialog"
msgstr ""

#: index.docbook:1114 index.docbook:1235 index.docbook:1236
#, no-c-format
msgid "A screenshot of &cervisia;'s update to tag dialog"
msgstr ""

#: index.docbook:1120
#, no-c-format
msgid ""
"In the annotate dialog, you see in a window the latest version of the "
"selected file. In the columns before the text, you get some information "
"related to the latest change in each line. In the first column the revision "
"number is displayed. In the second column you see the name of the author of "
"that revision. Finally, in the third column you see the date of the latest "
"change in the line."
msgstr ""

#: index.docbook:1129
#, no-c-format
msgid ""
"Consequently, when a certain line appears strange to you or you assume a bug "
"there, you can immediately see who is responsible for that line. But not "
"only that, you can also find out <emphasis>why</emphasis> that line was "
"changed. To this end, move the mouse cursor over the respective revision "
"number. Then a tooltip appears that shows the log message and the date of "
"the change."
msgstr ""

#: index.docbook:1144
#, no-c-format
msgid "Advanced usage"
msgstr ""

#: index.docbook:1147
#, no-c-format
msgid "Tagging and branching"
msgstr ""

#: index.docbook:1149
#, no-c-format
msgid ""
"We discuss here only the technical aspects of tagging and branching. If you "
"are only a <emphasis>user</emphasis>, not the administrator of the "
"repository, you will probably not be confronted with the problem. If however "
"you are your own administrator, you should first read about the "
"non-technical problems that accompany branching, in order to get an "
"impression of how time-consuming and error-prone maintaining different "
"branches of a project can be. The appendix includes some references about "
"this topic."
msgstr ""

#: index.docbook:1159
#, no-c-format
msgid ""
"Simple tagging is something you usually do when a release is made, so that "
"you can at any time easily get back to the project state at that time. Tags "
"are usually given a name consisting of the project name and the version "
"number. For example, &cervisia; 1.0 is available under the tag "
"<literal>CERVISIA_1_0</literal>. &cervisia; enforces &CVS;'s strict rules "
"about what constitutes valid tag name. It must begin with a letter and may "
"contain letters, digits, hypens and underscores."
msgstr ""

#: index.docbook:1169
#, no-c-format
msgid ""
"Normally, you will want to tag the whole project (although &CVS; of course "
"allows you to tag only a subset). To this end, mark the toplevel directory "
"in the view and choose "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Tag/Branch</guimenuitem>"
"</menuchoice>. Now enter the name of the tag, press <keycap>Return</keycap> "
"and you are done!"
msgstr ""

#: index.docbook:1177
#, no-c-format
msgid ""
"Creating a branch is not significantly more difficult: In the tag dialog, "
"check the box <guibutton>Create branch with this tag</guibutton>. You can "
"also delete an existing tag: Choose "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Delete "
"tag</guimenuitem></menuchoice> in the main view."
msgstr ""

#: index.docbook:1185
#, no-c-format
msgid "There are several ways to update to a certain state of the project:"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid ""
"You can update to a certain tag. Use "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Update to "
"tag/date</guimenuitem></menuchoice>"
" for this. The same procedure is used for updating to a branch. The command "
"issued by &cervisia; is"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid "cvs update -r <replaceable>tag</replaceable>"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid ""
"You can update to a certain date. This may be useful if an error was "
"introduced in the project between two releases, you know approximately "
"between, and have an opinion on when that was. You can go to some date by "
"choosing <menuchoice><guimenu>Advanced</guimenu><guimenuitem>Update to "
"tag/date</guimenuitem></menuchoice> and checking the box <guibutton>Update "
"to date</guibutton>. In the field below, you can enter a wide variety of "
"date formats. One possible format is <literal>yyyy-mm-dd</literal> where "
"<literal>yyyy</literal> is the year, <literal>mm</literal> is the month "
"(numerically) and <literal>dd</literal> is the day. Alternatives are some "
"english phrases like <literal>yesterday</literal> or <literal>2 weeks "
"ago</literal>. When you use this option, &cervisia; uses the command"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid "cvs update -D <replaceable>date</replaceable>"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid ""
"Both options above make a tag or date 'sticky', i.e. you can not commit "
"further modifications on that files (unless the tag is a branch tag). In "
"order to get back to the trunk, also known as the branch with the name "
"<literal>HEAD</literal>, use the menu item "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Update to "
"HEAD</guimenuitem></menuchoice>. This results in a command"
msgstr ""

#: index.docbook:1189
#, no-c-format
msgid "cvs update <option>-A</option>"
msgstr ""

#: index.docbook:1242
#, no-c-format
msgid ""
"Another aspect of branching is the merging of modifications from a branch to "
"the current branch. If you are going to do this, choose "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Merge...</guimenuitem>"
"</menuchoice>. The dialog that appears now gives you two options:"
msgstr ""

#: index.docbook:1249
#, no-c-format
msgid ""
"Either you may merge all modifications done on a branch to the current "
"branch. In that case, check the box <guibutton>Merge from branch</guibutton>"
" and fill in the branch you want to merge from. &cervisia; will then execute "
"the command"
msgstr ""

#: index.docbook:1256
#, no-c-format
msgid "cvs update <option>-j</option> <replaceable>branchtag</replaceable>"
msgstr ""

#: index.docbook:1260
#, no-c-format
msgid ""
"The other possibility is that you want to merge only the modifications made "
"between two tags on a branch. This usually happens when you merge from the "
"same branch to the trunk several times. In that case, check the box "
"<guibutton>Merge modifications</guibutton> and enter (in the correct order) "
"the two relevant tags. This will result in a command"
msgstr ""

#: index.docbook:1268
#, no-c-format
msgid ""
"cvs update <option>-j</option> <replaceable>branchtag1</replaceable> "
"<option>-j</option> <replaceable>branchtag2</replaceable>"
msgstr ""

#: index.docbook:1276
#, no-c-format
msgid "Using watches"
msgstr ""

#: index.docbook:1278
#, no-c-format
msgid ""
"A watch is the conventional name for &CVS;'s feature to notify users of the "
"repository whenever a file has been changed or a developer has started "
"editing a file. The usage of watches requires that the file "
"<filename><envar>$CVSROOT</envar>/CVSROOT/notify</filename> has been set up "
"properly. This is not discussed here; if you need further information on the "
"setup from the administrator's point of view, read one of the books listed "
"in the appendix."
msgstr ""

#: index.docbook:1288
#, no-c-format
msgid "&cervisia;'s main support of watches are six menu items."
msgstr ""

#: index.docbook:1292
#, no-c-format
msgid ""
"In order to add a watch to one or several files, use "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Add "
"watch...</guimenuitem></menuchoice>. In the dialog you get, you can choose "
"to get notified for any of the types of events that &CVS; supports. For "
"example, if you only want to get notified when a file is commited, check the "
"boxes <guibutton>Only</guibutton> and <guibutton>Commits</guibutton>"
". If you want to get notified about any event related to the marked files, "
"check the box <guibutton>All</guibutton>. The command line used when you "
"accept the dialog is"
msgstr ""

#: index.docbook:1304
#, no-c-format
msgid "cvs watch add -a commit <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1308
#, no-c-format
msgid "or with a similar option, depending on the events you chose to watch."
msgstr ""

#: index.docbook:1312
#, no-c-format
msgid ""
"If you are not interested in some files anymore, you can remove your watches "
"on them. To this end, use "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Remove "
"watch...</guimenuitem></menuchoice>. In the dialog you get here, the same "
"options are offered as in the form you filled out when adding the watch. "
"When you confirm this dialog, &cervisia; issues the command"
msgstr ""

#: index.docbook:1321
#, no-c-format
msgid "cvs watch remove <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1325
#, no-c-format
msgid "possibly with an option <option>-a</option> for the chosen events."
msgstr ""

#: index.docbook:1329
#, no-c-format
msgid ""
"Finally, you can get a list of the people who are watching a couple of "
"files. Choose <menuchoice><guimenu>Advanced</guimenu><guimenuitem>Show "
"watchers</guimenuitem></menuchoice>. Using this menu item will result in a "
"command"
msgstr ""

#: index.docbook:1336
#, no-c-format
msgid "cvs watchers <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1340
#, no-c-format
msgid ""
"In the normal usage scenario of &CVS;, each developer works separately in "
"his checked out sandbox. When he wants to modify some file, he can just open "
"it in his editor and start working on it. Nobody else will know about this "
"work until the file gets commited."
msgstr ""

#: index.docbook:1347
#, no-c-format
msgid ""
"For some developer groups, this is not the preferred model of cooperation. "
"They want to get notified about someone working on a file <emphasis>as soon "
"as</emphasis> he starts with it. This can be achieved by some further &CVS; "
"commands. Before you start editing a file, select it in &cervisia;'s main "
"window and choose "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Edit</guimenuitem>"
"</menuchoice>. This will execute the command"
msgstr ""

#: index.docbook:1357
#, no-c-format
msgid "cvs edit <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1361
#, no-c-format
msgid ""
"This will send out a notification to everyone who has set an "
"<literal>edit</literal> watch on this file. It will also register you as an "
"<emphasis>editor</emphasis> of the file. You can obtain a list of all "
"editors of a certain file by using "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Show "
"editors</guimenuitem></menuchoice>. This is equivalent to typing on the "
"command line"
msgstr ""

#: index.docbook:1371
#, no-c-format
msgid "cvs editors <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1375
#, no-c-format
msgid ""
"An editing session is automatically ended when you commit the affected file. "
"At that moment, an <literal>unedit</literal> notification gets sent out to "
"all people who have registered a respective watch on the file. Of course, "
"sometimes you may not want to commit the file, but abort the editing session "
"and revert to the previous version of the file. This is done by using "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Unedit</guimenuitem>"
"</menuchoice>. Note that &cervisia; will not ask you for confirmation! That "
"means, if you use this menu item, all your work done since you used "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Edit</guimenuitem>"
"</menuchoice> will get lost. Precisely, &cervisia; uses the command line"
msgstr ""

#: index.docbook:1388
#, no-c-format
msgid "echo y | cvs unedit <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1392
#, no-c-format
msgid ""
"So far, we have only the discussed the case where edits and unedits are used "
"voluntarily be the developers. In addition &CVS; supports a model which "
"<emphasis>enforces</emphasis> the usage of these commands. The responsible "
"command to switch to this model is <command>cvs watch on</command> which we "
"will not explain further because it is mostly used by the administrator of "
"the repository. However, the important point from the developer's point of "
"view is that when the project enforces edits, working copies are checked out "
"<emphasis>readony</emphasis>. That means you cannot edit a file by default "
"(unless you use tricks like <command>chmod</command>). Only when you use "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Edit</guimenuitem>"
"</menuchoice>"
", the file becomes writable. It is made readonly again when you commit the "
"file or use "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Unedit</guimenuitem>"
"</menuchoice>."
msgstr ""

#: index.docbook:1408
#, no-c-format
msgid ""
"&cervisia;'s editor interface helps you with projects that enforce watches "
"also in a different way. If you just started an editor with a readonly file "
"by double-clicking on it or by using "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Edit</guimenuitem>"
"</menuchoice>, you would not be able to save your modifications later. This "
"has of course a reason: Whenever you want to change a file, you should run "
"<command>cvs edit</command>"
" before, so that all people watching the file get a notification that you "
"are working on it."
msgstr ""

#: index.docbook:1419
#, no-c-format
msgid ""
"In such a case, it is advisable to check the option "
"<menuchoice><guimenu>Settings</guimenu><guimenuitem>Do cvs edit "
"automatically when necessary</guimenuitem></menuchoice>. Now, whenever you "
"edit a file by double-clicking it, &cervisia; will run <command>cvs "
"edit</command> before the editor is actually executed. Then you can edit "
"your file as usual. When you have finished your work, commit your files, and "
"the commited files are readonly again."
msgstr ""

#: index.docbook:1433
#, no-c-format
msgid "Locking"
msgstr ""

#: index.docbook:1435
#, no-c-format
msgid ""
"The development model usually followed when &CVS; is used is called "
"<emphasis>unreserved checkouts</emphasis>. Each developer has his own "
"sandbox where he can edit files as he likes. If when the watch features - "
"like <command>cvs edit</command>"
" - are used, multiple developers can work on files synchronously. Changes "
"done by a different developer are merged into the local sandbox when an "
"update is performed."
msgstr ""

#: index.docbook:1444
#, no-c-format
msgid ""
"Other revision control systems - like <acronym>RCS</acronym> and "
"<application>SourceSafe</application> use a different model. When a "
"developer wants to a edit a file, he has to <emphasis>lock</emphasis> it. "
"Only one developer at a time can a lock a file. When he has finished "
"editing, the lock is released. On the one hand, with this model, conflicts "
"can never happen. On the other hand, two developers can not work on the same "
"file at the same time, even when their changes do not affect each other. "
"This can be a bottleneck. We are not going to discuss the organizational "
"benefits of both approaches. Nevertheless we mention that although &CVS; has "
"some support for locking, it is not the preferred way of working with &CVS;. "
"You should not use these features unless you are sure that your project "
"manager allows them."
msgstr ""

#: index.docbook:1458
#, no-c-format
msgid ""
"With &cervisia;, you lock files as follows. Select the desired files in the "
"main view. Then choose "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Lock</guimenuitem>"
"</menuchoice>. This runs the command"
msgstr ""

#: index.docbook:1465
#, no-c-format
msgid "cvs admin -l <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1469
#, no-c-format
msgid ""
"The reverse effect is achieved by using "
"<menuchoice><guimenu>Advanced</guimenu><guimenuitem>Unlock</guimenuitem>"
"</menuchoice>. This runs the command"
msgstr ""

#: index.docbook:1473
#, no-c-format
msgid "cvs admin -u <replaceable>filenames</replaceable>"
msgstr ""

#: index.docbook:1483
#, no-c-format
msgid "Customizing &cervisia;"
msgstr ""

#: index.docbook:1485
#, no-c-format
msgid ""
"&cervisia; can be customized in various ways to your needs and preferences. "
"Some options which you may want to change regularly are directly available "
"in the <guimenu>Settings</guimenu> menu. Others are united in a common "
"dialog which is available via "
"<menuchoice><guimenu>Option</guimenu><guimenuitem>Settings...</guimenuitem>"
"</menuchoice>."
msgstr ""

#: index.docbook:1495
#, no-c-format
msgid "General"
msgstr "Ngokubanzi"

#: index.docbook:1498
#, no-c-format
msgid "User name for the ChangeLog editor"
msgstr ""

#: index.docbook:1499
#, no-c-format
msgid ""
"Whenever you use the menu item "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Insert ChangeLog "
"entry...</guimenuitem></menuchoice>"
", a new ChangeLog entry is generated with the current date and your "
"username. Normally, it is considered good style to insert your full name and "
"your email address into each of your ChangeLog entries. Here you can "
"configure this."
msgstr ""

#: index.docbook:1510
#, no-c-format
msgid "Path to cvs"
msgstr ""

#: index.docbook:1511
#, no-c-format
msgid ""
"Here you can set the name (or path) to the <command>cvs</command> command "
"line client. By default, the executable found in your <envar>$PATH</envar> "
"is used by &cervisia;."
msgstr ""

#: index.docbook:1519
#, no-c-format
msgid "Editor"
msgstr "Umhleli"

#: index.docbook:1520
#, no-c-format
msgid ""
"Here you can configure which editor is called when a file in the main view "
"is double-clicked. To execute the editor, the entry made here is "
"concatenated with the file name and given to a shell. So it is acceptable to "
"use programs like <command>gnuclient</command> here. You can also enter the "
"string <envar>$EDITOR</envar> if your environment variable "
"<envar>$EDITOR</envar> points to an editor which opens an X11 window itself."
msgstr ""

#: index.docbook:1533
#, no-c-format
msgid "Various commands"
msgstr ""

#: index.docbook:1536
#, no-c-format
msgid "Number of context lines in the diff dialog"
msgstr ""

#: index.docbook:1537
#, no-c-format
msgid ""
"For the diff dialog, &cervisia; uses the option <option>-U</option> to "
"<command>diff</command>. This lets <command>diff</command> show only a "
"limited number of lines around each difference region. Here you can set the "
"argument to <option>-U</option>."
msgstr ""

#: index.docbook:1546
#, no-c-format
msgid "Additional options for cvs diff"
msgstr ""

#: index.docbook:1547
#, no-c-format
msgid ""
"Here you can add additional arguments to the <command>diff</command>. A "
"popular example is <option>-b</option> which lets <command>diff</command> "
"ignore changes in the amount of whitespace."
msgstr ""

#: index.docbook:1555
#, no-c-format
msgid "Tab width in diff dialog"
msgstr ""

#: index.docbook:1556
#, no-c-format
msgid ""
"In the diff dialog, tab characters present in your file or in the output of "
"the <command>diff</command> command are expanded into a fixed number of "
"space characters. By default, each tab is replaced by eight spaces, but here "
"you can setup a different number."
msgstr ""

#: index.docbook:1565
#, no-c-format
msgid "External diff frontend"
msgstr ""

#: index.docbook:1566
#, no-c-format
msgid ""
"When you use any of the features which show the diff dialog, like "
"<menuchoice><guimenu>View</guimenu><guimenuitem>Difference to "
"Repository...</guimenuitem></menuchoice>, &cervisia; invokes its internal "
"diff frontend. If you prefer a different one, like "
"<application>Kompare</application>, <application>TkDiff</application>, or "
"<application>xxdiff</application>, you can configure this here."
msgstr ""

#: index.docbook:1577
#, no-c-format
msgid ""
"Start "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Status</guimenuitem>"
"</menuchoice> automatically"
msgstr ""

#: index.docbook:1581
#, no-c-format
msgid ""
"When you check this option, the "
"<menuchoice><guimenu>File</guimenu><guimenuitem>Status</guimenuitem>"
"</menuchoice> command is started whenever you open a sandbox. As this "
"command may need some time and also needs a connection to the server for "
"remote repositories (making it unusable for offline usage), you can set this "
"option separately for local and remote repositories."
msgstr ""

#: index.docbook:1592
#, no-c-format
msgid "Timeout after which a progress dialog appears"
msgstr ""

#: index.docbook:1593
#, no-c-format
msgid ""
"Practically all &CVS; commands started in a sandbox which belongs to a "
"remote repository need a connection to the &CVS; server. This is affected by "
"delays from the network connection or a high load on the server. For this "
"reason, for commands like "
"<menuchoice><guimenu>View</guimenu><guimenuitem>Difference to "
"repository...</guimenuitem></menuchoice> &cervisia; opens a dialog which "
"indicates that the command is still running and which allows you to abort "
"it. Furthermore, this dialog is used to show you error messages from &CVS;. "
"As this dialog may become annoying after some time, it is shown only after a "
"certain timeout which is 4 seconds by default. Here you can change this "
"value."
msgstr ""

#: index.docbook:1607
#, no-c-format
msgid "Default compression level"
msgstr ""

#: index.docbook:1608
#, no-c-format
msgid ""
"The <command>cvs</command>"
" client compresses files and patches when they are transferred over a "
"network. With the command line option <option>-z</option>, the compression "
"level can be set. You can setup &cervisia; to use this option by configuring "
"the level here. The value set here is used only as a default; additionally "
"there is a per-repository setting available in "
"<menuchoice><guimenu>Repository</guimenu><guimenuitem>"
"Repositories...</guimenuitem></menuchoice>."
msgstr ""

#: index.docbook:1622
#, no-c-format
msgid "Look'n'feel"
msgstr ""

#: index.docbook:1625
#, no-c-format
msgid "Split main window horizontally"
msgstr ""

#: index.docbook:1626
#, no-c-format
msgid ""
"&cervisia;'s main window is normally splitted vertically into a window with "
"the file tree and one with the output. Alternatively, you can arrange them "
"horizontally."
msgstr ""

#: index.docbook:1634
#, no-c-format
msgid "Font for protocol window"
msgstr ""

#: index.docbook:1635
#, no-c-format
msgid ""
"This is the font used in the protocol window. This is the window showing the "
"output of the <command>cvs</command> client."
msgstr ""

#: index.docbook:1642
#, no-c-format
msgid "Font for annotate view"
msgstr ""

#: index.docbook:1643
#, no-c-format
msgid "This is the font used in the annotate view."
msgstr ""

#: index.docbook:1649
#, no-c-format
msgid "Font for diff view"
msgstr ""

#: index.docbook:1650
#, no-c-format
msgid "This is the font used in diff dialogs."
msgstr ""

#: index.docbook:1660
#, no-c-format
msgid "Appendix"
msgstr ""

#: index.docbook:1663
#, no-c-format
msgid "Ignored files"
msgstr ""

#: index.docbook:1665
#, no-c-format
msgid ""
"In its main file tree, &cervisia; does not display all files which are "
"actually there. This is analogue to <command>cvs</command> itself and helps "
"to avoid clutter caused by uninteresting stuff like object files. &cervisia; "
"tries to mimic <command>cvs</command>"
"'s behaviour as close as possible, i.e. it gets ignore lists from the "
"following sources:"
msgstr ""

#: index.docbook:1673
#, no-c-format
msgid ""
"A static list of entries which includes things like <literal "
"role=\"extension\">*.o</literal> and <filename>core</filename>"
". For details, see the &CVS; documentation."
msgstr ""

#: index.docbook:1673
#, no-c-format
msgid "The file <filename><envar>$HOME</envar>/.cvsignore</filename>."
msgstr ""

#: index.docbook:1673
#, no-c-format
msgid "The environment variable <envar>$CVSIGNORE</envar>."
msgstr ""

#: index.docbook:1673
#, no-c-format
msgid "The <filename>.cvsignore</filename> file in the respective directory."
msgstr ""

#: index.docbook:1693
#, no-c-format
msgid ""
"<command>cvs</command> itself additionally looks up entries in "
"<filename><envar>$CVSROOT</envar>/CVSROOT/cvsignore</filename>, but this is "
"a file on the server, and &cervisia; should be able to start up offline. If "
"you are working with a group that prefers to use an ignore list on the "
"server, it's probably a good idea to take a look which patterns are listed "
"there and to put them into the <filename>.cvsignore</filename> file in your "
"home directory."
msgstr ""

#: index.docbook:1707
#, no-c-format
msgid "Further information and support"
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"&CVS; comes with a complete set of documentation in the form of info pages, "
"known as \"The Cederqvist\". If it is properly installed, you get browse it "
"by typing in <userinput>info:/cvs</userinput> into the locationbar of "
"<application>kdehelp</application>, <application>khelpcenter</application> "
"resp. Alternative, you can just choose "
"<menuchoice><guimenu>Help</guimenu><guimenuitem>CVS "
"Info</guimenuitem></menuchoice>"
" in &cervisia;. An online HTML version of the Cederqvist is available <ulink "
"url=\"http://cvshome.org/docs/manual/cvs.html\">on the web</ulink>."
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"As this book is maintained together with &CVS;, it is normally the most "
"up-to-date reference. Nevertheless I recommend considering other "
"documentation for learning to use &CVS;, in partical the following."
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"Karl Fogel has written the excellent book <ulink "
"url=\"http://cvsbook.red-bean.com/index.html\">Open Source Development with "
"CVS</ulink>. About half of this book is about the development process of "
"Open Source software. The other half is a technical documentation of &CVS;. "
"Thankfully, the technical part of the book has been made freely "
"redistributable under the GPL, so that you can download a HTML version of "
"it. A list of errata is available on the webpage mentioned above."
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"&CVS; issues are discussed on a dedicated <ulink "
"url=\"http://mail.gnu.org/mailman/listinfo/info-cvs\">mailing list</ulink>."
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"There is USENET group <literal>comp.software.config-mgmt</literal>"
" dedicated to configuration management in general. &CVS; is only marginally "
"a topic in this group, but nevertheless it may be interesting for discussing "
"merits of various revision control systems compared to &CVS;."
msgstr ""

#: index.docbook:1709
#, no-c-format
msgid ""
"Last but not least, there is a (low traffic) <ulink "
"url=\"http://lists.sourceforge.net/mailman/listinfo/cervisia-user\">"
"&cervisia; mailing list</ulink>."
msgstr ""

#: index.docbook:1763
#, no-c-format
msgid "Command Reference"
msgstr "Uthelekiso Lomyalelo"

#: index.docbook:1768
#, no-c-format
msgid "The File Menu"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Open Sandbox...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Opens a sandbox in the main window."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Recent sandboxes</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Opens one of the sandboxes that were in use recently."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Insert ChangeLog entry...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Opens the ChangeLog editor, prepared such that you can add a new entry with "
"the current date."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycombo><keycap>&Ctrl;</keycap><keycap>U</keycap></keycombo>"
"</shortcut> <guimenu>File</guimenu><guimenuitem>Update</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Runs 'cvs update' on selected files and changes the status and revision "
"numbers in the listing accordingly."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycap>F5</keycap></shortcut> "
"<guimenu>File</guimenu><guimenuitem>Status</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Runs 'cvs -n update' on selected files and changes the status and revision "
"numbers in the listing accordingly."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Edit</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Opens the selected file in your editor."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Resolve...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Opens a dialog for the selected file which allows you to resolve merge "
"conflicts in it."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycap>#</keycap></shortcut> "
"<guimenu>File</guimenu><guimenuitem>Commit...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Allows you to commit the selected files."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycap>+</keycap></shortcut> "
"<guimenu>File</guimenu><guimenuitem>Add to Repository...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Allows you to add the selected files to the repository."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Add binary...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Allows you to add the selected files to the repository as binaries "
"(<command>cvs add<option>-kb</option></command>)."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycap>-</keycap></shortcut> "
"<guimenu>File</guimenu><guimenuitem>Remove from Repository...</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Allows you to remove the selected files from the repository."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "<guimenu>File</guimenu><guimenuitem>Revert</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"Discards any local changes you have made to the selected files and reverts "
"to the version in the repository (Option <option>-C</option> to <command>"
"cvs update</command>)."
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid ""
"<shortcut><keycombo><keycap>&Ctrl;</keycap><keycap>Q</keycap></keycombo>"
"</shortcut> <guimenu>File</guimenu><guimenuitem>Exit</guimenuitem>"
msgstr ""

#: index.docbook:1770
#, no-c-format
msgid "Quits &cervisia;."
msgstr ""

#: index.docbook:1906
#, no-c-format
msgid "The View Menu"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"<shortcut><keycap>Escape</keycap></shortcut> "
"<guimenu>View</guimenu><guimenuitem>Stop</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "Aborts any running subprocesses."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"<shortcut><keycombo><keycap>&Ctrl;</keycap><keycap>L</keycap></keycombo>"
"</shortcut> <guimenu>View</guimenu><guimenuitem>Browse Log...</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "Shows the revision tree of the selected file."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"<shortcut><keycombo><keycap>&Ctrl;</keycap><keycap>A</keycap></keycombo>"
"</shortcut> <guimenu>View</guimenu><guimenuitem>Annotate...</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"Shows an annotated view of the selected file, i.e. a view where you can for "
"each line see which author modified it last."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"<shortcut><keycombo><keycap>&Ctrl;</keycap><keycap>D</keycap></keycombo>"
"</shortcut> <guimenu>View</guimenu><guimenuitem>Difference to "
"repository...</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"Shows the differences between the selected file in the sandbox and the "
"revision you last updated (BASE)."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "<guimenu>View</guimenu><guimenuitem>Last Change...</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"Shows the differences between the revision of the selected file you last "
"updated (BASE) and the revision before."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "<guimenu>View</guimenu><guimenuitem>History...</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "Shows the &CVS; history as reported by the server."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "<guimenu>View</guimenu><guimenuitem>Unfold file tree</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid ""
"Opens all branches in the file tree so that you can see all files and "
"directories."
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "<guimenu>View</guimenu><guimenuitem>Fold file tree</guimenuitem>"
msgstr ""

#: index.docbook:1908
#, no-c-format
msgid "Closes all branches in the file tree."
msgstr ""

#: index.docbook:1997
#, no-c-format
msgid "The Advanced Menu"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Tag/Branch...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Tags or branches the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Delete tag...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Removes a given tag from the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Update to Tag/Date...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Brings the selected files to a given tag or date, making it sticky."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Update to HEAD...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Brings the selected files to the respective HEAD revision."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Merge...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid ""
"Merges either a given branch or the modifications between two tags into the "
"selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Add watch...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Adds a watch for a set of events on the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Remove watch...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Removes a watch for a set of events from the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Show watchers</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Lists the watchers of the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Edit</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Runs <command>cvs edit</command> on the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Unedit</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Runs <command>cvs unedit</command> on the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Show editors</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Runs <command>cvs editors</command> on the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Lock</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Locks the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "<guimenu>Advanced</guimenu><guimenuitem>Unlock</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Unlocks the selected files."
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid ""
"<guimenu>Advanced</guimenu><guimenuitem>Create patch against "
"repository...</guimenuitem>"
msgstr ""

#: index.docbook:1999
#, no-c-format
msgid "Creates a patch from the modifications in your sandbox."
msgstr ""

#: index.docbook:2134
#, no-c-format
msgid "The Repository Menu"
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "<guimenu>Repository</guimenu><guimenuitem>Checkout...</guimenuitem>"
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "Opens a dialog which allows you to checkout a module from a repository."
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "<guimenu>Repository</guimenu><guimenuitem>Import...</guimenuitem>"
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "Opens a dialog which allows you to import a package into the repository."
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "<guimenu>Repository</guimenu><guimenuitem>Repositories...</guimenuitem>"
msgstr ""

#: index.docbook:2136
#, no-c-format
msgid "Configures a list of repositories you often use and how to access them."
msgstr ""

#: index.docbook:2173
#, no-c-format
msgid "The Settings Menu"
msgstr "Izicwangciso ze Menu"

#: index.docbook:2175
#, no-c-format
msgid "<guimenu>Settings</guimenu><guimenuitem>Configure Shortcuts...</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid "Opens a dialog for configuring keybindings."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid "<guimenu>Settings</guimenu><guimenuitem>Configure Cervisia...</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid "Opens a dialog for customizing &cervisia;."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"<guimenu>Settings</guimenu><guimenuitem>Create directories on "
"update</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"Determines whether updates create directories in the sandbox which weren't "
"there before (Option <option>-d</option> to <command>cvs update</command>)."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"<guimenu>Settings</guimenu><guimenuitem>Prune empty directories on "
"update</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"Determines whether updates remove empty directories in the sandbox. (Option "
"<option>-P</option> to <command>cvs update</command>)."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid "<guimenu>Settings</guimenu><guimenuitem>Update recursively</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"Determines whether updates are recursive (Option <option>-r</option> to "
"<command>cvs update</command>)."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"<guimenu>Settings</guimenu><guimenuitem>Commit and remove "
"recursively</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"Determines whether commits and removes are recursive (Option "
"<option>-r</option> to <command>cvs add</command>, <command>cvs "
"remove</command> resp.)."
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"<guimenu>Settings</guimenu><guimenuitem>Do cvs edit automatically when "
"necessary</guimenuitem>"
msgstr ""

#: index.docbook:2175
#, no-c-format
msgid ""
"Determines whether <command>cvs edit</command> is executed automatically "
"whenever you edit a file."
msgstr ""

#: index.docbook:2251
#, no-c-format
msgid "The Help Menu"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid ""
"<shortcut><keycap>F1</keycap></shortcut> "
"<guimenu>Help</guimenu><guimenuitem>Cervisia Handbook</guimenuitem>"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid ""
"Invokes the KDE Help system starting at the &cervisia; help pages. (this "
"document)."
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "<guimenu>Help</guimenu><guimenuitem>Report Bug...</guimenuitem>"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "Opens the Bug report dialog."
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "<guimenu>Help</guimenu> <guimenuitem>About &cervisia;</guimenuitem>"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "This will display version and author information."
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "<guimenu>Help</guimenu><guimenuitem>About KDE</guimenuitem>"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "This displays the KDE version and other basic information."
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "<guimenu>Help</guimenu><guimenuitem>CVS Manual</guimenuitem>"
msgstr ""

#: index.docbook:2253
#, no-c-format
msgid "Opens the &CVS; info pages in the KDE help system."
msgstr ""

#: index.docbook:2313
#, no-c-format
msgid "Credits And Licenses"
msgstr "Amatyala ne Layisenisi"
