1 # Jorge González <jorgegonz@svn.gnome.org>, 2007.
4 "Project-Id-Version: anjuta.help.HEAD\n"
5 "POT-Creation-Date: 2007-08-30 23:41+0100\n"
6 "PO-Revision-Date: 2007-12-16 13:55+0100\n"
7 "Last-Translator: Jorge González <jorgegonz@svn.gnome.org>\n"
8 "Language-Team: Spanish <gnome-es-list@gnome.org>\n"
10 "Content-Type: text/plain; charset=UTF-8\n"
11 "Content-Transfer-Encoding: 8bit\n"
12 "X-Generator: KBabel 1.11.4\n"
13 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
15 #: C/anjuta-manual.xml:25(title)
16 msgid "Anjuta IDE Manual"
17 msgstr "Manual para el EID Anjuta"
19 #: C/anjuta-manual.xml:26(edition)
23 #: C/anjuta-manual.xml:28(para)
24 msgid "Manual for the Anjuta IDE"
25 msgstr "Manual para el EID Anjuta"
27 #: C/anjuta-manual.xml:32(firstname)
31 #: C/anjuta-manual.xml:33(surname)
35 #: C/anjuta-manual.xml:36(firstname)
39 #: C/anjuta-manual.xml:37(surname)
43 #: C/anjuta-manual.xml:40(firstname)
47 #: C/anjuta-manual.xml:41(surname)
48 msgid "Chattopadhyayr"
49 msgstr "Chattopadhyayr"
51 #: C/anjuta-manual.xml:44(firstname)
55 #: C/anjuta-manual.xml:45(surname)
59 #: C/anjuta-manual.xml:49(year)
63 #: C/anjuta-manual.xml:50(year)
67 #: C/anjuta-manual.xml:51(holder)
68 msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
69 msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
71 #: C/anjuta-manual.xml:52(holder)
72 msgid "Johannes Schmid"
73 msgstr "Johannes Schmid"
75 #: C/anjuta-manual.xml:56(para)
77 "Permission is granted to copy, distribute and/or modify this document under "
78 "the terms of the <citetitle>GNU Free Documentation License</citetitle>, "
79 "Version 1.1 or any later version published by the Free Software Foundation "
80 "with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. "
81 "You may obtain a copy of the <citetitle>GNU Free Documentation License</"
82 "citetitle> from the Free Software Foundation by visiting <ulink type=\"http"
83 "\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to: Free "
84 "Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-"
88 #: C/anjuta-manual.xml:68(para)
90 "Many of the names used by companies to distinguish their products and "
91 "services are claimed as trademarks. Where those names appear in any GNOME "
92 "documentation, and those trademarks are made aware to the members of the "
93 "GNOME Documentation Project, the names have been printed in caps or initial "
96 "Muchos de los nombres usados por compañías para distinguir sus productos y "
97 "servicios se mencionan como marcas comerciales. Donde aparezcan dichos "
98 "nombres en cualquier documentación GNOME, y para que los miembros del "
99 "proyecto de documentación las reconozcan dichas marcas comerciales, dichos "
100 "nombres se imprimen en mayúsculas o iniciales mayúsculas."
102 #: C/anjuta-manual.xml:79(revnumber)
103 msgid "Anjuta Manual 2.1.0"
104 msgstr "Manual de Anjuta 2.1.0"
106 #: C/anjuta-manual.xml:80(date)
110 #: C/anjuta-manual.xml:82(para)
111 msgid "Johannes Schmid<email>jhs@gnome.org</email>"
112 msgstr "Johannes Schmid<email>jhs@gnome.org</email>"
114 #: C/anjuta-manual.xml:84(para)
116 msgstr "Equipo de Anjuta"
118 #: C/anjuta-manual.xml:3(title) C/anjuta-manual.xml:6(title)
120 msgstr "Introducción"
122 #: C/anjuta-manual.xml:4(para)
124 "<application>Anjuta</application> is a versatile Integrated Development "
125 "Environment (IDE) for the GNOME desktop. It features a number of advanced "
126 "programming facilities that include project management, application wizards, "
127 "an on-board interactive debugger, an integrated glade UI designer, "
128 "integrated devhelp API help, an integrated valgrind memory profiler, an "
129 "integrated gprof performance profiler, a class generator, a powerful source "
130 "editor, source browsing, and more. is a versatile Integrated Development "
133 "<application>Anjuta</application> es un Editor Integrado de Desarrollo (EID) versátil "
134 "para el escritorio GNOME. Tiene ciertas características para facilitar la programación "
135 "que incluyen gestión de proyectos, asistentes de aplicación, "
136 "un depurador integrado intergrado, un diseñador de IU Glade integrado, "
137 "una ayuda API de devhelp integrada, un perfilador de memoria valgrind integrado, "
138 "un perfilador de rendimiento grpof integrado, un generador de clases, un potente editor "
139 "de código fuente, búsqueda de fuentes y mucho más."
141 #: C/anjuta-manual.xml:15(para)
143 "Anjuta DevStudio has been designed to be simple to operate yet powerful "
144 "enough to fullfil all your programming needs. Many features have evolved "
145 "since the early days and several very attractive ones added. Our focus is on "
146 "delivering power and usability at the same time without overloading your "
147 "senses and making your software development a pleasurable process. We will "
148 "always be busy getting you one of the best IDE experiences by straighting up "
149 "all the neat features and stablizing it. We hope you will have a good time "
150 "using Anjuta. If not, please help us make it better by reporting bugs and "
151 "suggestions. Here are some of the things you will find in Anjuta."
154 #: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
155 msgid "Anjuta in action"
156 msgstr "Anjuta en acción"
158 #: C/anjuta-manual.xml:37(para)
160 "Anjuta has a very flexible and advanced docking system that allows you to "
161 "layout all views in whatever way you like. You can drag and drop the views "
162 "using drag bars and re-arrange the layout. The layouts are persistent for "
163 "each project so you can maintain different layouts required by projects. All "
164 "dock views are minimizable to avoid clutter in main window. Minimized views "
165 "appear as icons on left side of main window. All menu actions are "
166 "configurable either by type-in-the-menu (the usual GNOME way) or by a "
167 "dedicated shortcuts configuration UI."
170 #: C/anjuta-manual.xml:48(para)
172 "Please report any problems with <application>Anjuta</application> - this "
173 "will help to improve the software, as well as helping the Open Source "
176 "Por favor, informe de cualquier problema con <application>Anjuta</application>: esto "
177 "ayudará a mejorar el software así como ayuda a la comunidad código abierto («Open Source»)."
179 #: C/anjuta-manual.xml:2(title)
180 msgid "Getting Familiar with Anjuta"
181 msgstr "Familiarizarse con Anjuta"
183 #: C/anjuta-manual.xml:5(title)
184 msgid "Menus and shortcuts"
185 msgstr "Menús y atajos de teclado"
187 #: C/anjuta-manual.xml:6(para)
189 "At the top of the <application>Anjuta</application> main window is the "
190 "menubar. Almost all of the functions are available by activating the "
191 "appropriate menu item. The functions have been grouped according to their "
192 "type. For example, the file operations have been grouped into the "
193 "<guisubmenu>File</guisubmenu> menu."
195 "En la parte superior de la ventana principal de <application>Anjuta</application> está la "
196 "barra de menú. Casi todas las funciones están disponibles al activar el elemento "
197 "del menú apropiado. Las funciones se han agrupado de acuerdo con su "
198 "tipo. Por ejemplo, las operaciones con archivos se han agrupado dentro del "
199 "menú <guisubmenu>Archivo</guisubmenu>."
201 #: C/anjuta-manual.xml:15(title)
203 msgstr "Barra de menú"
205 #: C/anjuta-manual.xml:17(screeninfo)
206 msgid "Anjuta menubar"
207 msgstr "Barra de menú de Anjuta"
209 #: C/anjuta-manual.xml:22(para)
211 "Most of the menus and submenus can be detached. Click on the detach bar (the "
212 "dashed line just above the first menu item). Once the menu is detached, it "
213 "will become an independent window."
215 "La mayoría de los menús y submenús se pueden desacoplar. Pulse en la barra de desacoplamiento (la "
216 "línea en puntos suspensivos justo encima del primer elemento del menú). Una vez que el menú está desacoplado, "
217 "será una ventana independiente."
219 #: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
221 msgstr "Menú Archivo"
223 #: C/anjuta-manual.xml:36(para)
225 "Shortcut keys are available for many of the menu options. All of the "
226 "shortcut keys are shown alongside the corresponding menu items. A useful "
227 "reference to the shortcut keys which are not directly attachted with the "
228 "menu is also available in the next section. Some useful shortcuts are listed "
231 "Las teclas rápidas, o aceleradores de teclado, están disponibles para muchas de las opciones de los menús. Todas las "
232 "teclas rápidas se muestran junto con los elementos del menú correspondientes. También hay una referencia útil "
233 "acerca de las teclas rápidas que no están directamente adjuntas a los menús en la siguiente sección. A continuación se listan algunas teclas rápidas útiles."
235 #: C/anjuta-manual.xml:46(para)
237 "<emphasis>Switch Editor page:</emphasis> CTRL-TAB (forward) and CTRL-SHIFT-"
238 "TAB (backward) -- The pages could also be switched by right clicking on the "
239 "notebook tabs and selecting an editor tab (useful when all the tabs in the "
240 "editor are not visible at once). Some desktop configuration may already have "
241 "these shortcut keys assigned. In that case, you will need to reconfigure "
242 "them (not in anjuta, because they are fixed) if you want to avail these "
246 #: C/anjuta-manual.xml:55(para)
248 "<emphasis>Context Help:</emphasis> SHIFT-F1 -- Keep the cursor on the word "
249 "(for example, the function name) for which you want to get the API help and "
250 "press the shortcut. Context help only works if you have "
251 "<application>DevHelp</application> installed. If you do not have "
252 "<application>DevHelp</application> installed, the context help menu and "
253 "toolbar button will be inactive. You can get it from <application>DevHelp</"
254 "application> website. You will also have to install the related "
255 "<application>DevHelp</application> books."
258 #: C/anjuta-manual.xml:65(para)
260 "<emphasis>Auto complete:</emphasis> CTRL-ENTER -- Press the shortcut with "
261 "the cursor placed at the end of incomplete word and a list of words matching "
262 "the remaining part will appear. Scroll and select the right word from the "
263 "list if you find one."
265 "<emphasis>Autocompletar:</emphasis> Ctrl+Intro; pulse la combinación de teclas con "
266 "el cursor ubicado al final de una palabra incompleta y se mostrará una lista de palabras "
267 "que coincidan con la parte restante. Desplace la lista y seleccione la palabra correcta de "
268 "la lista, si encuentra una."
270 #: C/anjuta-manual.xml:72(para)
272 "<emphasis>More shortcus:</emphasis> Look for the shortcut keys displayed on "
273 "right side of the menu item labels. They could also be changed as explained "
276 "<emphasis>Más teclas rápidas:</emphasis> Consulte las teclas rápidas mostradas en "
277 "la parte derecha de las etiquetas de los elementos del menú. También se pueden cambiar como se explica "
278 "en el siguiente consejo."
280 #: C/anjuta-manual.xml:79(title)
281 msgid "Customize shortcuts"
282 msgstr "Personalizar los atajos de teclado"
284 #: C/anjuta-manual.xml:80(para)
286 "You can change the default shortcuts by using "
287 "<menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Customize "
288 "shortcuts</guimenuitem></menuchoice>."
289 msgstr "Puede cambiar las combinaciones de teclas predeterminadas usando <menuchoice><guisubmenu>Ajustes</guisubmenu><guimenuitem>Personalizar las teclas rápidas</guimenuitem></menuchoice>."
291 #: C/anjuta-manual.xml:90(title)
293 msgstr "Ventana principal"
295 #: C/anjuta-manual.xml:91(para)
297 "In the main window, there are several views which can be reordered by "
298 "dragging on their title bars. They can also be minimized by clicking on the "
299 "minimize buttons on the left of title bars."
301 "En la ventana principal hay varias vistas que se pueden reordenar "
302 "soltando sus barras de título. También se pueden minimizar pulsando en los "
303 "botones de minimizar en la parte izquierda de las barras de título."
305 #: C/anjuta-manual.xml:100(para)
307 "The <interface>Documents window</interface> will have one document active at "
308 "a time (if there are any files opened). All of the file commands will apply "
309 "to this active document. You can switch to any page by clicking on the page "
310 "tab. You can do the same by right-clicking on the page tabs and choosing the "
311 "document from the pop-up menu that will appear. This is especially useful "
312 "when you have a lot of files opened, but not all of them are visible in the "
316 #: C/anjuta-manual.xml:111(para)
318 "The <interface>Project window</interface> shows a tree of the project files "
319 "if you have a project opened. Otherwise, the <interface>Project window</"
320 "interface> is usually hidden. Double-clicking on any item in the "
321 "<interface>Project window</interface> will open that file."
324 #: C/anjuta-manual.xml:119(para)
326 "The <interface>Files window</interface> shows a file tree. If no project is "
327 "open, the file tree usually points to the file system root but you can "
328 "change it in the preferences. If a project is open it shows all files inside "
329 "the project. Double clicking opens a file in the appropriate application as "
330 "configured in the gnome mime preferences. Richt click opens a popup-menu "
331 "which gives you choices how to open the file."
334 #: C/anjuta-manual.xml:128(para)
336 "The <interface>Symbols window</interface> shows shows a tree of availible "
337 "symbols in the project generated from ctags parser. Double clicking opens an "
338 "editor window with the corresponding file and line."
340 "La <interface>ventana de símbolos</interface> muestra un árbol con los símbolos "
341 "disponibles en el proyecto generados desde el analizador ctags. Al pulsar dos veces se abre una "
342 "ventana del editor con el archivo y líneas correspondientes."
344 #: C/anjuta-manual.xml:133(para)
346 "There is also a <interface>Search tab</interface> in the Symbols window "
347 "where you can search for symbols."
349 "También existe una <interface>Barra de búsqueda</interface> en la ventana Símbolos "
350 "en la que puede buscar símbolos."
352 #: C/anjuta-manual.xml:139(para)
354 "The <interface>Message window</interface> will list all the messages (both "
355 "<filename>stdout</filename> and <filename>stderr</filename> outputs) when an "
356 "external command is executed. The <interface>Message window</interface> is "
357 "usually hidden, but appears as soon as an external command is executed, such "
358 "as during file or project compilation, debugging sessions, searches, and "
359 "many other operations. <application>Anjuta</application> also adds its own "
360 "messages here when necessary."
363 #: C/anjuta-manual.xml:147(para)
365 "The colors used to display the messages are important. Messages displayed in "
366 "the standard foreground color (usually Black) are normal messages. Those "
367 "displayed in Blue are important messages such as errors or other "
368 "information. Messages shown in Red are <emphasis>Hot Linked</emphasis>. "
369 "Double-clicking on such a message will take you to the particular file and "
370 "line number specified in the message."
373 #: C/anjuta-manual.xml:155(para)
375 "For example, when you compile a file which contains bugs, some red messages "
376 "will appear showing what the problems are, and where they occur. Double-"
377 "clicking on such messages will open the file and highlight the line "
378 "containing the error."
380 "Por ejemplo, cuando compila un archivo que contiene errores aparecerán algunos mensajes "
381 "en rojo mostrando los problemas y dónde ocurren. Al pulsar dos veces "
382 "sobre dichos mensajes se abrirá el archivo y se resaltará la línea que "
385 #: C/anjuta-manual.xml:163(para)
387 "The <interface>Terminal window</interface> is a terminal emulation where you "
388 "can type commands just like in the gnome-terminal."
390 "La <interface>Ventana del terminal</interface> es una emulación de un terminal donde puede "
391 "ejecutar comandos igual que en gnome-terminal."
393 #: C/anjuta-manual.xml:171(title)
394 msgid "Session management"
395 msgstr "Gestión de sesiones"
397 #: C/anjuta-manual.xml:172(para)
399 "All of the settings, including the window sizes and window positions, are "
400 "saved when you exit <application>Anjuta</application>. Session management is "
401 "still under development, so you should not exit <application>Anjuta</"
402 "application> with any unsaved documents. <application>Anjuta</application> "
403 "will display a warning if you try to exit with unsaved documents still open."
405 "Todos los ajustes, incluyendo los tamaños y posiciones de las ventanas, se guardan "
406 "al salir de <application>Anjuta</application>. La gestión de las sesiones "
407 "aún está bajo desarrollo, así que no debería salir de <application>Anjuta</application> "
408 "sin haber guardado antes sus documentos. <application>Anjuta</application> "
409 "mostrará una advertencia si intenta salir con documentos sin guardar abiertos."
411 #: C/anjuta-manual.xml:2(title)
412 msgid "File Operations"
413 msgstr "Operaciones con archivos"
415 #: C/anjuta-manual.xml:6(title)
416 msgid "Creating a New File and inserting texts"
417 msgstr "Crear un archivo nuevo e insertar texto"
419 #: C/anjuta-manual.xml:8(title)
420 msgid "Creating New File"
421 msgstr "Crear un archivo nuevo"
423 #: C/anjuta-manual.xml:9(para)
425 "To create a new file, choose <menuchoice><guisubmenu>File</"
426 "guisubmenu><guimenuitem>New</guimenuitem></menuchoice> from the menubar, or "
427 "click on the <guibutton>New File</guibutton> button on the toolbar. A new "
428 "page will appear in the editor (or a new window if the parent document is "
429 "windowed). This new document will be named <filename>newfile#1</filename>, "
430 "<filename>newfile#2</filename>, <filename>newfile#3</filename> and so on."
432 "Para crear un archivo nuevo, elija <menuchoice><guisubmenu>Archivo</guisubmenu><guimenuitem>Nuevo</guimenuitem></menuchoice> de la barra de menú o pulse el botón <guibutton>Archivo nuevo</guibutton> en la barra de herramientas. Se abrirá "
433 "una nueva página en el editor (o una nueva ventana si el documento padre está en una "
434 "ventana). Este nuevo documento se llamará <filename>newfile#1</filename>, <filename>newfile#2</filename>, <filename>newfile#3</filename> y demás."
436 #: C/anjuta-manual.xml:19(title)
438 msgstr "Guardar archivo"
440 #: C/anjuta-manual.xml:20(para)
442 "You should save new documents as soon as possible to avoid any data loss in "
445 "Debería guardar sus documentos nuevos tan pronto como le sea posible para evitar cualquier pérdida de datos en "
448 #: C/anjuta-manual.xml:27(title)
450 msgstr "Asistente de archivos"
452 #: C/anjuta-manual.xml:38(title)
453 msgid "New File Wizard"
454 msgstr "Nuevo asistente de archivos"
456 #: C/anjuta-manual.xml:40(screeninfo) C/anjuta-manual.xml:153(screeninfo)
457 msgid "The Open File dialog"
458 msgstr "El diálogo Abrir archivo"
460 #: C/anjuta-manual.xml:28(para)
462 "A wizard can also be used to create a new file.To create a new file, choose "
463 "<menuchoice><guisubmenu>File</guisubmenu><guisubmenu>New</"
464 "guisubmenu><guimenuitem>File</guimenuitem></menuchoice> from the menubar. "
465 "This will open the New File Wizard dialog. Select the file type. Enter the "
466 "File name. The suffix will be automatically added. You can add a license "
467 "information (according to your license choice) and a header. In case of C-C+"
468 "+ header file, you can also add an header template. Click <guibutton>OK</"
469 "guibutton> to validate the creation. <placeholder-1/>"
471 "También se puede usar un asistente para crear un archivo nuevo. Para crear un archivo nuevo, elija "
472 "<menuchoice><guisubmenu>Archivo</guisubmenu><guisubmenu>Nuevo</"
473 "guisubmenu><guimenuitem>Archivo</guimenuitem></menuchoice> de la barra de menú. "
474 "Esto abrirá el diálogo Archivo nuevo. Seleccione el tipo de archivo. Introduzca el "
475 "nombre del archivo. El sufijo se añadirá automáticamente. Puede añadir información "
476 "sobre la licencia (de acuerdo con la licencia a su elección) y una cabecera. En caso de que "
477 "sea una cabecera C o C++, también puede añadir una plantilla de cabecera. Pulse <guibutton>Aceptar</guibutton> "
478 "para validar la creación. <placeholder-1/>"
480 #: C/anjuta-manual.xml:45(para)
482 "<application>Anjuta</application> occatinally also creates new files during "
483 "some operations. For example, some CVS operations, such as diff, file log, "
484 "file status etc, create new files and add the output there. These could be "
485 "saved in real file just like normal new files."
487 "<application>Anjuta</application> ocasionalmente crea nuevos archivos durante "
488 "algunas operaciones. Por ejemplo, algunas operaciones sobre CVS, tales como diff, log de un archivo, "
489 "status de un archivo, etc, crean archivos nuevos y añaden la salida allí. Estos se pueden "
490 "guardar en un archivo real igual que los nuevos archivos normales."
492 #: C/anjuta-manual.xml:53(title)
493 msgid "Inserting Macros"
494 msgstr "Insertar macros"
496 #: C/anjuta-manual.xml:54(para)
497 msgid "Macros can be used to quickly edit repetitive sequences of text."
498 msgstr "Se pueden usar macros para editar rápidamente secuencias repetitivas de texto."
500 #: C/anjuta-manual.xml:58(para)
501 msgid "Macro plugin must be activated."
502 msgstr "El complemento de macros debe estar activado."
504 #: C/anjuta-manual.xml:63(title)
508 #: C/anjuta-manual.xml:64(para)
510 "Two types of macros are available: Anjuta macros and User macros (My "
511 "macros). Anjuta macros are not modifiable by the user. On the other hand, "
512 "User macros can be defined and modified by the user."
514 "Existen dos tipos de macros disponibles: Los macros de Anjuta y los macros del usuario (Mis "
515 "macros). Los macros de Anjuta no son modificables por el usuario. Por otra parte, "
516 "los macros del usuario se pueden definir y modificar por el usuario."
518 #: C/anjuta-manual.xml:69(para)
520 "To insert macro, move the cursor at the desired place. Select "
521 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
522 "guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. The dialog "
523 "window appears. Select the wanted macro in the list. The result of the macro "
524 "expansion is displayed in the window and a summary is shown in the dialog "
525 "window. Choose <guibutton>Insert</guibutton>. The expanded macro text is "
526 "inserted at the cursor position."
528 "Para insertar una macro, mueva el cursor al lugar deseado. Seleccione "
529 "<menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</"
530 "guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. Aparecerá "
531 "la ventana de diálogo. Seleccione la macro deseada de la lista. El resultado de la expansión "
532 "de la macro se mostrará en la ventana así como un resumen en la ventana de diálogo. "
533 "Elija <guibutton>Insertar</guibutton>. Se insertará el texto de la macro expandida en "
534 "la posición del cursor."
536 #: C/anjuta-manual.xml:82(title)
540 #: C/anjuta-manual.xml:84(screeninfo)
541 msgid "The Macro dialog"
542 msgstr "El diálogo Macro"
544 #: C/anjuta-manual.xml:77(para)
546 "Another possibility to insert macro is to select "
547 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
548 "guisubmenu><guimenuitem>Insert Macro...</guimenuitem></menuchoice>, then to "
549 "press the wanted macro shortcut. <placeholder-1/>"
551 "Otra posibilidad para insertar un macro es seleecionar "
552 "<menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</guisubmenu><guimenuitem>Insertar macro…</guimenuitem></menuchoice>, después "
553 "pulsar el atajo de teclado sobre el macro seleccionado. <placeholder-1/>"
555 #: C/anjuta-manual.xml:91(title)
556 msgid "Defining Macros"
557 msgstr "Definir macros"
559 #: C/anjuta-manual.xml:92(para)
561 "From the Insert-Macro window, choose <guibutton>Add</guibutton> or select "
562 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
563 "guisubmenu><guimenuitem>Add Macro... </guimenuitem></menuchoice>. The Add/"
564 "Edit window appears. Enter the macro name, choose or define a category and "
565 "enter a shortcut. Then edit text relative to your macro. The character ' | ' "
566 "will indicate the cursor position after the macro insertion. Choose "
567 "<guibutton>OK</guibutton>. The macro is added to the list."
569 "Desde la ventana de Insertar macro, elija <guibutton>Añadir</guibutton> o seleccione "
570 "<menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</"
571 "guisubmenu><guimenuitem>Añadir macro...</guimenuitem></menuchoice>. Aparecerá "
572 "la ventana de Añadir/editar. Introduzca el nombre de la macro, elija o defina una categoría e "
573 "introduzca un atajo. Después edite el texto relativo a la macro. El carácter «|» "
574 "indicará la posición del cursor después de la inserción de la macro. Elija "
575 "<guibutton>Aceptar</guibutton>. La macro se añadirá a la lista."
577 #: C/anjuta-manual.xml:100(para)
579 "The user can also erase a macro by selecting it in the list (only My Macros) "
580 "then by choosing <guibutton>Remove</guibutton>."
582 "El usuario también puede borrar un macro seleccionándolo en la lista (sólo Mis macros) "
583 "y después eligiendo <guibutton>Eliminar</guibutton>."
585 #: C/anjuta-manual.xml:108(title)
586 msgid "Add/Edit Macro"
587 msgstr "Añadir/Editar macro"
589 #: C/anjuta-manual.xml:110(screeninfo)
590 msgid "Add Edit dialog"
591 msgstr "Diálogo Añadir/Editar"
593 #: C/anjuta-manual.xml:104(para)
595 "Same manner, macro can be edited and modified by selecting it in the list "
596 "then by choosing <guibutton>Edit</guibutton>. <placeholder-1/>"
598 "De la misma manera se puede editar un macro y modificarlo seleccionándolo en la lista "
599 "y después eligiendo <guibutton>Editar</guibutton>. <placeholder-1/>"
601 #: C/anjuta-manual.xml:117(title)
602 msgid "Macro Keywords"
603 msgstr "Palabras clave de los macros"
605 #: C/anjuta-manual.xml:118(para)
607 "Macros Keywords are available. They can be integrated in the macro "
608 "definitions. The names of these macro Keywords start and finish by the "
611 "Están disponibles las palabras clave para los macros. Pueden integrarse en la definición "
612 "del macro. Los nombres de estas palabras clave de los macros comienzan y finalizan con el "
615 #: C/anjuta-manual.xml:126(title)
616 msgid "Keyword Macro"
617 msgstr "Palabra clave del macro"
619 #: C/anjuta-manual.xml:128(screeninfo)
620 msgid "The Keyword macro"
621 msgstr "La palabra clave del macro"
623 #: C/anjuta-manual.xml:122(para)
625 "Available macro keywords are : @DATE_TIME@, @DATE_YMD@, @DATE_Y@, "
626 "@USER_NAME@, @FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, "
627 "@TABSIZE@, @INDENTSIZE@, @USETABS@. <placeholder-1/>"
629 "Las palabras clave de macro disponibles son: @DATE_TIME@, @DATE_YMD@, @DATE_Y@, "
630 "@USER_NAME@, @FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, "
631 "@TABSIZE@, @INDENTSIZE@, @USETABS@. <placeholder-1/>"
633 #: C/anjuta-manual.xml:139(title)
634 msgid "Opening and Saving Files"
635 msgstr "Abrir y guardar archivos"
637 #: C/anjuta-manual.xml:151(title)
638 msgid "Open File dialog"
639 msgstr "Diálogo Abrir archivo"
641 #: C/anjuta-manual.xml:143(para)
643 "<emphasis>Opening a file:</emphasis> To open an existing file, choose "
644 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Open</guimenuitem></"
645 "menuchoice> from the menubar, click on the <guibutton>Open</guibutton> "
646 "button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>O</"
647 "keycap></keycombo>. This will display the <interface>Open File</interface> "
648 "dialog. <placeholder-1/> Select or enter the file you want to open, then "
649 "click <guibutton>Open</guibutton>. To open more than one file at once, "
650 "select multiple files to open by first pressing CTRL and clicking the files "
651 "in the list and press <guibutton>Open</guibutton>. If you change your mind, "
652 "click <guibutton>Cancel</guibutton> to dismiss the dialog without opening "
656 #: C/anjuta-manual.xml:172(title)
657 msgid "Open Multiple File dialog"
658 msgstr "Diálogo Abrir múltiples archivos"
660 #: C/anjuta-manual.xml:174(screeninfo)
661 msgid "The Open File dialog in multiple-select mode"
662 msgstr "El diálogo Abrir archivo en el modo de múltiple selección"
664 #: C/anjuta-manual.xml:164(para)
666 "For selecting multiple files at once, select a file in the dialog and press "
667 "CTRL once. This will bring the file selection dialog in multiple-select mode "
668 "and multiple files could be selected from the list. Multiple file select "
669 "mode is simlar to single file select mode, except that the file operation "
670 "(for which the file selection was being done) will be performed for all the "
671 "selected files. <placeholder-1/>"
674 #: C/anjuta-manual.xml:179(para)
676 "The <emphasis>Show Hidden</emphasis>, if switched on (Click right), will "
677 "make the hidden files (files starting with \".\"; visible in the file list. "
678 "Depress it to make them hide. <application>Anjuta</application> "
679 "fileselection dialog also has inbuild file type filter. Select the "
680 "appropiate file type filter in the dialog and the file list will be limited "
681 "to the files of the selected type only."
684 #: C/anjuta-manual.xml:199(screeninfo)
685 msgid "The Save As File"
686 msgstr "Guardar como archivo"
688 #: C/anjuta-manual.xml:189(para)
690 "<emphasis>Saving a file:</emphasis> To save a file, choose "
691 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save</guimenuitem></"
692 "menuchoice> from the menubar, click on the <guibutton>Save</guibutton> "
693 "button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>S</"
694 "keycap></keycombo>. This will save the file. If the file is new, a "
695 "<interface>Save As</interface> dialog will appear. Enter a filename and "
696 "click <guibutton>Save</guibutton> to save the new file with the name "
697 "supplied. <placeholder-1/>"
700 #: C/anjuta-manual.xml:204(title)
701 msgid "File auto save"
702 msgstr "Autoguardar archivos"
704 #: C/anjuta-manual.xml:205(para)
706 "If you have enabled auto-save, it will not auto-save any new files. You must "
707 "first save them manually. The same applies to the <guimenuitem>Save All</"
708 "guimenuitem> option: it will not save new files, if you haven't saved them "
709 "first manually. <emphasis>You must save a file manually before auto-save or "
710 "<guimenuitem>Save All</guimenuitem> will work with it.</emphasis>"
713 #: C/anjuta-manual.xml:216(para)
715 "<emphasis>Saving a file with a different name:</emphasis> You can explicitly "
716 "save a file with a new filename. To do this, choose "
717 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save As</guimenuitem></"
718 "menuchoice> from the menubar. A <interface>Save As</interface> dialog will "
719 "appear prompting you to enter the new filename. Enter the name and click "
720 "<guibutton>Save</guibutton>."
723 #: C/anjuta-manual.xml:224(title)
724 msgid "File save as overwrite"
725 msgstr "Sobreescribir archivo al guardar"
727 #: C/anjuta-manual.xml:225(para)
729 "When you use <guimenuitem>Save As</guimenuitem> with an existing file, the "
730 "original is not deleted. It is left unchanged since the last save. If a file "
731 "with the new filename already exists, a confirmation dialog will appear, to "
732 "ensure that you want to overwrite it. Clicking <guibutton>Yes</guibutton> "
733 "will overwrite the file with the file you are saving."
736 #: C/anjuta-manual.xml:237(para)
738 "<emphasis>Closing a file:</emphasis> To close a file, choose "
739 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Close</guimenuitem></"
740 "menuchoice> from the menubar, or click on the <guibutton>Close</guibutton> "
741 "button on the toolbar. The file could also be closed by clicking the "
742 "<guibutton>cross</guibutton> in the filename tab. This will close the "
743 "current file. If the file is not saved, or is a new file, then "
744 "<application>Anjuta</application> will prompt you to save the file before "
748 #: C/anjuta-manual.xml:254(title)
749 msgid "Editing Files"
752 #: C/anjuta-manual.xml:255(para)
754 "<application>Anjuta</application> has a number of helpful features which aid "
755 "in editing and working with source files. The following sections describe "
756 "how to use some of the interesting features available."
759 #: C/anjuta-manual.xml:261(title) C/anjuta-manual.xml:270(title)
760 msgid "Editor Margins"
761 msgstr "Márgenes del editor"
763 #: C/anjuta-manual.xml:272(screeninfo) C/anjuta-manual.xml:320(screeninfo)
764 #: C/anjuta-manual.xml:423(screeninfo)
765 msgid "The Tags toolbar"
766 msgstr "La barra de herramientas de etiquetas"
768 #: C/anjuta-manual.xml:262(para)
770 "<emphasis>Editor Margins:</emphasis> Editor margins are the small area on "
771 "the left of the editor for some special purposes. There are three editor "
772 "margins available and all of them may not be available when you first start "
773 "<application>anjuta</application>. They are Line numbers margin, Markers "
774 "margin and Code fold margin. By default (that is, when you run "
775 "<application>anjuta</application> for the first time) only the code fold "
776 "margin witll be visible. The rest could be made visible from "
777 "<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></"
778 "menuchoice>. <placeholder-1/>"
781 #: C/anjuta-manual.xml:277(para)
783 "The <emphasis>Line Numbers Margin</emphasis> is largest of all the three "
784 "margins (and slightly darker then rest) and displays the document's line "
785 "numbers. <emphasis>Line Number Margin</emphasis> could be made visible or "
786 "invisible by toggling <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
787 "guisubmenu><guimenuitem>Line Numbers Margin</guimenuitem></menuchoice>. "
788 "Single left clicking on this margin will select the whole line (including "
789 "the last newline, if present). You can set the font properties for line "
790 "number margin in the preferences."
793 #: C/anjuta-manual.xml:286(para)
795 "<emphasis>Markers Margin</emphasis> is the next margin which can be made "
796 "visible or invisible by selecting <menuchoice><guimenu>View</"
797 "guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Markers Margin</"
798 "guimenuitem></menuchoice>. This margin displays graphical icons to mark the "
799 "given line. The markers which will be displayed in this margin are Bookmark "
800 "marker (rectangular blue colored icon), Breakpoint marker (circular red "
801 "colored) and Line indicator (pointed arrow yellow colored). Bookmark marker "
802 "is used to indicate bookmaked lines which could be toggled from "
803 "<menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</"
804 "guisubmenu><guimenuitem> Toggle Bookmark</guimenuitem></menuchoice> with the "
805 "cursor placed in that line. The breakpoint marker is used in debugger to "
806 "mark the line with debugging breakpoints (see debugging section for more "
807 "details). The line indicator marker is used to indicate a line when we do a "
808 "jump from another part, for example when navigating the bookmarks and during "
809 "single stepping in debugger."
812 #: C/anjuta-manual.xml:299(para)
814 "<emphasis>Code folding margin</emphasis> is where the folding tree is "
815 "visisble. Clicking on these folding tree nodes will fold or unfold the code "
816 "blocks. An underline will also be drawn below the folded line to make it "
817 "more obvious that a block of code has been folded below the line. For more "
818 "details on code folding, see the section <emphasis>Code Folding</emphasis> "
822 #: C/anjuta-manual.xml:307(title)
823 msgid "Invisible margin marker"
824 msgstr "Marcador de márgenes invisibles"
826 #: C/anjuta-manual.xml:318(title)
827 msgid "Editor markes when markers margin is invisible"
828 msgstr "El editor marca cuando el margen del marcador es invisible"
830 #: C/anjuta-manual.xml:308(para)
832 "If the marker margin is not visible, the markers will be displayed by "
833 "changing the background color of the line. For example, if there a "
834 "breakpoint marker is set in a line and the marker margin is not visible, "
835 "that line will be displayed with red background. Similarly, for bookmark "
836 "marker and line indicatior marker, the background color of the line will be "
837 "sky blue and yellow, respectively. If you do not like this (perhaps due to "
838 "some contrasting themes), enable the <emphasis>Markers Margins</emphasis> "
839 "from <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
840 "guisubmenu><guimenuitem>Markers Margin</guimenuitem></menuchoice>. "
844 #: C/anjuta-manual.xml:328(title)
845 msgid "Editor Guides"
846 msgstr "Guías del editor"
848 #: C/anjuta-manual.xml:329(para)
850 "The editor could be made to make certain document information, which "
851 "otherwise are normally not visible. <emphasis>Indentation guides, white "
852 "spaces and line end characters</emphasis> are such information which could "
853 "be made visible for editing comfort. They could be make visible or invisible "
854 "by toggling the menu items in <menuchoice><guimenu>View</"
855 "guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. Indentation guides are "
856 "the small dotted lines drawn to connect the matching braces in the source "
857 "code. When the cursor is over one such maching braces, the dotted "
858 "indentation guide is highlighted to give a visual region of the indentation."
861 #: C/anjuta-manual.xml:339(title) C/anjuta-manual.xml:341(screeninfo)
862 msgid "Editor with guides"
863 msgstr "Editor con guías"
865 #: C/anjuta-manual.xml:347(title)
866 msgid "Syntax highlighting"
867 msgstr "Resaltado de sintaxis"
869 #: C/anjuta-manual.xml:348(para)
871 "<application>Anjuta</application> can highlight many different languages. "
872 "This is usually done automatically by determining the type of the file from "
873 "the file extension. If <application>Anjuta</application> cannot determine "
874 "the type of the file, there will be no syntax highlighting. You can "
875 "explicitly force a particular highlight style by selecting the style from "
876 "the menu <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
877 "guisubmenu><guisubmenu> Highlight Mode</guisubmenu></menuchoice>."
880 #: C/anjuta-manual.xml:359(title)
884 #: C/anjuta-manual.xml:360(para)
886 "Source files which have block coding properties (such as C, C++, Pascal, "
887 "Java etc.), have the advantage of working with <emphasis>code folds</"
888 "emphasis>. All of the code blocks in the source file can be folded or "
889 "unfolded by clicking on the fold points in the fold margin of the "
890 "<interface>Editor window</interface> (usually a +/- symbol or up/down "
891 "arrow). These fold points automatically appear for source files which use "
895 #: C/anjuta-manual.xml:368(para)
897 "Code folding is especially useful when editing big source files that run to "
898 "thousands of lines. Once the folds are closed, the document appears to "
899 "become smaller, facilitating easy browsing and editing of the file."
902 #: C/anjuta-manual.xml:374(para)
904 "Please note that code folding and editor guides are only avalible in the "
905 "scintilla based editor."
908 #: C/anjuta-manual.xml:381(title)
909 msgid "Auto-formatting source code"
912 #: C/anjuta-manual.xml:382(para)
914 "If the current file is a C or C++ source or header file, then it is possible "
915 "to automatically indent (auto-format) the file. This gives a clean look to "
916 "the source code, increases legibility, reduces the likelihood of syntax "
917 "errors, and above all it saves time. This can be performed by choosing "
918 "<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
919 "guisubmenu><guimenuitem>Auto-format </guimenuitem></menuchoice> on the "
920 "menubar. Change the style of formatting by customizing the choices in the "
924 #: C/anjuta-manual.xml:392(title)
928 #: C/anjuta-manual.xml:393(para)
930 "You will need to have the <application>indent</application> utility "
931 "installed in order to use this feature. Read the <ulink type=\"info\" url="
932 "\"info:indent\">info page for <application>indent</application></ulink> for "
936 #: C/anjuta-manual.xml:404(title)
937 msgid "Symbol browser and Browsing Files"
940 #: C/anjuta-manual.xml:405(para)
942 "All C and C++ source and header files can be browsed using the tags in the "
943 "files. All of the open C and C++ source and header files are scanned for "
944 "available tags (a \"tag\" refers to a function definition, structure, macro, "
945 "etc.). Please note that Tag and Symbol is used synonymously in this manual, "
946 "except when refering to Tags browser and Symbol browser, which two different "
950 #: C/anjuta-manual.xml:421(title) C/anjuta-manual.xml:444(title)
954 #: C/anjuta-manual.xml:427(title)
955 msgid "Function symbols"
958 #: C/anjuta-manual.xml:428(para)
960 "Function prototype and definition, if present in the same file, can be "
961 "usually distinguished from the corrosponding line numbers. Prototypes "
962 "usually comes before the definition, so they are likely to have smaller line "
966 #: C/anjuta-manual.xml:414(para)
968 "<emphasis>Tags Browser:</emphasis> Tags browser is available on the Browser "
969 "toolbar. It shows a list of tags available in the currently active file "
970 "(souce file). If there is no tags (or sysmbols) available in the file, the "
971 "tags list will be invisible and a \"No Tags\" will be displayed instead. The "
972 "tags in this list are shown along with the line numbers where they are "
973 "found. If there are multiple symbols with the same name, they will be shown "
974 "with different line numbers. <placeholder-1/><placeholder-2/>"
977 #: C/anjuta-manual.xml:446(screeninfo)
978 msgid "Symbol browser"
981 #: C/anjuta-manual.xml:436(para)
983 "<emphasis>Symbol Browser:</emphasis> If there is a project open, "
984 "<application>Anjuta</application> will scan for tags in all of the source "
985 "and header files of the project. This way it is possible to go to any "
986 "function definition, structure definition, class definition etc. without "
987 "manually opening the file. You don't even have to know which file that tag "
988 "is found in (except in the case of function definitions). The symbol browser "
989 "lists all the available symbols in the project. <placeholder-1/>"
992 #: C/anjuta-manual.xml:454(title)
993 msgid "Tags synchronization"
996 #: C/anjuta-manual.xml:455(para)
998 "You don't have to worry about the synchronization and update of the tag "
999 "database. <application>Anjuta</application> will take care of everything. "
1000 "You just have to decide which tag you want to go to!"
1003 #: C/anjuta-manual.xml:466(title)
1004 msgid "Searching for and Replacing text in files"
1007 #: C/anjuta-manual.xml:468(title)
1011 #: C/anjuta-manual.xml:469(para)
1013 "To search for a <emphasis>text</emphasis> or <emphasis>regular expression</"
1014 "emphasis> string in the current file, choose <menuchoice><guimenu>Edit</"
1015 "guimenu><guisubmenu>Search</guisubmenu><guimenuitem>Find</guimenuitem></"
1016 "menuchoice> or press <keycombo><keycap>Ctrl</keycap><keycap>F</keycap></"
1017 "keycombo>. This will open the <interface>Find</interface> dialog."
1020 #: C/anjuta-manual.xml:476(para)
1022 "Use the text box to specify the string to search for, and select whether it "
1023 "is a normal string or a regular expression (RegExp). It is also possible to "
1024 "specify the direction of search, whether the search is case-sensitive or "
1025 "not, and the scope of the search. Click <guibutton>Search</guibutton> to "
1029 #: C/anjuta-manual.xml:482(para)
1031 "If the search is successful, the matched text in the document will be "
1032 "highlighted, marked... (according to the search action choice). If the "
1033 "search is not successful, a <emphasis>match not found</emphasis> message "
1034 "will be displayed."
1037 #: C/anjuta-manual.xml:487(para)
1039 "If you want to search again, click on the <guibutton>Search</guibutton> "
1040 "button on the main toolbar or press <keycombo><keycap>Ctrl</"
1041 "keycap><keycap>G</keycap></keycombo>. This will find the next match "
1042 "(<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>G</keycap></"
1043 "keycombo> for the previous match). You can even change the search text when "
1044 "you do this. Enter the new string in the <guilabel>Search Expression</"
1045 "guilabel> text box in the main toolbar."
1048 #: C/anjuta-manual.xml:496(title)
1049 msgid "Search Text dialog"
1052 #: C/anjuta-manual.xml:501(para)
1053 msgid "To stop a long research, choose <guibutton>Stop</guibutton> button."
1056 #: C/anjuta-manual.xml:504(para)
1058 "If the \"Basic Search and Replace\" option is selected in the Setting "
1059 "window, the search direction can be choosen from the Expression window."
1062 #: C/anjuta-manual.xml:509(title)
1063 msgid "Basic Search Text dialog"
1066 #: C/anjuta-manual.xml:516(title)
1067 msgid "Specifying Search Range"
1070 #: C/anjuta-manual.xml:517(para)
1072 "In the \"Search Target dialog\", define the search location and the action "
1073 "to be done in case of search success."
1076 #: C/anjuta-manual.xml:521(para)
1077 msgid "The maximum number actions can be defined by User."
1080 #: C/anjuta-manual.xml:525(title)
1081 msgid "Search Target dialog"
1084 #: C/anjuta-manual.xml:530(para)
1085 msgid "The user can select where the text will be searched."
1088 #: C/anjuta-manual.xml:534(title)
1089 msgid "Search Target In choice"
1092 #: C/anjuta-manual.xml:540(title)
1093 msgid "Searching in Files"
1096 #: C/anjuta-manual.xml:541(para)
1098 "To find text in your project, select \"search in\" <menuchoice><guimenu> All "
1099 "Project Files</guimenu></menuchoice>."
1102 #: C/anjuta-manual.xml:545(para) C/anjuta-manual.xml:576(para)
1104 "Enter the text you want to search and specify search options (case-"
1105 "sensitive, complete words ...). Click <guibutton>Search</guibutton> to start "
1109 #: C/anjuta-manual.xml:550(para)
1111 "To find text in File list, select \"search in\" <menuchoice><guimenu> "
1112 "Specifying File List</guimenu></menuchoice>. Define the Search variables. "
1113 "Click <guibutton>Search</guibutton> to start searching."
1116 #: C/anjuta-manual.xml:557(title)
1117 msgid "Search File List"
1120 #: C/anjuta-manual.xml:565(title)
1121 msgid "Specifying File Patterns"
1124 #: C/anjuta-manual.xml:566(para)
1126 "To find in files and/or folders, select \"search in\" <menuchoice><guimenu> "
1127 "Specify File Patterns</guimenu></menuchoice>, choose the file types and/or "
1128 "folders you want to search."
1131 #: C/anjuta-manual.xml:571(para)
1133 "Remember, directories are searched recursively. All of the files under the "
1134 "directory, and the files under all the subdirectories, and the files under "
1135 "all of the sub-subdirectories (and so on) are all included in the search."
1138 #: C/anjuta-manual.xml:582(title)
1139 msgid "Search File Pattern"
1142 #: C/anjuta-manual.xml:592(title)
1143 msgid "Specifying Search Action"
1146 #: C/anjuta-manual.xml:593(para)
1147 msgid "The user selects which action will be done in case of search success."
1150 #: C/anjuta-manual.xml:596(para)
1152 "According to the previous selections (Search in, Search direction ...), some "
1153 "actions coul be unavailable."
1156 #: C/anjuta-manual.xml:601(title)
1157 msgid "Search Target Action choice"
1160 #: C/anjuta-manual.xml:609(title) C/anjuta-manual.xml:617(title)
1162 msgstr "Reemplazando"
1164 #: C/anjuta-manual.xml:610(para)
1166 "Search and replace is similar to just finding text, except that you also "
1167 "specify the replace text in the <guilabel>Replace Text</guilabel> text box, "
1168 "and whether or not you want to be prompted before the replace takes place "
1169 "(Replace First Match or Replace All Matches)."
1172 #: C/anjuta-manual.xml:622(para)
1174 "Choose <guibutton>Replace</guibutton> to replace the matched text or "
1175 "<guibutton>Forward</guibutton> to jump to the next matched text."
1178 #: C/anjuta-manual.xml:629(title)
1179 msgid "Search Setting"
1182 #: C/anjuta-manual.xml:630(para)
1183 msgid "The user has the possibility of saving the setting of his search options."
1186 #: C/anjuta-manual.xml:633(para)
1188 "Item highlighted in red is the active item. Item by defaultt is the search "
1189 "setting which is loaded at Anjuta launching."
1192 #: C/anjuta-manual.xml:638(title)
1193 msgid "Search Setting dialog"
1196 #: C/anjuta-manual.xml:649(title)
1197 msgid "Printing a file"
1200 #: C/anjuta-manual.xml:659(title)
1201 msgid "Print preview of a C file"
1204 #: C/anjuta-manual.xml:661(screeninfo)
1205 msgid "Print preview"
1206 msgstr "Vista preliminar de impresión"
1208 #: C/anjuta-manual.xml:650(para)
1210 "Print preview could be taken by selecting <menuchoice><guisubmenu>File</"
1211 "guisubmenu><guimenuitem>Print Preview</guimenuitem></menuchoice>. It will "
1212 "render the current file and present a preview of the print. Source codes "
1213 "which are hilighted in the editor are also highlighted similarly in the "
1214 "print (or preview). Addtional options are available to print with the line "
1215 "numbers, wrapped lines and/or headers in the Editor printing preferences "
1216 "from <menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Preferences. "
1217 "</guimenuitem></menuchoice><placeholder-1/>"
1220 #: C/anjuta-manual.xml:668(title)
1221 msgid "Print Preferences"
1224 #: C/anjuta-manual.xml:670(screeninfo)
1225 msgid "Print preferences"
1228 #: C/anjuta-manual.xml:675(para)
1230 "When you are ready to print and satisfied with the preview, select "
1231 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print</guimenuitem></"
1232 "menuchoice> or <guibutton>Print</guibutton> from the print preview window. "
1233 "This will bring up the actual print dialog as shown below. Select the "
1234 "appropriate print parameters and print the file with <guibutton>Print</"
1238 #: C/anjuta-manual.xml:687(title)
1239 msgid "Print Dialog"
1240 msgstr "Diálogo de impresión"
1242 #: C/anjuta-manual.xml:689(screeninfo)
1243 msgid "Print dialog"
1246 #: C/anjuta-manual.xml:682(para)
1248 "Landscaped or portrait page layout, paper size, page orientation and paper "
1249 "type could also be set. Remember to set them up properly according to your "
1250 "printer, otherwise printing may not come up properly. <placeholder-1/>"
1253 #: C/anjuta-manual.xml:3(title)
1254 msgid "Project Management"
1255 msgstr "Gestión de proyectos"
1257 #: C/anjuta-manual.xml:5(para)
1259 "Anjuta has a powerful Project Manager plugin which can open most <ulink type="
1260 "\"info\" url=\"info:automake\">automake/autoconf</ulink> based projects. It "
1261 "might fail on some oddly configured projects, but as long as the project is "
1262 "done by using automake/autoconf in a typical way, it should work."
1265 #: C/anjuta-manual.xml:13(para)
1267 "The neat thing is that it does not store any project information beyond what "
1268 "is already available in project struture. That is, there is no separate "
1269 "project data maintained by Anjuta and all project processing are done "
1270 "directly within the project structure. This allows the project to be "
1271 "maintained or developed outside Anjuta without having to so-called 'porting' "
1272 "or 'switching' to a new platform. Since technically Anjuta projects are just "
1273 "automake projects, mixed development of it (Anjuta and non-Anjuta users) or "
1274 "switching back and forth between Anjuta and other tools is quite possible "
1275 "without any hindrance."
1278 #: C/anjuta-manual.xml:26(title)
1279 msgid "Creating a New Project"
1280 msgstr "Crear un proyecto nuevo"
1282 #: C/anjuta-manual.xml:28(title)
1283 msgid "New project from template"
1286 #: C/anjuta-manual.xml:29(para)
1288 "The project wizard plugin uses a powerful template processing engine called "
1289 "<application>autogen</application>. All new projects are created from "
1290 "templates that are written in <application>autogen</application> syntax. "
1291 "Project wizard lets you create new projects from a selection of project "
1292 "templates. The selection includes simple generic, flat (no subdirectory), gtk"
1293 "+, gnome, java, python projects and more. New templates can be easily "
1294 "downloaded and installed since they are just a collection of text files."
1297 #: C/anjuta-manual.xml:41(para)
1299 "Choose the menu item <menuchoice><guisubmenu>File</"
1300 "guisubmenu><guisubmenu>New</guisubmenu><guimenuitem>Project …</guimenuitem></"
1301 "menuchoice> to start the application wizard. Read the <interface>first page</"
1302 "interface> carefully. Click on <guibutton>Next</guibutton> to proceed."
1305 #: C/anjuta-manual.xml:48(para)
1307 "Select the type of application you want to create in the <interface>second "
1308 "page</interface>. Click on <guibutton>Next</guibutton> to proceed."
1311 #: C/anjuta-manual.xml:54(para)
1313 "On the next pages, enter all necessary details for your project. You can "
1314 "change these settings later also, but it is advicable to put them right in "
1315 "first run to maintain the project's integrity. White spaces or any non-"
1316 "alphanumeric characters, except underscore (_) and dash (-), are not allowed "
1317 "in many of the entry boxes that would follow (except perhaps the "
1318 "<guilabel>Author</guilabel> text box)."
1321 #: C/anjuta-manual.xml:65(para)
1323 "You can also specify whether your project will have "
1324 "<emphasis>internationalization support</emphasis> using "
1325 "<application>gettext</application> (read the <ulink type=\"info\" url=\"info:"
1326 "gettext\">gettext info page</ulink> for more details). This gives your "
1327 "project multilingual support for different regional languages such as "
1328 "English, French, Dutch etc.. The rest of the options are for setting whether "
1329 "the GNU copyright statement should appear in the comments at the top of each "
1330 "file, and enabling GNOME desktop menu information if necessary. Shared "
1331 "library support allows adding shared library modules later in the project. "
1332 "If you plan to have libraries in your project, it would be good to enable. "
1333 "Depending on the project type that is being created, there would be other "
1334 "information requested."
1337 #: C/anjuta-manual.xml:81(para)
1339 "The final step is to verify the information you have just supplied. Click on "
1340 "<guibutton>Finish</guibutton> to start generating the project."
1343 #: C/anjuta-manual.xml:86(para)
1345 "Once project generation is over, you can try it out by building the project "
1349 #: C/anjuta-manual.xml:92(title)
1350 msgid "Importing Projects"
1353 #: C/anjuta-manual.xml:93(para)
1355 "The import project feature is used to import an already existing project and "
1356 "convert it into <application>anjuta</application> projcect. Activate the "
1357 "import project wizard from <menuchoice><guimenu>File</guimenu><guimenu>New</"
1358 "guimenu><guimenuitem>Project from existing sources</guimenuitem></"
1359 "menuchoice> and follow instructions dictated by the wizard. Once the project "
1360 "is imported, it could be opened in <application>anjuta</application> "
1361 "subsequently just like any other <application> anjuta</application> project."
1364 #: C/anjuta-manual.xml:103(para)
1366 "The import project features only works if your existing project is using "
1367 "<ulink type=\"info\" url=\"info:automake\">autoconf/automake</ulink> and, to "
1368 "a very limited extend, plain makefiles."
1371 #: C/anjuta-manual.xml:113(title)
1372 msgid "Loading and Saving Projects"
1375 #: C/anjuta-manual.xml:115(title)
1376 msgid "Loading Projects"
1379 #: C/anjuta-manual.xml:116(para)
1381 "To open a project, choose the menu item <menuchoice><guisubmenu>File</"
1382 "guisubmenu><guimenuitem>Open …</guimenuitem></menuchoice>. Select the "
1383 "project file (<filename>*.anjuta</filename>) in the dialog and click "
1384 "<guibutton>OK</guibutton>."
1387 #: C/anjuta-manual.xml:123(para)
1389 "If the project has recently been opened, then you will find it listed in the "
1390 "menu <menuchoice><guisubmenu>File</guisubmenu><guisubmenu>Recent</"
1391 "guisubmenu></menuchoice>. Choose the project file from the list, and the "
1392 "project will be opened."
1395 #: C/anjuta-manual.xml:128(para)
1397 "As soon as a project is opened, <application>Anjuta</application> will enter "
1398 "<emphasis>Project mode</emphasis>. There are three panes in the project "
1399 "window. The first is the project pane and lists the project files organized "
1400 "in file types. The second is the symbol browser, which has already been "
1401 "discussed in section <emphasis>Symbol Browser and tags Brwoser</emphasis>. "
1402 "The third pane is the file view of the project and is more or less similar "
1403 "to a mini file-manager. In file view, all the files present in the project "
1404 "tree is visible. Right clicking on these files will pop up the file "
1405 "operation submenu."
1408 #: C/anjuta-manual.xml:138(para)
1410 "If the project is also a CVS tree, then corresponing file revision numbers "
1411 "are also listing on the right of file names in the file view pane."
1414 #: C/anjuta-manual.xml:144(title)
1415 msgid "Saving Projects"
1418 #: C/anjuta-manual.xml:145(para)
1420 "The project is automatically saved when you close because all changes are "
1421 "made directly in the project structure."
1424 #: C/anjuta-manual.xml:153(title)
1425 msgid "Project structure"
1428 #: C/anjuta-manual.xml:154(para)
1430 "<interface>Project View</interface> lists the project in standard <ulink "
1431 "type=\"info\" url=\"info:automake\"><application>automake</application></"
1432 "ulink> heirarchy organized into groups of targets. <emphasis>Groups</"
1433 "emphasis> correspond to directories in your project and <emphasis>targets</"
1434 "emphasis> correspond to normal <application>automake</application> targets "
1435 "(not to be confused with make targets). <interface>Project View</interface> "
1436 "actually has two parts; one part (lower one) shows complete project "
1437 "heirarchy and the other part (upper one) lists important targets directly. "
1438 "Important targets constitute executable and library targets -- making them "
1439 "very accessible in from the view. This is particularly useful in big "
1440 "projects where the heirarchy could be deep and hard to navigate from the "
1441 "tree alone. Targets are, in turn, composed of source files."
1444 #: C/anjuta-manual.xml:174(para)
1446 "<emphasis>Groups</emphasis> are used to logically organize targets. A "
1447 "project can contain any number of groups. Each group can have sub-groups as "
1448 "well as targets. In automake projects, groups are just sub-directories in "
1449 "the project. The top level group is called root and is always \"/\"."
1452 #: C/anjuta-manual.xml:182(para)
1454 "<emphasis>Targets</emphasis> are the build targets in project, such as "
1455 "programs (executable binaries), scripts, libraries, miscellaneous data etc. "
1456 "Not all target types are built from sources, but exist just to organize the "
1457 "sources and therefore may not exist physically (e.g. Miscellaneous data "
1458 "target). Targets exist under groups. See <link linkend=\"adding-target\">"
1459 "\"Adding targets\"</link> for full list of available target types."
1462 #: C/anjuta-manual.xml:193(para)
1464 "<emphasis>Source files</emphasis> are the files used to build the targets or "
1465 "just to be part of it. They exist only under targets. Many target types "
1466 "expect certain type of source files (e.g. programs and libraries target "
1467 "types), but some can accept any file (e.g. Miscellaneous data target)."
1470 #: C/anjuta-manual.xml:203(para)
1472 "Each of the project groups and targets is configurable in standard "
1473 "<application>automake</application> way. You can set complier and linker "
1474 "flags directly for each target, or set configure variables. Groups allow "
1475 "setting installation destinations for its targets."
1478 #: C/anjuta-manual.xml:210(para)
1480 "Just like file manager, project manager view also has convenience actions "
1481 "(accessible from context menu) for the source files and targets."
1484 #: C/anjuta-manual.xml:215(para)
1486 "Many command-line tools are available to maintain and manage a project, and "
1487 "each tool has its own specific rules and capabilities. <application>Anjuta</"
1488 "application> tries to automate most of the common operations using plugins. "
1489 "However, you might occationally still need to do them manually."
1492 #: C/anjuta-manual.xml:223(para)
1494 "It is possible to make use of other tools or hand edit the project files "
1495 "simulaneously. It doesn't matter if the project is loaded in "
1496 "<application>Anjuta</application> or not. <application>Anjuta</application> "
1497 "would update itself with any external changes made to project."
1500 #: C/anjuta-manual.xml:232(title)
1501 msgid "Groups and targets"
1504 #: C/anjuta-manual.xml:235(title)
1505 msgid "Adding Groups"
1508 #: C/anjuta-manual.xml:240(para)
1510 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Group</"
1511 "guimenuitem></menuchoice> and a dialog to add a new group would popup."
1514 #: C/anjuta-manual.xml:247(para)
1515 msgid "Select the group under which to add new group."
1518 #: C/anjuta-manual.xml:250(para)
1519 msgid "Give a name of the new group and click Ok."
1522 #: C/anjuta-manual.xml:236(para)
1524 "To add a new group (a directory in automake based projects): <placeholder-1/"
1525 "> With automake projects, a new directory with the given name would be "
1526 "created under the parent group's directory."
1529 #: C/anjuta-manual.xml:257(para)
1531 "New group can also be added from the <guimenu>Operation</guimenu> menu in "
1532 "<interface>Project View</interface> by selecting <guimenuitem>Add Group</"
1533 "guimenuitem>. First select the group under which to add the group in "
1534 "<interface>Project View</interface>."
1537 #: C/anjuta-manual.xml:266(title)
1538 msgid "Removing Groups"
1541 #: C/anjuta-manual.xml:271(para)
1542 msgid "Select the target in <interface>Project Manager view</interface>."
1545 #: C/anjuta-manual.xml:274(para) C/anjuta-manual.xml:413(para)
1547 "Select <guimenuitem>Remove</guimenuitem> from the <guimenu>Operation</"
1551 #: C/anjuta-manual.xml:267(para)
1553 "To remove a group: <placeholder-1/> The target and sources associated with "
1554 "the group will also be removed from the project (they are not deleted from "
1555 "the file system, though. You can still add them later)."
1558 #: C/anjuta-manual.xml:285(title)
1559 msgid "Adding Targets"
1562 #: C/anjuta-manual.xml:290(para)
1564 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Target</"
1565 "guimenuitem></menuchoice> and a dialog to add a new target would popup."
1568 #: C/anjuta-manual.xml:295(para)
1569 msgid "Select the group under which to add the target."
1572 #: C/anjuta-manual.xml:298(para)
1573 msgid "Select the target type."
1576 #: C/anjuta-manual.xml:301(para)
1577 msgid "Give a name of the new target and click Ok."
1580 #: C/anjuta-manual.xml:286(para)
1581 msgid "To add a new target: <placeholder-1/>"
1584 #: C/anjuta-manual.xml:305(para)
1586 "New target can also be added from the <guimenu>Operation</guimenu> menu in "
1587 "<interface>Project View</interface> by selecting <guimenuitem>Add target</"
1588 "guimenuitem>. First select the group under which to add the target in "
1589 "<interface>Project View</interface>."
1592 #: C/anjuta-manual.xml:311(para)
1594 "Target names usually require some standard prefix and suffix, depending on "
1595 "the type of target. Anjuta would warn if the name is not valid and may give "
1596 "an example of a name."
1599 #: C/anjuta-manual.xml:320(para)
1601 "<emphasis>Program</emphasis> target type is for executable binaries. Select "
1602 "this if you want to add an executable to the project. By default, all "
1603 "program targets would be installed in standard executable directory, e.g. /"
1604 "usr/bin or /usr/local/bin. You can override it by specifying a different "
1605 "installation directory in its group properties."
1608 #: C/anjuta-manual.xml:329(para)
1610 "<emphasis>Shared Library</emphasis> target type is for shared or dynamic "
1611 "libraries. Select this if you are adding a shared library to the project. By "
1612 "default, all shared libraries are installed in standard libraries directory, "
1613 "e.g. /usr/lib or /usr/local/lib. You can override it by specifying a "
1614 "different installation directory in its group properties."
1617 #: C/anjuta-manual.xml:338(para)
1619 "<emphasis>Static Library</emphasis> target type is for static library. "
1620 "Select this if you are adding a static library to the project. By default, "
1621 "all static libraries are installed in standard libraries directory, e.g. /"
1622 "usr/lib or /usr/local/lib. You can override it by specifying a different "
1623 "installation directory in its group properties."
1626 #: C/anjuta-manual.xml:347(para)
1628 "<emphasis>Java module</emphasis> target type is for java module. Select this "
1629 "if you are grouping java sources into a module. You need to provide an "
1630 "installation directory for this target where the .class files will be "
1631 "installed. It can be set in group properties of the group where this target "
1635 #: C/anjuta-manual.xml:355(para)
1637 "There can really be only one java module in a group. This is a restriction "
1638 "put by automake. Please read automake info page for more details."
1641 #: C/anjuta-manual.xml:363(para)
1643 "<emphasis>Python module</emphasis> target type is for python module. Select "
1644 "this if you are grouping python sources into a module. You need to provide "
1645 "an installation directory for this target where the sources will be "
1646 "installed. It can be set in group properties of the group where this target "
1650 #: C/anjuta-manual.xml:372(para)
1652 "<emphasis>Scripts</emphasis> target is to group scripts. They will be "
1653 "installed in standard executable directory."
1656 #: C/anjuta-manual.xml:378(para)
1658 "<emphasis>Miscellaneous Data</emphasis> target type is to group simple files "
1659 "in the project. An installation directory needs to be specified in its group "
1663 #: C/anjuta-manual.xml:385(para)
1665 "<emphasis>Header Files</emphasis> target type is to group C/C++ header files "
1666 "that need to be installed in system (for example as part of library API). "
1667 "For header files that do not need to be installed, make them part of the "
1668 "Program target along with the sources. They will be installed in standard "
1669 "include directory unless installation path is specified in its group "
1673 #: C/anjuta-manual.xml:395(para)
1675 "<emphasis>Man documentation</emphasis> and <emphasis>Info documentation</"
1676 "emphasis> target types are for grouping man and info documentation "
1677 "respectively. By default, they will be installed in standard installation "
1681 #: C/anjuta-manual.xml:316(para)
1683 "There are several target types for automake project. They are: <placeholder-"
1687 #: C/anjuta-manual.xml:405(title)
1688 msgid "Removing Targets"
1691 #: C/anjuta-manual.xml:410(para)
1692 msgid "Select the target in <interface>Project Manager view</interface>"
1695 #: C/anjuta-manual.xml:406(para)
1697 "To remove a target: <placeholder-1/> The sources associated with the targets "
1698 "will also be removed from the project (they are not deleted from the file "
1702 #: C/anjuta-manual.xml:425(title)
1703 msgid "Adding and Removing Files"
1706 #: C/anjuta-manual.xml:427(title)
1707 msgid "Adding Source Files"
1710 #: C/anjuta-manual.xml:428(para)
1712 "Select menu item <menuchoice><guisubmenu>Project</"
1713 "guisubmenu><guimenuitem>Add Source File</guimenuitem></menuchoice>. From the "
1714 "dialog, select the target to which the file should be added and the file "
1715 "itself. You can add multiple files at once. To do that, select multiple "
1716 "files from the fileselection dialog using either SHIFT or CONTROL key. Then "
1717 "click <guibutton>Add</guibutton> button to finally add the files in project."
1720 #: C/anjuta-manual.xml:437(para)
1722 "By default, current editor file would be preselected for addtion in the "
1723 "dialog. Other convenient way to add a file is to select it in "
1724 "<interface>File Manager</interface> and choosing <guimenuitem>Add to "
1725 "project</guimenuitem> from the <guimenu>Operation</guimenu> popup menu."
1728 #: C/anjuta-manual.xml:444(para)
1730 "If the file you choose has already been added to the project, then "
1731 "<application>Anjuta</application> will not add it again. It will also give "
1732 "you a warning that the file is already added."
1735 #: C/anjuta-manual.xml:449(para)
1737 "If the file you choose is not in the project directory, you will be asked to "
1738 "confirm that you wish to copy the file into the target's directory. "
1739 "<application>Anjuta</application> cannot add files which are outside of "
1740 "target's directory."
1743 #: C/anjuta-manual.xml:457(title)
1744 msgid "Removing Source Files"
1747 #: C/anjuta-manual.xml:458(para)
1749 "To remove a file from the project, select the file you want to remove from "
1750 "the <interface>Project View</interface>, right-click to open the "
1751 "<guimenu>Operation</guimenu> popup menu and choose <guimenuitem>Remove</"
1755 #: C/anjuta-manual.xml:464(para)
1757 "A confirmation dialog will appear, and the file will be removed from the "
1761 #: C/anjuta-manual.xml:469(title)
1762 msgid "The file is not deleted!"
1765 #: C/anjuta-manual.xml:470(para)
1767 "The file is not deleted from the filesystem. It still exists, and you can "
1768 "add it back again later if you so wish. The file is only removed from the "
1769 "project listing, and will not take part in any of the project operations "
1770 "such as compiling, building, distribution etc.."
1773 #: C/anjuta-manual.xml:481(title)
1774 msgid "Project Configuration"
1777 #: C/anjuta-manual.xml:482(para)
1779 "Project configuration involves setting the correct build flags for targets, "
1780 "groups and project itself. You can set these flags in their respective "
1781 "properties dialog."
1784 #: C/anjuta-manual.xml:488(para)
1786 "You can freely use autoconf and automake variables that are automatically "
1787 "set for the project during configuration. Apart from these automatically set "
1788 "variables, you can also defined your own variables in <link linkend="
1789 "\"project-properties\">Project Properties</link> use them in properties. "
1790 "This will make it easy to update flags later, especially when the variable "
1791 "is used in several targets."
1794 #: C/anjuta-manual.xml:503(para)
1796 "<emphasis>$(prefix)</emphasis>: The installation prefix. The project is "
1797 "installed under various sub-directories under this prefix. By default it is /"
1801 #: C/anjuta-manual.xml:510(para)
1803 "<emphasis>$(bindir)</emphasis>: The installation directory for executable "
1804 "binaries. All your executable and scripts targets would be installed in this "
1805 "directory. By default, it is $(prefix)/bin."
1808 #: C/anjuta-manual.xml:517(para)
1810 "<emphasis>$(libdir)</emphasis>: The installation directory for libraries. "
1811 "All your library targets (both shared and static) would be installed in this "
1812 "directory or a subdirectory below it. By default, it is $(prefix)/lib."
1815 #: C/anjuta-manual.xml:525(para)
1817 "<emphasis>$(module_CFLAGS)</emphasis> and $(module_LIBS): These flags are "
1818 "set by configure for the packages that your project depends on. The packages "
1819 "used by the project are set in <link linkend=\"project-properties\">Project "
1820 "Properties</link>. 'module' is the packages group that you give in project "
1824 #: C/anjuta-manual.xml:497(para)
1826 "Some of the many common variables are listed here. For full list of them see "
1827 "<ulink url=\"info:automake\">automake info documentation</ulink>. "
1831 #: C/anjuta-manual.xml:539(title)
1832 msgid "Project properties"
1833 msgstr "Propiedades del proyecto"
1835 #: C/anjuta-manual.xml:546(para)
1837 "Set project name, version and URL in <guibutton>General</guibutton> page. "
1838 "Configure variables can also be use in these fields. The URL is the bug "
1839 "report URL for the project."
1842 #: C/anjuta-manual.xml:553(para)
1844 "Add and remove dependencies for your project in <guibutton>Packages</"
1845 "guibutton> page. See below for details."
1848 #: C/anjuta-manual.xml:559(para)
1850 "Create more configure variables in <guibutton>Variables</guibutton> page to "
1851 "use in group and target properties."
1854 #: C/anjuta-manual.xml:540(para)
1856 "Project properties dialog can be only brought by choosing "
1857 "<menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
1858 "guimenuitem></menuchoice>. You can: <placeholder-1/>"
1861 #: C/anjuta-manual.xml:574(title) C/anjuta-manual.xml:576(screeninfo)
1862 msgid "Project properties dialog"
1865 #: C/anjuta-manual.xml:566(para)
1867 "Dependencies are external packages that the project uses and hence required "
1868 "to build it. Only packages installed using <ulink url=\"info:pkg-config"
1869 "\">pkg-config</ulink> can be added from this interface. For others, the "
1870 "configure.ac file can be edited manually. <placeholder-1/>"
1873 #: C/anjuta-manual.xml:581(para)
1875 "External package dependencies are grouped into <emphasis>modules</emphasis>, "
1876 "so that their combined build flags can be conviniently added to different "
1877 "targets. <emphasis>Modules</emphasis> are just arbitrary names given to "
1878 "group the packages and can be named anything (only alphanumeric and _ are "
1879 "allowed in module name). Usually, they follow the name of targets they would "
1880 "be use in. Consequently, for small projects with single targets, just one "
1881 "module to hold all dependencies is enough."
1884 #: C/anjuta-manual.xml:590(para)
1886 "Each package exports a set of <emphasis>compiler flags</emphasis> and "
1887 "<emphasis>libraries</emphasis>. They are aggregated together for all "
1888 "packages under a module and configure variables <emphasis>$(module_CFLAGS)</"
1889 "emphasis> and <emphasis>$(module_LIBS)</emphasis> are defined. These "
1890 "variables can then be used in <link linkend=\"group-properties\">Group "
1891 "properties</link> and <link linkend=\"target-properties\">Target properties</"
1895 #: C/anjuta-manual.xml:603(para)
1897 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
1898 "guimenuitem></menuchoice> to bring up project properties dialog."
1901 #: C/anjuta-manual.xml:610(para)
1902 msgid "Select the tab <guibutton>Packages</guibutton> to bring up packages page."
1905 #: C/anjuta-manual.xml:614(para)
1907 "Select the <emphasis>module</emphasis> to add the package to. If there is no "
1908 "module created yet or there is no appropriate module, create one by clicking "
1909 "<guibutton>Add module</guibutton>. Give a sensible name to the module, "
1910 "preferably in UPPERCASE to match with rest of configure variables (only use "
1911 "alphanumeric and '_' characters) and press <keycap>Enter</keycap> to create "
1915 #: C/anjuta-manual.xml:624(para)
1917 "Click <guibutton>Add package</guibutton> to bring up package selection "
1921 #: C/anjuta-manual.xml:627(para)
1922 msgid "Select the package to add and click <guibutton>Add</guibutton>."
1925 #: C/anjuta-manual.xml:630(para)
1926 msgid "Click <guibutton>Close</guibutton> to close the properties dialog."
1927 msgstr "Pulse <guibutton>Cerrar</guibutton> para cerrar el diálogo de propiedades."
1929 #: C/anjuta-manual.xml:599(para)
1930 msgid "To add a package dependency: <placeholder-1/>"
1933 #: C/anjuta-manual.xml:637(title)
1934 msgid "Group properties"
1935 msgstr "Propiedades del grupo"
1937 #: C/anjuta-manual.xml:638(para)
1939 "To set group properties, select it in the <interface>Project View</"
1940 "interface> and active it. You can also bring it by selecting "
1941 "<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
1942 "guimenuitem></menuchoice>"
1945 #: C/anjuta-manual.xml:654(para)
1947 "<emphasis>Includes</emphasis>: Set your $(module_CFLAGS) variables and other "
1948 "include directories for your c and c++ targets. You need to provide the full "
1949 "include options of the compiler here, e.g. -I/usr/include/blah. The include "
1950 "paths will be use to find the include files in your source files. You can "
1951 "also add other sort of compiler flags here, but they are prefered to be set "
1952 "in their respective compiler flags properties (see below)."
1955 #: C/anjuta-manual.xml:664(para)
1957 "Usually your configure script would also make some automatically determined "
1958 "compiler flags. The variables usually end with _CFLAGS, e.g "
1959 "$(PACKAGE_CFLAGS). They are also set here. See setting <link linkend="
1960 "\"project-properties\">Project properties</link> for more details on these "
1964 #: C/anjuta-manual.xml:674(para) C/anjuta-manual.xml:715(para)
1966 "<emphasis>Compiler settings</emphasis>: Set your compiler specific flags "
1967 "here. There are different fields for different compiler categories. Flags "
1968 "that can be set here depend on the actual compiler used. The default "
1969 "compiler use for c/c++ is gcc/g++ (gnu c compiler). Check out <ulink url="
1970 "\"info:gcc\">gcc info documentation</ulink> for more details."
1973 #: C/anjuta-manual.xml:684(para)
1975 "<emphasis>Install directories</emphasis>: Targets in the group that require "
1976 "installation directories would each get a field to enter the installation "
1977 "directory. Set their installation directories as relative to one of the many "
1978 "automake directory variables, such as $(prefix), $(bindir), $(libdir), "
1982 #: C/anjuta-manual.xml:645(para)
1984 "<emphasis>Group Properties</emphasis> set to a group applies to all the "
1985 "targets under it. So any compiler or linker flags set there would be "
1986 "automatically be part of all the targets in it (in addition the targets "
1987 "individual properties). Folowing flags are available in group properties. "
1991 #: C/anjuta-manual.xml:699(title)
1992 msgid "Target properties"
1993 msgstr "Propiedades del destino"
1995 #: C/anjuta-manual.xml:700(para)
1997 "To set target properties, select it in the <interface>Project View</"
1998 "interface> and active it. You can also bring it by selecting "
1999 "<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
2000 "guimenuitem></menuchoice>"
2003 #: C/anjuta-manual.xml:725(para)
2005 "<emphasis>Linker flags</emphasis>: Set linker flags that should be used when "
2006 "linking the target. It applies only to Program and library targets. See "
2007 "<ulink url=\"info:ld\">ld info documentation</ulink> for available linker "
2011 #: C/anjuta-manual.xml:733(para)
2013 "<emphasis>Libraries</emphasis>: Set the libraries that the target depends "
2014 "on. Usually they are the $(module_LIBS) configure variables. See setting "
2015 "<link linkend=\"project-properties\">Project properties</link> for more "
2016 "details on these variables."
2019 #: C/anjuta-manual.xml:707(para)
2021 "<emphasis>Target Properties</emphasis> set to a target applies to that "
2022 "target. So any compiler or linker flags set there would be just part of it "
2023 "(in addition the its group properties). Folowing flags are available in "
2024 "target properties. <placeholder-1/>"
2027 #: C/anjuta-manual.xml:748(title)
2028 msgid "Compiling and Building"
2031 #: C/anjuta-manual.xml:750(title)
2033 msgstr "Vista general"
2035 #: C/anjuta-manual.xml:751(para)
2036 msgid "An executable for a project is generated in two steps:"
2039 #: C/anjuta-manual.xml:756(para)
2043 #: C/anjuta-manual.xml:757(para)
2047 #: C/anjuta-manual.xml:760(para)
2049 "These steps are collectively known as <emphasis>Building</emphasis>. Some "
2050 "other steps may also be involved in the build process, but for the sake of "
2051 "simplicity, we will only look at these two steps."
2054 #: C/anjuta-manual.xml:765(para)
2056 "<emphasis>Compiling</emphasis> is the step in which object files are "
2057 "generated from their corresponding source files. For instance, a source file "
2058 "<filename>hello.c</filename> will generate <filename>hello.o</filename> "
2059 "after compilation. Usually you do not need to worry about these object files "
2060 "— just think of them as intermediate files involved in creating the final "
2064 #: C/anjuta-manual.xml:772(para)
2066 "Once the object files (<filename>*.o</filename> files) are ready, they are "
2067 "all linked together (along with any libraries) to generate the final "
2068 "executable. This step is called <emphasis>Linking</emphasis>."
2071 #: C/anjuta-manual.xml:779(title)
2072 msgid "Compiling the source"
2073 msgstr "Compilar los fuentes"
2075 #: C/anjuta-manual.xml:780(para)
2077 "In a project, the individual source files can be compiled separately into "
2078 "objects (<filename>*.o</filename> files). Although you do not have to worry "
2079 "about these object files, sometimes it is handy to compile a file first (for "
2080 "example, to make sure there are no syntax errors). Building a whole project "
2081 "can take a lot of time, especially in the case of larger and more complex "
2082 "applications. Therefore, you will probably go through a series of edit-"
2083 "compile-edit-compile-.... loops while a developing the project."
2086 #: C/anjuta-manual.xml:788(para)
2088 "To compile a file, choose the menu item <menuchoice><guisubmenu>Build</"
2089 "guisubmenu><guimenuitem>Compile</guimenuitem></menuchoice> or press "
2090 "<keycap>F11</keycap>. This will compile the active file."
2093 #: C/anjuta-manual.xml:795(title)
2094 msgid "Building an executable"
2095 msgstr "Construir un ejecutable"
2097 #: C/anjuta-manual.xml:796(para)
2099 "<application>Anjuta</application> has no separate link command, simply "
2100 "because it is not necessary. The build process will compile all the source "
2101 "files and link them together along with the libraries. The build command "
2102 "will note recompile those files which are already up-to-date (this is called "
2103 "the <emphasis>dependency check</emphasis>). If you have already compiled all "
2104 "of the files individually, then the only thing the build step performs is "
2105 "the link. If you have already built the project and no dependent file has "
2106 "been modified, even the link stage will be skipped."
2109 #: C/anjuta-manual.xml:805(para)
2111 "So how exactly does the dependency check influence the project development? "
2112 "If you have modified a file, then all of the source files that depend on the "
2113 "modified file are recompiled. All files (not only the object files and "
2114 "executable) in the project are checked for these dependencies during the "
2115 "build process. If it is found that a particular file is dependent on some "
2116 "other file which has been modified, then that file will be re-generated."
2119 #: C/anjuta-manual.xml:813(para)
2121 "Since you have now got a rough understanding of the value of the dependency "
2122 "check, can you imagine how your life (as a programmer) would be if it had "
2123 "not been there? If you cannot answer just yet, then will find out when you "
2124 "start developing big projects!"
2127 #: C/anjuta-manual.xml:818(para)
2129 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></"
2130 "menuchoice> will build all of the files in the <filename class=\"directory"
2131 "\">src</filename> (source) directory, and generate the executable. "
2132 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build All</"
2133 "guimenuitem></menuchoice> will build the whole project — all of the "
2134 "subdirectories (including <filename class=\"directory\">src</filename>), are "
2135 "built recursively."
2138 #: C/anjuta-manual.xml:828(title)
2139 msgid "Creating a distribution package"
2140 msgstr "Crear un paquete de distribución"
2142 #: C/anjuta-manual.xml:829(para)
2144 "To build the tarball distribution of the project choose "
2145 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Tarball</"
2146 "guimenuitem></menuchoice>. This will create a tarball (<filename>*.tar.gz</"
2147 "filename>) and put it in the top level project directory. Copy the file to a "
2148 "safe place for distribution."
2151 #: C/anjuta-manual.xml:837(title)
2153 msgstr "Instalación"
2155 #: C/anjuta-manual.xml:838(para)
2157 "Choosing the menu item <menuchoice><guisubmenu>Build</"
2158 "guisubmenu><guimenuitem>Install</guimenuitem></menuchoice> will install the "
2159 "generated application on your system."
2162 #: C/anjuta-manual.xml:844(title)
2163 msgid "System wide installation"
2166 #: C/anjuta-manual.xml:845(para)
2168 "You must be logged in as root to perform a system-wide install. Also note "
2169 "that for a GNOME application to use the pixmaps in the project, it must be "
2170 "installed as a system-wide application. Otherwise, when the application is "
2171 "executed in your project, there will be lots of \"pixmap not found\" errors. "
2172 "You can configure anjuta to use <command>sudo</command> or <command>su</"
2173 "command> before installing the project in the build preferences."
2176 #: C/anjuta-manual.xml:855(title)
2180 #: C/anjuta-manual.xml:856(para)
2182 "To run the <filename>configure</filename> script found in the top level "
2183 "project directory, choose the menu item <menuchoice><guisubmenu>Build</"
2184 "guisubmenu><guimenuitem>Configure</guimenuitem></menuchoice>. The script "
2185 "will determine the system configuration and create some of the files "
2186 "required to perform a build (such as <filename>Makefile</filename> and "
2187 "<filename>config.h</filename>). This is necessary because the application "
2188 "may depend on specific configuration of some of these options."
2191 #: C/anjuta-manual.xml:865(title)
2192 msgid "When to configure"
2195 #: C/anjuta-manual.xml:866(para)
2197 "Until you run <filename>configure</filename>, you cannot start building the "
2201 #: C/anjuta-manual.xml:871(para)
2203 "The <filename>configure</filename> script is (usually) run only once at the "
2204 "beginning of the first build process — for example, just after you have "
2205 "extracted a source tarball of a project distribution. After that, "
2206 "configuration is automatically handled by the subsequent build processes. If "
2207 "you have used the <emphasis>Application Wizard</emphasis> to create the "
2208 "application, then you will not need to run <filename>configure</filename> "
2209 "separately: the wizard will run it as a part of the project generation "
2213 #: C/anjuta-manual.xml:879(para)
2215 "You can also supply additional options to the configuration script. After "
2216 "choosing the <guimenuitem>Configure</guimenuitem> menu item, a dialog will "
2217 "appear to prompt for additional options."
2220 #: C/anjuta-manual.xml:885(title) C/anjuta-manual.xml:887(screeninfo)
2221 msgid "Configure options dialog"
2224 #: C/anjuta-manual.xml:891(para)
2226 "Enter any options (or leave it blank to accept the defaults) and click "
2227 "<guibutton>OK</guibutton>. To find out the options available to the "
2228 "<filename>configure</filename> script, enter <userinput>--help</userinput> "
2229 "in the option entry box and click <guibutton>OK</guibutton>. The options "
2230 "will be displayed in the <interface>Message window</interface>."
2233 #: C/anjuta-manual.xml:898(para)
2235 "There is no requirement to run <filename>configure</filename> only once. It "
2236 "can be run at any time, usually when the configuration options need to be "
2237 "changed. One thing to note is that, if the <filename>config.h</filename> "
2238 "file in the top level directory is changed, running <filename>configure</"
2239 "filename> again will not overwrite it."
2242 #: C/anjuta-manual.xml:906(title)
2243 msgid "Auto generate"
2246 #: C/anjuta-manual.xml:907(para)
2248 "Auto generation consists of two steps: running <application>automake</"
2249 "application> and then running <application>autoconf</application>. If an "
2250 "executable <filename>autogen.sh</filename> script is found in the top level "
2251 "project directory, this file will be executed instead of the two steps. Like "
2252 "<emphasis>configuration</emphasis>, auto generation is automatically handled "
2253 "by the build process. It can also be run in cases where it is difficult to "
2254 "configure the project (such as lots of errors reported due to mis-"
2255 "synchronization after modifying lots of build files)."
2258 #: C/anjuta-manual.xml:918(title)
2259 msgid "When to autogen.sh"
2262 #: C/anjuta-manual.xml:919(para)
2264 "Unlike configuration, auto generation does not need to be run even once — in "
2265 "fact, it does not need to be run at all! The option is available because it "
2266 "can be handy in some circumstances."
2269 #: C/anjuta-manual.xml:925(para)
2271 "Choose the menu item <menuchoice><guisubmenu>Build</"
2272 "guisubmenu><guimenuitem>Auto generate</guimenuitem></menuchoice> to auto "
2273 "generate the project."
2276 #: C/anjuta-manual.xml:929(para)
2278 "Read the info pages of <ulink type=\"info\" url=\"info:automake"
2279 "\"><application>automake</application></ulink> and <ulink type=\"info\" url="
2280 "\"info:autoconf\"><application>autoconf</application></ulink> for more "
2281 "details on how these tools work."
2284 #: C/anjuta-manual.xml:936(title)
2288 #: C/anjuta-manual.xml:937(para)
2290 "This option cleans the project and leaves it in a state that requires "
2291 "<guimenuitem>Build All</guimenuitem> to be performed. It deletes all of the "
2292 "files generated by the build process, including all object files "
2293 "(<filename>*.o</filename> files) and the executable(s) in the <filename "
2294 "class=\"directory\">src</filename> directory (and other directories)."
2297 #: C/anjuta-manual.xml:944(para)
2299 "Choose the menu item <menuchoice><guisubmenu>Build</"
2300 "guisubmenu><guimenuitem>Clean</guimenuitem></menuchoice> to clean the "
2304 #: C/anjuta-manual.xml:950(title)
2308 #: C/anjuta-manual.xml:951(para)
2310 "There is not a great deal to say about <guimenuitem>Clean All</guimenuitem> "
2311 "(which might also be called <emphasis>Clean distribution</emphasis>, or "
2312 "<emphasis>clean dist</emphasis> for short). It cleans the project and leaves "
2313 "it in a state that requires <guimenuitem>Configure</guimenuitem> and "
2314 "<guimenuitem>Build All</guimenuitem> to be performed. It deletes all of the "
2315 "files generated by the build processes, including all the object files "
2316 "(<filename>*.o</filename> files), executable(s) and Makefiles. In other "
2317 "words, it leaves the project as though it has just been extracted from a "
2318 "distribution tarball."
2321 #: C/anjuta-manual.xml:961(para)
2323 "Choose the menu item <menuchoice><guisubmenu>Build</"
2324 "guisubmenu><guimenuitem>Clean All</guimenuitem></menuchoice> to completely "
2325 "clean the project."
2328 #: C/anjuta-manual.xml:968(title)
2329 msgid "Executing program"
2332 #: C/anjuta-manual.xml:969(para)
2334 "Once an executable is ready after the build, you can execute it by choosing "
2335 "the menu item <menuchoice><guisubmenu>Build</"
2336 "guisubmenu><guimenuitem>Execute</guimenuitem></menuchoice>, or pressing "
2337 "<keycap>F3</keycap>. You can specify which executable you want to use in "
2338 "case your project provides more than one and specify command line arguments."
2341 #: C/anjuta-manual.xml:976(title)
2342 msgid "Dependencies"
2345 #: C/anjuta-manual.xml:977(para)
2347 "Unlike the build stage, execution doesn't check for dependencies (at least "
2348 "for the time being). In other words, it does not check if the executable is "
2349 "up-to-date before it executes the program. So, <emphasis>you must take care "
2350 "of that yourself.</emphasis>"
2353 #: C/anjuta-manual.xml:987(title)
2354 msgid "Choose executable and set program parameters"
2357 #: C/anjuta-manual.xml:989(screeninfo)
2358 msgid "Setting program parameters"
2361 #: C/anjuta-manual.xml:3(title)
2365 #: C/anjuta-manual.xml:5(emphasis)
2366 msgid "To debug is human. To fix it is divine..."
2369 #: C/anjuta-manual.xml:7(para)
2371 "Well, the <emphasis>human</emphasis> part is what this section is about. The "
2372 "<emphasis>divine</emphasis> part is up to you!"
2375 #: C/anjuta-manual.xml:11(para)
2377 "When a program does not behave in the way it is supposed to, we say the "
2378 "program contains a bug or bugs. This does not refer to compilation errors — "
2379 "those are simply errors and they are relatively easy to clear, because the "
2380 "compiler tells you where the problems are. On the other hand, "
2381 "<emphasis>bugs</emphasis> are errors that happen during the execution of the "
2382 "program and they can be hard (sometimes very hard!) to detect."
2385 #: C/anjuta-manual.xml:19(para)
2387 "Any program that you think is bug-free is never completely bug-free. All we "
2388 "can try to do is to reduce the number of bugs contained in the program. The "
2389 "process of removing bugs is known as <emphasis>debugging</emphasis>, and the "
2390 "tool that is used for debugging is called the <emphasis>debugger</emphasis>. "
2391 "<application>Anjuta</application> provides a very user-friendly and powerful "
2392 "debugging environment (actually, a GUI wrapper over <application>gdb</"
2393 "application>, a powerful command line debugging tool and standard on Linux)."
2396 #: C/anjuta-manual.xml:27(para)
2398 "A debugger tracks and traces the execution of the program and provides "
2399 "various views of information needed to study the execution of the program."
2402 #: C/anjuta-manual.xml:33(para)
2404 "The debugger has been heavily changed since anjuta 2.0.2. Some features have "
2405 "been dropped but will be reenabled, a few have been added."
2408 #: C/anjuta-manual.xml:42(title)
2409 msgid "Start and stop"
2412 #: C/anjuta-manual.xml:47(emphasis) C/anjuta-manual.xml:53(title)
2413 msgid "Running an executable"
2416 #: C/anjuta-manual.xml:48(emphasis)
2417 msgid "Attaching to a process"
2420 #: C/anjuta-manual.xml:44(para)
2421 msgid "There are two ways to start the debugger: <placeholder-1/>"
2424 #: C/anjuta-manual.xml:54(para)
2426 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2427 "guisubmenu><guimenuitem>Run Target…</guimenuitem></menuchoice> to display a "
2428 "dialog box where you can select the executable that you want to debug, the "
2429 "command line parameters and if you want a terminal or not. The popup menu of "
2430 "the target combo box is already filled with all executables of the current "
2431 "project, so you can easily select one of them. But it is not mandatory, you "
2432 "can select any other executable. The debugger accepts libtool executable, I "
2433 "mean script wrapping the real executable generated by libtool. When you have "
2434 "set everything you can click on <guibutton>Execute</guibutton> to start the "
2435 "debugger, load your program and stop at its beginning."
2438 #: C/anjuta-manual.xml:68(para)
2440 "In order to better user the debugger, it is recommended to debug program "
2441 "with debugging information (-g for gcc) and no optimization (-O0 for gcc)."
2444 #: C/anjuta-manual.xml:76(title)
2445 msgid "Attaching to a Process"
2448 #: C/anjuta-manual.xml:77(para)
2450 "It is also possible to attach to a running process for debugging. Choose the "
2451 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Attach to "
2452 "Process …</guimenuitem></menuchoice>. A list of all the process running on "
2453 "the system will appear."
2456 #: C/anjuta-manual.xml:84(title) C/anjuta-manual.xml:86(screeninfo)
2457 msgid "Attach to Process dialog"
2460 #: C/anjuta-manual.xml:90(para)
2461 msgid "Select the process to attach to and click <guibutton>OK</guibutton>."
2464 #: C/anjuta-manual.xml:94(para)
2466 "It is currently not possible to load symbol information for the attached "
2470 #: C/anjuta-manual.xml:102(title)
2471 msgid "Restarting an executable"
2474 #: C/anjuta-manual.xml:103(para)
2476 "After running a executable at least one time, you can choose the menu item "
2477 "<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Restart Target</"
2478 "guimenuitem></menuchoice> to restart your program. It is just a shortcut "
2479 "that will stop the debugger if it is currently running and restart it with "
2480 "the last executable."
2483 #: C/anjuta-manual.xml:113(title)
2484 msgid "Stopping the Debugger"
2487 #: C/anjuta-manual.xml:114(para)
2489 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2490 "guisubmenu><guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the "
2491 "debugger. This option will kill the program which is being debugged. If the "
2492 "debugger has been attached to a running process, it will just detach from it "
2493 "without killing it. You will get a confirmation box if a program is "
2494 "currently attached or running."
2497 #: C/anjuta-manual.xml:128(title)
2501 #: C/anjuta-manual.xml:129(para)
2503 "Execution of a program in the debugger can be finely controlled. The program "
2504 "can be executed in single steps, or allowed to continue until it encounters "
2505 "a breakpoint. Executing like this is essential for tracking program "
2506 "behaviour. Like a video editing session, the program can be executed in "
2507 "<emphasis>slow motion</emphasis> with the ability to go forward, pause, "
2511 #: C/anjuta-manual.xml:136(para)
2513 "The methods that can be used to execute a program in the debugger are "
2514 "described in the next few sections."
2517 #: C/anjuta-manual.xml:142(title)
2518 msgid "Single stepping (step in)"
2521 #: C/anjuta-manual.xml:143(para)
2523 "Single stepping executes only one statement of the program (from the place "
2524 "where it has stopped) and then returns control. If the statement that is "
2525 "executed contains one or more functions, the debugger tries to step inside "
2526 "the functions (in the sequence in which the functions are executed). Once "
2527 "the statement is executed and control is passed back, it is possible to "
2528 "study the various program parameters."
2531 #: C/anjuta-manual.xml:150(para)
2532 msgid "If the program need to been started to use single stepping."
2535 #: C/anjuta-manual.xml:153(para)
2537 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2538 "guisubmenu><guimenuitem>Step In</guimenuitem></menuchoice> or click on the "
2539 "<guibutton>Step In</guibutton> icon in the <interface>Debug toolbar</"
2540 "interface> to step into a program."
2543 #: C/anjuta-manual.xml:162(title)
2544 msgid "Single stepping (step over)"
2547 #: C/anjuta-manual.xml:163(para)
2549 "<emphasis>Step over</emphasis> is similar to <emphasis>step in</emphasis>, "
2550 "except that it does not step inside any function in the statement being "
2551 "executed. The statement will be executed in one go."
2554 #: C/anjuta-manual.xml:168(para)
2556 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2557 "guisubmenu><guimenuitem>Step Over</guimenuitem></menuchoice> or click on the "
2558 "<guibutton>Step Over</guibutton> icon in the <interface>Debug toolbar</"
2559 "interface> to step over statements in a program."
2562 #: C/anjuta-manual.xml:175(para)
2564 "If a dynamic library is loaded during the step, the program will not stop at "
2565 "the end of the step. But it will run until it finds a breakpoint or you stop "
2569 #: C/anjuta-manual.xml:184(title)
2570 msgid "Single stepping (step out)"
2573 #: C/anjuta-manual.xml:185(para)
2575 "<emphasis>Step out</emphasis> will execute the current function until it "
2576 "returns. The program will be stopped once it exits from the function. Step "
2577 "out is not really single stepping, because it does not only execute a single "
2578 "statement — it executes the whole function until that function returns to "
2579 "the calling function."
2582 #: C/anjuta-manual.xml:192(para)
2584 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2585 "guisubmenu><guimenuitem>Step Out</guimenuitem></menuchoice> or click on the "
2586 "<guibutton>Step Out</guibutton> icon in the <interface>Debug toolbar</"
2587 "interface> to step out in a program."
2590 #: C/anjuta-manual.xml:201(title)
2591 msgid "Run/Continue"
2592 msgstr "Ejecutar/Seguir"
2594 #: C/anjuta-manual.xml:202(para)
2596 "This option will continue the execution of the program until a breakpoint is "
2597 "encountered, or the program exits."
2600 #: C/anjuta-manual.xml:206(para)
2602 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2603 "guisubmenu><guimenuitem>Run/Continue</guimenuitem></menuchoice> or click on "
2604 "the <guibutton>Run/Continue</guibutton> icon in the <interface>Debug "
2605 "toolbar</interface> to continue the execution of a program."
2608 #: C/anjuta-manual.xml:215(title)
2612 #: C/anjuta-manual.xml:216(para)
2614 "This option will continue the execution of the program until the line where "
2615 "cursor is is reached."
2618 #: C/anjuta-manual.xml:220(para)
2620 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2621 "guisubmenu><guimenuitem>Run to Cursor</guimenuitem></menuchoice> or click on "
2622 "the <guibutton>Run to Cursor</guibutton> icon in the <interface>Debug "
2623 "toolbar</interface> to run until the line at cursor is reached."
2626 #: C/anjuta-manual.xml:229(title)
2627 msgid "Stop Program"
2630 #: C/anjuta-manual.xml:230(para)
2632 "While the program is running and has control, no debugging tasks can be "
2633 "performed. To obtain control while the program is running, choose the menu "
2634 "item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Interrupt "
2635 "Program</guimenuitem></menuchoice> or click on the <guibutton>Stop Program</"
2636 "guibutton> icon in the <interface>Debug toolbar</interface>. This will "
2637 "interrupt the program and return control to the debugger."
2640 #: C/anjuta-manual.xml:245(title)
2642 msgstr "Puntos de parada"
2644 #: C/anjuta-manual.xml:246(para)
2646 "When debugging a program, it is useful to be able to stop the execution of "
2647 "the program at a particular point, so that the state of the program can be "
2648 "examined at that location. Breakpoints enable this to happen. Breakpoints "
2649 "can be set at different locations in a source file, and then the program is "
2650 "allowed to run. When a breakpoint is encountered, the execution of the "
2651 "program is suspended, enabling expressions to be evaluated, variables to be "
2652 "inspected, the stack trace to be studied, and so on."
2655 #: C/anjuta-manual.xml:256(title)
2656 msgid "Listing Breakpoints"
2659 #: C/anjuta-manual.xml:257(para)
2661 "The <interface>Breakpoint list window</interface> can be opened by choosing "
2662 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Breakpoints</"
2663 "guimenuitem></menuchoice>"
2666 #: C/anjuta-manual.xml:264(title) C/anjuta-manual.xml:266(screeninfo)
2667 msgid "Breakpoint view"
2670 #: C/anjuta-manual.xml:271(para)
2672 "<emphasis>Location</emphasis>, refers to the location of the code in the "
2673 "source file. <emphasis>Location</emphasis> can be specified in any of the "
2674 "following formats:"
2677 #: C/anjuta-manual.xml:278(para)
2678 msgid "File_name:Line_number"
2681 #: C/anjuta-manual.xml:279(para)
2682 msgid "Function_name"
2685 #: C/anjuta-manual.xml:280(para)
2686 msgid "File:Function_name"
2689 #: C/anjuta-manual.xml:283(para)
2691 "The first one is obvious — The location refers to the line number "
2692 "<emphasis>Line_number</emphasis> in the source file <emphasis>File</"
2693 "emphasis>. The second refers to the first line of the function "
2694 "<emphasis>Function_name</emphasis>. The third is similar to the second, "
2695 "except that this notation is used where there is more than one function with "
2696 "the name <emphasis>Function_name</emphasis> in the program. It is possible "
2697 "to differentiate between them by providing the <emphasis>File</emphasis>, so "
2698 "the notation refers to the function <emphasis>Function_name</emphasis> in "
2699 "the file <emphasis>File</emphasis>."
2702 #: C/anjuta-manual.xml:297(para)
2703 msgid "Break condition"
2704 msgstr "Condición de parada"
2706 #: C/anjuta-manual.xml:298(para)
2708 msgstr "Conteo de pasadas"
2710 #: C/anjuta-manual.xml:294(para)
2711 msgid "Two parameters can be associated with each breakpoint: <placeholder-1/>"
2712 msgstr "Se pueden asociar dos parámetros con cada punto de parada: <placeholder-1/>"
2714 #: C/anjuta-manual.xml:301(para)
2716 "The <emphasis>Break condition</emphasis> is a valid C expression which "
2717 "should evaluate to a Boolean value — that is, the evaluation of the "
2718 "expression should result in either TRUE(1) or FALSE(0). If the final "
2719 "evaluation value is not a Boolean value, then it will be appropriately type "
2720 "casted to a Boolean."
2723 #: C/anjuta-manual.xml:308(para)
2725 "Every time the breakpoint is encountered during the execution, the break "
2726 "condition will be evaluated. The debugger will break the execution only if "
2727 "the evaluation results in a TRUE value, otherwise it will continue the "
2728 "execution as though there had been no breakpoint."
2731 #: C/anjuta-manual.xml:314(para)
2733 "The default value of <emphasis>Break condition</emphasis> is always TRUE. "
2734 "The debugger will break the execution at the breakpoint location."
2736 "El valor predeterminado de la <emphasis>Condición de parada</emphasis> es siempre TRUE. "
2737 "El depurador parará la ejecución en la posición del punto de parada."
2739 #: C/anjuta-manual.xml:318(para)
2741 "The <emphasis>Pass count</emphasis> is an integer (unsigned) value which "
2742 "tells the debugger to skip the breakpoint that number of times before it is "
2743 "considered. <emphasis>Pass count</emphasis> has a higher priority than the "
2744 "<emphasis>Break condition</emphasis>. Only when the <emphasis>Pass count</"
2745 "emphasis> reaches zero will the debugger evaluate the <emphasis>Break "
2746 "condition</emphasis> (if any condition is present). If there is no "
2747 "condition, the debugger will break the execution once the <emphasis>Pass "
2748 "count</emphasis> counts down to zero."
2751 #: C/anjuta-manual.xml:328(para)
2753 "The default value of the <emphasis>Pass count</emphasis> is zero. The "
2754 "breakpoint will be considered when it is first encountered."
2756 "El valor predeterminado del <emphasis>Conteo de pasadas<emphasis> es cero. El "
2757 "punto de parada se considerará cuando se encuentre por primera vez."
2759 #: C/anjuta-manual.xml:333(para)
2761 "All breakpoints are kept across anjuta session even if they correspond to a "
2762 "non existing place. The interface try to set them each time the program is "
2763 "started or a new dynamic library is loaded."
2766 #: C/anjuta-manual.xml:342(title)
2767 msgid "Adding or Setting Breakpoints"
2768 msgstr "Añadir o establecer puntos de parada"
2770 #: C/anjuta-manual.xml:343(para)
2772 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2773 "guisubmenu><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> or "
2774 "<menuchoice><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> in the "
2775 "breakpoint list popup menu to open the add breakpoint dialog."
2778 #: C/anjuta-manual.xml:351(title) C/anjuta-manual.xml:353(screeninfo)
2779 msgid "Breakpoint add dialog"
2780 msgstr "Diálogo de adición de punto de parada"
2782 #: C/anjuta-manual.xml:358(para)
2784 "Enter the location at which to set the breakpoint. Optionally, enter the "
2785 "<emphasis>Break condition</emphasis> and the <emphasis>Pass count</emphasis> "
2786 "in the appropriate entry boxes. Click <guibutton>OK</guibutton> to set the "
2790 #: C/anjuta-manual.xml:364(para)
2792 "A breakpoint may also be by selecting a line in the editor and choosing the "
2793 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Toggle "
2794 "Breakpoint</guimenuitem></menuchoice>, the editor popup menu item "
2795 "<menuchoice><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice> or the "
2796 "<guibutton>Toggle Breakpoint</guibutton> icon in the <interface>Debug "
2797 "toolbar</interface>."
2800 #: C/anjuta-manual.xml:374(para)
2802 "Breakpoints can be added even if the debugger is not started or in dynamic "
2803 "library not loaded yet. But they cannot be added while a program is running "
2804 "under control of the debugger."
2807 #: C/anjuta-manual.xml:383(title)
2808 msgid "Editing Breakpoints"
2809 msgstr "Editar puntos de parada"
2811 #: C/anjuta-manual.xml:384(para)
2813 "It is possible to change the condition of a breakpoint of the pass count by "
2814 "selecting the breakpoint to edit in the breakpoint list and click in the "
2815 "popup menu item <menuchoice><guimenuitem>Edit Breakpoint</guimenuitem></"
2819 #: C/anjuta-manual.xml:389(para)
2821 "Edit the entries as required and click on <guibutton>OK</guibutton> to "
2822 "commit the changes."
2824 "Edite las entradas como se requiere y pulse <guibutton>Aceptar</guibutton> para "
2825 "efectuar los cambios."
2827 #: C/anjuta-manual.xml:396(title)
2828 msgid "Deleting Breakpoints"
2829 msgstr "Borrar puntos de parada"
2831 #: C/anjuta-manual.xml:397(para)
2833 "Select the breakpoint to delete in the breakpoint list view and click on "
2834 "<menuchoice><guimenuitem>Remove Breakpoint</guimenuitem></menuchoice>."
2837 #: C/anjuta-manual.xml:401(para)
2839 "A existing breakpoint may also be deleted by selecting the line in the "
2840 "editor and choosing the menu item <menuchoice><guisubmenu>Debug</"
2841 "guisubmenu><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice>, the "
2842 "editor popup menu item <menuchoice><guimenuitem>Toggle Breakpoint</"
2843 "guimenuitem></menuchoice> or the <guibutton>Toggle Breakpoint</guibutton> "
2844 "icon in the <interface>Debug toolbar</interface>."
2847 #: C/anjuta-manual.xml:413(title)
2848 msgid "Enabling or Disabling Breakpoints"
2851 #: C/anjuta-manual.xml:414(para)
2853 "Click on the Enable column of the <interface>Breakpoint list window</"
2854 "interface> or in the menu item <menuchoice><guimenuitem>Enable Breakpoint</"
2855 "guimenuitem></menuchoice> to enable or disable the selected breakpoint. The "
2856 "breakpoint will be enabled or disabled, depending on the current state."
2859 #: C/anjuta-manual.xml:420(para)
2861 "To disable all breakpoints, click on <menuchoice><guisubmenu>Debug</"
2862 "guisubmenu><guimenuitem>Disable All Breakpoints</guimenuitem></menuchoice> "
2863 "or on <menuchoice><guimenuitem>Disable All Breakpoints</guimenuitem></"
2864 "menuchoice> in the breakpoint list popup menu."
2867 #: C/anjuta-manual.xml:431(title)
2871 #: C/anjuta-manual.xml:434(title)
2872 msgid "Listing local variable"
2875 #: C/anjuta-manual.xml:435(para)
2877 "When a program is running under the control of the debugger, the "
2878 "<interface>Locals list window</interface> can be opened by choosing "
2879 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Locals</guimenuitem></"
2883 #: C/anjuta-manual.xml:449(title) C/anjuta-manual.xml:451(screeninfo)
2884 msgid "Local variables"
2887 #: C/anjuta-manual.xml:441(para)
2889 "Local variables of the current frame (the current funtion in which the "
2890 "program control is present) are displayed in the <interface>Locals list "
2891 "window</interface>. During execution of the program (eg. during single "
2892 "stepping), local variables will be updated. If any varialble value was "
2893 "changed in the last debugging step, its value will be highlight in red. The "
2894 "variables are presented in a tree form for easy view. <placeholder-1/>"
2897 #: C/anjuta-manual.xml:456(para)
2899 "The value of a local variable can be modified by selecting it and clicking "
2900 "in the value column."
2903 #: C/anjuta-manual.xml:461(para)
2905 "Gdb is more and more often used as a back end for a graphical front end. It "
2906 "has been improved recently in this area. It is recommanded to use the latest "
2907 "version (6.6) of gdb. On older version, gdb can crash when the front end ask "
2908 "for an pointer with an invalid (but not used) value."
2911 #: C/anjuta-manual.xml:471(title)
2912 msgid "Listing watched expressions"
2915 #: C/anjuta-manual.xml:472(para)
2917 "Inspecting or evaluating an expression provides the result only once. To "
2918 "continuously monitor some variables or expressions, use <emphasis>expression "
2922 #: C/anjuta-manual.xml:476(para)
2924 "Choose the menu item <menuchoice><guisubmenu>View</"
2925 "guisubmenu><guimenuitem>Watch Window</guimenuitem></menuchoice> to display "
2926 "the <interface>expression watch window</interface>."
2929 #: C/anjuta-manual.xml:483(title)
2930 msgid "Adding an expression to watch"
2933 #: C/anjuta-manual.xml:484(para)
2935 "Right-click on the <interface>expression watch window</interface> to open "
2936 "the <interface>Operation menu</interface>. Choose the menu item "
2937 "<guimenuitem>Add Watch…</guimenuitem>. Alternatively, you can use "
2938 "<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Add Watch…</"
2939 "guimenuitem></menuchoice> A dialog prompting for the expression will appear. "
2940 "Enter the expression and click <guibutton>OK</guibutton>."
2943 #: C/anjuta-manual.xml:493(para)
2945 "By default watch expression are updated automatically each time the program "
2946 "is stopped. This can be changed in the add watch dialog or later using the "
2947 "<guimenuitem>Automatic update</guimenuitem> menu item in the "
2948 "<interface>expression watch window</interface> popup menu. A watched "
2949 "expression can be update manually by choosing <guimenuitem>Update Watch</"
2950 "guimenuitem> or <guimenuitem>Update All</guimenuitem> in the previous menu."
2953 #: C/anjuta-manual.xml:502(para)
2955 "It is not necessary to have the debugger running to add a new watch "
2956 "expression. If the debugger is not running or the corresponding expression "
2957 "cannot be found, the front end will try to create the watch expression, each "
2958 "time the program is stopped."
2961 #: C/anjuta-manual.xml:511(title)
2962 msgid "Removing an expression from watch"
2965 #: C/anjuta-manual.xml:512(para)
2967 "Select the watch expression that you want to remove in the "
2968 "<interface>expression watch window</interface>, then open the "
2969 "<interface>Operation menu</interface>, clicking with the right mouse button, "
2970 "and choose the menu item <guimenuitem>Remove</guimenuitem> to remove it."
2973 #: C/anjuta-manual.xml:518(para)
2975 "All watch can be removed by choosing <guimenuitem>Remove All</guimenuitem> "
2976 "in the popup menu of the <interface>expression watch window</interface>."
2979 #: C/anjuta-manual.xml:525(title)
2980 msgid "Evaluating expressions"
2983 #: C/anjuta-manual.xml:526(para)
2985 "When control is returned from a program — possibly at a breakpoint — it is "
2986 "possible to evaluate expressions or inspect the values of variables in the "
2987 "program. Choose the menu item <menuchoice><guisubmenu>Debug</"
2988 "guisubmenu><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice>, "
2989 "<menuchoice><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice> in "
2990 "the popup menu of the editor or click the <guibutton>Inspect</guibutton> "
2991 "button on the <interface>Debug Toolbar</interface>."
2994 #: C/anjuta-manual.xml:535(para)
2995 msgid "A window will appear showing the result of the evaluation."
2998 #: C/anjuta-manual.xml:538(para)
3000 "If an expression is highlighted in the editor, it is already displayed else "
3001 "the window is empty. In both cases, you an select a new expression by "
3002 "clicking on the name column and writing the new expression."
3005 #: C/anjuta-manual.xml:543(para)
3007 "The expression can be added directly in the list of watched expressions by "
3008 "clicking on <guibutton>Add</guibutton> button."
3011 #: C/anjuta-manual.xml:553(title)
3012 msgid "Stack Trace and Thread"
3015 #: C/anjuta-manual.xml:556(title)
3016 msgid "Stack Window"
3017 msgstr "Ventana de pila"
3019 #: C/anjuta-manual.xml:557(para)
3021 "The <interface>Stack trace window</interface> shows the contents of the "
3022 "program stack. It lists all of the functions and their arguments in the "
3023 "sequence they were called. There is also a number representing each call. "
3024 "This number is called the <emphasis>Frame</emphasis>. Each call in the trace "
3025 "exists in a different frame. This starts from frame 0 (the last function "
3026 "called) and grows higher as the function nesting become deeper."
3029 #: C/anjuta-manual.xml:565(para)
3031 "Choose the menu item <menuchoice><guisubmenu>View</"
3032 "guisubmenu><guimenuitem>Program Stack</guimenuitem></menuchoice>, to open "
3033 "the stack trace for the program being debugged."
3036 #: C/anjuta-manual.xml:572(title) C/anjuta-manual.xml:574(screeninfo)
3037 msgid "Stack trace window"
3040 #: C/anjuta-manual.xml:579(para)
3042 "A small arrow points to the currently selected frame in the stack trace. By "
3043 "default, this will be frame 0, the last function called. All of the "
3044 "evaluation and inspection of expressions or variables will be with reference "
3045 "to this selected frame. The scope of the variables or expressions being "
3046 "evaluated will be limited to the selected frame only. The same applies for "
3047 "new expressions only in the watch."
3050 #: C/anjuta-manual.xml:589(title)
3051 msgid "Setting the current frame"
3054 #: C/anjuta-manual.xml:590(para)
3056 "Double-clicking on any frame in the stack trace will set that frame as the "
3057 "currently selected frame (the arrow will point to the frame, indicating that "
3058 "it has been selected as the current frame). Alternatively, open the "
3059 "<interface>Operation menu</interface> by right-clicking on the "
3060 "<interface>Stack trace window</interface>, and choose the menu item "
3061 "<guimenuitem>Set frame</guimenuitem> to set the frame."
3064 #: C/anjuta-manual.xml:598(para)
3066 "Changing the stack frame will change the <interface>Locals list window</"
3067 "interface> content, but not the <interface>expression watch window</"
3068 "interface> as each expression is evaluated in the frame used when it was "
3072 #: C/anjuta-manual.xml:606(title)
3073 msgid "Thread Window"
3076 #: C/anjuta-manual.xml:607(para)
3078 "The <interface>Thread window</interface> show all threads used by the "
3079 "program and display the current thread. Choose the menu item "
3080 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Thread</guimenuitem></"
3081 "menuchoice>, to open this window."
3084 #: C/anjuta-manual.xml:612(para)
3086 "A small arrow points to the current thread. When the programm is stopped, it "
3087 "correspond to the thread which has been interrupted. Each thread has its own "
3088 "stack frame,so changing the current thread will change the current stack "
3092 #: C/anjuta-manual.xml:621(title)
3093 msgid "Setting the current thread"
3096 #: C/anjuta-manual.xml:622(para)
3098 "Double-clicking on any thread in the thread list will set that thread as the "
3099 "currently selected thread (the arrow will point to the thread, indicating "
3100 "that it has been selected as the current thread). Alternatively, open the "
3101 "<interface>Operation menu</interface> by right-clicking on the "
3102 "<interface>Thread list window</interface>, and choose the menu item "
3103 "<guimenuitem>Set thread</guimenuitem> to set the thread."
3106 #: C/anjuta-manual.xml:630(para)
3108 "Changing the thread will change the value of CPU registers and the current "
3109 "stack frame, so the <interface>Locals list window</interface> will change "
3113 #: C/anjuta-manual.xml:639(title)
3117 #: C/anjuta-manual.xml:642(title)
3118 msgid "Register window"
3119 msgstr "Ventana de registros"
3121 #: C/anjuta-manual.xml:643(para)
3123 "It is possible to examine the contents of the internal registers of the CPU "
3124 "(microprocessor). Choose the menu item <menuchoice><guisubmenu>View</"
3125 "guisubmenu><guimenuitem>Registers</guimenuitem></menuchoice>. A window "
3126 "listing all of the available registers in the microprocessor and their "
3127 "corresponding contents will appear."
3129 "Es posible examinar el contenido de los registros internos de la CPU "
3130 "(microprocesador). Elija el elemento del menú <menuchoice><guisubmenu>Ver</"
3131 "guisubmenu><guimenuitem>Registros</guimenuitem></menuchoice>. Aparecerá "
3132 "una ventana listando todos los registros disponibles en el microprocesador y "
3133 "su correspondiente contenido."
3135 #: C/anjuta-manual.xml:650(para)
3137 "If any register value was changed in the last debugging step, its value will "
3138 "be highlight in red. It is possible to change one register value by "
3139 "selecting it and clicking in the value column."
3141 "Si cualquier valor de un registro se cambió en el último paso de depuración, su valor "
3142 "se resaltará en rojo. Es posible cambiar el valor de un registro "
3143 "seleccionándolo y pulsando en la columna de valor."
3145 #: C/anjuta-manual.xml:658(title)
3146 msgid "Memory window"
3147 msgstr "Ventana de memoria"
3149 #: C/anjuta-manual.xml:659(para)
3151 "Choose the menu item <menuchoice><guisubmenu>View</"
3152 "guisubmenu><guimenuitem>Memory </guimenuitem></menuchoice>, to open the "
3153 "<interface>memory window</interface> for the program being debugged. This "
3154 "window shows the contents of all memory."
3156 "Elija el elemento del menú <menuchoice><guisubmenu>Ver</"
3157 "guisubmenu><guimenuitem>Memoria</guimenuitem></menuchoice> para abrir la "
3158 "<interface>ventana de memoria</interface> para el programa que se está depurando. Esta "
3159 "ventana muestra el contenido de toda la memoria."
3161 #: C/anjuta-manual.xml:664(para)
3163 "The first is the memory address in hexadecimal, the second is the memory "
3164 "content in hexadecimal too and the last column is the memory content in "
3167 "Lo primero son las direcciones de memoria en hexadecimal, lo segundo es el contenido "
3168 "de la memoria en hexadecimal y la última columna es el contenido de la memoria en "
3171 #: C/anjuta-manual.xml:668(para)
3173 "The addressing space of even a 32 bits microprocessor is quite big(4 Giga "
3174 "bytes), so it is very difficult to go to a particular address with the "
3175 "scrollbar. But you can click on the right mouse button, get a new menu and "
3176 "select <menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to "
3177 "get a small edit box where you can enter an address in hexadecimal."
3180 #: C/anjuta-manual.xml:678(title)
3181 msgid "Disassembly window"
3184 #: C/anjuta-manual.xml:679(para)
3186 "Choose the menu item <menuchoice><guisubmenu>View</"
3187 "guisubmenu><guimenuitem>Disassembly </guimenuitem></menuchoice>, to open the "
3188 "<interface>disassembly window</interface> for the program being debugged. "
3192 #: C/anjuta-manual.xml:685(para)
3194 "The first column is the address in hexadecimal. In the second column, you "
3195 "can have a label starting at the beginning of the line and ended with a "
3196 "colon or a assembler instruction starting after 4 space characters."
3199 #: C/anjuta-manual.xml:690(para)
3201 "Again, as the addressing space is very big, the scrollbar is quite useless. "
3202 "You can click on the right mouse button, get a new menu and select "
3203 "<menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to get a "
3204 "small edit box where you can enter an address in hexadecimal. The position "
3205 "in the disassembly window will be changed to the program counter value when "
3206 "the program is stopped."
3209 #: C/anjuta-manual.xml:703(title)
3213 #: C/anjuta-manual.xml:705(para)
3215 "There are a number of other debugger features used less frequently and not "
3216 "very well integrated in the new front end but which are still working."
3218 "Existe cierto número de características del depurador que se no se usan tan frecuentemente y "
3219 "no están muy bien integradas en el nuevo front-end pero se está trabajando en ello."
3221 #: C/anjuta-manual.xml:711(title)
3222 msgid "Dynamically loaded Libraries"
3223 msgstr "Bibliotecas cargadas dinámicamente"
3225 #: C/anjuta-manual.xml:712(para)
3227 "To obtain a list of the dynamic libraries used by the program, choose the "
3228 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
3229 "guisubmenu><guimenuitem>Shared Libraries</guimenuitem></menuchoice>. This "
3230 "will bring open a window which will list all the shared libraries the "
3231 "program has loaded and their locations in the memory. It also shows whether "
3232 "the symbol table is loaded or not (Yes/No)."
3234 "Para obtener una lista de las bibliotecas usadas dinámicamente por el programa, elija "
3235 "el elemento del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</"
3236 "guisubmenu><guimenuitem>Bibliotecas compartidas</guimenuitem></menuchoice>. Esto "
3237 "abrirá una nueva ventana que listará todas las bibliotecas compartidas que "
3238 "el programa ha cargado y sus ubicaciones en la memoria. También muestra si "
3239 "la tabla de símbolos se ha cargado o no (Sí/No)."
3241 #: C/anjuta-manual.xml:722(title) C/anjuta-manual.xml:724(screeninfo)
3242 msgid "Shared Libraries window"
3243 msgstr "Ventana de bibliotecas compartidas."
3245 #: C/anjuta-manual.xml:732(title)
3246 msgid "Kernel Signals"
3247 msgstr "Señales del núcleo"
3249 #: C/anjuta-manual.xml:733(para)
3251 "Kernel signals are a way of signaling between processes in Linux. The list "
3252 "of signals available for a program can be displayed by choosing the menu "
3253 "item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
3254 "guisubmenu><guimenuitem>Kernel Signals</guimenuitem></menuchoice>. A window "
3255 "will open which lists all of the signals available in the system along with "
3256 "a brief description of each signal."
3258 "Las señales del núcleo son una forma de señalizar procesos en Linux. La lista de "
3259 "señales disponibles para un programa se puede mostrar eligiendo el elemento "
3260 "del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información<menuchoice><guisubmenu>Señales del núcleo</guisubmenu><guisubmenu>. Se abrirá una ventana "
3261 "listando todas las señales disponibles en el sistema junto con "
3262 "una breve descripción de cada señal."
3264 #: C/anjuta-manual.xml:742(title) C/anjuta-manual.xml:744(screeninfo)
3265 msgid "Kernel Signals window"
3266 msgstr "Ventana de señales del núcleo"
3268 #: C/anjuta-manual.xml:749(para)
3269 msgid "There are three columns which specify what to do when the signal is received:"
3270 msgstr "Existen tres columnas que especifican qué hacer cuando se recibe una señal:"
3272 #: C/anjuta-manual.xml:755(para)
3274 "<emphasis>Stop</emphasis> — this tells the debugger whether to stop the "
3275 "program execution (and return control) when the program receives this signal."
3277 "<emphasis>Parar</emphasis>; esto le dice al depurador si debe parar la "
3278 "ejecución del programa (y devolver el control) cuando el programa recibe esta señal."
3280 #: C/anjuta-manual.xml:761(para)
3282 "<emphasis>Print</emphasis> — this tells the debugger whether to display the "
3285 "<emphasis>Imprimir</emphasis>; esto de dice al depurador si debe mostrar la "
3288 #: C/anjuta-manual.xml:766(para)
3290 "<emphasis>Pass</emphasis> — this tells the debugger whether to pass the "
3291 "signal to the program."
3293 "<emphasis>Pasar</emphasis>; esto le dice al depurador si debe pasar la "
3294 "señal al programa."
3296 #: C/anjuta-manual.xml:772(para)
3298 "The popup menu that is displayed when you click on the right mouse button "
3299 "has all its item disabled because the corresponding functions are not "
3302 "El menú emergente que se muestra al pulsar con el botón derecho del ratón "
3303 "tiene todos sus elementos desactivados porque las funciones correspondientes no "
3304 "están aún implementadas."
3306 #: C/anjuta-manual.xml:781(title)
3307 msgid "Information about used files"
3308 msgstr "Información acerca de archivos usados"
3310 #: C/anjuta-manual.xml:782(para)
3312 "It is possible to get some information about the files used by the debugged "
3313 "program. by choosing the menu item <menuchoice><guisubmenu>Debug</"
3314 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Target files</"
3315 "guimenuitem></menuchoice>. A window will open displaying all informations."
3317 "Es posible obtener alguna información acerca de los archivos usados por el programa "
3318 "depurado, eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Información de archivos objetivo</guimenuitem></menuchoice>. Se abrirá una ventana mostrando toda la información."
3320 #: C/anjuta-manual.xml:791(title)
3321 msgid "Information about debugged program"
3322 msgstr "Información acerca del programa depurado"
3324 #: C/anjuta-manual.xml:792(para)
3326 "It is possible to get some information about the debugged program by "
3327 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3328 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Program</"
3329 "guimenuitem></menuchoice>. A window will open displaying all informations."
3331 "Es posible obtener alguna información acerca del programa depurado "
3332 "eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</"
3333 "guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Programa</"
3334 "guimenuitem></menuchoice>. Se abrirá una ventana mostrando toda la información."
3336 #: C/anjuta-manual.xml:801(title)
3337 msgid "Information about kernel structure"
3338 msgstr "Información acerca de la estructura del núcleo"
3340 #: C/anjuta-manual.xml:802(para)
3342 "It is possible to get some information kernel data on the current process by "
3343 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3344 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Kernel user "
3345 "struct</guimenuitem></menuchoice>. A window will open displaying all "
3348 "Es posible obtener alguna información de los datos del núcleo acerca de los procesos actuales "
3349 "eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Información del user struct del núcleo</guimenuitem></menuchoice>. Se abrirá una ventana mostrando toda la información."
3351 #: C/anjuta-manual.xml:811(title)
3352 msgid "Information about global variables"
3353 msgstr "Información acerca de las variables globales"
3355 #: C/anjuta-manual.xml:812(para)
3357 "It is possible to list all global variables by choosing the menu item "
3358 "<menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Information</"
3359 "guisubmenu><guimenuitem>Info Global Variable</guimenuitem></menuchoice>. A "
3360 "window will open listing all global variables."
3362 "Es posible listar todas las variables globales eligiendo el elemento del menú "
3363 "<menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Info variables globales</guimenuitem></menuchoice>. Se abrirá una ventana listando todas las variables globales."
3365 #: C/anjuta-manual.xml:821(title)
3366 msgid "Information about the current frame"
3367 msgstr "Información acerca del marco actual"
3369 #: C/anjuta-manual.xml:822(para)
3371 "It is possible to obtain information about the currently selected frame by "
3372 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3373 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Info Current "
3374 "Frame</guimenuitem></menuchoice>. A window will open describing the current "
3377 "Es posible obtener información acerca del marco actualmente seleccionado "
3378 "eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Marco actual</guimenuitem></menuchoice>. Se abrirá una ventana describiendo el marco actual."
3380 #: C/anjuta-manual.xml:831(title)
3381 msgid "Information about the current function arguments"
3382 msgstr "Información acerca de los argumentos actuales de la función"
3384 #: C/anjuta-manual.xml:832(para)
3386 "It is possible to obtain information about the arguments of the current "
3387 "function by choosing the menu item <menuchoice><guisubmenu>Debug</"
3388 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Arguments</"
3389 "guimenuitem></menuchoice>. A window will open describing the arguments."
3391 "Es posible obtener información acerca de los argumentos de la función "
3392 "actual eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Argumentos</guimenuitem></menuchoice>. Se abrirá una ventana describiendo los argumentos."
3394 #: C/anjuta-manual.xml:841(title)
3395 msgid "User command"
3396 msgstr "Comando de usuario"
3398 #: C/anjuta-manual.xml:842(para)
3400 "To send directly a command to the back end choose the menu item "
3401 "<menuchoice><guimenu>Debug</guimenu><guimenuitem>Debugger command</"
3402 "guimenuitem></menuchoice>. This will bring a small dialog where you can "
3403 "enter commands that will be send to the debugger when you press "
3404 "<keycap>Return</keycap>."
3406 "Para enviar directamente un comando al «backend» elija el elemento del menú "
3407 "<menuchoice><guimenu>Depurar</guimenu><guimenuitem>Comando del depurador</guimenuitem></menuchoice>. Se mostrará un pequeño diálogo donde podrá "
3408 "introducir los comandos que se enviarán al depurador cuando pulse "
3409 "<keycap>Intro</keycap>."
3411 #: C/anjuta-manual.xml:850(para)
3413 "The front end sends this command directly to the back end without doing any "
3414 "check. By example if you set a breakpoint like this, it will not appear in "
3415 "the <interface>breakpoint list window</interface>. It is better to avoid "
3416 "using this command unless you know exactly what you are doing."
3418 "El «frontend» envía este comando directamente al «backend» sin ninguna "
3419 "comprobación. Por ejemplo, si establece un punto de parada como este, no aparecerá "
3420 "en la <interface>ventana de lista de puntos de parada</interface>. Es mejor evitar "
3421 "el uso de este comando a no ser que sepa exactamente qué está haciendo."
3423 #: C/anjuta-manual.xml:3(title)
3425 msgstr "Preferencias"
3427 #: C/anjuta-manual.xml:4(para)
3429 "Preferences are ways to customize <application>anjuta</application> to suit "
3430 "your tastes. Activate <menuchoice><guimenu>Settings</"
3431 "guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> to bring up the "
3432 "preferences dialog. If you want to reset the preferences to their default "
3433 "values, it can be done from <menuchoice><guimenu>Settings</"
3434 "guimenu><guimenuitem> Set Default Preferences</guimenuitem></menuchoice>. "
3435 "Some are explained below."
3437 "Las preferencias siempre son personalizables para que <application>Anjuta</application> se ajuste "
3438 "a sus gustos. Active <menuchoice><guimenu>Opciones</guimenu><guimenuitem>Preferencias</guimenuitem></menuchoice> para "
3439 "mostrar el diálogo de preferencias. Si quiere restablecer las preferencias a los valores predeterminados, "
3440 "puede hacerlo desde <menuchoice><guimenu>Opciones</guimenu><guimenuitem>Preferencias predeterminadas</guimenuitem></menuchoice>. Algunas se explican debajo."
3442 #: C/anjuta-manual.xml:11(title)
3446 #: C/anjuta-manual.xml:13(para)
3448 "<emphasis>Project Directory</emphasis> is the path where you plan to put all "
3449 "your projects. Application wizard creates new projects in this directory "
3450 "only. The default project directory is ~/Projects and generally, this is "
3451 "just fine for most people. Also, when Open project is activated, this is the "
3452 "base directory where the file selectior will start."
3454 "<emphasis>Directorio del proyecto:</emphasis> Es la ruta donde planea poner todos "
3455 "sus proyectos. El asistente de aplicación crea los nuevos proyectos sólo en este directorio. "
3456 "El directorio de proyecto predeterminado es ~/Projects y generalmente es suficiente "
3457 "para la mayoría de las personas. Además, cuando Abrir proyecto está activado, es el "
3458 "directorio base donde el selector de archivos comenzará."
3460 #: C/anjuta-manual.xml:20(para)
3462 "<emphasis>User Info:</emphasis> Provide your correct Name and Email address "
3463 "here. They are not used to do software registration (pun), rather they are "
3464 "used to create ChangeLog entries and other insert text bits."
3466 "<emphasis>Información del usuario:</emphasis> Proporciona su nombre y dirección de "
3467 "correo electrónico. No se utilizan para registrar el software, sino para crear entradas en el "
3468 "archivo ChangeLog e insertar otros bits de texto."
3470 #: C/anjuta-manual.xml:27(title)
3471 msgid "File Manager"
3472 msgstr "Gestor de archivos"
3474 #: C/anjuta-manual.xml:29(para)
3476 "<emphasis>Root directory if no project is open</emphasis> is the path where "
3477 "the root of the file manager points to if no project is currently open."
3479 "<emphasis>Directorio raíz si no hay un proyecto abierto</emphasis> es la ruta donde "
3480 "apunta la raíz del gestor de archivos si actualmente no hay ningún proyecto abierto."
3482 #: C/anjuta-manual.xml:34(para)
3484 "<emphasis>File Filter:</emphasis> It is possible to filter out some file "
3485 "from the file tree, for example hidden files or files that are ignored by "
3486 "the version control system which usually means they are generated at build "
3487 "time and should not be changed."
3489 "<emphasis>Filtro de archivos:</emphasis> Es posible filtrar algunos archivos "
3490 "del árbol de archivos, por ejemplo los archivos ocultos o los archivos ignorados "
3491 "por el sistema de control de versiones que generalmente significa que se general "
3492 "durante la compilación y no se deberían cambiar."
3494 #: C/anjuta-manual.xml:3(title)
3495 msgid "User-defined Tools"
3496 msgstr "Herramientas definidas por el usuario"
3498 #: C/anjuta-manual.xml:7(para)
3500 "Often, you'll find the inbuilt functionality provided by Anjuta to be "
3501 "insufficient. In these cases, you might be tempted to either add the feature "
3502 "yourself to the Anjuta codebase or submit a feature request to implement the "
3503 "feature. However, both approaches are likely to be slow and problematic, "
3504 "especially if your tool is a specialized one. In these circumstances, it is "
3505 "advisable to use the Anjuta tools framework instead."
3507 "A menudo encontrará que las funcionalidades propias proporcionadas por Anjuta son "
3508 "insuficientes. En estos casos, puede que esté tentado a añadir la característica "
3509 "al código fuente de Anjuta usted mismo o enviar una petición de implementación de "
3510 "característica. No obstante, ambos casos suelen ser lentos y problemáticos, "
3511 "especialmente si su herramienta es especializada. Bajo estas circunstancias, es mejor "
3512 "usar el entorno de trabajo de las herramientas de Anjuta."
3514 #: C/anjuta-manual.xml:16(para)
3516 "Anjuta provides a powerful framework for defining user-defined tools for "
3517 "extending it's functionality. Tools have access to almost all features of "
3518 "the IDE through the use of variables. You can add tools under any menu item, "
3519 "specify input, output and error redirection within the GUI framework and "
3520 "supply command line parameters to the tool."
3522 "Anjuta proporciona un potente entorno de trabajo para definir herramientas definidas por el usuario para "
3523 "extender su funcionalidad. Las herramientas acceden a casi todas las características del "
3524 "EID a través del uso de variables. Puede añadir herramientas bajo cualquier elemento del menú, "
3525 "entradas específicas, salidas y redirecciones de errores dentro del entorno de trabajo del IGU así "
3526 "como proporcionar parámetros de la línea de comandos a la herramienta."
3528 #: C/anjuta-manual.xml:24(para)
3529 msgid "The tools plugin has to be enabled to use this feature!"
3530 msgstr "El complemento de herramientas debe estar activado para usar esta característica."
3532 #: C/anjuta-manual.xml:31(title)
3533 msgid "Tools Examples"
3534 msgstr "Ejemplos de herramientas"
3536 #: C/anjuta-manual.xml:32(para)
3538 "This is a simple example how to use the tools plugin to integrate the GNOME "
3539 "ChangeLog generation script"
3541 "Este es un simple ejemplo de cómo usar el complemento de herramientas para integrar el "
3542 "script generador de registro de cambios de GNOME."
3544 #: C/anjuta-manual.xml:38(title) C/anjuta-manual.xml:40(screeninfo)
3545 msgid "The tool editor"
3546 msgstr "La herramienta de edición"
3548 #: C/anjuta-manual.xml:2(title)
3552 #: C/anjuta-manual.xml:3(para)
3554 "The <application>Anjuta</application> project was founded by Naba Kumar. "
3555 "Please visit <ulink type=\"http\" url=\"http://anjuta.org?page=authors/"
3556 "\">this online list</ulink> to know all Anjuta contributors."
3558 "Naba Kumar fundó el proyecto <application>Anjuta</application>. "
3559 "Visite <ulink type=\"http\" url=\"http://anjuta.org?page=authors/\">esta "
3560 "lista en línea</ulink> para conocer todos los contribuidores de Anjuta."
3562 #: C/anjuta-manual.xml:10(para)
3564 "For more information on <application>Anjuta</application>, please visit the "
3565 "project website at <ulink type=\"http\" url=\"http://anjuta.org/\">http://"
3566 "anjuta.org</ulink>. Bug reports should be made using the Bug Tracker at the "
3567 "project development site <ulink type=\"http\" url=\"http://www.sourceforge."
3568 "net/projects/anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>"
3570 "Para obtener más información acerca de <application>Anjuta</application>, visite la "
3571 "página web del proyecto en <ulink type=\"http\" url=\"http://anjuta.org/\">http://anjuta.orghttp://anjuta.org. "
3572 "Los informes de error se deben rellenar usando Bug Tracker en la "
3573 "página web de desarrollo del proyecto en <ulink type=\"http\" url=\"http://www.sourceforge."
3574 "net/projects/anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>."
3576 #: C/anjuta-manual.xml:18(para)
3578 "This manual was written by Naba Kumar and Andy Piper. Please send all "
3579 "comments and suggestions regarding this manual to Anjuta Devel list "
3580 "<email>anjuta-devel@list.sourceforge.net</email>. Comments may also be "
3581 "submitted via the project trackers at SourceForge."
3583 "Naba Kumar y Andy Piper escribieron este manual. Envíe cualquier comentario y "
3584 "sugerencia acerca de este manual a la lista de desarrollo de Anjuta "
3585 "<email>anjuta-devel@list.sourceforge.net</email>. También se pueden enviar comentarios "
3586 "a traes de la página del proyecto en SourceForge."
3588 #: C/anjuta-manual.xml:2(title)
3592 #: C/anjuta-manual.xml:3(para)
3594 "This program is free software; you can redistribute it and/or modify it "
3595 "under the terms of the <ulink type=\"ghelp\" url=\"gnome-help:gpl\">GNU "
3596 "General Public License</ulink> as published by the Free Software Foundation; "
3597 "either version 2 of the License, or (at your option) any later version."
3599 "Este programa es software libre; puede redistribuirlo y/o modificarlo "
3600 "bajo los términos de la <ulink type=\"ghelp\" url=\"gnome-help:gpl\">Licencia "
3601 "Pública General GNU</ulink> tal como la publica la Free Software Foundation; "
3602 "tanto en la versión 2 de la Licencia, o (a su opción) cualquier otra versión posterior."
3604 #: C/anjuta-manual.xml:10(para)
3606 "This program is distributed in the hope that it will be useful, but WITHOUT "
3607 "ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or "
3608 "FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public "
3609 "License</citetitle> for more details."
3611 "Este programa se distribuye con la esperanza de que le sea útil, pero SIN "
3612 "NINGUNA GARANTÍA; sin incluso la garantía implícita de MERCANTILIDAD o "
3613 "IDONEIDAD PARA UN PROPÓSITO PARTICULAR. Vea la <citetitle>Licencia Pública "
3614 "General GNU</citetitle> para más detalles."
3616 #: C/anjuta-manual.xml:16(para)
3618 "A copy of the <citetitle>GNU General Public License</citetitle> is included "
3619 "as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also "
3620 "obtain a copy of the <citetitle>GNU General Public License</citetitle> from "
3621 "the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://"
3622 "www.fsf.org\"> their Web site</ulink> or by writing to <address> Free "
3623 "Software Foundation, Inc. <street>51 Franklin Street</street> Fifth Floor "
3624 "<city>Boston</city>, <state>MA</state><postcode>02110-1301</"
3625 "postcode><country>USA</country></address>"
3627 "Una copia de la <citetitle>Licencia Pública General GNU</citetitle> está incluida"
3628 "como un apéndice de la <citetitle>Guía del usuario de GNOME</citetitle>. También puede "
3629 "obtener una copia de la <citetitle>Licencia Pública General GNU</citetitle> a través de la "
3630 "Free Software Foundation visitando <ulink type=\"http\" url=\"http://"
3631 "www.fsf.org\">su página web</ulink> o escribiendo a la <address> Free "
3632 "Software Foundation, Inc. <street>51 Franklin Street</street> Fifth Floor "
3633 "<city>Boston</city>, <state>MA</state><postcode>02110-1301</"
3634 "postcode><country>EE. UU.</country></address>"
3636 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
3637 #: C/anjuta-manual.xml:0(None)
3638 msgid "translator-credits"
3639 msgstr "Jorge González <jorgegonz@svn.gnome.org>, 2007"