# Occitan translation of anjuta.
# Copyright (C) 2001-2006, 2007 Free Software Foundation, Inc.
# This file is under the same licence as the anjuta package.
#
# Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>, 2007.
msgid ""
msgstr ""
"Project-Id-Version: oc\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2008-03-11 14:08+0000\n"
"PO-Revision-Date: 2007-12-28 10:28+0100\n"
"Last-Translator: Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>\n"
"Language-Team: Occitan <ubuntu-l10n-oci@lists.ubuntu.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);X-Generator: KBabel 1.11.4\n"

#: C/anjuta-manual.xml:25(title)
msgid "Anjuta IDE Manual"
msgstr ""

#: C/anjuta-manual.xml:26(edition)
msgid "v1.0.0"
msgstr "v1.0.0"

#: C/anjuta-manual.xml:28(para)
msgid "Manual for the Anjuta IDE"
msgstr ""

#: C/anjuta-manual.xml:32(firstname)
msgid "Naba"
msgstr "Naba"

#: C/anjuta-manual.xml:33(surname)
msgid "Kumar"
msgstr "Kumar"

#: C/anjuta-manual.xml:36(firstname)
msgid "Andy"
msgstr "Andy"

#: C/anjuta-manual.xml:37(surname)
msgid "Piper"
msgstr "Piper"

#: C/anjuta-manual.xml:40(firstname)
msgid "Biswapesh"
msgstr "Biswapesh"

#: C/anjuta-manual.xml:41(surname)
msgid "Chattopadhyayr"
msgstr "Chattopadhyayr"

#: C/anjuta-manual.xml:44(firstname)
msgid "Johannes"
msgstr "Johannes"

#: C/anjuta-manual.xml:45(surname)
msgid "Schmid"
msgstr "Schmid"

#: C/anjuta-manual.xml:49(year)
msgid "2001-2002"
msgstr "2001-2002"

#: C/anjuta-manual.xml:50(year)
msgid "2006"
msgstr "2006"

#: C/anjuta-manual.xml:51(holder)
msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"

#: C/anjuta-manual.xml:52(holder)
msgid "Johannes Schmid"
msgstr "Johannes Schmid"

#: C/anjuta-manual.xml:56(para)
msgid ""
"Permission is granted to copy, distribute and/or modify this document under "
"the terms of the <citetitle>GNU Free Documentation License</citetitle>, "
"Version 1.1 or any later version published by the Free Software Foundation "
"with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. "
"You may obtain a copy of the <citetitle>GNU Free Documentation License</"
"citetitle> from the Free Software Foundation by visiting <ulink type=\"http"
"\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to: Free "
"Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-"
"1301, USA."
msgstr ""

#: C/anjuta-manual.xml:68(para)
msgid ""
"Many of the names used by companies to distinguish their products and "
"services are claimed as trademarks. Where those names appear in any GNOME "
"documentation, and those trademarks are made aware to the members of the "
"GNOME Documentation Project, the names have been printed in caps or initial "
"caps."
msgstr ""

#: C/anjuta-manual.xml:79(revnumber)
msgid "Anjuta Manual 2.1.0"
msgstr "Manual d'Anjuta 2.1.0"

#: C/anjuta-manual.xml:80(date)
msgid "2007"
msgstr "2007"

#: C/anjuta-manual.xml:82(para)
msgid "Johannes Schmid<email>jhs@gnome.org</email>"
msgstr "Johannes Schmid<email>jhs@gnome.org</email>"

#: C/anjuta-manual.xml:84(para)
msgid "Anjuta Team"
msgstr "Còla d'Anjuta"

#: C/anjuta-manual.xml:3(title) C/anjuta-manual.xml:6(title)
msgid "Introduction"
msgstr "Introduccion"

#: C/anjuta-manual.xml:4(para)
msgid ""
"<application>Anjuta</application> is a versatile Integrated Development "
"Environment (IDE) for the GNOME desktop. It features a number of advanced "
"programming facilities that include project management, application wizards, "
"an on-board interactive debugger, an integrated glade UI designer, "
"integrated devhelp API help, an integrated valgrind memory profiler, an "
"integrated gprof performance profiler, a class generator, a powerful source "
"editor, source browsing, and more. is a versatile Integrated Development "
"Environment"
msgstr ""

#: C/anjuta-manual.xml:15(para)
msgid ""
"Anjuta DevStudio has been designed to be simple to operate yet powerful "
"enough to fulfill all your programming needs. Many features have evolved "
"since the early days and several very attractive ones added. Our focus is on "
"delivering power and usability at the same time without overloading your "
"senses and making your software development a pleasurable process. We will "
"always be busy getting you one of the best IDE experiences by straighting up "
"all the neat features and stabilizing it. We hope you will have a good time "
"using Anjuta. If not, please help us make it better by reporting bugs and "
"suggestions. Here are some of the things you will find in Anjuta."
msgstr ""

#: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
msgid "Anjuta in action"
msgstr ""

#: C/anjuta-manual.xml:37(para)
msgid ""
"Anjuta has a very flexible and advanced docking system that allows you to "
"layout all views in whatever way you like. You can drag and drop the views "
"using drag bars and re-arrange the layout. The layouts are persistent for "
"each project so you can maintain different layouts required by projects. All "
"dock views are minimizable to avoid clutter in main window. Minimized views "
"appear as icons on left side of main window. All menu actions are "
"configurable either by type-in-the-menu (the usual GNOME way) or by a "
"dedicated shortcuts configuration UI."
msgstr ""

#: C/anjuta-manual.xml:48(para)
msgid ""
"Please report any problems with <application>Anjuta</application> - this "
"will help to improve the software, as well as helping the Open Source "
"community."
msgstr ""

#: C/anjuta-manual.xml:2(title)
msgid "Getting Familiar with Anjuta"
msgstr ""

#: C/anjuta-manual.xml:5(title)
msgid "Menus and shortcuts"
msgstr "Menuts e acorchis"

#: C/anjuta-manual.xml:6(para)
msgid ""
"At the top of the <application>Anjuta</application> main window is the "
"menubar. Almost all of the functions are available by activating the "
"appropriate menu item. The functions have been grouped according to their "
"type. For example, the file operations have been grouped into the "
"<guisubmenu>File</guisubmenu> menu."
msgstr ""

#: C/anjuta-manual.xml:15(title)
msgid "Menubar"
msgstr "Barra de menuts"

#: C/anjuta-manual.xml:17(screeninfo)
msgid "Anjuta menubar"
msgstr "La barra de menuts d'Anjuta"

#: C/anjuta-manual.xml:22(para)
msgid ""
"Most of the menus and submenus can be detached. Click on the detach bar (the "
"dashed line just above the first menu item). Once the menu is detached, it "
"will become an independent window."
msgstr ""

#: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
msgid "File menu"
msgstr ""

#: C/anjuta-manual.xml:36(para)
msgid ""
"Shortcut keys are available for many of the menu options. All of the "
"shortcut keys are shown alongside the corresponding menu items. A useful "
"reference to the shortcut keys which are not directly attached with the menu "
"is also available in the next section. Some useful shortcuts are listed here."
msgstr ""

#: C/anjuta-manual.xml:46(para)
msgid ""
"<emphasis>Switch Editor page:</emphasis> CTRL-TAB (forward) and CTRL-SHIFT-"
"TAB (backward) -- The pages could also be switched by right clicking on the "
"notebook tabs and selecting an editor tab (useful when all the tabs in the "
"editor are not visible at once). Some desktop configuration may already have "
"these shortcut keys assigned. In that case, you will need to reconfigure "
"them (not in anjuta, because they are fixed) if you want to avail these "
"shortcuts."
msgstr ""

#: C/anjuta-manual.xml:55(para)
msgid ""
"<emphasis>Context Help:</emphasis> SHIFT-F1 -- Keep the cursor on the word "
"(for example, the function name) for which you want to get the API help and "
"press the shortcut. Context help only works if you have "
"<application>DevHelp</application> installed. If you do not have "
"<application>DevHelp</application> installed, the context help menu and "
"toolbar button will be inactive. You can get it from <application>DevHelp</"
"application> website. You will also have to install the related "
"<application>DevHelp</application> books."
msgstr ""

#: C/anjuta-manual.xml:65(para)
msgid ""
"<emphasis>Auto complete:</emphasis> CTRL-ENTER -- Press the shortcut with "
"the cursor placed at the end of incomplete word and a list of words matching "
"the remaining part will appear. Scroll and select the right word from the "
"list if you find one."
msgstr ""

#: C/anjuta-manual.xml:72(para)
msgid ""
"<emphasis>More shortcuts:</emphasis> Look for the shortcut keys displayed on "
"right side of the menu item labels. They could also be changed as explained "
"in the tip below."
msgstr ""

#: C/anjuta-manual.xml:79(title)
msgid "Customize shortcuts"
msgstr ""

#: C/anjuta-manual.xml:80(para)
msgid ""
"You can change the default shortcuts by using <menuchoice><guisubmenu>Edit</"
"guisubmenu><guimenuitem>Preferences</guimenuitem></menuchoice> and selecting "
"the <interface> Shortcuts</interface> tab."
msgstr ""

#: C/anjuta-manual.xml:91(title)
msgid "Main Window"
msgstr "Fenèstra principala"

#: C/anjuta-manual.xml:92(para)
msgid ""
"In the main window, there are several views which can be reordered by "
"dragging on their title bars. They can also be minimized by clicking on the "
"minimize buttons on the left of title bars."
msgstr ""

#: C/anjuta-manual.xml:101(para)
msgid ""
"The <interface>Documents window</interface> will have one document active at "
"a time (if there are any files opened). All of the file commands will apply "
"to this active document. You can switch to any page by clicking on the page "
"tab. You can do the same by right-clicking on the page tabs and choosing the "
"document from the pop-up menu that will appear. This is especially useful "
"when you have a lot of files opened, but not all of them are visible in the "
"page tab area."
msgstr ""

#: C/anjuta-manual.xml:112(para)
msgid ""
"The <interface>Project window</interface> shows a tree of the project files "
"if you have a project opened. Otherwise, the <interface>Project window</"
"interface> is usually hidden. Double-clicking on any item in the "
"<interface>Project window</interface> will open that file."
msgstr ""

#: C/anjuta-manual.xml:120(para)
msgid ""
"The <interface>Files window</interface> shows a file tree. If no project is "
"open, the file tree usually points to the file system root but you can "
"change it in the preferences. If a project is open it shows all files inside "
"the project. Double clicking opens a file in the appropriate application as "
"configured in the gnome mime preferences. Right click opens a popup-menu "
"which gives you choices how to open the file."
msgstr ""

#: C/anjuta-manual.xml:129(para)
msgid ""
"The <interface>Symbols window</interface> shows shows a tree of available "
"symbols in the project generated from ctags parser. Double clicking opens an "
"editor window with the corresponding file and line."
msgstr ""

#: C/anjuta-manual.xml:134(para)
msgid ""
"There is also a <interface>Search tab</interface> in the Symbols window "
"where you can search for symbols."
msgstr ""

#: C/anjuta-manual.xml:140(para)
msgid ""
"The <interface>Message window</interface> will list all the messages (both "
"<filename>stdout</filename> and <filename>stderr</filename> outputs) when an "
"external command is executed. The <interface>Message window</interface> is "
"usually hidden, but appears as soon as an external command is executed, such "
"as during file or project compilation, debugging sessions, searches, and "
"many other operations. <application>Anjuta</application> also adds its own "
"messages here when necessary."
msgstr ""

#: C/anjuta-manual.xml:148(para)
msgid ""
"The colors used to display the messages are important. Messages displayed in "
"the standard foreground color (usually Black) are normal messages. Those "
"displayed in Blue are important messages such as errors or other "
"information. Messages shown in Red are <emphasis>Hot Linked</emphasis>. "
"Double-clicking on such a message will take you to the particular file and "
"line number specified in the message."
msgstr ""

#: C/anjuta-manual.xml:156(para)
msgid ""
"For example, when you compile a file which contains bugs, some red messages "
"will appear showing what the problems are, and where they occur. Double-"
"clicking on such messages will open the file and highlight the line "
"containing the error."
msgstr ""

#: C/anjuta-manual.xml:164(para)
msgid ""
"The <interface>Terminal window</interface> is a terminal emulation where you "
"can type commands just like in the gnome-terminal."
msgstr ""

#: C/anjuta-manual.xml:172(title)
msgid "Session management"
msgstr "Gestion de session"

#: C/anjuta-manual.xml:173(para)
msgid ""
"All of the settings, including the window sizes and window positions, are "
"saved when you exit <application>Anjuta</application>. Session management is "
"still under development, so you should not exit <application>Anjuta</"
"application> with any unsaved documents. <application>Anjuta</application> "
"will display a warning if you try to exit with unsaved documents still open."
msgstr ""

#: C/anjuta-manual.xml:2(title)
msgid "File Operations"
msgstr ""

#: C/anjuta-manual.xml:6(title)
msgid "Creating a New File and inserting texts"
msgstr ""

#: C/anjuta-manual.xml:8(title)
msgid "Creating New File"
msgstr "Crear un fichièr novèl"

#: C/anjuta-manual.xml:9(para)
msgid ""
"To create a new file, choose <menuchoice><guisubmenu>File</"
"guisubmenu><guimenuitem>New</guimenuitem></menuchoice> from the menubar, or "
"click on the <guibutton>New File</guibutton> button on the toolbar. A new "
"page will appear in the editor (or a new window if the parent document is "
"windowed). This new document will be named <filename>newfile#1</filename>, "
"<filename>newfile#2</filename>, <filename>newfile#3</filename> and so on."
msgstr ""

#: C/anjuta-manual.xml:19(title)
msgid "Save file"
msgstr "Enregistrar lo fichièr"

#: C/anjuta-manual.xml:20(para)
msgid ""
"You should save new documents as soon as possible to avoid any data loss in "
"case of a crash."
msgstr ""

#: C/anjuta-manual.xml:27(title)
msgid "File Wizard"
msgstr ""

#: C/anjuta-manual.xml:38(title)
msgid "New File Wizard"
msgstr ""

#: C/anjuta-manual.xml:40(screeninfo) C/anjuta-manual.xml:153(screeninfo)
msgid "The Open File dialog"
msgstr ""

#: C/anjuta-manual.xml:28(para)
msgid ""
"A wizard can also be used to create a new file. To create a new file, choose "
"<menuchoice><guisubmenu>File</guisubmenu><guisubmenu>New</"
"guisubmenu><guimenuitem>File</guimenuitem></menuchoice> from the menubar. "
"This will open the New File Wizard dialog. Select the file type. Enter the "
"File name. The suffix will be automatically added. You can add a license "
"information (according to your license choice) and a header. In case of C-C+"
"+ header file, you can also add an header template. Click <guibutton>OK</"
"guibutton> to validate the creation. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:45(para)
msgid ""
"<application>Anjuta</application> occasionally also creates new files during "
"some operations. For example, some CVS operations, such as diff, file log, "
"file status etc, create new files and add the output there. These could be "
"saved in real file just like normal new files."
msgstr ""

#: C/anjuta-manual.xml:53(title)
msgid "Inserting Macros"
msgstr "Inserir de macròs"

#: C/anjuta-manual.xml:54(para)
msgid "Macros can be used to quickly edit repetitive sequences of text."
msgstr ""

#: C/anjuta-manual.xml:58(para)
msgid "Macro plugin must be activated."
msgstr ""

#: C/anjuta-manual.xml:63(title)
msgid "Inserting"
msgstr "Inserir"

#: C/anjuta-manual.xml:64(para)
msgid ""
"Two types of macros are available: Anjuta macros and User macros (My "
"macros). Anjuta macros are not modifiable by the user. On the other hand, "
"User macros can be defined and modified by the user."
msgstr ""

#: C/anjuta-manual.xml:69(para)
msgid ""
"To insert macro, move the cursor at the desired place. Select "
"<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
"guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. The dialog "
"window appears. Select the wanted macro in the list. The result of the macro "
"expansion is displayed in the window and a summary is shown in the dialog "
"window. Choose <guibutton>Insert</guibutton>. The expanded macro text is "
"inserted at the cursor position."
msgstr ""

#: C/anjuta-manual.xml:82(title)
msgid "Macro"
msgstr "Macrò"

#: C/anjuta-manual.xml:84(screeninfo)
msgid "The Macro dialog"
msgstr ""

#: C/anjuta-manual.xml:77(para)
msgid ""
"Another possibility to insert macro is to select "
"<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
"guisubmenu><guimenuitem>Insert Macro...</guimenuitem></menuchoice>, then to "
"press the wanted macro shortcut. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:91(title)
msgid "Defining Macros"
msgstr ""

#: C/anjuta-manual.xml:92(para)
msgid ""
"From the Insert-Macro window, choose <guibutton>Add</guibutton> or select "
"<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
"guisubmenu><guimenuitem>Add Macro... </guimenuitem></menuchoice>. The Add/"
"Edit window appears. Enter the macro name, choose or define a category and "
"enter a shortcut. Then edit text relative to your macro. The character ' | ' "
"will indicate the cursor position after the macro insertion. Choose "
"<guibutton>OK</guibutton>. The macro is added to the list."
msgstr ""

#: C/anjuta-manual.xml:100(para)
msgid ""
"The user can also erase a macro by selecting it in the list (only My Macros) "
"then by choosing <guibutton>Remove</guibutton>."
msgstr ""

#: C/anjuta-manual.xml:108(title)
msgid "Add/Edit Macro"
msgstr "Apondre/modificar una macrò"

#: C/anjuta-manual.xml:110(screeninfo)
msgid "Add Edit dialog"
msgstr ""

#: C/anjuta-manual.xml:104(para)
msgid ""
"Same manner, macro can be edited and modified by selecting it in the list "
"then by choosing <guibutton>Edit</guibutton>. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:117(title)
msgid "Macro Keywords"
msgstr ""

#: C/anjuta-manual.xml:118(para)
msgid ""
"Macros Keywords are available. They can be integrated in the macro "
"definitions. The names of these macro Keywords start and finish by the "
"character ' @ '."
msgstr ""

#: C/anjuta-manual.xml:126(title)
msgid "Keyword Macro"
msgstr ""

#: C/anjuta-manual.xml:128(screeninfo)
msgid "The Keyword macro"
msgstr ""

#: C/anjuta-manual.xml:122(para)
msgid ""
"Available macro keywords are : @DATE_TIME@, @DATE_YMD@, @DATE_Y@, "
"@USER_NAME@, @FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, "
"@TABSIZE@, @INDENTSIZE@, @USETABS@. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:139(title)
msgid "Opening and Saving Files"
msgstr ""

#: C/anjuta-manual.xml:151(title)
msgid "Open File dialog"
msgstr ""

#: C/anjuta-manual.xml:143(para)
msgid ""
"<emphasis>Opening a file:</emphasis> To open an existing file, choose "
"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Open</guimenuitem></"
"menuchoice> from the menubar, click on the <guibutton>Open</guibutton> "
"button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>O</"
"keycap></keycombo>. This will display the <interface>Open File</interface> "
"dialog. <placeholder-1/> Select or enter the file you want to open, then "
"click <guibutton>Open</guibutton>. To open more than one file at once, "
"select multiple files to open by first pressing CTRL and clicking the files "
"in the list and press <guibutton>Open</guibutton>. If you change your mind, "
"click <guibutton>Cancel</guibutton> to dismiss the dialog without opening "
"the file."
msgstr ""

#: C/anjuta-manual.xml:172(title)
msgid "Open Multiple File dialog"
msgstr ""

#: C/anjuta-manual.xml:174(screeninfo)
msgid "The Open File dialog in multiple-select mode"
msgstr ""

#: C/anjuta-manual.xml:164(para)
msgid ""
"For selecting multiple files at once, select a file in the dialog and press "
"CTRL once. This will bring the file selection dialog in multiple-select mode "
"and multiple files could be selected from the list. Multiple file select "
"mode is similar to single file select mode, except that the file operation "
"(for which the file selection was being done) will be performed for all the "
"selected files. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:179(para)
msgid ""
"The <emphasis>Show Hidden Files</emphasis>, if switched on (Click right), "
"will make the hidden files (files starting with \".\"; visible in the file "
"list. Depress it to make them hide. <application>Anjuta</application> file "
"selection dialog also has inbuilt file type filter. Select the appropriate "
"file type filter in the dialog and the file list will be limited to the "
"files of the selected type only."
msgstr ""

#: C/anjuta-manual.xml:199(screeninfo)
msgid "The Save As File"
msgstr ""

#: C/anjuta-manual.xml:189(para)
msgid ""
"<emphasis>Saving a file:</emphasis> To save a file, choose "
"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save</guimenuitem></"
"menuchoice> from the menubar, click on the <guibutton>Save</guibutton> "
"button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>S</"
"keycap></keycombo>. This will save the file. If the file is new, a "
"<interface>Save As</interface> dialog will appear. Enter a filename and "
"click <guibutton>Save</guibutton> to save the new file with the name "
"supplied. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:204(title)
msgid "File auto save"
msgstr "Enregistrament automatic de fichièr"

#: C/anjuta-manual.xml:205(para)
msgid ""
"If you have enabled auto-save, it will not auto-save any new files. You must "
"first save them manually. The same applies to the <guimenuitem>Save All</"
"guimenuitem> option: it will not save new files, if you haven't saved them "
"first manually. <emphasis>You must save a file manually before auto-save or "
"<guimenuitem>Save All</guimenuitem> will work with it.</emphasis>"
msgstr ""

#: C/anjuta-manual.xml:216(para)
msgid ""
"<emphasis>Saving a file with a different name:</emphasis> You can explicitly "
"save a file with a new filename. To do this, choose "
"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save As</guimenuitem></"
"menuchoice> from the menubar. A <interface>Save As</interface> dialog will "
"appear prompting you to enter the new filename. Enter the name and click "
"<guibutton>Save</guibutton>."
msgstr ""

#: C/anjuta-manual.xml:224(title)
msgid "File save as overwrite"
msgstr ""

#: C/anjuta-manual.xml:225(para)
msgid ""
"When you use <guimenuitem>Save As</guimenuitem> with an existing file, the "
"original is not deleted. It is left unchanged since the last save. If a file "
"with the new filename already exists, a confirmation dialog will appear, to "
"ensure that you want to overwrite it. Clicking <guibutton>Yes</guibutton> "
"will overwrite the file with the file you are saving."
msgstr ""

#: C/anjuta-manual.xml:237(para)
msgid ""
"<emphasis>Closing a file:</emphasis> To close a file, choose "
"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Close</guimenuitem></"
"menuchoice> from the menubar, or click on the <guibutton>Close</guibutton> "
"button on the toolbar. The file could also be closed by clicking the "
"<guibutton>cross</guibutton> in the filename tab. This will close the "
"current file. If the file is not saved, or is a new file, then "
"<application>Anjuta</application> will prompt you to save the file before "
"closing it."
msgstr ""

#: C/anjuta-manual.xml:254(title)
msgid "Editing Files"
msgstr "Modificar de fichièrs"

#: C/anjuta-manual.xml:255(para)
msgid ""
"<application>Anjuta</application> has a number of helpful features which aid "
"in editing and working with source files. The following sections describe "
"how to use some of the interesting features available."
msgstr ""

#: C/anjuta-manual.xml:261(title) C/anjuta-manual.xml:270(title)
msgid "Editor Margins"
msgstr ""

#: C/anjuta-manual.xml:272(screeninfo) C/anjuta-manual.xml:320(screeninfo)
#: C/anjuta-manual.xml:415(screeninfo)
msgid "The Tags toolbar"
msgstr ""

#: C/anjuta-manual.xml:262(para)
msgid ""
"<emphasis>Editor Margins:</emphasis> Editor margins are the small area on "
"the left of the editor for some special purposes. There are three editor "
"margins available and all of them may not be available when you first start "
"<application>anjuta</application>. They are Line numbers margin, Markers "
"margin and Code fold margin. By default (that is, when you run "
"<application>anjuta</application> for the first time) only the code fold "
"margin will be visible. The rest could be made visible from "
"<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></"
"menuchoice>. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:277(para)
msgid ""
"The <emphasis>Line Numbers Margin</emphasis> is largest of all the three "
"margins (and slightly darker then rest) and displays the document's line "
"numbers. <emphasis>Line Number Margin</emphasis> could be made visible or "
"invisible by toggling <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
"guisubmenu><guimenuitem>Line Numbers Margin</guimenuitem></menuchoice>. "
"Single left clicking on this margin will select the whole line (including "
"the last newline, if present). You can set the font properties for line "
"number margin in the preferences."
msgstr ""

#: C/anjuta-manual.xml:286(para)
msgid ""
"<emphasis>Markers Margin</emphasis> is the next margin which can be made "
"visible or invisible by selecting <menuchoice><guimenu>View</"
"guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Markers Margin</"
"guimenuitem></menuchoice>. This margin displays graphical icons to mark the "
"given line. The markers which will be displayed in this margin are Bookmark "
"marker (rectangular blue colored icon), Breakpoint marker (circular red "
"colored) and Line indicator (pointed arrow yellow colored). Bookmark marker "
"is used to indicate bookmarked lines which could be toggled from "
"<menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</"
"guisubmenu><guimenuitem> Toggle Bookmark</guimenuitem></menuchoice> with the "
"cursor placed in that line. The breakpoint marker is used in debugger to "
"mark the line with debugging breakpoints (see debugging section for more "
"details). The line indicator marker is used to indicate a line when we do a "
"jump from another part, for example when navigating the bookmarks and during "
"single stepping in debugger."
msgstr ""

#: C/anjuta-manual.xml:299(para)
msgid ""
"<emphasis>Code folding margin</emphasis> is where the folding tree is "
"visible. Clicking on these folding tree nodes will fold or unfold the code "
"blocks. An underline will also be drawn below the folded line to make it "
"more obvious that a block of code has been folded below the line. For more "
"details on code folding, see the section <emphasis>Code Folding</emphasis> "
"below."
msgstr ""

#: C/anjuta-manual.xml:307(title)
msgid "Invisible margin marker"
msgstr ""

#: C/anjuta-manual.xml:318(title)
msgid "Editor markers when markers margin is invisible"
msgstr ""

#: C/anjuta-manual.xml:308(para)
msgid ""
"If the marker margin is not visible, the markers will be displayed by "
"changing the background color of the line. For example, if there a "
"breakpoint marker is set in a line and the marker margin is not visible, "
"that line will be displayed with red background. Similarly, for bookmark "
"marker and line indication marker, the background color of the line will be "
"sky blue and yellow, respectively. If you do not like this (perhaps due to "
"some contrasting themes), enable the <emphasis>Markers Margins</emphasis> "
"from <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
"guisubmenu><guimenuitem>Markers Margin</guimenuitem></menuchoice>. "
"<placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:328(title)
msgid "Editor Guides"
msgstr ""

#: C/anjuta-manual.xml:329(para)
msgid ""
"The editor could be made to make certain document information, which "
"otherwise are normally not visible. <emphasis>Indentation guides, white "
"spaces and line end characters</emphasis> are such information which could "
"be made visible for editing comfort. They could be make visible or invisible "
"by toggling the menu items in <menuchoice><guimenu>View</"
"guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. Indentation guides are "
"the small dotted lines drawn to connect the matching braces in the source "
"code. When the cursor is over one such matching braces, the dotted "
"indentation guide is highlighted to give a visual region of the indentation."
msgstr ""

#: C/anjuta-manual.xml:339(title) C/anjuta-manual.xml:341(screeninfo)
msgid "Editor with guides"
msgstr ""

#: C/anjuta-manual.xml:347(title)
msgid "Syntax highlighting"
msgstr ""

#: C/anjuta-manual.xml:348(para)
msgid ""
"<application>Anjuta</application> can highlight many different languages. "
"This is usually done automatically by determining the type of the file from "
"the file extension. If <application>Anjuta</application> cannot determine "
"the type of the file, there will be no syntax highlighting. You can "
"explicitly force a particular highlight style by selecting the style from "
"the menu <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
"guisubmenu><guisubmenu> Highlight Mode</guisubmenu></menuchoice>."
msgstr ""

#: C/anjuta-manual.xml:359(title)
msgid "Code folding"
msgstr ""

#: C/anjuta-manual.xml:360(para)
msgid ""
"Source files which have block coding properties (such as C, C++, Pascal, "
"Java etc.), have the advantage of working with <emphasis>code folds</"
"emphasis>. All of the code blocks in the source file can be folded or "
"unfolded by clicking on the fold points in the fold margin of the "
"<interface>Editor window</interface> (usually a +/- symbol or up/down "
"arrow). These fold points automatically appear for source files which use "
"code blocks."
msgstr ""

#: C/anjuta-manual.xml:368(para)
msgid ""
"Code folding is especially useful when editing big source files that run to "
"thousands of lines. Once the folds are closed, the document appears to "
"become smaller, facilitating easy browsing and editing of the file."
msgstr ""

#: C/anjuta-manual.xml:374(para)
msgid ""
"Please note that code folding and editor guides are only available in the "
"scintilla based editor."
msgstr ""

#: C/anjuta-manual.xml:381(title)
msgid "Auto-formatting source code"
msgstr ""

#: C/anjuta-manual.xml:382(para)
msgid ""
"If the current file is a C or C++ source or header file, then it is possible "
"to automatically indent (auto-format) the file. This gives a clean look to "
"the source code, increases legibility, reduces the likelihood of syntax "
"errors, and above all it saves time. This can be performed by choosing "
"<menuchoice><guimenu>Edit</guimenu><guimenuitem>Auto Indent </guimenuitem></"
"menuchoice> on the menubar. Change the style of formatting by customizing "
"the choices in the preferences."
msgstr ""

#: C/anjuta-manual.xml:396(title)
msgid "Symbol browser and Browsing Files"
msgstr ""

#: C/anjuta-manual.xml:397(para)
msgid ""
"All C and C++ source and header files can be browsed using the tags in the "
"files. All of the open C and C++ source and header files are scanned for "
"available tags (a \"tag\" refers to a function definition, structure, macro, "
"etc.). Please note that Tag and Symbol is used synonymously in this manual, "
"except when referring to Tags browser and Symbol browser, which two "
"different interfaces."
msgstr ""

#: C/anjuta-manual.xml:413(title) C/anjuta-manual.xml:436(title)
msgid "Tags toolbar"
msgstr ""

#: C/anjuta-manual.xml:419(title)
msgid "Function symbols"
msgstr ""

#: C/anjuta-manual.xml:420(para)
msgid ""
"Function prototype and definition, if present in the same file, can be "
"usually distinguished from the corresponding line numbers. Prototypes "
"usually comes before the definition, so they are likely to have smaller line "
"numbers."
msgstr ""

#: C/anjuta-manual.xml:406(para)
msgid ""
"<emphasis>Tags Browser:</emphasis> Tags browser is available on the Browser "
"toolbar. It shows a list of tags available in the currently active file "
"(source file). If there is no tags (or symbols) available in the file, the "
"tags list will be invisible and a \"No Tags\" will be displayed instead. The "
"tags in this list are shown along with the line numbers where they are "
"found. If there are multiple symbols with the same name, they will be shown "
"with different line numbers. <placeholder-1/><placeholder-2/>"
msgstr ""

#: C/anjuta-manual.xml:438(screeninfo)
msgid "Symbol browser"
msgstr ""

#: C/anjuta-manual.xml:428(para)
msgid ""
"<emphasis>Symbol Browser:</emphasis> If there is a project open, "
"<application>Anjuta</application> will scan for tags in all of the source "
"and header files of the project. This way it is possible to go to any "
"function definition, structure definition, class definition etc. without "
"manually opening the file. You don't even have to know which file that tag "
"is found in (except in the case of function definitions). The symbol browser "
"lists all the available symbols in the project. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:446(title)
msgid "Tags synchronization"
msgstr ""

#: C/anjuta-manual.xml:447(para)
msgid ""
"You don't have to worry about the synchronization and update of the tag "
"database. <application>Anjuta</application> will take care of everything. "
"You just have to decide which tag you want to go to!"
msgstr ""

#: C/anjuta-manual.xml:458(title)
msgid "Searching for and Replacing text in files"
msgstr ""

#: C/anjuta-manual.xml:460(title)
msgid "Searching"
msgstr "Recèrca"

#: C/anjuta-manual.xml:461(para)
msgid ""
"To search for a <emphasis>text</emphasis> or <emphasis>regular expression</"
"emphasis> string in the current file, choose <menuchoice><guimenu>Edit</"
"guimenu><guisubmenu>Search</guisubmenu><guimenuitem>Find</guimenuitem></"
"menuchoice> or press <keycombo><keycap>Ctrl</keycap><keycap>F</keycap></"
"keycombo>. This will open the <interface>Find</interface> dialog."
msgstr ""

#: C/anjuta-manual.xml:468(para)
msgid ""
"Use the text box to specify the string to search for, and select whether it "
"is a normal string or a regular expression (RegExp). It is also possible to "
"specify the direction of search, whether the search is case-sensitive or "
"not, and the scope of the search. Click <guibutton>Search</guibutton> to "
"start searching."
msgstr ""

#: C/anjuta-manual.xml:474(para)
msgid ""
"If the search is successful, the matched text in the document will be "
"highlighted, marked... (according to the search action choice). If the "
"search is not successful, a <emphasis>The match \"search text\" was not "
"found</emphasis> message will be displayed."
msgstr ""

#: C/anjuta-manual.xml:479(para)
msgid ""
"If you want to search again, click on the <guibutton>Search</guibutton> "
"button on the main toolbar or press <keycombo><keycap>Ctrl</"
"keycap><keycap>G</keycap></keycombo>. This will find the next match "
"(<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>G</keycap></"
"keycombo> for the previous match). You can even change the search text when "
"you do this. Enter the new string in the <guilabel>Search Expression</"
"guilabel> text box in the main toolbar."
msgstr ""

#: C/anjuta-manual.xml:488(title)
msgid "Search Text dialog"
msgstr ""

#: C/anjuta-manual.xml:493(para)
msgid "To stop a long research, choose <guibutton>Stop</guibutton> button."
msgstr ""

#: C/anjuta-manual.xml:496(para)
msgid ""
"If the \"Basic Search\" option is selected in the Setting window, the search "
"direction can be chosen from the Expression window."
msgstr ""

#: C/anjuta-manual.xml:501(title)
msgid "Basic Search Text dialog"
msgstr ""

#: C/anjuta-manual.xml:508(title)
msgid "Specifying Search Range"
msgstr ""

#: C/anjuta-manual.xml:509(para)
msgid ""
"In the \"Search Target dialog\", define the search location and the action "
"to be done in case of search success."
msgstr ""

#: C/anjuta-manual.xml:513(para)
msgid "The maximum number actions can be defined by User."
msgstr ""

#: C/anjuta-manual.xml:517(title)
msgid "Search Target dialog"
msgstr ""

#: C/anjuta-manual.xml:522(para)
msgid "The user can select where the text will be searched."
msgstr ""

#: C/anjuta-manual.xml:526(title)
msgid "Search Target In choice"
msgstr ""

#: C/anjuta-manual.xml:532(title)
msgid "Searching in Files"
msgstr ""

#: C/anjuta-manual.xml:533(para)
msgid ""
"To find text in your project, select \"search in\" <menuchoice><guimenu> All "
"Project Files</guimenu></menuchoice>."
msgstr ""

#: C/anjuta-manual.xml:537(para)
msgid ""
"Enter the text you want to search and specify search options (case-"
"sensitive, complete words ...). Click <guibutton>Search</guibutton> to start "
"searching."
msgstr ""

#: C/anjuta-manual.xml:542(para)
msgid ""
"To find text in File list, select \"search in\" <menuchoice><guimenu> "
"Specifying File List</guimenu></menuchoice>. Define the Search variables. "
"Click <guibutton>Search</guibutton> to start searching."
msgstr ""

#: C/anjuta-manual.xml:548(title)
msgid "Search File Pattern"
msgstr ""

#: C/anjuta-manual.xml:558(title)
msgid "Specifying Search Action"
msgstr ""

#: C/anjuta-manual.xml:559(para)
msgid "The user selects which action will be done in case of search success."
msgstr ""

#: C/anjuta-manual.xml:562(para)
msgid ""
"According to the previous selections (Search in, Search direction ...), some "
"actions could be unavailable."
msgstr ""

#: C/anjuta-manual.xml:567(title)
msgid "Search Target Action choice"
msgstr ""

#: C/anjuta-manual.xml:575(title) C/anjuta-manual.xml:583(title)
msgid "Replacing"
msgstr ""

#: C/anjuta-manual.xml:576(para)
msgid ""
"Search and replace is similar to just finding text, except that you also "
"specify the replace text in the <guilabel>Replace With:</guilabel> text box, "
"and whether or not you want to be prompted before the replace takes place "
"(Replace First Match or Replace All Matches)."
msgstr ""

#: C/anjuta-manual.xml:588(para)
msgid ""
"Choose <guibutton>Replace</guibutton> to replace the matched text or "
"<guibutton>Forward</guibutton> to jump to the next matched text."
msgstr ""

#: C/anjuta-manual.xml:595(title)
msgid "Search Setting"
msgstr ""

#: C/anjuta-manual.xml:596(para)
msgid ""
"The user has the possibility of saving the setting of his search options."
msgstr ""

#: C/anjuta-manual.xml:599(para)
msgid ""
"Item highlighted in red is the active item. Item by default is the search "
"setting which is loaded at Anjuta launching."
msgstr ""

#: C/anjuta-manual.xml:604(title)
msgid "Search Setting dialog"
msgstr ""

#: C/anjuta-manual.xml:615(title)
msgid "Printing a file"
msgstr "Estampar un fichièr"

#: C/anjuta-manual.xml:624(title)
msgid "Print preview of a C file"
msgstr ""

#: C/anjuta-manual.xml:626(screeninfo)
msgid "Print preview"
msgstr "Previsualizacion de l'estampatge"

#: C/anjuta-manual.xml:616(para)
msgid ""
"Print preview could be taken by selecting <menuchoice><guisubmenu>File</"
"guisubmenu><guimenuitem>Print Preview</guimenuitem></menuchoice>. It will "
"render the current file and present a preview of the print. Source codes "
"which are highlighted in the editor are also highlighted similarly in the "
"print (or preview). Additional options are available to print with the line "
"numbers, wrapped lines and/or headers in the <guilabel>Printing</guilabel> "
"tab of your editor plugin preferences. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:633(title)
msgid "Print Preferences"
msgstr "Preferéncias d'estampatge"

#: C/anjuta-manual.xml:635(screeninfo)
msgid "Print preferences"
msgstr "Preferéncias d'estampatge"

#: C/anjuta-manual.xml:640(para)
msgid ""
"When you are ready to print and satisfied with the preview, select "
"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print</guimenuitem></"
"menuchoice> or <guibutton>Print</guibutton> from the print preview window. "
"This will bring up the actual print dialog as shown below. Select the "
"appropriate print parameters and print the file with <guibutton>Print</"
"guibutton> on it."
msgstr ""

#: C/anjuta-manual.xml:647(para)
msgid ""
"Landscaped or portrait page layout, paper size, page orientation and paper "
"type could also be set. Remember to set them up properly according to your "
"printer, otherwise printing may not come up properly."
msgstr ""

#: C/anjuta-manual.xml:654(title) C/anjuta-manual.xml:656(screeninfo)
msgid "Print Dialog"
msgstr ""

#: C/anjuta-manual.xml:3(title)
msgid "Project Management"
msgstr "Gestion de projècte"

#: C/anjuta-manual.xml:5(para)
msgid ""
"Anjuta has a powerful Project Manager plugin which can open most <ulink type="
"\"info\" url=\"info:automake\">automake/autoconf</ulink> based projects. It "
"might fail on some oddly configured projects, but as long as the project is "
"done by using automake/autoconf in a typical way, it should work."
msgstr ""

#: C/anjuta-manual.xml:13(para)
msgid ""
"The neat thing is that it does not store any project information beyond what "
"is already available in project structure. That is, there is no separate "
"project data maintained by Anjuta and all project processing are done "
"directly within the project structure. This allows the project to be "
"maintained or developed outside Anjuta without having to so-called 'porting' "
"or 'switching' to a new platform. Since technically Anjuta projects are just "
"automake projects, mixed development of it (Anjuta and non-Anjuta users) or "
"switching back and forth between Anjuta and other tools is quite possible "
"without any hindrance."
msgstr ""

#: C/anjuta-manual.xml:26(title)
msgid "Creating a New Project"
msgstr "Crear un projècte novèl"

#: C/anjuta-manual.xml:28(title)
msgid "New project from template"
msgstr ""

#: C/anjuta-manual.xml:29(para)
msgid ""
"The project wizard plugin uses a powerful template processing engine called "
"<application>autogen</application>. All new projects are created from "
"templates that are written in <application>autogen</application> syntax. "
"Project wizard lets you create new projects from a selection of project "
"templates. The selection includes simple generic, flat (no subdirectory), gtk"
"+, gnome, java, python projects and more. New templates can be easily "
"downloaded and installed since they are just a collection of text files."
msgstr ""

#: C/anjuta-manual.xml:41(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>File</"
"guisubmenu><guisubmenu>New</guisubmenu><guimenuitem>Project …</guimenuitem></"
"menuchoice> to start the application wizard. Read the <interface>first page</"
"interface> carefully. Click on <guibutton>Next</guibutton> to proceed."
msgstr ""

#: C/anjuta-manual.xml:48(para)
msgid ""
"Select the type of application you want to create in the <interface>second "
"page</interface>. Click on <guibutton>Next</guibutton> to proceed."
msgstr ""

#: C/anjuta-manual.xml:54(para)
msgid ""
"On the next pages, enter all necessary details for your project. You can "
"change these settings later also, but it is advisable to put them right in "
"first run to maintain the project's integrity. White spaces or any non-"
"alphanumeric characters, except underscore (_) and dash (-), are not allowed "
"in many of the entry boxes that would follow (except perhaps the "
"<guilabel>Author</guilabel> text box)."
msgstr ""

#: C/anjuta-manual.xml:65(para)
msgid ""
"You can also specify whether your project will have "
"<emphasis>internationalization support</emphasis> using "
"<application>gettext</application> (read the <ulink type=\"info\" url=\"info:"
"gettext\">gettext info page</ulink> for more details). This gives your "
"project multilingual support for different regional languages such as "
"English, French, Dutch etc.. The rest of the options are for setting whether "
"the GNU copyright statement should appear in the comments at the top of each "
"file, and enabling GNOME desktop menu information if necessary. Shared "
"library support allows adding shared library modules later in the project. "
"If you plan to have libraries in your project, it would be good to enable. "
"Depending on the project type that is being created, there would be other "
"information requested."
msgstr ""

#: C/anjuta-manual.xml:81(para)
msgid ""
"The final step is to verify the information you have just supplied. Click on "
"<guibutton>Finish</guibutton> to start generating the project."
msgstr ""

#: C/anjuta-manual.xml:86(para)
msgid ""
"Once project generation is over, you can try it out by building the project "
"and executing it."
msgstr ""

#: C/anjuta-manual.xml:92(title)
msgid "Importing Projects"
msgstr "Importar de projèctes"

#: C/anjuta-manual.xml:93(para)
msgid ""
"The import project feature is used to import an already existing project and "
"convert it into <application>anjuta</application> project. Activate the "
"import project wizard from <menuchoice><guimenu>File</guimenu><guimenu>New</"
"guimenu><guimenuitem>Project from existing sources</guimenuitem></"
"menuchoice> and follow instructions dictated by the wizard. Once the project "
"is imported, it could be opened in <application>anjuta</application> "
"subsequently just like any other <application> anjuta</application> project."
msgstr ""

#: C/anjuta-manual.xml:103(para)
msgid ""
"The import project features only works if your existing project is using "
"<ulink type=\"info\" url=\"info:automake\">autoconf/automake</ulink> and, to "
"a very limited extend, plain makefiles."
msgstr ""

#: C/anjuta-manual.xml:113(title)
msgid "Loading and Saving Projects"
msgstr ""

#: C/anjuta-manual.xml:115(title)
msgid "Loading Projects"
msgstr ""

#: C/anjuta-manual.xml:116(para)
msgid ""
"To open a project, choose the menu item <menuchoice><guisubmenu>File</"
"guisubmenu><guimenuitem>Open …</guimenuitem></menuchoice>. Select the "
"project file (<filename>*.anjuta</filename>) in the dialog and click "
"<guibutton>OK</guibutton>."
msgstr ""

#: C/anjuta-manual.xml:123(para)
msgid ""
"If the project has recently been opened, then you will find it listed in the "
"menu <menuchoice><guisubmenu>File</guisubmenu><guisubmenu>Recent</"
"guisubmenu></menuchoice>. Choose the project file from the list, and the "
"project will be opened."
msgstr ""

#: C/anjuta-manual.xml:128(para)
msgid ""
"As soon as a project is opened, <application>Anjuta</application> will enter "
"<emphasis>Project mode</emphasis>. There are three panes in the project "
"window. The first is the project pane and lists the project files organized "
"in file types. The second is the symbol browser, which has already been "
"discussed in section <emphasis>Symbol Browser and tags Browser</emphasis>. "
"The third pane is the file view of the project and is more or less similar "
"to a mini file-manager. In file view, all the files present in the project "
"tree is visible. Right clicking on these files will pop up the file "
"<guimenu>Operation menu</guimenu>."
msgstr ""

#: C/anjuta-manual.xml:138(para)
msgid ""
"If the project is also a CVS tree, then corresponding file revision numbers "
"are also listing on the right of file names in the file view pane."
msgstr ""

#: C/anjuta-manual.xml:144(title)
msgid "Saving Projects"
msgstr "Enregistrar de projèctes"

#: C/anjuta-manual.xml:145(para)
msgid ""
"The project is automatically saved when you close because all changes are "
"made directly in the project structure."
msgstr ""

#: C/anjuta-manual.xml:153(title)
msgid "Project structure"
msgstr "Estructura de projècte"

#: C/anjuta-manual.xml:159(title)
msgid "Project window"
msgstr ""

#: C/anjuta-manual.xml:161(screeninfo)
msgid "The Project window"
msgstr ""

#: C/anjuta-manual.xml:154(para)
msgid ""
"Here is the <interface>Project window</interface> with the the "
"<guimenu>Operation menu</guimenu> (accessible by clicking on the right mouse "
"button). <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:166(para)
msgid ""
"<interface>Project window</interface> lists the project in standard <ulink "
"type=\"info\" url=\"info:automake\"><application>automake</application></"
"ulink> hierarchy organized into groups of targets. <emphasis>Groups</"
"emphasis> correspond to directories in your project and <emphasis>targets</"
"emphasis> correspond to normal <application>automake</application> targets "
"(not to be confused with make targets). <interface>Project window</"
"interface> actually has two parts; one part (lower one) shows complete "
"project hierarchy and the other part (upper one) lists important targets "
"directly. Important targets constitute executable and library targets -- "
"making them very accessible in from the view. This is particularly useful in "
"big projects where the hierarchy could be deep and hard to navigate from the "
"tree alone. Targets are, in turn, composed of source files."
msgstr ""

#: C/anjuta-manual.xml:186(para)
msgid ""
"<emphasis>Groups</emphasis> are used to logically organize targets. A "
"project can contain any number of groups. Each group can have sub-groups as "
"well as targets. In automake projects, groups are just sub-directories in "
"the project. The top level group is called root and is always \"/\"."
msgstr ""

#: C/anjuta-manual.xml:194(para)
msgid ""
"<emphasis>Targets</emphasis> are the build targets in project, such as "
"programs (executable binaries), scripts, libraries, miscellaneous data etc. "
"Not all target types are built from sources, but exist just to organize the "
"sources and therefore may not exist physically (e.g. Miscellaneous data "
"target). Targets exist under groups. See <link linkend=\"adding-target\">"
"\"Adding targets\"</link> for full list of available target types."
msgstr ""

#: C/anjuta-manual.xml:205(para)
msgid ""
"<emphasis>Source files</emphasis> are the files used to build the targets or "
"just to be part of it. They exist only under targets. Many target types "
"expect certain type of source files (e.g. programs and libraries target "
"types), but some can accept any file (e.g. Miscellaneous data target)."
msgstr ""

#: C/anjuta-manual.xml:215(para)
msgid ""
"Each of the project groups and targets is configurable in standard "
"<application>automake</application> way. You can set complier and linker "
"flags directly for each target, or set configure variables. Groups allow "
"setting installation destinations for its targets."
msgstr ""

#: C/anjuta-manual.xml:222(para)
msgid ""
"Just like file manager, project manager view also has convenience actions "
"(accessible from the <guimenu>Operation menu</guimenu>) for the source files "
"and targets."
msgstr ""

#: C/anjuta-manual.xml:228(para)
msgid ""
"Many command-line tools are available to maintain and manage a project, and "
"each tool has its own specific rules and capabilities. <application>Anjuta</"
"application> tries to automate most of the common operations using plugins. "
"However, you might occasionally still need to do them manually."
msgstr ""

#: C/anjuta-manual.xml:236(para)
msgid ""
"It is possible to make use of other tools or hand edit the project files "
"simultaneously. It doesn't matter if the project is loaded in "
"<application>Anjuta</application> or not. <application>Anjuta</application> "
"would update itself with any external changes made to project."
msgstr ""

#: C/anjuta-manual.xml:245(title)
msgid "Groups and targets"
msgstr ""

#: C/anjuta-manual.xml:248(title)
msgid "Adding Groups"
msgstr "Apondre de grops"

#: C/anjuta-manual.xml:253(para)
msgid ""
"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Group</"
"guimenuitem></menuchoice> and a dialog to add a new group would popup."
msgstr ""

#: C/anjuta-manual.xml:260(para)
msgid "Select the group under which to add new group."
msgstr ""

#: C/anjuta-manual.xml:263(para)
msgid "Give a name of the new group and click Ok."
msgstr ""

#: C/anjuta-manual.xml:249(para)
msgid ""
"To add a new group (a directory in automake based projects): <placeholder-1/"
"> With automake projects, a new directory with the given name would be "
"created under the parent group's directory."
msgstr ""

#: C/anjuta-manual.xml:270(para)
msgid ""
"New group can also be added from the <guimenu>Operation menu</guimenu> in "
"<interface>Project window</interface> by selecting <guimenuitem>Add Group</"
"guimenuitem>. First select the group under which to add the group in "
"<interface>Project window</interface>."
msgstr ""

#: C/anjuta-manual.xml:279(title)
msgid "Removing Groups"
msgstr "Suprimir de grops"

#: C/anjuta-manual.xml:284(para)
msgid "Select the target in <interface>Project Manager view</interface>."
msgstr ""

#: C/anjuta-manual.xml:287(para) C/anjuta-manual.xml:426(para)
msgid ""
"Select <guimenuitem>Remove</guimenuitem> from the <guimenu>Operation menu</"
"guimenu>."
msgstr ""

#: C/anjuta-manual.xml:280(para)
msgid ""
"To remove a group: <placeholder-1/> The target and sources associated with "
"the group will also be removed from the project (they are not deleted from "
"the file system, though. You can still add them later)."
msgstr ""

#: C/anjuta-manual.xml:298(title)
msgid "Adding Targets"
msgstr ""

#: C/anjuta-manual.xml:303(para)
msgid ""
"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Target</"
"guimenuitem></menuchoice> and a dialog to add a new target would popup."
msgstr ""

#: C/anjuta-manual.xml:308(para)
msgid "Select the group under which to add the target."
msgstr ""

#: C/anjuta-manual.xml:311(para)
msgid "Select the target type."
msgstr ""

#: C/anjuta-manual.xml:314(para)
msgid "Give a name of the new target and click Ok."
msgstr ""

#: C/anjuta-manual.xml:299(para)
msgid "To add a new target: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:318(para)
msgid ""
"New target can also be added from the <guimenu>Operation menu</guimenu> in "
"<interface>Project window</interface> by selecting <guimenuitem>Add target</"
"guimenuitem>. First select the group under which to add the target in "
"<interface>Project window</interface>."
msgstr ""

#: C/anjuta-manual.xml:324(para)
msgid ""
"Target names usually require some standard prefix and suffix, depending on "
"the type of target. Anjuta would warn if the name is not valid and may give "
"an example of a name."
msgstr ""

#: C/anjuta-manual.xml:333(para)
msgid ""
"<emphasis>Program</emphasis> target type is for executable binaries. Select "
"this if you want to add an executable to the project. By default, all "
"program targets would be installed in standard executable directory, e.g. /"
"usr/bin or /usr/local/bin. You can override it by specifying a different "
"installation directory in its group properties."
msgstr ""

#: C/anjuta-manual.xml:342(para)
msgid ""
"<emphasis>Shared Library</emphasis> target type is for shared or dynamic "
"libraries. Select this if you are adding a shared library to the project. By "
"default, all shared libraries are installed in standard libraries directory, "
"e.g. /usr/lib or /usr/local/lib. You can override it by specifying a "
"different installation directory in its group properties."
msgstr ""

#: C/anjuta-manual.xml:351(para)
msgid ""
"<emphasis>Static Library</emphasis> target type is for static library. "
"Select this if you are adding a static library to the project. By default, "
"all static libraries are installed in standard libraries directory, e.g. /"
"usr/lib or /usr/local/lib. You can override it by specifying a different "
"installation directory in its group properties."
msgstr ""

#: C/anjuta-manual.xml:360(para)
msgid ""
"<emphasis>Java module</emphasis> target type is for java module. Select this "
"if you are grouping java sources into a module. You need to provide an "
"installation directory for this target where the .class files will be "
"installed. It can be set in group properties of the group where this target "
"belongs."
msgstr ""

#: C/anjuta-manual.xml:368(para)
msgid ""
"There can really be only one java module in a group. This is a restriction "
"put by automake. Please read automake info page for more details."
msgstr ""

#: C/anjuta-manual.xml:376(para)
msgid ""
"<emphasis>Python module</emphasis> target type is for python module. Select "
"this if you are grouping python sources into a module. You need to provide "
"an installation directory for this target where the sources will be "
"installed. It can be set in group properties of the group where this target "
"belongs."
msgstr ""

#: C/anjuta-manual.xml:385(para)
msgid ""
"<emphasis>Scripts</emphasis> target is to group scripts. They will be "
"installed in standard executable directory."
msgstr ""

#: C/anjuta-manual.xml:391(para)
msgid ""
"<emphasis>Miscellaneous Data</emphasis> target type is to group simple files "
"in the project. An installation directory needs to be specified in its group "
"properties."
msgstr ""

#: C/anjuta-manual.xml:398(para)
msgid ""
"<emphasis>Header Files</emphasis> target type is to group C/C++ header files "
"that need to be installed in system (for example as part of library API). "
"For header files that do not need to be installed, make them part of the "
"Program target along with the sources. They will be installed in standard "
"include directory unless installation path is specified in its group "
"properties."
msgstr ""

#: C/anjuta-manual.xml:408(para)
msgid ""
"<emphasis>Man documentation</emphasis> and <emphasis>Info documentation</"
"emphasis> target types are for grouping man and info documentation "
"respectively. By default, they will be installed in standard installation "
"directories."
msgstr ""

#: C/anjuta-manual.xml:329(para)
msgid ""
"There are several target types for automake project. They are: <placeholder-"
"1/>"
msgstr ""

#: C/anjuta-manual.xml:418(title)
msgid "Removing Targets"
msgstr ""

#: C/anjuta-manual.xml:423(para)
msgid "Select the target in <interface>Project Manager view</interface>"
msgstr ""

#: C/anjuta-manual.xml:419(para)
msgid ""
"To remove a target: <placeholder-1/> The sources associated with the targets "
"will also be removed from the project (they are not deleted from the file "
"system, though)."
msgstr ""

#: C/anjuta-manual.xml:438(title)
msgid "Adding and Removing Files"
msgstr ""

#: C/anjuta-manual.xml:440(title)
msgid "Adding Source Files"
msgstr ""

#: C/anjuta-manual.xml:441(para)
msgid ""
"Select menu item <menuchoice><guisubmenu>Project</"
"guisubmenu><guimenuitem>Add Source File</guimenuitem></menuchoice>. From the "
"dialog, select the target to which the file should be added and the file "
"itself. You can add multiple files at once. To do that, select multiple "
"files from the file selection dialog using either SHIFT or CONTROL key. Then "
"click <guibutton>Add</guibutton> button to finally add the files in project."
msgstr ""

#: C/anjuta-manual.xml:450(para)
msgid ""
"By default, current editor file would be preselected for addition in the "
"dialog. Other convenient way to add a file is to select it in "
"<interface>File Manager</interface> and choosing <guimenuitem>Add to "
"project</guimenuitem> from the <guimenu>Operation menu</guimenu>."
msgstr ""

#: C/anjuta-manual.xml:457(para)
msgid ""
"If the file you choose has already been added to the project, then "
"<application>Anjuta</application> will not add it again. It will also give "
"you a warning that the file is already added."
msgstr ""

#: C/anjuta-manual.xml:462(para)
msgid ""
"If the file you choose is not in the project directory, you will be asked to "
"confirm that you wish to copy the file into the target's directory. "
"<application>Anjuta</application> cannot add files which are outside of "
"target's directory."
msgstr ""

#: C/anjuta-manual.xml:470(title)
msgid "Removing Source Files"
msgstr ""

#: C/anjuta-manual.xml:471(para)
msgid ""
"To remove a file from the project, select the file you want to remove from "
"the <interface>Project window</interface>, right-click to open the "
"<guimenu>Operation menu</guimenu> and choose <guimenuitem>Remove</"
"guimenuitem>."
msgstr ""

#: C/anjuta-manual.xml:477(para)
msgid ""
"A confirmation dialog will appear, and the file will be removed from the "
"project."
msgstr ""

#: C/anjuta-manual.xml:482(title)
msgid "The file is not deleted!"
msgstr "Lo fichièr es pas suprimit !"

#: C/anjuta-manual.xml:483(para)
msgid ""
"The file is not deleted from the filesystem. It still exists, and you can "
"add it back again later if you so wish. The file is only removed from the "
"project listing, and will not take part in any of the project operations "
"such as compiling, building, distribution etc.."
msgstr ""

#: C/anjuta-manual.xml:494(title)
msgid "Project Configuration"
msgstr "Configuracion del projècte"

#: C/anjuta-manual.xml:495(para)
msgid ""
"Project configuration involves setting the correct build flags for targets, "
"groups and project itself. You can set these flags in their respective "
"properties dialog."
msgstr ""

#: C/anjuta-manual.xml:501(para)
msgid ""
"You can freely use autoconf and automake variables that are automatically "
"set for the project during configuration. Apart from these automatically set "
"variables, you can also defined your own variables in <link linkend="
"\"project-properties\">Project Properties</link> use them in properties. "
"This will make it easy to update flags later, especially when the variable "
"is used in several targets."
msgstr ""

#: C/anjuta-manual.xml:516(para)
msgid ""
"<emphasis>$(prefix)</emphasis>: The installation prefix. The project is "
"installed under various sub-directories under this prefix. By default it is /"
"usr/local."
msgstr ""

#: C/anjuta-manual.xml:523(para)
msgid ""
"<emphasis>$(bindir)</emphasis>: The installation directory for executable "
"binaries. All your executable and scripts targets would be installed in this "
"directory. By default, it is $(prefix)/bin."
msgstr ""

#: C/anjuta-manual.xml:530(para)
msgid ""
"<emphasis>$(libdir)</emphasis>: The installation directory for libraries. "
"All your library targets (both shared and static) would be installed in this "
"directory or a subdirectory below it. By default, it is $(prefix)/lib."
msgstr ""

#: C/anjuta-manual.xml:538(para)
msgid ""
"<emphasis>$(module_CFLAGS)</emphasis> and $(module_LIBS): These flags are "
"set by configure for the packages that your project depends on. The packages "
"used by the project are set in <link linkend=\"project-properties\">Project "
"Properties</link>. 'module' is the packages group that you give in project "
"properties."
msgstr ""

#: C/anjuta-manual.xml:510(para)
msgid ""
"Some of the many common variables are listed here. For full list of them see "
"<ulink url=\"info:automake\">automake info documentation</ulink>. "
"<placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:552(title)
msgid "Project properties"
msgstr "Propietats del projècte"

#: C/anjuta-manual.xml:559(para)
msgid ""
"Set project name, version and URL in <guibutton>General</guibutton> page. "
"Configure variables can also be use in these fields. The URL is the bug "
"report URL for the project."
msgstr ""

#: C/anjuta-manual.xml:566(para)
msgid ""
"Add and remove dependencies for your project in <guibutton>Packages</"
"guibutton> page. See below for details."
msgstr ""

#: C/anjuta-manual.xml:572(para)
msgid ""
"Create more configure variables in <guibutton>Variables</guibutton> page to "
"use in group and target properties."
msgstr ""

#: C/anjuta-manual.xml:553(para)
msgid ""
"Project properties dialog can be only brought by choosing "
"<menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
"guimenuitem></menuchoice>. You can: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:587(title) C/anjuta-manual.xml:589(screeninfo)
msgid "Project properties dialog"
msgstr ""

#: C/anjuta-manual.xml:579(para)
msgid ""
"Dependencies are external packages that the project uses and hence required "
"to build it. Only packages installed using <ulink url=\"info:pkg-config"
"\">pkg-config</ulink> can be added from this interface. For others, the "
"configure.ac file can be edited manually. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:594(para)
msgid ""
"External package dependencies are grouped into <emphasis>modules</emphasis>, "
"so that their combined build flags can be conveniently added to different "
"targets. <emphasis>Modules</emphasis> are just arbitrary names given to "
"group the packages and can be named anything (only alphanumeric and _ are "
"allowed in module name). Usually, they follow the name of targets they would "
"be use in. Consequently, for small projects with single targets, just one "
"module to hold all dependencies is enough."
msgstr ""

#: C/anjuta-manual.xml:603(para)
msgid ""
"Each package exports a set of <emphasis>compiler flags</emphasis> and "
"<emphasis>libraries</emphasis>. They are aggregated together for all "
"packages under a module and configure variables <emphasis>$(module_CFLAGS)</"
"emphasis> and <emphasis>$(module_LIBS)</emphasis> are defined. These "
"variables can then be used in <link linkend=\"group-properties\">Group "
"properties</link> and <link linkend=\"target-properties\">Target properties</"
"link>."
msgstr ""

#: C/anjuta-manual.xml:616(para)
msgid ""
"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
"guimenuitem></menuchoice> to bring up project properties dialog."
msgstr ""

#: C/anjuta-manual.xml:623(para)
msgid ""
"Select the tab <guibutton>Packages</guibutton> to bring up packages page."
msgstr ""

#: C/anjuta-manual.xml:627(para)
msgid ""
"Select the <emphasis>module</emphasis> to add the package to. If there is no "
"module created yet or there is no appropriate module, create one by clicking "
"<guibutton>Add module</guibutton>. Give a sensible name to the module, "
"preferably in UPPERCASE to match with rest of configure variables (only use "
"alphanumeric and '_' characters) and press <keycap>Enter</keycap> to create "
"it."
msgstr ""

#: C/anjuta-manual.xml:637(para)
msgid ""
"Click <guibutton>Add Package</guibutton> to bring up package selection "
"dialog."
msgstr ""

#: C/anjuta-manual.xml:640(para)
msgid "Select the package to add and click <guibutton>Add</guibutton>."
msgstr ""

#: C/anjuta-manual.xml:643(para)
msgid "Click <guibutton>Close</guibutton> to close the properties dialog."
msgstr ""

#: C/anjuta-manual.xml:612(para)
msgid "To add a package dependency: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:650(title)
msgid "Group properties"
msgstr "Propietats del grop"

#: C/anjuta-manual.xml:651(para)
msgid ""
"To set group properties, select it in the <interface>Project window</"
"interface> and active it. You can also bring it by selecting "
"<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
"guimenuitem></menuchoice>"
msgstr ""

#: C/anjuta-manual.xml:667(para)
msgid ""
"<emphasis>Includes</emphasis>: Set your $(module_CFLAGS) variables and other "
"include directories for your c and c++ targets. You need to provide the full "
"include options of the compiler here, e.g. -I/usr/include/blah. The include "
"paths will be use to find the include files in your source files. You can "
"also add other sort of compiler flags here, but they are preferred to be set "
"in their respective compiler flags properties (see below)."
msgstr ""

#: C/anjuta-manual.xml:677(para)
msgid ""
"Usually your configure script would also make some automatically determined "
"compiler flags. The variables usually end with _CFLAGS, e.g "
"$(PACKAGE_CFLAGS). They are also set here. See setting <link linkend="
"\"project-properties\">Project properties</link> for more details on these "
"variables."
msgstr ""

#: C/anjuta-manual.xml:687(para) C/anjuta-manual.xml:728(para)
msgid ""
"<emphasis>Compiler settings</emphasis>: Set your compiler specific flags "
"here. There are different fields for different compiler categories. Flags "
"that can be set here depend on the actual compiler used. The default "
"compiler use for c/c++ is gcc/g++ (gnu c compiler). Check out <ulink url="
"\"info:gcc\">gcc info documentation</ulink> for more details."
msgstr ""

#: C/anjuta-manual.xml:697(para)
msgid ""
"<emphasis>Install directories</emphasis>: Targets in the group that require "
"installation directories would each get a field to enter the installation "
"directory. Set their installation directories as relative to one of the many "
"automake directory variables, such as $(prefix), $(bindir), $(libdir), "
"$(datadir) etc."
msgstr ""

#: C/anjuta-manual.xml:658(para)
msgid ""
"<emphasis>Group Properties</emphasis> set to a group applies to all the "
"targets under it. So any compiler or linker flags set there would be "
"automatically be part of all the targets in it (in addition the targets "
"individual properties). Following flags are available in group properties. "
"<placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:712(title)
msgid "Target properties"
msgstr ""

#: C/anjuta-manual.xml:713(para)
msgid ""
"To set target properties, select it in the <interface>Project window</"
"interface> and active it. You can also bring it by selecting "
"<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
"guimenuitem></menuchoice>"
msgstr ""

#: C/anjuta-manual.xml:738(para)
msgid ""
"<emphasis>Linker flags</emphasis>: Set linker flags that should be used when "
"linking the target. It applies only to Program and library targets. See "
"<ulink url=\"info:ld\">ld info documentation</ulink> for available linker "
"options."
msgstr ""

#: C/anjuta-manual.xml:746(para)
msgid ""
"<emphasis>Libraries</emphasis>: Set the libraries that the target depends "
"on. Usually they are the $(module_LIBS) configure variables. See setting "
"<link linkend=\"project-properties\">Project properties</link> for more "
"details on these variables."
msgstr ""

#: C/anjuta-manual.xml:720(para)
msgid ""
"<emphasis>Target Properties</emphasis> set to a target applies to that "
"target. So any compiler or linker flags set there would be just part of it "
"(in addition the its group properties). Following flags are available in "
"target properties. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:761(title)
msgid "Compiling and Building"
msgstr ""

#: C/anjuta-manual.xml:763(title)
msgid "Overview"
msgstr ""

#: C/anjuta-manual.xml:764(para)
msgid "An executable for a project is generated in two steps:"
msgstr ""

#: C/anjuta-manual.xml:769(para)
msgid "Compiling"
msgstr ""

#: C/anjuta-manual.xml:770(para)
msgid "Linking"
msgstr ""

#: C/anjuta-manual.xml:773(para)
msgid ""
"These steps are collectively known as <emphasis>Building</emphasis>. Some "
"other steps may also be involved in the build process, but for the sake of "
"simplicity, we will only look at these two steps."
msgstr ""

#: C/anjuta-manual.xml:778(para)
msgid ""
"<emphasis>Compiling</emphasis> is the step in which object files are "
"generated from their corresponding source files. For instance, a source file "
"<filename>hello.c</filename> will generate <filename>hello.o</filename> "
"after compilation. Usually you do not need to worry about these object files "
"— just think of them as intermediate files involved in creating the final "
"executable."
msgstr ""

#: C/anjuta-manual.xml:785(para)
msgid ""
"Once the object files (<filename>*.o</filename> files) are ready, they are "
"all linked together (along with any libraries) to generate the final "
"executable. This step is called <emphasis>Linking</emphasis>."
msgstr ""

#: C/anjuta-manual.xml:792(title)
msgid "Compiling the source"
msgstr ""

#: C/anjuta-manual.xml:793(para)
msgid ""
"In a project, the individual source files can be compiled separately into "
"objects (<filename>*.o</filename> files). Although you do not have to worry "
"about these object files, sometimes it is handy to compile a file first (for "
"example, to make sure there are no syntax errors). Building a whole project "
"can take a lot of time, especially in the case of larger and more complex "
"applications. Therefore, you will probably go through a series of edit-"
"compile-edit-compile-.... loops while a developing the project."
msgstr ""

#: C/anjuta-manual.xml:801(para)
msgid ""
"To compile a file, choose the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Compile</guimenuitem></menuchoice> or press "
"<keycap>F11</keycap>. This will compile the active file."
msgstr ""

#: C/anjuta-manual.xml:808(title)
msgid "Building an executable"
msgstr ""

#: C/anjuta-manual.xml:809(para)
msgid ""
"<application>Anjuta</application> has no separate link command, simply "
"because it is not necessary. The build process will compile all the source "
"files and link them together along with the libraries. The build command "
"will note recompile those files which are already up-to-date (this is called "
"the <emphasis>dependency check</emphasis>). If you have already compiled all "
"of the files individually, then the only thing the build step performs is "
"the link. If you have already built the project and no dependent file has "
"been modified, even the link stage will be skipped."
msgstr ""

#: C/anjuta-manual.xml:818(para)
msgid ""
"So how exactly does the dependency check influence the project development? "
"If you have modified a file, then all of the source files that depend on the "
"modified file are recompiled. All files (not only the object files and "
"executable) in the project are checked for these dependencies during the "
"build process. If it is found that a particular file is dependent on some "
"other file which has been modified, then that file will be re-generated."
msgstr ""

#: C/anjuta-manual.xml:826(para)
msgid ""
"Since you have now got a rough understanding of the value of the dependency "
"check, can you imagine how your life (as a programmer) would be if it had "
"not been there? If you cannot answer just yet, then will find out when you "
"start developing big projects!"
msgstr ""

#: C/anjuta-manual.xml:831(para)
msgid ""
"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></"
"menuchoice> will build all of the files in the <filename class=\"directory"
"\">src</filename> (source) directory, and generate the executable. "
"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Project</"
"guimenuitem></menuchoice> will build the whole project — all of the "
"subdirectories (including <filename class=\"directory\">src</filename>), are "
"built recursively."
msgstr ""

#: C/anjuta-manual.xml:841(title)
msgid "Creating a distribution package"
msgstr ""

#: C/anjuta-manual.xml:842(para)
msgid ""
"To build the tarball distribution of the project choose "
"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Tarball</"
"guimenuitem></menuchoice>. This will create a tarball (<filename>*.tar.gz</"
"filename>) and put it in the top level project directory. Copy the file to a "
"safe place for distribution."
msgstr ""

#: C/anjuta-manual.xml:850(title)
msgid "Install"
msgstr "Installar"

#: C/anjuta-manual.xml:851(para)
msgid ""
"Choosing the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Install</guimenuitem></menuchoice> will install the "
"generated application on your system."
msgstr ""

#: C/anjuta-manual.xml:857(title)
msgid "System wide installation"
msgstr ""

#: C/anjuta-manual.xml:858(para)
msgid ""
"You must be logged in as root to perform a system-wide install. Also note "
"that for a GNOME application to use the pixmaps in the project, it must be "
"installed as a system-wide application. Otherwise, when the application is "
"executed in your project, there will be lots of \"pixmap not found\" errors. "
"You can configure anjuta to use <command>sudo</command> or <command>su</"
"command> before installing the project in the build preferences."
msgstr ""

#: C/anjuta-manual.xml:868(title)
msgid "Configure"
msgstr "Configurar"

#: C/anjuta-manual.xml:869(para)
msgid ""
"To run the <filename>configure</filename> script found in the top level "
"project directory, choose the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Run Configure…</guimenuitem></menuchoice>. The "
"script will determine the system configuration and create some of the files "
"required to perform a build (such as <filename>Makefile</filename> and "
"<filename>config.h</filename>). This is necessary because the application "
"may depend on specific configuration of some of these options."
msgstr ""

#: C/anjuta-manual.xml:878(title)
#, fuzzy
msgid "When to run configure"
msgstr "Quora configurar"

#: C/anjuta-manual.xml:879(para)
msgid ""
"Until you run <filename>configure</filename>, you cannot start building the "
"project."
msgstr ""

#: C/anjuta-manual.xml:884(para)
msgid ""
"The <filename>configure</filename> script is (usually) run only once at the "
"beginning of the first build process — for example, just after you have "
"extracted a source tarball of a project distribution. After that, "
"configuration is automatically handled by the subsequent build processes. If "
"you have used the <emphasis>Application Wizard</emphasis> to create the "
"application, then you will not need to run <filename>configure</filename> "
"separately: the wizard will run it as a part of the project generation "
"process."
msgstr ""

#: C/anjuta-manual.xml:892(para)
msgid ""
"You can also supply additional options to the configuration script. After "
"choosing the <guimenuitem>Run Configure…</guimenuitem> menu item, a dialog "
"will appear to prompt for additional options."
msgstr ""

#: C/anjuta-manual.xml:898(title) C/anjuta-manual.xml:900(screeninfo)
msgid "Configure options dialog"
msgstr ""

#: C/anjuta-manual.xml:904(para)
msgid ""
"Enter any options (or leave it blank to accept the defaults) and click "
"<guibutton>OK</guibutton>. To find out the options available to the "
"<filename>configure</filename> script, enter <userinput>--help</userinput> "
"in the option entry box and click <guibutton>OK</guibutton>. The options "
"will be displayed in the <interface>Message window</interface>."
msgstr ""

#: C/anjuta-manual.xml:911(para)
msgid ""
"There is no requirement to run <filename>configure</filename> only once. It "
"can be run at any time, usually when the configuration options need to be "
"changed. One thing to note is that, if the <filename>config.h</filename> "
"file in the top level directory is changed, running <filename>configure</"
"filename> again will not overwrite it."
msgstr ""

#: C/anjuta-manual.xml:919(title)
msgid "Auto generate"
msgstr ""

#: C/anjuta-manual.xml:920(para)
msgid ""
"Auto generation consists of two steps: running <application>automake</"
"application> and then running <application>autoconf</application>. If an "
"executable <filename>autogen.sh</filename> script is found in the top level "
"project directory, this file will be executed instead of the two steps. Like "
"<emphasis>configuration</emphasis>, auto generation is automatically handled "
"by the build process. It can also be run in cases where it is difficult to "
"configure the project (such as lots of errors reported due to mis-"
"synchronization after modifying lots of build files)."
msgstr ""

#: C/anjuta-manual.xml:931(title)
#, fuzzy
msgid "When to run autogen.sh"
msgstr "Quora aviar autogen.sh"

#: C/anjuta-manual.xml:932(para)
msgid ""
"Unlike configuration, auto generation does not need to be run even once — in "
"fact, it does not need to be run at all! The option is available because it "
"can be handy in some circumstances."
msgstr ""

#: C/anjuta-manual.xml:938(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Run Autogenerate…</guimenuitem></menuchoice> to auto "
"generate the project."
msgstr ""

#: C/anjuta-manual.xml:942(para)
msgid ""
"Read the info pages of <ulink type=\"info\" url=\"info:automake"
"\"><application>automake</application></ulink> and <ulink type=\"info\" url="
"\"info:autoconf\"><application>autoconf</application></ulink> for more "
"details on how these tools work."
msgstr ""

#: C/anjuta-manual.xml:949(title)
msgid "Clean"
msgstr ""

#: C/anjuta-manual.xml:950(para)
msgid ""
"This option cleans the project and leaves it in a state that requires "
"<guimenuitem>Build Project</guimenuitem> to be performed. It deletes all of "
"the files generated by the build process, including all object files "
"(<filename>*.o</filename> files) and the executable(s) in the <filename "
"class=\"directory\">src</filename> directory (and other directories)."
msgstr ""

#: C/anjuta-manual.xml:957(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Clean</guimenuitem></menuchoice> to clean the "
"project."
msgstr ""

#: C/anjuta-manual.xml:963(title)
#, fuzzy
msgid "Clean Project"
msgstr "Enregistrar de projèctes"

#: C/anjuta-manual.xml:964(para)
msgid ""
"There is not a great deal to say about <guimenuitem>Clean Project</"
"guimenuitem> (which might also be called <emphasis>Clean distribution</"
"emphasis>, or <emphasis>clean dist</emphasis> for short). It cleans the "
"project and leaves it in a state that requires <guimenuitem>Run Configure…</"
"guimenuitem> and <guimenuitem>Build Project</guimenuitem> to be performed. "
"It deletes all of the files generated by the build processes, including all "
"the object files (<filename>*.o</filename> files), executable(s) and "
"Makefiles. In other words, it leaves the project as though it has just been "
"extracted from a distribution tarball."
msgstr ""

#: C/anjuta-manual.xml:974(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Clean Project</guimenuitem></menuchoice> to "
"completely clean the project."
msgstr ""

#: C/anjuta-manual.xml:981(title)
msgid "Executing program"
msgstr "Executar un programa"

#: C/anjuta-manual.xml:982(para)
msgid ""
"Once an executable is ready after the build, you can execute it by choosing "
"the menu item <menuchoice><guisubmenu>Build</"
"guisubmenu><guimenuitem>Execute</guimenuitem></menuchoice>, or pressing "
"<keycap>F3</keycap>. You can specify which executable you want to use in "
"case your project provides more than one and specify command line arguments."
msgstr ""

#: C/anjuta-manual.xml:989(title)
msgid "Dependencies"
msgstr "Dependéncias"

#: C/anjuta-manual.xml:990(para)
msgid ""
"Unlike the build stage, execution doesn't check for dependencies (at least "
"for the time being). In other words, it does not check if the executable is "
"up-to-date before it executes the program. So, <emphasis>you must take care "
"of that yourself.</emphasis>"
msgstr ""

#: C/anjuta-manual.xml:1000(title)
msgid "Choose executable and set program parameters"
msgstr ""

#: C/anjuta-manual.xml:1002(screeninfo)
msgid "Setting program parameters"
msgstr ""

#: C/anjuta-manual.xml:3(title)
msgid "Debugging"
msgstr ""

#: C/anjuta-manual.xml:5(emphasis)
msgid "To debug is human. To fix it is divine..."
msgstr ""

#: C/anjuta-manual.xml:7(para)
msgid ""
"Well, the <emphasis>human</emphasis> part is what this section is about. The "
"<emphasis>divine</emphasis> part is up to you!"
msgstr ""

#: C/anjuta-manual.xml:11(para)
msgid ""
"When a program does not behave in the way it is supposed to, we say the "
"program contains a bug or bugs. This does not refer to compilation errors — "
"those are simply errors and they are relatively easy to clear, because the "
"compiler tells you where the problems are. On the other hand, "
"<emphasis>bugs</emphasis> are errors that happen during the execution of the "
"program and they can be hard (sometimes very hard!) to detect."
msgstr ""

#: C/anjuta-manual.xml:19(para)
msgid ""
"Any program that you think is bug-free is never completely bug-free. All we "
"can try to do is to reduce the number of bugs contained in the program. The "
"process of removing bugs is known as <emphasis>debugging</emphasis>, and the "
"tool that is used for debugging is called the <emphasis>debugger</emphasis>. "
"<application>Anjuta</application> provides a very user-friendly and powerful "
"debugging environment (actually, a GUI wrapper over <application>gdb</"
"application>, a powerful command line debugging tool and standard on Linux)."
msgstr ""

#: C/anjuta-manual.xml:27(para)
msgid ""
"A debugger tracks and traces the execution of the program and provides "
"various views of information needed to study the execution of the program."
msgstr ""

#: C/anjuta-manual.xml:35(title)
msgid "Start and stop"
msgstr ""

#: C/anjuta-manual.xml:40(emphasis) C/anjuta-manual.xml:46(title)
msgid "Running an executable"
msgstr ""

#: C/anjuta-manual.xml:41(emphasis)
msgid "Attaching to a process"
msgstr ""

#: C/anjuta-manual.xml:37(para)
msgid ""
"The debugger is always started with a program loaded. There are two ways to "
"do this: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:52(listitem)
msgid "The program that you want to debug"
msgstr ""

#: C/anjuta-manual.xml:53(listitem)
msgid "The command line parameters"
msgstr ""

#: C/anjuta-manual.xml:54(listitem)
msgid "If you want a terminal or not (the Anjuta terminal plugin is used)"
msgstr ""

#: C/anjuta-manual.xml:55(listitem)
msgid "If you want to stop the program at the beginning or not"
msgstr ""

#: C/anjuta-manual.xml:47(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Run Target…</guimenuitem></menuchoice> to display a "
"dialog box where you can select: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:58(para)
msgid ""
"The drop-down menu of the target drop-down combination box is already filled "
"with all executables of the current project. But you can select another "
"executable not part of the project. The debugger accepts libtool executable, "
"it means script,generated by libtool, wrapping the real executable. Note "
"that an URI is expected here, not a file path even if the debugger currently "
"supports only local files."
msgstr ""

#: C/anjuta-manual.xml:66(para)
msgid ""
"When you have set everything you can click on <guibutton>Execute</guibutton> "
"to start the debugger, load your program and stop at its beginning if "
"requested."
msgstr ""

#: C/anjuta-manual.xml:71(para)
msgid ""
"In order to better user the debugger, it is strongly recommended to debug "
"program with debugging information (-g for gcc) and no optimization (-O0 for "
"gcc)."
msgstr ""

#: C/anjuta-manual.xml:79(title)
msgid "Attaching to a Process"
msgstr ""

#: C/anjuta-manual.xml:80(para)
msgid ""
"It is also possible to attach to a running process and debugging it by "
"choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Attach to Process …</guimenuitem></menuchoice>. A "
"list of all the process running on the system will appear."
msgstr ""

#: C/anjuta-manual.xml:87(title) C/anjuta-manual.xml:89(screeninfo)
msgid "Attach to Process dialog"
msgstr ""

#: C/anjuta-manual.xml:93(para)
msgid ""
"Select the process to attach to and click <guibutton>OK</guibutton> to start "
"the debugger, attach to the selected process and stop it."
msgstr ""

#: C/anjuta-manual.xml:98(para)
msgid ""
"It is currently not possible to load symbol informations for the attached "
"process. They should be included in the process."
msgstr ""

#: C/anjuta-manual.xml:106(title)
msgid "Restarting an executable"
msgstr ""

#: C/anjuta-manual.xml:107(para)
msgid ""
"After running an executable at least one time, you can choose the menu item "
"<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Restart Target</"
"guimenuitem></menuchoice> to restart your program. It is just a shortcut "
"that will stop the debugger if it is currently running and restart it with "
"the last executable without displaying the start dialog."
msgstr ""

#: C/anjuta-manual.xml:117(title)
msgid "Stopping the Debugger"
msgstr ""

#: C/anjuta-manual.xml:118(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the "
"debugger. This option will kill the program which is being debugged. If the "
"debugger has been attached to a running process, it will just detach from it "
"without killing it. You will get a confirmation box if a program is "
"currently attached or running."
msgstr ""

#: C/anjuta-manual.xml:128(title)
msgid "Adding source directories"
msgstr ""

#: C/anjuta-manual.xml:129(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Add source paths…</guimenuitem></menuchoice> to "
"display a dialog box allowing you to add and remove source directories."
msgstr ""

#: C/anjuta-manual.xml:134(para)
msgid ""
"Most executables include full file paths, so defining the directories where "
"are the source files is not useful. But some executables include only file "
"names without paths, in this case, the source files will be searched in all "
"these directories by the debugger. The directories order can be important if "
"several files have the same name, so you can change it using the "
"<guibutton>Up</guibutton> and <guibutton>Down</guibutton> buttons. The "
"directories list is send to the debugger when it is started. After changing "
"it, you need to restart the debugger to take it in account."
msgstr ""

#: C/anjuta-manual.xml:150(title)
msgid "Execution"
msgstr "Execucion"

#: C/anjuta-manual.xml:151(para)
msgid ""
"Execution of a program in the debugger can be finely controlled. The program "
"can be executed in single steps, or allowed to continue until it encounters "
"a breakpoint. Executing like this is essential for tracking program "
"behavior. Like a video editing session, the program can be executed in "
"<emphasis>slow motion</emphasis> with the ability to go forward, pause, "
"stop, and so on. You cannot go backward yet though."
msgstr ""

#: C/anjuta-manual.xml:158(para)
msgid ""
"The methods those can be used to execute a program in the debugger are "
"described in the next sections. These commands are available only when the "
"program is already started."
msgstr ""

#: C/anjuta-manual.xml:165(title)
msgid "Single stepping (step in)"
msgstr ""

#: C/anjuta-manual.xml:166(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Step In</guimenuitem></menuchoice> or click on the "
"<guibutton>Step In</guibutton> icon in the <interface>Debug toolbar</"
"interface> to step into a program."
msgstr ""

#: C/anjuta-manual.xml:172(para)
msgid ""
"Single stepping executes only one statement of the program (from the place "
"where it has stopped) and then returns control. If the statement that is "
"executed contains one or more functions, the debugger tries to step inside "
"the functions (in the sequence in which the functions are executed). Once "
"the statement is executed and control is passed back, it is possible to "
"study the various program parameters."
msgstr ""

#: C/anjuta-manual.xml:179(para)
msgid ""
"If the <interface>Disassembly window</interface> has the focus when this "
"command is selected, it executes only one assembler instruction."
msgstr ""

#: C/anjuta-manual.xml:186(title)
msgid "Single stepping (step over)"
msgstr ""

#: C/anjuta-manual.xml:187(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Step Over</guimenuitem></menuchoice> or click on the "
"<guibutton>Step Over</guibutton> icon in the <interface>Debug toolbar</"
"interface> to step over statements in a program."
msgstr ""

#: C/anjuta-manual.xml:193(para)
msgid ""
"<emphasis>Step over</emphasis> is similar to <emphasis>step in</emphasis>, "
"except that it does not step inside any function in the statement being "
"executed. The statement will be executed in one go."
msgstr ""

#: C/anjuta-manual.xml:198(para)
msgid ""
"If the <interface>Disassembly window</interface> has the focus when this "
"command is selected, it executes one assembler instruction but does not stop "
"inside if this instruction is a call to a subroutine."
msgstr ""

#: C/anjuta-manual.xml:204(para)
msgid ""
"If a dynamic library is loaded during the step, the program will not stop at "
"the end of the step. But it will run until it finds a breakpoint or you stop "
"it."
msgstr ""

#: C/anjuta-manual.xml:213(title)
msgid "Single stepping (step out)"
msgstr ""

#: C/anjuta-manual.xml:214(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Step Out</guimenuitem></menuchoice> or click on the "
"<guibutton>Step Out</guibutton> icon in the <interface>Debug toolbar</"
"interface> to step out in a program."
msgstr ""

#: C/anjuta-manual.xml:220(para)
msgid ""
"<emphasis>Step out</emphasis> will execute the current function until it "
"returns. The program will be stopped once it exits from the function. Step "
"out is not really single stepping, because it does not only execute a single "
"statement — it executes the whole function until that function returns to "
"the calling function."
msgstr ""

#: C/anjuta-manual.xml:230(title)
msgid "Run/Continue"
msgstr ""

#: C/anjuta-manual.xml:231(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Run/Continue</guimenuitem></menuchoice> or click on "
"the <guibutton>Run/Continue</guibutton> icon in the <interface>Debug "
"toolbar</interface> to continue the execution of a program."
msgstr ""

#: C/anjuta-manual.xml:237(para)
msgid ""
"This option continues the execution of the program until a breakpoint is "
"encountered, or the program exits."
msgstr ""

#: C/anjuta-manual.xml:244(title)
msgid "Run To"
msgstr ""

#: C/anjuta-manual.xml:245(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Run to Cursor</guimenuitem></menuchoice> or click on "
"the <guibutton>Run to Cursor</guibutton> icon in the <interface>Debug "
"toolbar</interface> to run until the line at cursor is reached."
msgstr ""

#: C/anjuta-manual.xml:251(para)
msgid ""
"This option continues the execution of the program until the line or the "
"address (if the <interface>Disassembly window</interface> has the focus) "
"where the cursor is reached."
msgstr ""

#: C/anjuta-manual.xml:259(title)
msgid "Stop Program"
msgstr ""

#: C/anjuta-manual.xml:260(para)
msgid ""
"While the program is running and has control, no debugging tasks can be "
"performed. To obtain control while the program is running, choose the menu "
"item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Pause Program</"
"guimenuitem></menuchoice> or click on the <guibutton>Pause Program</"
"guibutton> icon in the <interface>Debug toolbar</interface>. This will "
"interrupt the program and return control to the debugger."
msgstr ""

#: C/anjuta-manual.xml:275(title)
msgid "Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:276(para)
msgid ""
"When debugging a program, it is useful to be able to stop the execution of "
"the program at a particular point, so that the state of the program can be "
"examined at that location. Breakpoints enable this to happen. Breakpoints "
"can be set at different locations in a source file and then the program is "
"allowed to run. When a breakpoint is encountered, the execution of the "
"program is suspended, enabling expressions to be evaluated, variables to be "
"inspected, the stack trace to be studied, and so on."
msgstr ""

#: C/anjuta-manual.xml:286(title)
msgid "Listing Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:287(para)
msgid ""
"The <interface>Breakpoint list window</interface> can be opened by choosing "
"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Breakpoints</"
"guimenuitem></menuchoice>"
msgstr ""

#: C/anjuta-manual.xml:294(title) C/anjuta-manual.xml:296(screeninfo)
msgid "Breakpoint view"
msgstr ""

#: C/anjuta-manual.xml:305(term) C/anjuta-manual.xml:401(term)
#, fuzzy
msgid "Location"
msgstr "Introduccion"

#: C/anjuta-manual.xml:307(para)
msgid ""
"This is the position of the breakpoint in the source file. When the "
"breakpoint is set by the debugger, you can get additional information like "
"the function where is the breakpoint."
msgstr ""

#: C/anjuta-manual.xml:315(term)
msgid "Address"
msgstr ""

#: C/anjuta-manual.xml:317(para)
msgid ""
"This field is filled with the address of the breakpoint when it is set by "
"the debugger."
msgstr ""

#: C/anjuta-manual.xml:324(term)
msgid "Type"
msgstr ""

#: C/anjuta-manual.xml:326(para)
msgid ""
"This displays always \"breakpoint\". It will be used in a next version "
"supporting different kind of breakpoints."
msgstr ""

#: C/anjuta-manual.xml:333(term) C/anjuta-manual.xml:428(term)
msgid "Condition"
msgstr ""

#: C/anjuta-manual.xml:335(para)
msgid ""
"This is the breakpoint condition, it is empty if no condition is defined."
msgstr ""

#: C/anjuta-manual.xml:341(term)
msgid "Pass count"
msgstr ""

#: C/anjuta-manual.xml:343(para)
msgid ""
"When the debugger is not running, this column displays the pass count of the "
"breakpoint, zero if it is not defined."
msgstr ""

#: C/anjuta-manual.xml:347(para)
msgid ""
"When the debugger is running, if pass count is zero, this column displays "
"the number of time this breakpoint has been triggered. If pass count is not "
"zero, both numbers are displayed. The pass count is the second number."
msgstr ""

#: C/anjuta-manual.xml:355(term)
msgid "State"
msgstr ""

#: C/anjuta-manual.xml:360(para)
msgid "Pending: breakpoint is not set in your program."
msgstr ""

#: C/anjuta-manual.xml:361(para)
msgid ""
"Permanent: breakpoint is set (id number in given inside the parenthesis)."
msgstr ""

#: C/anjuta-manual.xml:362(para)
msgid "Temporary: breakpoint is set but will be deleted if reached."
msgstr ""

#: C/anjuta-manual.xml:357(para)
msgid "This is the state of the breakpoint. You could have. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:301(para)
msgid "The view has the following columns: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:370(para)
msgid ""
"All breakpoints are kept across anjuta session even if they correspond to a "
"non existing place. In this case their state are set as pending.The "
"interface try to set them each time the program is started or a new dynamic "
"library is loaded."
msgstr ""

#: C/anjuta-manual.xml:379(title)
msgid "Adding or Setting Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:380(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> or "
"<menuchoice><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> in the "
"breakpoint list popup menu to open the add breakpoint dialog."
msgstr ""

#: C/anjuta-manual.xml:388(title) C/anjuta-manual.xml:390(screeninfo)
msgid "Breakpoint add dialog"
msgstr ""

#: C/anjuta-manual.xml:408(para)
msgid "File_name:Line_number"
msgstr ""

#: C/anjuta-manual.xml:409(para)
msgid "Function_name"
msgstr ""

#: C/anjuta-manual.xml:410(para)
msgid "File:Function_name"
msgstr ""

#: C/anjuta-manual.xml:403(para)
msgid ""
"Enter the location at which to set the breakpoint. It has to be specified in "
"one of the following formats: <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:414(para)
msgid ""
"The first one is obvious — The location refers to the line number "
"<emphasis>Line_number</emphasis> in the source file <emphasis>File</"
"emphasis>. The second refers to the first line of the function "
"<emphasis>Function_name</emphasis>. The third is similar to the second, "
"except that this notation is used where there is more than one function with "
"the name <emphasis>Function_name</emphasis> in the program. It is possible "
"to differentiate between them by providing the <emphasis>File</emphasis>, so "
"the notation refers to the function <emphasis>Function_name</emphasis> in "
"the file <emphasis>File</emphasis>."
msgstr ""

#: C/anjuta-manual.xml:430(para)
msgid ""
"The <emphasis>Condition</emphasis> parameter displays a associated "
"expression which should evaluate to a Boolean value — that is, the "
"evaluation of the expression should result in either TRUE(1) or FALSE(0). If "
"the final evaluation value is not a Boolean value, then it will be "
"appropriately type casted to a Boolean."
msgstr ""

#: C/anjuta-manual.xml:437(para)
msgid ""
"Every time the breakpoint is encountered during the execution, the break "
"condition will be evaluated. The debugger will break the execution only if "
"the evaluation results in a TRUE value, otherwise it will continue the "
"execution as though there had been no breakpoint."
msgstr ""

#: C/anjuta-manual.xml:443(para)
msgid ""
"The default value, if you left this field blank, of <emphasis>Break "
"condition</emphasis> is TRUE. The debugger will always break the execution "
"at the breakpoint location."
msgstr ""

#: C/anjuta-manual.xml:450(term)
msgid "Pass Count"
msgstr ""

#: C/anjuta-manual.xml:452(para)
msgid ""
"The <emphasis>Pass count</emphasis> is an integer (unsigned) value which "
"tells the debugger to skip the breakpoint that number of times before it is "
"considered. <emphasis>Pass count</emphasis> has a higher priority than the "
"<emphasis>Break condition</emphasis>. Only when the <emphasis>Pass count</"
"emphasis> reaches zero will the debugger evaluate the <emphasis>Break "
"condition</emphasis> (if any condition is present). If there is no "
"condition, the debugger will break the execution once the <emphasis>Pass "
"count</emphasis> counts down to zero."
msgstr ""

#: C/anjuta-manual.xml:462(para)
msgid ""
"The default value, if you left this field blank, of the <emphasis>Pass "
"count</emphasis> is zero. The breakpoint will be considered when it is first "
"encountered."
msgstr ""

#: C/anjuta-manual.xml:395(para)
msgid ""
"You need to enter the location and optionally, the break condition and the "
"pass count then click <guibutton>OK</guibutton> to set the breakpoint. "
"<placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:470(para)
msgid ""
"A breakpoint may also be set by selecting a line in the editor and choosing "
"the menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Toggle "
"Breakpoint</guimenuitem></menuchoice> in the editor popup menu item or the "
"<guibutton>Toggle Breakpoint</guibutton> icon in the <interface>Debug "
"toolbar</interface>."
msgstr ""

#: C/anjuta-manual.xml:479(para)
msgid ""
"Breakpoints can be added even if the debugger is not started or in dynamic "
"library not loaded yet. But they cannot be added while a program is running "
"under control of the debugger."
msgstr ""

#: C/anjuta-manual.xml:488(title)
msgid "Editing Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:489(para)
msgid ""
"It is possible to change the condition and the pass count by selecting the "
"breakpoint in the breakpoint list and click in the popup menu item "
"<menuchoice><guimenuitem>Edit Breakpoint</guimenuitem></menuchoice>."
msgstr ""

#: C/anjuta-manual.xml:494(para)
msgid ""
"Edit the entries as required and click on <guibutton>OK</guibutton> to "
"commit the changes."
msgstr ""

#: C/anjuta-manual.xml:501(title)
msgid "Deleting Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:502(para)
msgid ""
"Select the breakpoint in the breakpoint list view and click on "
"<menuchoice><guimenuitem>Remove Breakpoint</guimenuitem></menuchoice> to "
"delete it."
msgstr ""

#: C/anjuta-manual.xml:506(para)
msgid ""
"A existing breakpoint may also be deleted by selecting the line in the "
"editor and choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice>, the "
"editor popup menu item <menuchoice><guimenuitem>Toggle Breakpoint</"
"guimenuitem></menuchoice> or the <guibutton>Toggle Breakpoint</guibutton> "
"icon in the <interface>Debug toolbar</interface>."
msgstr ""

#: C/anjuta-manual.xml:515(para)
msgid ""
"It is possible to remove all breakpoints by clicking on "
"<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Remove All "
"Breakpoints</guimenuitem></menuchoice> or on <menuchoice><guimenuitem>Remove "
"All Breakpoints</guimenuitem></menuchoice> in the breakpoint list popup menu."
msgstr ""

#: C/anjuta-manual.xml:524(title)
msgid "Enabling or Disabling Breakpoints"
msgstr ""

#: C/anjuta-manual.xml:525(para)
msgid ""
"Click on the Enable column of the <interface>Breakpoint list window</"
"interface> or in the menu item <menuchoice><guimenuitem>Enable Breakpoint</"
"guimenuitem></menuchoice> to enable or disable the selected breakpoint. The "
"breakpoint will be enabled or disabled, depending on its current state."
msgstr ""

#: C/anjuta-manual.xml:531(para)
msgid ""
"To disable all breakpoints, click on <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Disable All Breakpoints</guimenuitem></menuchoice> "
"or on <menuchoice><guimenuitem>Disable All Breakpoints</guimenuitem></"
"menuchoice> in the breakpoint list popup menu."
msgstr ""

#: C/anjuta-manual.xml:542(title)
msgid "Expressions"
msgstr "Expressions"

#: C/anjuta-manual.xml:545(title)
msgid "Listing local variable"
msgstr ""

#: C/anjuta-manual.xml:546(para)
msgid ""
"When a program is running under the control of the debugger, the "
"<interface>Locals list window</interface> can be opened by choosing "
"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Locals</guimenuitem></"
"menuchoice>"
msgstr ""

#: C/anjuta-manual.xml:560(title) C/anjuta-manual.xml:562(screeninfo)
msgid "Local variables"
msgstr ""

#: C/anjuta-manual.xml:552(para)
msgid ""
"Local variables of the current frame (the current function in which the "
"program control is present) are displayed in the <interface>Locals list "
"window</interface>. During execution of the program (eg. during single "
"stepping), local variables will be updated. If any variable value was "
"changed in the last debugging step, its value will be highlight in red. The "
"variables are presented in a tree form for easy view. <placeholder-1/>"
msgstr ""

#: C/anjuta-manual.xml:567(para)
msgid ""
"The value of a local variable can be modified by selecting it and clicking "
"in the value column."
msgstr ""

#: C/anjuta-manual.xml:572(para)
msgid ""
"Gdb is more and more often used as a back end for a graphical front end. It "
"has been improved recently in this area. It is recommended to use the latest "
"version (6.6) of gdb. On older version, gdb can crash when the front end ask "
"for an pointer with an invalid (but not used) value."
msgstr ""

#: C/anjuta-manual.xml:582(title)
msgid "Listing watched expressions"
msgstr ""

#: C/anjuta-manual.xml:583(para)
msgid ""
"Inspecting or evaluating an expression provides the result only once. To "
"continuously monitor some variables or expressions, use <emphasis>expression "
"watch</emphasis>."
msgstr ""

#: C/anjuta-manual.xml:587(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>View</"
"guisubmenu><guimenuitem>Watches</guimenuitem></menuchoice> to display the "
"<interface>expression watch window</interface>."
msgstr ""

#: C/anjuta-manual.xml:594(title)
msgid "Adding an expression to watch"
msgstr ""

#: C/anjuta-manual.xml:595(para)
msgid ""
"Right-click on the <interface>expression watch window</interface> to open "
"the <interface>Operation menu</interface>. Choose the menu item "
"<guimenuitem>Add Watch…</guimenuitem>. Alternatively, you can use "
"<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Add Watch…</"
"guimenuitem></menuchoice> A dialog prompting for the expression will appear. "
"Enter the expression and click <guibutton>OK</guibutton>."
msgstr ""

#: C/anjuta-manual.xml:604(para)
msgid ""
"By default watch expression are updated automatically each time the program "
"is stopped. This can be changed in the add watch dialog or later using the "
"<guimenuitem>Automatic update</guimenuitem> menu item in the "
"<interface>expression watch window</interface> popup menu. A watched "
"expression can be update manually by choosing <guimenuitem>Update Watch</"
"guimenuitem> or <guimenuitem>Update All</guimenuitem> in the previous menu."
msgstr ""

#: C/anjuta-manual.xml:613(para)
msgid ""
"It is not necessary to have the debugger running to add a new watch "
"expression. If the debugger is not running or the corresponding expression "
"cannot be found, the front end will try to create the watch expression, each "
"time the program is stopped."
msgstr ""

#: C/anjuta-manual.xml:622(title)
msgid "Removing an expression from watch"
msgstr ""

#: C/anjuta-manual.xml:623(para)
msgid ""
"Select the watch expression that you want to remove in the "
"<interface>expression watch window</interface>, then open the "
"<interface>Operation menu</interface>, clicking with the right mouse button, "
"and choose the menu item <guimenuitem>Remove</guimenuitem> to remove it."
msgstr ""

#: C/anjuta-manual.xml:629(para)
msgid ""
"All watch can be removed by choosing <guimenuitem>Remove All</guimenuitem> "
"in the popup menu of the <interface>expression watch window</interface>."
msgstr ""

#: C/anjuta-manual.xml:636(title)
msgid "Evaluating expressions"
msgstr ""

#: C/anjuta-manual.xml:637(para)
msgid ""
"When control is returned from a program — possibly at a breakpoint — it is "
"possible to evaluate expressions or inspect the values of variables in the "
"program. Choose the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice>, "
"<menuchoice><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice> in "
"the popup menu of the editor or click the <guibutton>Inspect</guibutton> "
"button on the <interface>Debug Toolbar</interface>."
msgstr ""

#: C/anjuta-manual.xml:646(para)
msgid ""
"A window will appear showing the evaluation of the expression highlighted in "
"the editor. You can evaluate a new expression by clicking on the name column "
"and entering the new one."
msgstr ""

#: C/anjuta-manual.xml:652(para)
msgid ""
"The expression can be added directly in the list of watched expressions by "
"clicking on <guibutton>Add</guibutton> button."
msgstr ""

#: C/anjuta-manual.xml:659(title)
msgid "Inspecting expressions in editor window"
msgstr ""

#: C/anjuta-manual.xml:660(para)
msgid ""
"When the debugger is active with the program stopped, you can get the value "
"of an expression just by putting the pointer over it and stay here for a few "
"time. If the expression is already present in the local or watch window, its "
"value is displayed in a tool tips window."
msgstr ""

#: C/anjuta-manual.xml:666(para)
msgid ""
"It is currently working only for simple variable, not for structures or "
"arrays."
msgstr ""

#: C/anjuta-manual.xml:675(title)
msgid "Stack Trace"
msgstr ""

#: C/anjuta-manual.xml:678(title)
msgid "Stack Window"
msgstr ""

#: C/anjuta-manual.xml:679(para)
msgid ""
"The <interface>Stack trace window</interface> shows the contents of the "
"program stack. It lists all of the functions and their arguments in the "
"sequence they were called. There is also a number representing each call. "
"This number is called the <emphasis>Frame</emphasis>. Each call in the trace "
"exists in a different frame. This starts from frame 0 (the last function "
"called) and grows higher as the function nesting become deeper."
msgstr ""

#: C/anjuta-manual.xml:687(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>View </"
"guisubmenu><guimenuitem>Stack</guimenuitem></menuchoice>, to open the stack "
"trace for the program being debugged."
msgstr ""

#: C/anjuta-manual.xml:694(title) C/anjuta-manual.xml:696(screeninfo)
msgid "Stack trace window"
msgstr ""

#: C/anjuta-manual.xml:701(para)
msgid ""
"A small arrow points to the currently selected frame in the stack trace. By "
"default, this will be frame 0, the last function called. All of the "
"evaluation and inspection of expressions or variables will be with reference "
"to this selected frame. The scope of the variables or expressions being "
"evaluated will be limited to the selected frame only. The same applies for "
"new expressions only in the watch."
msgstr ""

#: C/anjuta-manual.xml:711(title)
msgid "Setting the current frame"
msgstr ""

#: C/anjuta-manual.xml:712(para)
msgid ""
"Double-clicking on any frame in the stack trace set that frame as the "
"currently selected frame (the arrow will point to the frame, indicating that "
"it has been selected as the current frame). Alternatively, open the "
"<interface>Operation menu</interface> by right-clicking on the "
"<interface>Stack trace window</interface>, and choose the menu item "
"<guimenuitem>Set current frame</guimenuitem> to set the frame."
msgstr ""

#: C/anjuta-manual.xml:720(para)
msgid ""
"Changing the stack frame changes the <interface>Locals list window</"
"interface> content, but not the <interface>expression watch window</"
"interface> as each expression is evaluated in the frame used when it was "
"defined."
msgstr ""

#: C/anjuta-manual.xml:730(title)
msgid "Thread"
msgstr ""

#: C/anjuta-manual.xml:733(title)
msgid "Thread Window"
msgstr ""

#: C/anjuta-manual.xml:734(para)
msgid ""
"The <interface>Thread window</interface> show all threads used by the "
"program and display the current thread. Choose the menu item "
"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Thread</guimenuitem></"
"menuchoice>, to open this window."
msgstr ""

#: C/anjuta-manual.xml:739(para)
msgid ""
"A small arrow points to the current thread. When the program is stopped, it "
"correspond to the thread which has been interrupted. Each thread has its own "
"stack frame,so changing the current thread change the current stack frame."
msgstr ""

#: C/anjuta-manual.xml:748(title)
msgid "Setting the current thread"
msgstr ""

#: C/anjuta-manual.xml:749(para)
msgid ""
"Double-clicking on any thread in the thread list will set that thread as the "
"currently selected thread (the arrow will point to the thread, indicating "
"that it has been selected as the current thread). Alternatively, open the "
"<interface>Operation menu</interface> by right-clicking on the "
"<interface>Thread list window</interface>, and choose the menu item "
"<guimenuitem>Set current thread</guimenuitem> to set the thread."
msgstr ""

#: C/anjuta-manual.xml:757(para)
msgid ""
"Changing the thread changes the value of CPU registers and the current stack "
"frame, so the <interface>Locals list window</interface> change too."
msgstr ""

#: C/anjuta-manual.xml:766(title)
msgid "CPU"
msgstr ""

#: C/anjuta-manual.xml:769(title)
msgid "Register window"
msgstr ""

#: C/anjuta-manual.xml:770(para)
msgid ""
"It is possible to examine the contents of the internal registers of the CPU "
"(microprocessor). Choose the menu item <menuchoice><guisubmenu>View</"
"guisubmenu><guimenuitem>Registers</guimenuitem></menuchoice>. A window "
"listing all of the available registers in the microprocessor and their "
"corresponding contents will appear."
msgstr ""

#: C/anjuta-manual.xml:777(para)
msgid ""
"If any register value was changed in the last debugging step, its value will "
"be highlight in red. It is possible to change one register value by "
"selecting it and clicking in the value column."
msgstr ""

#: C/anjuta-manual.xml:785(title)
msgid "Memory window"
msgstr ""

#: C/anjuta-manual.xml:786(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>View</"
"guisubmenu><guimenuitem>Memory </guimenuitem></menuchoice>, to open the "
"<interface>memory window</interface> for the program being debugged. This "
"window shows the contents of all memory."
msgstr ""

#: C/anjuta-manual.xml:791(para)
msgid ""
"The first is the memory address in hexadecimal, the second is the memory "
"content in hexadecimal too and the last column is the memory content in "
"ASCII."
msgstr ""

#: C/anjuta-manual.xml:795(para)
msgid ""
"The addressing space of even a 32 bits microprocessor is quite big(4 Giga "
"bytes), so it is very difficult to go to a particular address with the "
"scrollbar. But you can click on the right mouse button, get a new menu and "
"select <menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to "
"get a small edit box where you can enter an address in hexadecimal."
msgstr ""

#: C/anjuta-manual.xml:805(title)
msgid "Disassembly window"
msgstr ""

#: C/anjuta-manual.xml:806(para)
msgid ""
"Choose the menu item <menuchoice><guisubmenu>View</"
"guisubmenu><guimenuitem>Disassembly </guimenuitem></menuchoice>, to open the "
"<interface>disassembly window</interface> for the program being debugged."
msgstr ""

#: C/anjuta-manual.xml:811(para)
msgid ""
"The first column is the address in hexadecimal. In the second column, you "
"can have a label starting at the beginning of the line and ended with a "
"colon or a assembler instruction starting after 4 space characters."
msgstr ""

#: C/anjuta-manual.xml:816(para)
msgid ""
"Again, as the addressing space is very big, the scrollbar is quite useless. "
"You can click on the right mouse button, get a new menu and select "
"<menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to get a "
"small edit box where you can enter an address in hexadecimal. The position "
"in the disassembly window will be changed to the program counter value when "
"the program is stopped."
msgstr ""

#: C/anjuta-manual.xml:829(title)
msgid "Others"
msgstr "Autres"

#: C/anjuta-manual.xml:831(para)
msgid ""
"There are a number of other debugger features used less frequently and not "
"very well integrated in the new front end but which are still working."
msgstr ""

#: C/anjuta-manual.xml:837(title)
msgid "Dynamically loaded Libraries"
msgstr ""

#: C/anjuta-manual.xml:838(para)
msgid ""
"To obtain a list of the dynamic libraries used by the program, choose the "
"menu item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
"guisubmenu><guimenuitem>Shared Libraries</guimenuitem></menuchoice>. This "
"will bring open a window which will list all the shared libraries the "
"program has loaded and their locations in the memory. It also shows whether "
"the symbol table is loaded or not (Yes/No)."
msgstr ""

#: C/anjuta-manual.xml:848(title) C/anjuta-manual.xml:850(screeninfo)
msgid "Shared Libraries window"
msgstr ""

#: C/anjuta-manual.xml:858(title)
msgid "Kernel Signals"
msgstr ""

#: C/anjuta-manual.xml:859(para)
msgid ""
"Kernel signals are a way of signaling between processes in Linux. The list "
"of signals available for a program can be displayed by choosing the menu "
"item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
"guisubmenu><guimenuitem>Kernel Signals</guimenuitem></menuchoice>. A window "
"will open which lists all of the signals available in the system along with "
"a brief description of each signal."
msgstr ""

#: C/anjuta-manual.xml:868(title) C/anjuta-manual.xml:870(screeninfo)
msgid "Kernel Signals window"
msgstr ""

#: C/anjuta-manual.xml:875(para)
msgid ""
"There are three columns which specify what to do when the signal is received:"
msgstr ""

#: C/anjuta-manual.xml:881(para)
msgid ""
"<emphasis>Stop</emphasis> — this tells the debugger whether to stop the "
"program execution (and return control) when the program receives this signal."
msgstr ""

#: C/anjuta-manual.xml:887(para)
msgid ""
"<emphasis>Print</emphasis> — this tells the debugger whether to display the "
"received signal."
msgstr ""

#: C/anjuta-manual.xml:892(para)
msgid ""
"<emphasis>Pass</emphasis> — this tells the debugger whether to pass the "
"signal to the program."
msgstr ""

#: C/anjuta-manual.xml:898(para)
msgid ""
"The popup menu that is displayed when you click on the right mouse button "
"has all its item disabled because the corresponding functions are not "
"implemented yet."
msgstr ""

#: C/anjuta-manual.xml:907(title)
msgid "Information about used files"
msgstr "Entresenhas a prepaus de fichièrs utilizats"

#: C/anjuta-manual.xml:908(para)
msgid ""
"It is possible to get some information about the files used by the debugged "
"program. by choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Target files</"
"guimenuitem></menuchoice>. A window will open displaying all informations."
msgstr ""

#: C/anjuta-manual.xml:917(title)
msgid "Information about debugged program"
msgstr ""

#: C/anjuta-manual.xml:918(para)
msgid ""
"It is possible to get some information about the debugged program by "
"choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Program</"
"guimenuitem></menuchoice>. A window will open displaying all informations."
msgstr ""

#: C/anjuta-manual.xml:927(title)
msgid "Information about kernel structure"
msgstr ""

#: C/anjuta-manual.xml:928(para)
msgid ""
"It is possible to get some information kernel data on the current process by "
"choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Kernel user "
"struct</guimenuitem></menuchoice>. A window will open displaying all "
"informations."
msgstr ""

#: C/anjuta-manual.xml:937(title)
msgid "Information about global variables"
msgstr ""

#: C/anjuta-manual.xml:938(para)
msgid ""
"It is possible to list all global variables by choosing the menu item "
"<menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Information</"
"guisubmenu><guimenuitem>Info Global Variable</guimenuitem></menuchoice>. A "
"window will open listing all global variables."
msgstr ""

#: C/anjuta-manual.xml:947(title)
msgid "Information about the current frame"
msgstr ""

#: C/anjuta-manual.xml:948(para)
msgid ""
"It is possible to obtain information about the currently selected frame by "
"choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Info Current "
"Frame</guimenuitem></menuchoice>. A window will open describing the current "
"frame."
msgstr ""

#: C/anjuta-manual.xml:957(title)
msgid "Information about the current function arguments"
msgstr ""

#: C/anjuta-manual.xml:958(para)
msgid ""
"It is possible to obtain information about the arguments of the current "
"function by choosing the menu item <menuchoice><guisubmenu>Debug</"
"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Arguments</"
"guimenuitem></menuchoice>. A window will open describing the arguments."
msgstr ""

#: C/anjuta-manual.xml:967(title)
msgid "User command"
msgstr "Comanda personalizada"

#: C/anjuta-manual.xml:968(para)
msgid ""
"To send directly a command to the back end choose the menu item "
"<menuchoice><guimenu>Debug</guimenu><guimenuitem>Debugger command</"
"guimenuitem></menuchoice>. This will bring a small dialog where you can "
"enter commands that will be send to the debugger when you press "
"<keycap>Return</keycap>."
msgstr ""

#: C/anjuta-manual.xml:976(para)
msgid ""
"The front end sends this command directly to the back end without doing any "
"check. By example if you set a breakpoint like this, it will not appear in "
"the <interface>breakpoint list window</interface>. It is better to avoid "
"using this command unless you know exactly what you are doing."
msgstr ""

#: C/anjuta-manual.xml:3(title)
msgid "Preferences"
msgstr "Preferéncias"

#: C/anjuta-manual.xml:4(para)
msgid ""
"Preferences are ways to customize <application>anjuta</application> to suit "
"your tastes. Activate <menuchoice><guimenu>Settings</"
"guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> to bring up the "
"preferences dialog. If you want to reset the preferences to their default "
"values, it can be done from <menuchoice><guimenu>Settings</"
"guimenu><guimenuitem> Set Default Preferences</guimenuitem></menuchoice>. "
"Some are explained below."
msgstr ""

#: C/anjuta-manual.xml:11(title)
msgid "General"
msgstr "General"

#: C/anjuta-manual.xml:13(para)
msgid ""
"<emphasis>Project Directory</emphasis> is the path where you plan to put all "
"your projects. Application wizard creates new projects in this directory "
"only. The default project directory is ~/Projects and generally, this is "
"just fine for most people. Also, when Open project is activated, this is the "
"base directory where the file selection will start."
msgstr ""

#: C/anjuta-manual.xml:20(para)
msgid ""
"<emphasis>User Info:</emphasis> Provide your correct Name and Email address "
"here. They are not used to do software registration (pun), rather they are "
"used to create ChangeLog entries and other insert text bits."
msgstr ""

#: C/anjuta-manual.xml:27(title)
msgid "File Manager"
msgstr "Gestionari de fichièrs"

#: C/anjuta-manual.xml:29(para)
msgid ""
"<emphasis>Root directory if no project is open</emphasis> is the path where "
"the root of the file manager points to if no project is currently open."
msgstr ""

#: C/anjuta-manual.xml:34(para)
msgid ""
"<emphasis>File Filter:</emphasis> It is possible to filter out some file "
"from the file tree, for example hidden files or files that are ignored by "
"the version control system which usually means they are generated at build "
"time and should not be changed."
msgstr ""

#: C/anjuta-manual.xml:3(title)
msgid "User-defined Tools"
msgstr ""

#: C/anjuta-manual.xml:7(para)
msgid ""
"Often, you'll find the inbuilt functionality provided by Anjuta to be "
"insufficient. In these cases, you might be tempted to either add the feature "
"yourself to the Anjuta codebase or submit a feature request to implement the "
"feature. However, both approaches are likely to be slow and problematic, "
"especially if your tool is a specialized one. In these circumstances, it is "
"advisable to use the Anjuta tools framework instead."
msgstr ""

#: C/anjuta-manual.xml:16(para)
msgid ""
"Anjuta provides a powerful framework for defining user-defined tools for "
"extending it's functionality. Tools have access to almost all features of "
"the IDE through the use of variables. You can add tools under any menu item, "
"specify input, output and error redirection within the GUI framework and "
"supply command line parameters to the tool."
msgstr ""

#: C/anjuta-manual.xml:24(para)
msgid "The tools plugin has to be enabled to use this feature!"
msgstr ""

#: C/anjuta-manual.xml:31(title)
msgid "Tools Examples"
msgstr ""

#: C/anjuta-manual.xml:32(para)
msgid ""
"This is a simple example how to use the tools plugin to integrate the GNOME "
"ChangeLog generation script"
msgstr ""

#: C/anjuta-manual.xml:38(title) C/anjuta-manual.xml:40(screeninfo)
msgid "The tool editor"
msgstr ""

#: C/anjuta-manual.xml:2(title)
msgid "Authors"
msgstr "Autors"

#: C/anjuta-manual.xml:3(para)
msgid ""
"The <application>Anjuta</application> project was founded by Naba Kumar. "
"Please visit <ulink type=\"http\" url=\"http://anjuta.org?page=authors/"
"\">this online list</ulink> to know all Anjuta contributors."
msgstr ""

#: C/anjuta-manual.xml:10(para)
msgid ""
"For more information on <application>Anjuta</application>, please visit the "
"project website at <ulink type=\"http\" url=\"http://anjuta.org/\">http://"
"anjuta.org</ulink>. Bug reports should be made using the Bug Tracker at the "
"project development site <ulink type=\"http\" url=\"http://www.sourceforge."
"net/projects/anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>"
msgstr ""

#: C/anjuta-manual.xml:18(para)
msgid ""
"This manual was written by Naba Kumar and Andy Piper. Please send all "
"comments and suggestions regarding this manual to Anjuta Devel list "
"<email>anjuta-devel@list.sourceforge.net</email>. Comments may also be "
"submitted via the project trackers at SourceForge."
msgstr ""

#: C/anjuta-manual.xml:2(title)
msgid "License"
msgstr "Licéncia"

#: C/anjuta-manual.xml:3(para)
msgid ""
"This program is free software; you can redistribute it and/or modify it "
"under the terms of the <ulink type=\"ghelp\" url=\"gnome-help:gpl\">GNU "
"General Public License</ulink> as published by the Free Software Foundation; "
"either version 2 of the License, or (at your option) any later version."
msgstr ""

#: C/anjuta-manual.xml:10(para)
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. See the <citetitle>GNU General Public "
"License</citetitle> for more details."
msgstr ""

#: C/anjuta-manual.xml:16(para)
msgid ""
"A copy of the <citetitle>GNU General Public License</citetitle> is included "
"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also "
"obtain a copy of the <citetitle>GNU General Public License</citetitle> from "
"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://"
"www.fsf.org\"> their Web site</ulink> or by writing to <address> Free "
"Software Foundation, Inc. <street>51 Franklin Street</street> Fifth Floor "
"<city>Boston</city>, <state>MA</state><postcode>02110-1301</"
"postcode><country>USA</country></address>"
msgstr ""

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
#: C/anjuta-manual.xml:0(None)
msgid "translator-credits"
msgstr "Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>"