1 # translation of anjuta.help.HEAD.po to Español
2 # Jorge González <jorgegonz@svn.gnome.org>, 2007.
5 "Project-Id-Version: anjuta.help.HEAD\n"
6 "POT-Creation-Date: 2007-12-16 12:55+0000\n"
7 "PO-Revision-Date: 2007-12-30 01:43+0100\n"
8 "Last-Translator: Jorge González <jorgegonz@svn.gnome.org>\n"
9 "Language-Team: Español <<gnome-es-list@gnome.org>\n"
11 "Content-Type: text/plain; charset=UTF-8\n"
12 "Content-Transfer-Encoding: 8bit\n"
13 "X-Generator: KBabel 1.11.4\n"
14 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
16 #: C/anjuta-manual.xml:25(title)
17 msgid "Anjuta IDE Manual"
18 msgstr "Manual para el EID Anjuta"
20 #: C/anjuta-manual.xml:26(edition)
24 #: C/anjuta-manual.xml:28(para)
25 msgid "Manual for the Anjuta IDE"
26 msgstr "Manual para el EID Anjuta"
28 #: C/anjuta-manual.xml:32(firstname)
32 #: C/anjuta-manual.xml:33(surname)
36 #: C/anjuta-manual.xml:36(firstname)
40 #: C/anjuta-manual.xml:37(surname)
44 #: C/anjuta-manual.xml:40(firstname)
48 #: C/anjuta-manual.xml:41(surname)
49 msgid "Chattopadhyayr"
50 msgstr "Chattopadhyayr"
52 #: C/anjuta-manual.xml:44(firstname)
56 #: C/anjuta-manual.xml:45(surname)
60 #: C/anjuta-manual.xml:49(year)
64 #: C/anjuta-manual.xml:50(year)
68 #: C/anjuta-manual.xml:51(holder)
69 msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
70 msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
72 #: C/anjuta-manual.xml:52(holder)
73 msgid "Johannes Schmid"
74 msgstr "Johannes Schmid"
76 #: C/anjuta-manual.xml:56(para)
78 "Permission is granted to copy, distribute and/or modify this document under "
79 "the terms of the <citetitle>GNU Free Documentation License</citetitle>, "
80 "Version 1.1 or any later version published by the Free Software Foundation "
81 "with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. "
82 "You may obtain a copy of the <citetitle>GNU Free Documentation License</"
83 "citetitle> from the Free Software Foundation by visiting <ulink type=\"http"
84 "\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to: Free "
85 "Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-"
89 #: C/anjuta-manual.xml:68(para)
91 "Many of the names used by companies to distinguish their products and "
92 "services are claimed as trademarks. Where those names appear in any GNOME "
93 "documentation, and those trademarks are made aware to the members of the "
94 "GNOME Documentation Project, the names have been printed in caps or initial "
97 "Muchos de los nombres usados por compañías para distinguir sus productos y "
98 "servicios se mencionan como marcas comerciales. Donde aparezcan dichos "
99 "nombres en cualquier documentación GNOME, y para que los miembros del "
100 "proyecto de documentación las reconozcan dichas marcas comerciales, dichos "
101 "nombres se imprimen en mayúsculas o iniciales mayúsculas."
103 #: C/anjuta-manual.xml:79(revnumber)
104 msgid "Anjuta Manual 2.1.0"
105 msgstr "Manual de Anjuta 2.1.0"
107 #: C/anjuta-manual.xml:80(date)
111 #: C/anjuta-manual.xml:82(para)
112 msgid "Johannes Schmid<email>jhs@gnome.org</email>"
113 msgstr "Johannes Schmid<email>jhs@gnome.org</email>"
115 #: C/anjuta-manual.xml:84(para)
117 msgstr "Equipo de Anjuta"
119 #: C/anjuta-manual.xml:3(title) C/anjuta-manual.xml:6(title)
121 msgstr "Introducción"
123 #: C/anjuta-manual.xml:4(para)
125 "<application>Anjuta</application> is a versatile Integrated Development "
126 "Environment (IDE) for the GNOME desktop. It features a number of advanced "
127 "programming facilities that include project management, application wizards, "
128 "an on-board interactive debugger, an integrated glade UI designer, "
129 "integrated devhelp API help, an integrated valgrind memory profiler, an "
130 "integrated gprof performance profiler, a class generator, a powerful source "
131 "editor, source browsing, and more. is a versatile Integrated Development "
134 "<application>Anjuta</application> es un Editor Integrado de Desarrollo (EID) "
135 "versátil para el escritorio GNOME. Tiene ciertas características para "
136 "facilitar la programación que incluyen gestión de proyectos, asistentes de "
137 "aplicación, un depurador integrado intergrado, un diseñador de IU Glade "
138 "integrado, una ayuda API de devhelp integrada, un perfilador de memoria "
139 "valgrind integrado, un perfilador de rendimiento grpof integrado, un "
140 "generador de clases, un potente editor de código fuente, búsqueda de fuentes "
143 #: C/anjuta-manual.xml:15(para)
145 "Anjuta DevStudio has been designed to be simple to operate yet powerful "
146 "enough to fullfil all your programming needs. Many features have evolved "
147 "since the early days and several very attractive ones added. Our focus is on "
148 "delivering power and usability at the same time without overloading your "
149 "senses and making your software development a pleasurable process. We will "
150 "always be busy getting you one of the best IDE experiences by straighting up "
151 "all the neat features and stablizing it. We hope you will have a good time "
152 "using Anjuta. If not, please help us make it better by reporting bugs and "
153 "suggestions. Here are some of the things you will find in Anjuta."
156 #: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
157 msgid "Anjuta in action"
158 msgstr "Anjuta en acción"
160 #: C/anjuta-manual.xml:37(para)
162 "Anjuta has a very flexible and advanced docking system that allows you to "
163 "layout all views in whatever way you like. You can drag and drop the views "
164 "using drag bars and re-arrange the layout. The layouts are persistent for "
165 "each project so you can maintain different layouts required by projects. All "
166 "dock views are minimizable to avoid clutter in main window. Minimized views "
167 "appear as icons on left side of main window. All menu actions are "
168 "configurable either by type-in-the-menu (the usual GNOME way) or by a "
169 "dedicated shortcuts configuration UI."
172 #: C/anjuta-manual.xml:48(para)
174 "Please report any problems with <application>Anjuta</application> - this "
175 "will help to improve the software, as well as helping the Open Source "
178 "Por favor, informe de cualquier problema con <application>Anjuta</"
179 "application>: esto ayudará a mejorar el software así como ayuda a la "
180 "comunidad código abierto («Open Source»)."
182 #: C/anjuta-manual.xml:2(title)
183 msgid "Getting Familiar with Anjuta"
184 msgstr "Familiarizarse con Anjuta"
186 #: C/anjuta-manual.xml:5(title)
187 msgid "Menus and shortcuts"
188 msgstr "Menús y atajos de teclado"
190 #: C/anjuta-manual.xml:6(para)
192 "At the top of the <application>Anjuta</application> main window is the "
193 "menubar. Almost all of the functions are available by activating the "
194 "appropriate menu item. The functions have been grouped according to their "
195 "type. For example, the file operations have been grouped into the "
196 "<guisubmenu>File</guisubmenu> menu."
198 "En la parte superior de la ventana principal de <application>Anjuta</"
199 "application> está la barra de menú. Casi todas las funciones están "
200 "disponibles al activar el elemento del menú apropiado. Las funciones se han "
201 "agrupado de acuerdo con su tipo. Por ejemplo, las operaciones con archivos "
202 "se han agrupado dentro del menú <guisubmenu>Archivo</guisubmenu>."
204 #: C/anjuta-manual.xml:15(title)
206 msgstr "Barra de menú"
208 #: C/anjuta-manual.xml:17(screeninfo)
209 msgid "Anjuta menubar"
210 msgstr "Barra de menú de Anjuta"
212 #: C/anjuta-manual.xml:22(para)
214 "Most of the menus and submenus can be detached. Click on the detach bar (the "
215 "dashed line just above the first menu item). Once the menu is detached, it "
216 "will become an independent window."
218 "La mayoría de los menús y submenús se pueden desacoplar. Pulse en la barra "
219 "de desacoplamiento (la línea en puntos suspensivos justo encima del primer "
220 "elemento del menú). Una vez que el menú está desacoplado, será una ventana "
223 #: C/anjuta-manual.xml:29(title) C/anjuta-manual.xml:31(screeninfo)
225 msgstr "Menú Archivo"
227 #: C/anjuta-manual.xml:36(para)
229 "Shortcut keys are available for many of the menu options. All of the "
230 "shortcut keys are shown alongside the corresponding menu items. A useful "
231 "reference to the shortcut keys which are not directly attachted with the "
232 "menu is also available in the next section. Some useful shortcuts are listed "
235 "Las teclas rápidas, o aceleradores de teclado, están disponibles para muchas "
236 "de las opciones de los menús. Todas las teclas rápidas se muestran junto con "
237 "los elementos del menú correspondientes. También hay una referencia útil "
238 "acerca de las teclas rápidas que no están directamente adjuntas a los menús "
239 "en la siguiente sección. A continuación se listan algunas teclas rápidas "
242 #: C/anjuta-manual.xml:46(para)
244 "<emphasis>Switch Editor page:</emphasis> CTRL-TAB (forward) and CTRL-SHIFT-"
245 "TAB (backward) -- The pages could also be switched by right clicking on the "
246 "notebook tabs and selecting an editor tab (useful when all the tabs in the "
247 "editor are not visible at once). Some desktop configuration may already have "
248 "these shortcut keys assigned. In that case, you will need to reconfigure "
249 "them (not in anjuta, because they are fixed) if you want to avail these "
253 #: C/anjuta-manual.xml:55(para)
255 "<emphasis>Context Help:</emphasis> SHIFT-F1 -- Keep the cursor on the word "
256 "(for example, the function name) for which you want to get the API help and "
257 "press the shortcut. Context help only works if you have "
258 "<application>DevHelp</application> installed. If you do not have "
259 "<application>DevHelp</application> installed, the context help menu and "
260 "toolbar button will be inactive. You can get it from <application>DevHelp</"
261 "application> website. You will also have to install the related "
262 "<application>DevHelp</application> books."
265 #: C/anjuta-manual.xml:65(para)
267 "<emphasis>Auto complete:</emphasis> CTRL-ENTER -- Press the shortcut with "
268 "the cursor placed at the end of incomplete word and a list of words matching "
269 "the remaining part will appear. Scroll and select the right word from the "
270 "list if you find one."
272 "<emphasis>Autocompletar:</emphasis> Ctrl+Intro; pulse la combinación de "
273 "teclas con el cursor ubicado al final de una palabra incompleta y se "
274 "mostrará una lista de palabras que coincidan con la parte restante. Desplace "
275 "la lista y seleccione la palabra correcta de la lista, si encuentra una."
277 #: C/anjuta-manual.xml:72(para)
279 "<emphasis>More shortcus:</emphasis> Look for the shortcut keys displayed on "
280 "right side of the menu item labels. They could also be changed as explained "
283 "<emphasis>Más teclas rápidas:</emphasis> Consulte las teclas rápidas "
284 "mostradas en la parte derecha de las etiquetas de los elementos del menú. "
285 "También se pueden cambiar como se explica en el siguiente consejo."
287 #: C/anjuta-manual.xml:79(title)
288 msgid "Customize shortcuts"
289 msgstr "Personalizar los atajos de teclado"
291 #: C/anjuta-manual.xml:80(para)
293 "You can change the default shortcuts by using "
294 "<menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Customize "
295 "shortcuts</guimenuitem></menuchoice>."
297 "Puede cambiar las combinaciones de teclas predeterminadas usando "
298 "<menuchoice><guisubmenu>Ajustes</guisubmenu><guimenuitem>Personalizar las "
299 "teclas rápidas</guimenuitem></menuchoice>."
301 #: C/anjuta-manual.xml:90(title)
303 msgstr "Ventana principal"
305 #: C/anjuta-manual.xml:91(para)
307 "In the main window, there are several views which can be reordered by "
308 "dragging on their title bars. They can also be minimized by clicking on the "
309 "minimize buttons on the left of title bars."
311 "En la ventana principal hay varias vistas que se pueden reordenar soltando "
312 "sus barras de título. También se pueden minimizar pulsando en los botones de "
313 "minimizar en la parte izquierda de las barras de título."
315 #: C/anjuta-manual.xml:100(para)
317 "The <interface>Documents window</interface> will have one document active at "
318 "a time (if there are any files opened). All of the file commands will apply "
319 "to this active document. You can switch to any page by clicking on the page "
320 "tab. You can do the same by right-clicking on the page tabs and choosing the "
321 "document from the pop-up menu that will appear. This is especially useful "
322 "when you have a lot of files opened, but not all of them are visible in the "
326 #: C/anjuta-manual.xml:111(para)
328 "The <interface>Project window</interface> shows a tree of the project files "
329 "if you have a project opened. Otherwise, the <interface>Project window</"
330 "interface> is usually hidden. Double-clicking on any item in the "
331 "<interface>Project window</interface> will open that file."
334 #: C/anjuta-manual.xml:119(para)
336 "The <interface>Files window</interface> shows a file tree. If no project is "
337 "open, the file tree usually points to the file system root but you can "
338 "change it in the preferences. If a project is open it shows all files inside "
339 "the project. Double clicking opens a file in the appropriate application as "
340 "configured in the gnome mime preferences. Richt click opens a popup-menu "
341 "which gives you choices how to open the file."
344 #: C/anjuta-manual.xml:128(para)
346 "The <interface>Symbols window</interface> shows shows a tree of availible "
347 "symbols in the project generated from ctags parser. Double clicking opens an "
348 "editor window with the corresponding file and line."
350 "La <interface>ventana de símbolos</interface> muestra un árbol con los "
351 "símbolos disponibles en el proyecto generados desde el analizador ctags. Al "
352 "pulsar dos veces se abre una ventana del editor con el archivo y líneas "
355 #: C/anjuta-manual.xml:133(para)
357 "There is also a <interface>Search tab</interface> in the Symbols window "
358 "where you can search for symbols."
360 "También existe una <interface>Barra de búsqueda</interface> en la ventana "
361 "Símbolos en la que puede buscar símbolos."
363 #: C/anjuta-manual.xml:139(para)
365 "The <interface>Message window</interface> will list all the messages (both "
366 "<filename>stdout</filename> and <filename>stderr</filename> outputs) when an "
367 "external command is executed. The <interface>Message window</interface> is "
368 "usually hidden, but appears as soon as an external command is executed, such "
369 "as during file or project compilation, debugging sessions, searches, and "
370 "many other operations. <application>Anjuta</application> also adds its own "
371 "messages here when necessary."
374 #: C/anjuta-manual.xml:147(para)
376 "The colors used to display the messages are important. Messages displayed in "
377 "the standard foreground color (usually Black) are normal messages. Those "
378 "displayed in Blue are important messages such as errors or other "
379 "information. Messages shown in Red are <emphasis>Hot Linked</emphasis>. "
380 "Double-clicking on such a message will take you to the particular file and "
381 "line number specified in the message."
384 #: C/anjuta-manual.xml:155(para)
386 "For example, when you compile a file which contains bugs, some red messages "
387 "will appear showing what the problems are, and where they occur. Double-"
388 "clicking on such messages will open the file and highlight the line "
389 "containing the error."
391 "Por ejemplo, cuando compila un archivo que contiene errores aparecerán "
392 "algunos mensajes en rojo mostrando los problemas y dónde ocurren. Al pulsar "
393 "dos veces sobre dichos mensajes se abrirá el archivo y se resaltará la línea "
394 "que contiene el error."
396 #: C/anjuta-manual.xml:163(para)
398 "The <interface>Terminal window</interface> is a terminal emulation where you "
399 "can type commands just like in the gnome-terminal."
401 "La <interface>Ventana del terminal</interface> es una emulación de un "
402 "terminal donde puede ejecutar comandos igual que en gnome-terminal."
404 #: C/anjuta-manual.xml:171(title)
405 msgid "Session management"
406 msgstr "Gestión de sesiones"
408 #: C/anjuta-manual.xml:172(para)
410 "All of the settings, including the window sizes and window positions, are "
411 "saved when you exit <application>Anjuta</application>. Session management is "
412 "still under development, so you should not exit <application>Anjuta</"
413 "application> with any unsaved documents. <application>Anjuta</application> "
414 "will display a warning if you try to exit with unsaved documents still open."
416 "Todos los ajustes, incluyendo los tamaños y posiciones de las ventanas, se "
417 "guardan al salir de <application>Anjuta</application>. La gestión de las "
418 "sesiones aún está bajo desarrollo, así que no debería salir de "
419 "<application>Anjuta</application> sin haber guardado antes sus documentos. "
420 "<application>Anjuta</application> mostrará una advertencia si intenta salir "
421 "con documentos sin guardar abiertos."
423 #: C/anjuta-manual.xml:2(title)
424 msgid "File Operations"
425 msgstr "Operaciones con archivos"
427 #: C/anjuta-manual.xml:6(title)
428 msgid "Creating a New File and inserting texts"
429 msgstr "Crear un archivo nuevo e insertar texto"
431 #: C/anjuta-manual.xml:8(title)
432 msgid "Creating New File"
433 msgstr "Crear un archivo nuevo"
435 #: C/anjuta-manual.xml:9(para)
437 "To create a new file, choose <menuchoice><guisubmenu>File</"
438 "guisubmenu><guimenuitem>New</guimenuitem></menuchoice> from the menubar, or "
439 "click on the <guibutton>New File</guibutton> button on the toolbar. A new "
440 "page will appear in the editor (or a new window if the parent document is "
441 "windowed). This new document will be named <filename>newfile#1</filename>, "
442 "<filename>newfile#2</filename>, <filename>newfile#3</filename> and so on."
444 "Para crear un archivo nuevo, elija <menuchoice><guisubmenu>Archivo</"
445 "guisubmenu><guimenuitem>Nuevo</guimenuitem></menuchoice> de la barra de menú "
446 "o pulse el botón <guibutton>Archivo nuevo</guibutton> en la barra de "
447 "herramientas. Se abrirá una nueva página en el editor (o una nueva ventana "
448 "si el documento padre está en una ventana). Este nuevo documento se llamará "
449 "<filename>newfile#1</filename>, <filename>newfile#2</filename>, "
450 "<filename>newfile#3</filename> y demás."
452 #: C/anjuta-manual.xml:19(title)
454 msgstr "Guardar archivo"
456 #: C/anjuta-manual.xml:20(para)
458 "You should save new documents as soon as possible to avoid any data loss in "
461 "Debería guardar sus documentos nuevos tan pronto como le sea posible para "
462 "evitar cualquier pérdida de datos en caso de cuelgue."
464 #: C/anjuta-manual.xml:27(title)
466 msgstr "Asistente de archivos"
468 #: C/anjuta-manual.xml:38(title)
469 msgid "New File Wizard"
470 msgstr "Nuevo asistente de archivos"
472 #: C/anjuta-manual.xml:40(screeninfo) C/anjuta-manual.xml:153(screeninfo)
473 msgid "The Open File dialog"
474 msgstr "El diálogo Abrir archivo"
476 #: C/anjuta-manual.xml:28(para)
478 "A wizard can also be used to create a new file.To create a new file, choose "
479 "<menuchoice><guisubmenu>File</guisubmenu><guisubmenu>New</"
480 "guisubmenu><guimenuitem>File</guimenuitem></menuchoice> from the menubar. "
481 "This will open the New File Wizard dialog. Select the file type. Enter the "
482 "File name. The suffix will be automatically added. You can add a license "
483 "information (according to your license choice) and a header. In case of C-C+"
484 "+ header file, you can also add an header template. Click <guibutton>OK</"
485 "guibutton> to validate the creation. <placeholder-1/>"
487 "También se puede usar un asistente para crear un archivo nuevo. Para crear "
488 "un archivo nuevo, elija <menuchoice><guisubmenu>Archivo</"
489 "guisubmenu><guisubmenu>Nuevo</guisubmenu><guimenuitem>Archivo</guimenuitem></"
490 "menuchoice> de la barra de menú. Esto abrirá el diálogo Archivo nuevo. "
491 "Seleccione el tipo de archivo. Introduzca el nombre del archivo. El sufijo "
492 "se añadirá automáticamente. Puede añadir información sobre la licencia (de "
493 "acuerdo con la licencia a su elección) y una cabecera. En caso de que sea "
494 "una cabecera C o C++, también puede añadir una plantilla de cabecera. Pulse "
495 "<guibutton>Aceptar</guibutton> para validar la creación. <placeholder-1/>"
497 #: C/anjuta-manual.xml:45(para)
499 "<application>Anjuta</application> occatinally also creates new files during "
500 "some operations. For example, some CVS operations, such as diff, file log, "
501 "file status etc, create new files and add the output there. These could be "
502 "saved in real file just like normal new files."
504 "<application>Anjuta</application> ocasionalmente crea nuevos archivos "
505 "durante algunas operaciones. Por ejemplo, algunas operaciones sobre CVS, "
506 "tales como diff, log de un archivo, status de un archivo, etc, crean "
507 "archivos nuevos y añaden la salida allí. Estos se pueden guardar en un "
508 "archivo real igual que los nuevos archivos normales."
510 #: C/anjuta-manual.xml:53(title)
511 msgid "Inserting Macros"
512 msgstr "Insertar macros"
514 #: C/anjuta-manual.xml:54(para)
515 msgid "Macros can be used to quickly edit repetitive sequences of text."
517 "Se pueden usar macros para editar rápidamente secuencias repetitivas de "
520 #: C/anjuta-manual.xml:58(para)
521 msgid "Macro plugin must be activated."
522 msgstr "El complemento de macros debe estar activado."
524 #: C/anjuta-manual.xml:63(title)
528 #: C/anjuta-manual.xml:64(para)
530 "Two types of macros are available: Anjuta macros and User macros (My "
531 "macros). Anjuta macros are not modifiable by the user. On the other hand, "
532 "User macros can be defined and modified by the user."
534 "Existen dos tipos de macros disponibles: Los macros de Anjuta y los macros "
535 "del usuario (Mis macros). Los macros de Anjuta no son modificables por el "
536 "usuario. Por otra parte, los macros del usuario se pueden definir y "
537 "modificar por el usuario."
539 #: C/anjuta-manual.xml:69(para)
541 "To insert macro, move the cursor at the desired place. Select "
542 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
543 "guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. The dialog "
544 "window appears. Select the wanted macro in the list. The result of the macro "
545 "expansion is displayed in the window and a summary is shown in the dialog "
546 "window. Choose <guibutton>Insert</guibutton>. The expanded macro text is "
547 "inserted at the cursor position."
549 "Para insertar una macro, mueva el cursor al lugar deseado. Seleccione "
550 "<menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</"
551 "guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. Aparecerá la "
552 "ventana de diálogo. Seleccione la macro deseada de la lista. El resultado de "
553 "la expansión de la macro se mostrará en la ventana así como un resumen en la "
554 "ventana de diálogo. Elija <guibutton>Insertar</guibutton>. Se insertará el "
555 "texto de la macro expandida en la posición del cursor."
557 #: C/anjuta-manual.xml:82(title)
561 #: C/anjuta-manual.xml:84(screeninfo)
562 msgid "The Macro dialog"
563 msgstr "El diálogo Macro"
565 #: C/anjuta-manual.xml:77(para)
567 "Another possibility to insert macro is to select "
568 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
569 "guisubmenu><guimenuitem>Insert Macro...</guimenuitem></menuchoice>, then to "
570 "press the wanted macro shortcut. <placeholder-1/>"
572 "Otra posibilidad para insertar un macro es seleecionar "
573 "<menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</"
574 "guisubmenu><guimenuitem>Insertar macro…</guimenuitem></menuchoice>, después "
575 "pulsar el atajo de teclado sobre el macro seleccionado. <placeholder-1/>"
577 #: C/anjuta-manual.xml:91(title)
578 msgid "Defining Macros"
579 msgstr "Definir macros"
581 #: C/anjuta-manual.xml:92(para)
583 "From the Insert-Macro window, choose <guibutton>Add</guibutton> or select "
584 "<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
585 "guisubmenu><guimenuitem>Add Macro... </guimenuitem></menuchoice>. The Add/"
586 "Edit window appears. Enter the macro name, choose or define a category and "
587 "enter a shortcut. Then edit text relative to your macro. The character ' | ' "
588 "will indicate the cursor position after the macro insertion. Choose "
589 "<guibutton>OK</guibutton>. The macro is added to the list."
591 "Desde la ventana de Insertar macro, elija <guibutton>Añadir</guibutton> o "
592 "seleccione <menuchoice><guisubmenu>Editar</guisubmenu><guisubmenu>Macros</"
593 "guisubmenu><guimenuitem>Añadir macro...</guimenuitem></menuchoice>. "
594 "Aparecerá la ventana de Añadir/editar. Introduzca el nombre de la macro, "
595 "elija o defina una categoría e introduzca un atajo. Después edite el texto "
596 "relativo a la macro. El carácter «|» indicará la posición del cursor después "
597 "de la inserción de la macro. Elija <guibutton>Aceptar</guibutton>. La macro "
598 "se añadirá a la lista."
600 #: C/anjuta-manual.xml:100(para)
602 "The user can also erase a macro by selecting it in the list (only My Macros) "
603 "then by choosing <guibutton>Remove</guibutton>."
605 "El usuario también puede borrar un macro seleccionándolo en la lista (sólo "
606 "Mis macros) y después eligiendo <guibutton>Eliminar</guibutton>."
608 #: C/anjuta-manual.xml:108(title)
609 msgid "Add/Edit Macro"
610 msgstr "Añadir/Editar macro"
612 #: C/anjuta-manual.xml:110(screeninfo)
613 msgid "Add Edit dialog"
614 msgstr "Diálogo Añadir/Editar"
616 #: C/anjuta-manual.xml:104(para)
618 "Same manner, macro can be edited and modified by selecting it in the list "
619 "then by choosing <guibutton>Edit</guibutton>. <placeholder-1/>"
621 "De la misma manera se puede editar un macro y modificarlo seleccionándolo en "
622 "la lista y después eligiendo <guibutton>Editar</guibutton>. <placeholder-1/>"
624 #: C/anjuta-manual.xml:117(title)
625 msgid "Macro Keywords"
626 msgstr "Palabras clave de los macros"
628 #: C/anjuta-manual.xml:118(para)
630 "Macros Keywords are available. They can be integrated in the macro "
631 "definitions. The names of these macro Keywords start and finish by the "
634 "Están disponibles las palabras clave para los macros. Pueden integrarse en "
635 "la definición del macro. Los nombres de estas palabras clave de los macros "
636 "comienzan y finalizan con el carácter «@»."
638 #: C/anjuta-manual.xml:126(title)
639 msgid "Keyword Macro"
640 msgstr "Palabra clave del macro"
642 #: C/anjuta-manual.xml:128(screeninfo)
643 msgid "The Keyword macro"
644 msgstr "La palabra clave del macro"
646 #: C/anjuta-manual.xml:122(para)
648 "Available macro keywords are : @DATE_TIME@, @DATE_YMD@, @DATE_Y@, "
649 "@USER_NAME@, @FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, "
650 "@TABSIZE@, @INDENTSIZE@, @USETABS@. <placeholder-1/>"
652 "Las palabras clave de macro disponibles son: @DATE_TIME@, @DATE_YMD@, "
653 "@DATE_Y@, @USER_NAME@, @FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, "
654 "@EMAIL@, @TABSIZE@, @INDENTSIZE@, @USETABS@. <placeholder-1/>"
656 #: C/anjuta-manual.xml:139(title)
657 msgid "Opening and Saving Files"
658 msgstr "Abrir y guardar archivos"
660 #: C/anjuta-manual.xml:151(title)
661 msgid "Open File dialog"
662 msgstr "Diálogo Abrir archivo"
664 #: C/anjuta-manual.xml:143(para)
666 "<emphasis>Opening a file:</emphasis> To open an existing file, choose "
667 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Open</guimenuitem></"
668 "menuchoice> from the menubar, click on the <guibutton>Open</guibutton> "
669 "button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>O</"
670 "keycap></keycombo>. This will display the <interface>Open File</interface> "
671 "dialog. <placeholder-1/> Select or enter the file you want to open, then "
672 "click <guibutton>Open</guibutton>. To open more than one file at once, "
673 "select multiple files to open by first pressing CTRL and clicking the files "
674 "in the list and press <guibutton>Open</guibutton>. If you change your mind, "
675 "click <guibutton>Cancel</guibutton> to dismiss the dialog without opening "
679 #: C/anjuta-manual.xml:172(title)
680 msgid "Open Multiple File dialog"
681 msgstr "Diálogo Abrir múltiples archivos"
683 #: C/anjuta-manual.xml:174(screeninfo)
684 msgid "The Open File dialog in multiple-select mode"
685 msgstr "El diálogo Abrir archivo en el modo de múltiple selección"
687 #: C/anjuta-manual.xml:164(para)
689 "For selecting multiple files at once, select a file in the dialog and press "
690 "CTRL once. This will bring the file selection dialog in multiple-select mode "
691 "and multiple files could be selected from the list. Multiple file select "
692 "mode is simlar to single file select mode, except that the file operation "
693 "(for which the file selection was being done) will be performed for all the "
694 "selected files. <placeholder-1/>"
697 #: C/anjuta-manual.xml:179(para)
699 "The <emphasis>Show Hidden</emphasis>, if switched on (Click right), will "
700 "make the hidden files (files starting with \".\"; visible in the file list. "
701 "Depress it to make them hide. <application>Anjuta</application> "
702 "fileselection dialog also has inbuild file type filter. Select the "
703 "appropiate file type filter in the dialog and the file list will be limited "
704 "to the files of the selected type only."
707 #: C/anjuta-manual.xml:199(screeninfo)
708 msgid "The Save As File"
709 msgstr "Guardar como archivo"
711 #: C/anjuta-manual.xml:189(para)
713 "<emphasis>Saving a file:</emphasis> To save a file, choose "
714 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save</guimenuitem></"
715 "menuchoice> from the menubar, click on the <guibutton>Save</guibutton> "
716 "button on the toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>S</"
717 "keycap></keycombo>. This will save the file. If the file is new, a "
718 "<interface>Save As</interface> dialog will appear. Enter a filename and "
719 "click <guibutton>Save</guibutton> to save the new file with the name "
720 "supplied. <placeholder-1/>"
723 #: C/anjuta-manual.xml:204(title)
724 msgid "File auto save"
725 msgstr "Autoguardar archivos"
727 #: C/anjuta-manual.xml:205(para)
729 "If you have enabled auto-save, it will not auto-save any new files. You must "
730 "first save them manually. The same applies to the <guimenuitem>Save All</"
731 "guimenuitem> option: it will not save new files, if you haven't saved them "
732 "first manually. <emphasis>You must save a file manually before auto-save or "
733 "<guimenuitem>Save All</guimenuitem> will work with it.</emphasis>"
736 #: C/anjuta-manual.xml:216(para)
738 "<emphasis>Saving a file with a different name:</emphasis> You can explicitly "
739 "save a file with a new filename. To do this, choose "
740 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save As</guimenuitem></"
741 "menuchoice> from the menubar. A <interface>Save As</interface> dialog will "
742 "appear prompting you to enter the new filename. Enter the name and click "
743 "<guibutton>Save</guibutton>."
746 #: C/anjuta-manual.xml:224(title)
747 msgid "File save as overwrite"
748 msgstr "Sobreescribir archivo al guardar"
750 #: C/anjuta-manual.xml:225(para)
752 "When you use <guimenuitem>Save As</guimenuitem> with an existing file, the "
753 "original is not deleted. It is left unchanged since the last save. If a file "
754 "with the new filename already exists, a confirmation dialog will appear, to "
755 "ensure that you want to overwrite it. Clicking <guibutton>Yes</guibutton> "
756 "will overwrite the file with the file you are saving."
759 #: C/anjuta-manual.xml:237(para)
761 "<emphasis>Closing a file:</emphasis> To close a file, choose "
762 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Close</guimenuitem></"
763 "menuchoice> from the menubar, or click on the <guibutton>Close</guibutton> "
764 "button on the toolbar. The file could also be closed by clicking the "
765 "<guibutton>cross</guibutton> in the filename tab. This will close the "
766 "current file. If the file is not saved, or is a new file, then "
767 "<application>Anjuta</application> will prompt you to save the file before "
771 #: C/anjuta-manual.xml:254(title)
772 msgid "Editing Files"
773 msgstr "Editar archivos"
775 #: C/anjuta-manual.xml:255(para)
777 "<application>Anjuta</application> has a number of helpful features which aid "
778 "in editing and working with source files. The following sections describe "
779 "how to use some of the interesting features available."
781 "<application>Anjuta</application> posee cierto número de características de ayuda para "
782 "la edición y el trabajo con archivos de código fuente. Las siguientes secciones describen "
783 "cómo usar algunas de las interesantes características disponibles."
785 #: C/anjuta-manual.xml:261(title) C/anjuta-manual.xml:270(title)
786 msgid "Editor Margins"
787 msgstr "Márgenes del editor"
789 #: C/anjuta-manual.xml:272(screeninfo) C/anjuta-manual.xml:320(screeninfo)
790 #: C/anjuta-manual.xml:423(screeninfo)
791 msgid "The Tags toolbar"
792 msgstr "La barra de herramientas de etiquetas"
794 #: C/anjuta-manual.xml:262(para)
796 "<emphasis>Editor Margins:</emphasis> Editor margins are the small area on "
797 "the left of the editor for some special purposes. There are three editor "
798 "margins available and all of them may not be available when you first start "
799 "<application>anjuta</application>. They are Line numbers margin, Markers "
800 "margin and Code fold margin. By default (that is, when you run "
801 "<application>anjuta</application> for the first time) only the code fold "
802 "margin witll be visible. The rest could be made visible from "
803 "<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></"
804 "menuchoice>. <placeholder-1/>"
807 #: C/anjuta-manual.xml:277(para)
809 "The <emphasis>Line Numbers Margin</emphasis> is largest of all the three "
810 "margins (and slightly darker then rest) and displays the document's line "
811 "numbers. <emphasis>Line Number Margin</emphasis> could be made visible or "
812 "invisible by toggling <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
813 "guisubmenu><guimenuitem>Line Numbers Margin</guimenuitem></menuchoice>. "
814 "Single left clicking on this margin will select the whole line (including "
815 "the last newline, if present). You can set the font properties for line "
816 "number margin in the preferences."
819 #: C/anjuta-manual.xml:286(para)
821 "<emphasis>Markers Margin</emphasis> is the next margin which can be made "
822 "visible or invisible by selecting <menuchoice><guimenu>View</"
823 "guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Markers Margin</"
824 "guimenuitem></menuchoice>. This margin displays graphical icons to mark the "
825 "given line. The markers which will be displayed in this margin are Bookmark "
826 "marker (rectangular blue colored icon), Breakpoint marker (circular red "
827 "colored) and Line indicator (pointed arrow yellow colored). Bookmark marker "
828 "is used to indicate bookmaked lines which could be toggled from "
829 "<menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</"
830 "guisubmenu><guimenuitem> Toggle Bookmark</guimenuitem></menuchoice> with the "
831 "cursor placed in that line. The breakpoint marker is used in debugger to "
832 "mark the line with debugging breakpoints (see debugging section for more "
833 "details). The line indicator marker is used to indicate a line when we do a "
834 "jump from another part, for example when navigating the bookmarks and during "
835 "single stepping in debugger."
838 #: C/anjuta-manual.xml:299(para)
840 "<emphasis>Code folding margin</emphasis> is where the folding tree is "
841 "visisble. Clicking on these folding tree nodes will fold or unfold the code "
842 "blocks. An underline will also be drawn below the folded line to make it "
843 "more obvious that a block of code has been folded below the line. For more "
844 "details on code folding, see the section <emphasis>Code Folding</emphasis> "
848 #: C/anjuta-manual.xml:307(title)
849 msgid "Invisible margin marker"
850 msgstr "Marcador de márgenes invisibles"
852 #: C/anjuta-manual.xml:318(title)
853 msgid "Editor markes when markers margin is invisible"
854 msgstr "El editor marca cuando el margen del marcador es invisible"
856 #: C/anjuta-manual.xml:308(para)
858 "If the marker margin is not visible, the markers will be displayed by "
859 "changing the background color of the line. For example, if there a "
860 "breakpoint marker is set in a line and the marker margin is not visible, "
861 "that line will be displayed with red background. Similarly, for bookmark "
862 "marker and line indicatior marker, the background color of the line will be "
863 "sky blue and yellow, respectively. If you do not like this (perhaps due to "
864 "some contrasting themes), enable the <emphasis>Markers Margins</emphasis> "
865 "from <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
866 "guisubmenu><guimenuitem>Markers Margin</guimenuitem></menuchoice>. "
870 #: C/anjuta-manual.xml:328(title)
871 msgid "Editor Guides"
872 msgstr "Guías del editor"
874 #: C/anjuta-manual.xml:329(para)
876 "The editor could be made to make certain document information, which "
877 "otherwise are normally not visible. <emphasis>Indentation guides, white "
878 "spaces and line end characters</emphasis> are such information which could "
879 "be made visible for editing comfort. They could be make visible or invisible "
880 "by toggling the menu items in <menuchoice><guimenu>View</"
881 "guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. Indentation guides are "
882 "the small dotted lines drawn to connect the matching braces in the source "
883 "code. When the cursor is over one such maching braces, the dotted "
884 "indentation guide is highlighted to give a visual region of the indentation."
887 #: C/anjuta-manual.xml:339(title) C/anjuta-manual.xml:341(screeninfo)
888 msgid "Editor with guides"
889 msgstr "Editor con guías"
891 #: C/anjuta-manual.xml:347(title)
892 msgid "Syntax highlighting"
893 msgstr "Resaltado de sintaxis"
895 #: C/anjuta-manual.xml:348(para)
897 "<application>Anjuta</application> can highlight many different languages. "
898 "This is usually done automatically by determining the type of the file from "
899 "the file extension. If <application>Anjuta</application> cannot determine "
900 "the type of the file, there will be no syntax highlighting. You can "
901 "explicitly force a particular highlight style by selecting the style from "
902 "the menu <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
903 "guisubmenu><guisubmenu> Highlight Mode</guisubmenu></menuchoice>."
906 #: C/anjuta-manual.xml:359(title)
910 #: C/anjuta-manual.xml:360(para)
912 "Source files which have block coding properties (such as C, C++, Pascal, "
913 "Java etc.), have the advantage of working with <emphasis>code folds</"
914 "emphasis>. All of the code blocks in the source file can be folded or "
915 "unfolded by clicking on the fold points in the fold margin of the "
916 "<interface>Editor window</interface> (usually a +/- symbol or up/down "
917 "arrow). These fold points automatically appear for source files which use "
921 #: C/anjuta-manual.xml:368(para)
923 "Code folding is especially useful when editing big source files that run to "
924 "thousands of lines. Once the folds are closed, the document appears to "
925 "become smaller, facilitating easy browsing and editing of the file."
928 #: C/anjuta-manual.xml:374(para)
930 "Please note that code folding and editor guides are only avalible in the "
931 "scintilla based editor."
934 #: C/anjuta-manual.xml:381(title)
935 msgid "Auto-formatting source code"
936 msgstr "Autoformatear el código fuente"
938 #: C/anjuta-manual.xml:382(para)
940 "If the current file is a C or C++ source or header file, then it is possible "
941 "to automatically indent (auto-format) the file. This gives a clean look to "
942 "the source code, increases legibility, reduces the likelihood of syntax "
943 "errors, and above all it saves time. This can be performed by choosing "
944 "<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
945 "guisubmenu><guimenuitem>Auto-format </guimenuitem></menuchoice> on the "
946 "menubar. Change the style of formatting by customizing the choices in the "
950 #: C/anjuta-manual.xml:392(title)
954 #: C/anjuta-manual.xml:393(para)
956 "You will need to have the <application>indent</application> utility "
957 "installed in order to use this feature. Read the <ulink type=\"info\" url="
958 "\"info:indent\">info page for <application>indent</application></ulink> for "
961 "Para poder usar esta característica deberá tener instalada la utilidad ç "
962 "<application>indent</application>. Para obtener más detalles, lea la <ulink type=\"info\" url="
963 "\"info:indent\">página de ayuda para <application>indent</application></ulink>."
965 #: C/anjuta-manual.xml:404(title)
966 msgid "Symbol browser and Browsing Files"
967 msgstr "Examinador de símbolos y Examinador de archivos"
969 #: C/anjuta-manual.xml:405(para)
971 "All C and C++ source and header files can be browsed using the tags in the "
972 "files. All of the open C and C++ source and header files are scanned for "
973 "available tags (a \"tag\" refers to a function definition, structure, macro, "
974 "etc.). Please note that Tag and Symbol is used synonymously in this manual, "
975 "except when refering to Tags browser and Symbol browser, which two different "
979 #: C/anjuta-manual.xml:421(title) C/anjuta-manual.xml:444(title)
981 msgstr "Barra de herramientas de etiquetas"
983 #: C/anjuta-manual.xml:427(title)
984 msgid "Function symbols"
985 msgstr "Símbolos de funciones"
987 #: C/anjuta-manual.xml:428(para)
989 "Function prototype and definition, if present in the same file, can be "
990 "usually distinguished from the corrosponding line numbers. Prototypes "
991 "usually comes before the definition, so they are likely to have smaller line "
995 #: C/anjuta-manual.xml:414(para)
997 "<emphasis>Tags Browser:</emphasis> Tags browser is available on the Browser "
998 "toolbar. It shows a list of tags available in the currently active file "
999 "(souce file). If there is no tags (or sysmbols) available in the file, the "
1000 "tags list will be invisible and a \"No Tags\" will be displayed instead. The "
1001 "tags in this list are shown along with the line numbers where they are "
1002 "found. If there are multiple symbols with the same name, they will be shown "
1003 "with different line numbers. <placeholder-1/><placeholder-2/>"
1006 #: C/anjuta-manual.xml:446(screeninfo)
1007 msgid "Symbol browser"
1008 msgstr "Examinador de símbolos"
1010 #: C/anjuta-manual.xml:436(para)
1012 "<emphasis>Symbol Browser:</emphasis> If there is a project open, "
1013 "<application>Anjuta</application> will scan for tags in all of the source "
1014 "and header files of the project. This way it is possible to go to any "
1015 "function definition, structure definition, class definition etc. without "
1016 "manually opening the file. You don't even have to know which file that tag "
1017 "is found in (except in the case of function definitions). The symbol browser "
1018 "lists all the available symbols in the project. <placeholder-1/>"
1021 #: C/anjuta-manual.xml:454(title)
1022 msgid "Tags synchronization"
1023 msgstr "Sincronización de etiquetas"
1025 #: C/anjuta-manual.xml:455(para)
1027 "You don't have to worry about the synchronization and update of the tag "
1028 "database. <application>Anjuta</application> will take care of everything. "
1029 "You just have to decide which tag you want to go to!"
1032 #: C/anjuta-manual.xml:466(title)
1033 msgid "Searching for and Replacing text in files"
1036 #: C/anjuta-manual.xml:468(title)
1040 #: C/anjuta-manual.xml:469(para)
1042 "To search for a <emphasis>text</emphasis> or <emphasis>regular expression</"
1043 "emphasis> string in the current file, choose <menuchoice><guimenu>Edit</"
1044 "guimenu><guisubmenu>Search</guisubmenu><guimenuitem>Find</guimenuitem></"
1045 "menuchoice> or press <keycombo><keycap>Ctrl</keycap><keycap>F</keycap></"
1046 "keycombo>. This will open the <interface>Find</interface> dialog."
1049 #: C/anjuta-manual.xml:476(para)
1051 "Use the text box to specify the string to search for, and select whether it "
1052 "is a normal string or a regular expression (RegExp). It is also possible to "
1053 "specify the direction of search, whether the search is case-sensitive or "
1054 "not, and the scope of the search. Click <guibutton>Search</guibutton> to "
1058 #: C/anjuta-manual.xml:482(para)
1060 "If the search is successful, the matched text in the document will be "
1061 "highlighted, marked... (according to the search action choice). If the "
1062 "search is not successful, a <emphasis>match not found</emphasis> message "
1063 "will be displayed."
1066 #: C/anjuta-manual.xml:487(para)
1068 "If you want to search again, click on the <guibutton>Search</guibutton> "
1069 "button on the main toolbar or press <keycombo><keycap>Ctrl</"
1070 "keycap><keycap>G</keycap></keycombo>. This will find the next match "
1071 "(<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>G</keycap></"
1072 "keycombo> for the previous match). You can even change the search text when "
1073 "you do this. Enter the new string in the <guilabel>Search Expression</"
1074 "guilabel> text box in the main toolbar."
1077 #: C/anjuta-manual.xml:496(title)
1078 msgid "Search Text dialog"
1081 #: C/anjuta-manual.xml:501(para)
1082 msgid "To stop a long research, choose <guibutton>Stop</guibutton> button."
1085 #: C/anjuta-manual.xml:504(para)
1087 "If the \"Basic Search and Replace\" option is selected in the Setting "
1088 "window, the search direction can be choosen from the Expression window."
1091 #: C/anjuta-manual.xml:509(title)
1092 msgid "Basic Search Text dialog"
1095 #: C/anjuta-manual.xml:516(title)
1096 msgid "Specifying Search Range"
1099 #: C/anjuta-manual.xml:517(para)
1101 "In the \"Search Target dialog\", define the search location and the action "
1102 "to be done in case of search success."
1105 #: C/anjuta-manual.xml:521(para)
1106 msgid "The maximum number actions can be defined by User."
1109 #: C/anjuta-manual.xml:525(title)
1110 msgid "Search Target dialog"
1113 #: C/anjuta-manual.xml:530(para)
1114 msgid "The user can select where the text will be searched."
1117 #: C/anjuta-manual.xml:534(title)
1118 msgid "Search Target In choice"
1121 #: C/anjuta-manual.xml:540(title)
1122 msgid "Searching in Files"
1125 #: C/anjuta-manual.xml:541(para)
1127 "To find text in your project, select \"search in\" <menuchoice><guimenu> All "
1128 "Project Files</guimenu></menuchoice>."
1131 #: C/anjuta-manual.xml:545(para) C/anjuta-manual.xml:576(para)
1133 "Enter the text you want to search and specify search options (case-"
1134 "sensitive, complete words ...). Click <guibutton>Search</guibutton> to start "
1138 #: C/anjuta-manual.xml:550(para)
1140 "To find text in File list, select \"search in\" <menuchoice><guimenu> "
1141 "Specifying File List</guimenu></menuchoice>. Define the Search variables. "
1142 "Click <guibutton>Search</guibutton> to start searching."
1145 #: C/anjuta-manual.xml:557(title)
1146 msgid "Search File List"
1149 #: C/anjuta-manual.xml:565(title)
1150 msgid "Specifying File Patterns"
1153 #: C/anjuta-manual.xml:566(para)
1155 "To find in files and/or folders, select \"search in\" <menuchoice><guimenu> "
1156 "Specify File Patterns</guimenu></menuchoice>, choose the file types and/or "
1157 "folders you want to search."
1160 #: C/anjuta-manual.xml:571(para)
1162 "Remember, directories are searched recursively. All of the files under the "
1163 "directory, and the files under all the subdirectories, and the files under "
1164 "all of the sub-subdirectories (and so on) are all included in the search."
1167 #: C/anjuta-manual.xml:582(title)
1168 msgid "Search File Pattern"
1171 #: C/anjuta-manual.xml:592(title)
1172 msgid "Specifying Search Action"
1175 #: C/anjuta-manual.xml:593(para)
1176 msgid "The user selects which action will be done in case of search success."
1179 #: C/anjuta-manual.xml:596(para)
1181 "According to the previous selections (Search in, Search direction ...), some "
1182 "actions coul be unavailable."
1185 #: C/anjuta-manual.xml:601(title)
1186 msgid "Search Target Action choice"
1189 #: C/anjuta-manual.xml:609(title) C/anjuta-manual.xml:617(title)
1191 msgstr "Reemplazando"
1193 #: C/anjuta-manual.xml:610(para)
1195 "Search and replace is similar to just finding text, except that you also "
1196 "specify the replace text in the <guilabel>Replace Text</guilabel> text box, "
1197 "and whether or not you want to be prompted before the replace takes place "
1198 "(Replace First Match or Replace All Matches)."
1201 #: C/anjuta-manual.xml:622(para)
1203 "Choose <guibutton>Replace</guibutton> to replace the matched text or "
1204 "<guibutton>Forward</guibutton> to jump to the next matched text."
1207 #: C/anjuta-manual.xml:629(title)
1208 msgid "Search Setting"
1211 #: C/anjuta-manual.xml:630(para)
1212 msgid "The user has the possibility of saving the setting of his search options."
1215 #: C/anjuta-manual.xml:633(para)
1217 "Item highlighted in red is the active item. Item by defaultt is the search "
1218 "setting which is loaded at Anjuta launching."
1221 #: C/anjuta-manual.xml:638(title)
1222 msgid "Search Setting dialog"
1225 #: C/anjuta-manual.xml:649(title)
1226 msgid "Printing a file"
1229 #: C/anjuta-manual.xml:659(title)
1230 msgid "Print preview of a C file"
1233 #: C/anjuta-manual.xml:661(screeninfo)
1234 msgid "Print preview"
1235 msgstr "Vista preliminar de impresión"
1237 #: C/anjuta-manual.xml:650(para)
1239 "Print preview could be taken by selecting <menuchoice><guisubmenu>File</"
1240 "guisubmenu><guimenuitem>Print Preview</guimenuitem></menuchoice>. It will "
1241 "render the current file and present a preview of the print. Source codes "
1242 "which are hilighted in the editor are also highlighted similarly in the "
1243 "print (or preview). Addtional options are available to print with the line "
1244 "numbers, wrapped lines and/or headers in the Editor printing preferences "
1245 "from <menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Preferences. "
1246 "</guimenuitem></menuchoice><placeholder-1/>"
1249 #: C/anjuta-manual.xml:668(title)
1250 msgid "Print Preferences"
1253 #: C/anjuta-manual.xml:670(screeninfo)
1254 msgid "Print preferences"
1257 #: C/anjuta-manual.xml:675(para)
1259 "When you are ready to print and satisfied with the preview, select "
1260 "<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print</guimenuitem></"
1261 "menuchoice> or <guibutton>Print</guibutton> from the print preview window. "
1262 "This will bring up the actual print dialog as shown below. Select the "
1263 "appropriate print parameters and print the file with <guibutton>Print</"
1267 #: C/anjuta-manual.xml:687(title)
1268 msgid "Print Dialog"
1269 msgstr "Diálogo de impresión"
1271 #: C/anjuta-manual.xml:689(screeninfo)
1272 msgid "Print dialog"
1275 #: C/anjuta-manual.xml:682(para)
1277 "Landscaped or portrait page layout, paper size, page orientation and paper "
1278 "type could also be set. Remember to set them up properly according to your "
1279 "printer, otherwise printing may not come up properly. <placeholder-1/>"
1282 #: C/anjuta-manual.xml:3(title)
1283 msgid "Project Management"
1284 msgstr "Gestión de proyectos"
1286 #: C/anjuta-manual.xml:5(para)
1288 "Anjuta has a powerful Project Manager plugin which can open most <ulink type="
1289 "\"info\" url=\"info:automake\">automake/autoconf</ulink> based projects. It "
1290 "might fail on some oddly configured projects, but as long as the project is "
1291 "done by using automake/autoconf in a typical way, it should work."
1294 #: C/anjuta-manual.xml:13(para)
1296 "The neat thing is that it does not store any project information beyond what "
1297 "is already available in project struture. That is, there is no separate "
1298 "project data maintained by Anjuta and all project processing are done "
1299 "directly within the project structure. This allows the project to be "
1300 "maintained or developed outside Anjuta without having to so-called 'porting' "
1301 "or 'switching' to a new platform. Since technically Anjuta projects are just "
1302 "automake projects, mixed development of it (Anjuta and non-Anjuta users) or "
1303 "switching back and forth between Anjuta and other tools is quite possible "
1304 "without any hindrance."
1307 #: C/anjuta-manual.xml:26(title)
1308 msgid "Creating a New Project"
1309 msgstr "Crear un proyecto nuevo"
1311 #: C/anjuta-manual.xml:28(title)
1312 msgid "New project from template"
1315 #: C/anjuta-manual.xml:29(para)
1317 "The project wizard plugin uses a powerful template processing engine called "
1318 "<application>autogen</application>. All new projects are created from "
1319 "templates that are written in <application>autogen</application> syntax. "
1320 "Project wizard lets you create new projects from a selection of project "
1321 "templates. The selection includes simple generic, flat (no subdirectory), gtk"
1322 "+, gnome, java, python projects and more. New templates can be easily "
1323 "downloaded and installed since they are just a collection of text files."
1326 #: C/anjuta-manual.xml:41(para)
1328 "Choose the menu item <menuchoice><guisubmenu>File</"
1329 "guisubmenu><guisubmenu>New</guisubmenu><guimenuitem>Project …</guimenuitem></"
1330 "menuchoice> to start the application wizard. Read the <interface>first page</"
1331 "interface> carefully. Click on <guibutton>Next</guibutton> to proceed."
1334 #: C/anjuta-manual.xml:48(para)
1336 "Select the type of application you want to create in the <interface>second "
1337 "page</interface>. Click on <guibutton>Next</guibutton> to proceed."
1340 #: C/anjuta-manual.xml:54(para)
1342 "On the next pages, enter all necessary details for your project. You can "
1343 "change these settings later also, but it is advicable to put them right in "
1344 "first run to maintain the project's integrity. White spaces or any non-"
1345 "alphanumeric characters, except underscore (_) and dash (-), are not allowed "
1346 "in many of the entry boxes that would follow (except perhaps the "
1347 "<guilabel>Author</guilabel> text box)."
1350 #: C/anjuta-manual.xml:65(para)
1352 "You can also specify whether your project will have "
1353 "<emphasis>internationalization support</emphasis> using "
1354 "<application>gettext</application> (read the <ulink type=\"info\" url=\"info:"
1355 "gettext\">gettext info page</ulink> for more details). This gives your "
1356 "project multilingual support for different regional languages such as "
1357 "English, French, Dutch etc.. The rest of the options are for setting whether "
1358 "the GNU copyright statement should appear in the comments at the top of each "
1359 "file, and enabling GNOME desktop menu information if necessary. Shared "
1360 "library support allows adding shared library modules later in the project. "
1361 "If you plan to have libraries in your project, it would be good to enable. "
1362 "Depending on the project type that is being created, there would be other "
1363 "information requested."
1366 #: C/anjuta-manual.xml:81(para)
1368 "The final step is to verify the information you have just supplied. Click on "
1369 "<guibutton>Finish</guibutton> to start generating the project."
1372 #: C/anjuta-manual.xml:86(para)
1374 "Once project generation is over, you can try it out by building the project "
1378 #: C/anjuta-manual.xml:92(title)
1379 msgid "Importing Projects"
1382 #: C/anjuta-manual.xml:93(para)
1384 "The import project feature is used to import an already existing project and "
1385 "convert it into <application>anjuta</application> projcect. Activate the "
1386 "import project wizard from <menuchoice><guimenu>File</guimenu><guimenu>New</"
1387 "guimenu><guimenuitem>Project from existing sources</guimenuitem></"
1388 "menuchoice> and follow instructions dictated by the wizard. Once the project "
1389 "is imported, it could be opened in <application>anjuta</application> "
1390 "subsequently just like any other <application> anjuta</application> project."
1393 #: C/anjuta-manual.xml:103(para)
1395 "The import project features only works if your existing project is using "
1396 "<ulink type=\"info\" url=\"info:automake\">autoconf/automake</ulink> and, to "
1397 "a very limited extend, plain makefiles."
1400 #: C/anjuta-manual.xml:113(title)
1401 msgid "Loading and Saving Projects"
1404 #: C/anjuta-manual.xml:115(title)
1405 msgid "Loading Projects"
1408 #: C/anjuta-manual.xml:116(para)
1410 "To open a project, choose the menu item <menuchoice><guisubmenu>File</"
1411 "guisubmenu><guimenuitem>Open …</guimenuitem></menuchoice>. Select the "
1412 "project file (<filename>*.anjuta</filename>) in the dialog and click "
1413 "<guibutton>OK</guibutton>."
1416 #: C/anjuta-manual.xml:123(para)
1418 "If the project has recently been opened, then you will find it listed in the "
1419 "menu <menuchoice><guisubmenu>File</guisubmenu><guisubmenu>Recent</"
1420 "guisubmenu></menuchoice>. Choose the project file from the list, and the "
1421 "project will be opened."
1424 #: C/anjuta-manual.xml:128(para)
1426 "As soon as a project is opened, <application>Anjuta</application> will enter "
1427 "<emphasis>Project mode</emphasis>. There are three panes in the project "
1428 "window. The first is the project pane and lists the project files organized "
1429 "in file types. The second is the symbol browser, which has already been "
1430 "discussed in section <emphasis>Symbol Browser and tags Brwoser</emphasis>. "
1431 "The third pane is the file view of the project and is more or less similar "
1432 "to a mini file-manager. In file view, all the files present in the project "
1433 "tree is visible. Right clicking on these files will pop up the file "
1434 "operation submenu."
1437 #: C/anjuta-manual.xml:138(para)
1439 "If the project is also a CVS tree, then corresponing file revision numbers "
1440 "are also listing on the right of file names in the file view pane."
1443 #: C/anjuta-manual.xml:144(title)
1444 msgid "Saving Projects"
1447 #: C/anjuta-manual.xml:145(para)
1449 "The project is automatically saved when you close because all changes are "
1450 "made directly in the project structure."
1453 #: C/anjuta-manual.xml:153(title)
1454 msgid "Project structure"
1457 #: C/anjuta-manual.xml:154(para)
1459 "<interface>Project View</interface> lists the project in standard <ulink "
1460 "type=\"info\" url=\"info:automake\"><application>automake</application></"
1461 "ulink> heirarchy organized into groups of targets. <emphasis>Groups</"
1462 "emphasis> correspond to directories in your project and <emphasis>targets</"
1463 "emphasis> correspond to normal <application>automake</application> targets "
1464 "(not to be confused with make targets). <interface>Project View</interface> "
1465 "actually has two parts; one part (lower one) shows complete project "
1466 "heirarchy and the other part (upper one) lists important targets directly. "
1467 "Important targets constitute executable and library targets -- making them "
1468 "very accessible in from the view. This is particularly useful in big "
1469 "projects where the heirarchy could be deep and hard to navigate from the "
1470 "tree alone. Targets are, in turn, composed of source files."
1473 #: C/anjuta-manual.xml:174(para)
1475 "<emphasis>Groups</emphasis> are used to logically organize targets. A "
1476 "project can contain any number of groups. Each group can have sub-groups as "
1477 "well as targets. In automake projects, groups are just sub-directories in "
1478 "the project. The top level group is called root and is always \"/\"."
1481 #: C/anjuta-manual.xml:182(para)
1483 "<emphasis>Targets</emphasis> are the build targets in project, such as "
1484 "programs (executable binaries), scripts, libraries, miscellaneous data etc. "
1485 "Not all target types are built from sources, but exist just to organize the "
1486 "sources and therefore may not exist physically (e.g. Miscellaneous data "
1487 "target). Targets exist under groups. See <link linkend=\"adding-target\">"
1488 "\"Adding targets\"</link> for full list of available target types."
1491 #: C/anjuta-manual.xml:193(para)
1493 "<emphasis>Source files</emphasis> are the files used to build the targets or "
1494 "just to be part of it. They exist only under targets. Many target types "
1495 "expect certain type of source files (e.g. programs and libraries target "
1496 "types), but some can accept any file (e.g. Miscellaneous data target)."
1499 #: C/anjuta-manual.xml:203(para)
1501 "Each of the project groups and targets is configurable in standard "
1502 "<application>automake</application> way. You can set complier and linker "
1503 "flags directly for each target, or set configure variables. Groups allow "
1504 "setting installation destinations for its targets."
1507 #: C/anjuta-manual.xml:210(para)
1509 "Just like file manager, project manager view also has convenience actions "
1510 "(accessible from context menu) for the source files and targets."
1513 #: C/anjuta-manual.xml:215(para)
1515 "Many command-line tools are available to maintain and manage a project, and "
1516 "each tool has its own specific rules and capabilities. <application>Anjuta</"
1517 "application> tries to automate most of the common operations using plugins. "
1518 "However, you might occationally still need to do them manually."
1521 #: C/anjuta-manual.xml:223(para)
1523 "It is possible to make use of other tools or hand edit the project files "
1524 "simulaneously. It doesn't matter if the project is loaded in "
1525 "<application>Anjuta</application> or not. <application>Anjuta</application> "
1526 "would update itself with any external changes made to project."
1529 #: C/anjuta-manual.xml:232(title)
1530 msgid "Groups and targets"
1533 #: C/anjuta-manual.xml:235(title)
1534 msgid "Adding Groups"
1537 #: C/anjuta-manual.xml:240(para)
1539 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Group</"
1540 "guimenuitem></menuchoice> and a dialog to add a new group would popup."
1543 #: C/anjuta-manual.xml:247(para)
1544 msgid "Select the group under which to add new group."
1547 #: C/anjuta-manual.xml:250(para)
1548 msgid "Give a name of the new group and click Ok."
1551 #: C/anjuta-manual.xml:236(para)
1553 "To add a new group (a directory in automake based projects): <placeholder-1/"
1554 "> With automake projects, a new directory with the given name would be "
1555 "created under the parent group's directory."
1558 #: C/anjuta-manual.xml:257(para)
1560 "New group can also be added from the <guimenu>Operation</guimenu> menu in "
1561 "<interface>Project View</interface> by selecting <guimenuitem>Add Group</"
1562 "guimenuitem>. First select the group under which to add the group in "
1563 "<interface>Project View</interface>."
1566 #: C/anjuta-manual.xml:266(title)
1567 msgid "Removing Groups"
1570 #: C/anjuta-manual.xml:271(para)
1571 msgid "Select the target in <interface>Project Manager view</interface>."
1574 #: C/anjuta-manual.xml:274(para) C/anjuta-manual.xml:413(para)
1576 "Select <guimenuitem>Remove</guimenuitem> from the <guimenu>Operation</"
1580 #: C/anjuta-manual.xml:267(para)
1582 "To remove a group: <placeholder-1/> The target and sources associated with "
1583 "the group will also be removed from the project (they are not deleted from "
1584 "the file system, though. You can still add them later)."
1587 #: C/anjuta-manual.xml:285(title)
1588 msgid "Adding Targets"
1591 #: C/anjuta-manual.xml:290(para)
1593 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Target</"
1594 "guimenuitem></menuchoice> and a dialog to add a new target would popup."
1597 #: C/anjuta-manual.xml:295(para)
1598 msgid "Select the group under which to add the target."
1601 #: C/anjuta-manual.xml:298(para)
1602 msgid "Select the target type."
1605 #: C/anjuta-manual.xml:301(para)
1606 msgid "Give a name of the new target and click Ok."
1609 #: C/anjuta-manual.xml:286(para)
1610 msgid "To add a new target: <placeholder-1/>"
1613 #: C/anjuta-manual.xml:305(para)
1615 "New target can also be added from the <guimenu>Operation</guimenu> menu in "
1616 "<interface>Project View</interface> by selecting <guimenuitem>Add target</"
1617 "guimenuitem>. First select the group under which to add the target in "
1618 "<interface>Project View</interface>."
1621 #: C/anjuta-manual.xml:311(para)
1623 "Target names usually require some standard prefix and suffix, depending on "
1624 "the type of target. Anjuta would warn if the name is not valid and may give "
1625 "an example of a name."
1628 #: C/anjuta-manual.xml:320(para)
1630 "<emphasis>Program</emphasis> target type is for executable binaries. Select "
1631 "this if you want to add an executable to the project. By default, all "
1632 "program targets would be installed in standard executable directory, e.g. /"
1633 "usr/bin or /usr/local/bin. You can override it by specifying a different "
1634 "installation directory in its group properties."
1637 #: C/anjuta-manual.xml:329(para)
1639 "<emphasis>Shared Library</emphasis> target type is for shared or dynamic "
1640 "libraries. Select this if you are adding a shared library to the project. By "
1641 "default, all shared libraries are installed in standard libraries directory, "
1642 "e.g. /usr/lib or /usr/local/lib. You can override it by specifying a "
1643 "different installation directory in its group properties."
1646 #: C/anjuta-manual.xml:338(para)
1648 "<emphasis>Static Library</emphasis> target type is for static library. "
1649 "Select this if you are adding a static library to the project. By default, "
1650 "all static libraries are installed in standard libraries directory, e.g. /"
1651 "usr/lib or /usr/local/lib. You can override it by specifying a different "
1652 "installation directory in its group properties."
1655 #: C/anjuta-manual.xml:347(para)
1657 "<emphasis>Java module</emphasis> target type is for java module. Select this "
1658 "if you are grouping java sources into a module. You need to provide an "
1659 "installation directory for this target where the .class files will be "
1660 "installed. It can be set in group properties of the group where this target "
1664 #: C/anjuta-manual.xml:355(para)
1666 "There can really be only one java module in a group. This is a restriction "
1667 "put by automake. Please read automake info page for more details."
1670 #: C/anjuta-manual.xml:363(para)
1672 "<emphasis>Python module</emphasis> target type is for python module. Select "
1673 "this if you are grouping python sources into a module. You need to provide "
1674 "an installation directory for this target where the sources will be "
1675 "installed. It can be set in group properties of the group where this target "
1679 #: C/anjuta-manual.xml:372(para)
1681 "<emphasis>Scripts</emphasis> target is to group scripts. They will be "
1682 "installed in standard executable directory."
1685 #: C/anjuta-manual.xml:378(para)
1687 "<emphasis>Miscellaneous Data</emphasis> target type is to group simple files "
1688 "in the project. An installation directory needs to be specified in its group "
1692 #: C/anjuta-manual.xml:385(para)
1694 "<emphasis>Header Files</emphasis> target type is to group C/C++ header files "
1695 "that need to be installed in system (for example as part of library API). "
1696 "For header files that do not need to be installed, make them part of the "
1697 "Program target along with the sources. They will be installed in standard "
1698 "include directory unless installation path is specified in its group "
1702 #: C/anjuta-manual.xml:395(para)
1704 "<emphasis>Man documentation</emphasis> and <emphasis>Info documentation</"
1705 "emphasis> target types are for grouping man and info documentation "
1706 "respectively. By default, they will be installed in standard installation "
1710 #: C/anjuta-manual.xml:316(para)
1712 "There are several target types for automake project. They are: <placeholder-"
1716 #: C/anjuta-manual.xml:405(title)
1717 msgid "Removing Targets"
1720 #: C/anjuta-manual.xml:410(para)
1721 msgid "Select the target in <interface>Project Manager view</interface>"
1724 #: C/anjuta-manual.xml:406(para)
1726 "To remove a target: <placeholder-1/> The sources associated with the targets "
1727 "will also be removed from the project (they are not deleted from the file "
1731 #: C/anjuta-manual.xml:425(title)
1732 msgid "Adding and Removing Files"
1735 #: C/anjuta-manual.xml:427(title)
1736 msgid "Adding Source Files"
1739 #: C/anjuta-manual.xml:428(para)
1741 "Select menu item <menuchoice><guisubmenu>Project</"
1742 "guisubmenu><guimenuitem>Add Source File</guimenuitem></menuchoice>. From the "
1743 "dialog, select the target to which the file should be added and the file "
1744 "itself. You can add multiple files at once. To do that, select multiple "
1745 "files from the fileselection dialog using either SHIFT or CONTROL key. Then "
1746 "click <guibutton>Add</guibutton> button to finally add the files in project."
1749 #: C/anjuta-manual.xml:437(para)
1751 "By default, current editor file would be preselected for addtion in the "
1752 "dialog. Other convenient way to add a file is to select it in "
1753 "<interface>File Manager</interface> and choosing <guimenuitem>Add to "
1754 "project</guimenuitem> from the <guimenu>Operation</guimenu> popup menu."
1757 #: C/anjuta-manual.xml:444(para)
1759 "If the file you choose has already been added to the project, then "
1760 "<application>Anjuta</application> will not add it again. It will also give "
1761 "you a warning that the file is already added."
1764 #: C/anjuta-manual.xml:449(para)
1766 "If the file you choose is not in the project directory, you will be asked to "
1767 "confirm that you wish to copy the file into the target's directory. "
1768 "<application>Anjuta</application> cannot add files which are outside of "
1769 "target's directory."
1772 #: C/anjuta-manual.xml:457(title)
1773 msgid "Removing Source Files"
1776 #: C/anjuta-manual.xml:458(para)
1778 "To remove a file from the project, select the file you want to remove from "
1779 "the <interface>Project View</interface>, right-click to open the "
1780 "<guimenu>Operation</guimenu> popup menu and choose <guimenuitem>Remove</"
1784 #: C/anjuta-manual.xml:464(para)
1786 "A confirmation dialog will appear, and the file will be removed from the "
1790 #: C/anjuta-manual.xml:469(title)
1791 msgid "The file is not deleted!"
1794 #: C/anjuta-manual.xml:470(para)
1796 "The file is not deleted from the filesystem. It still exists, and you can "
1797 "add it back again later if you so wish. The file is only removed from the "
1798 "project listing, and will not take part in any of the project operations "
1799 "such as compiling, building, distribution etc.."
1802 #: C/anjuta-manual.xml:481(title)
1803 msgid "Project Configuration"
1806 #: C/anjuta-manual.xml:482(para)
1808 "Project configuration involves setting the correct build flags for targets, "
1809 "groups and project itself. You can set these flags in their respective "
1810 "properties dialog."
1813 #: C/anjuta-manual.xml:488(para)
1815 "You can freely use autoconf and automake variables that are automatically "
1816 "set for the project during configuration. Apart from these automatically set "
1817 "variables, you can also defined your own variables in <link linkend="
1818 "\"project-properties\">Project Properties</link> use them in properties. "
1819 "This will make it easy to update flags later, especially when the variable "
1820 "is used in several targets."
1823 #: C/anjuta-manual.xml:503(para)
1825 "<emphasis>$(prefix)</emphasis>: The installation prefix. The project is "
1826 "installed under various sub-directories under this prefix. By default it is /"
1830 #: C/anjuta-manual.xml:510(para)
1832 "<emphasis>$(bindir)</emphasis>: The installation directory for executable "
1833 "binaries. All your executable and scripts targets would be installed in this "
1834 "directory. By default, it is $(prefix)/bin."
1837 #: C/anjuta-manual.xml:517(para)
1839 "<emphasis>$(libdir)</emphasis>: The installation directory for libraries. "
1840 "All your library targets (both shared and static) would be installed in this "
1841 "directory or a subdirectory below it. By default, it is $(prefix)/lib."
1844 #: C/anjuta-manual.xml:525(para)
1846 "<emphasis>$(module_CFLAGS)</emphasis> and $(module_LIBS): These flags are "
1847 "set by configure for the packages that your project depends on. The packages "
1848 "used by the project are set in <link linkend=\"project-properties\">Project "
1849 "Properties</link>. 'module' is the packages group that you give in project "
1853 #: C/anjuta-manual.xml:497(para)
1855 "Some of the many common variables are listed here. For full list of them see "
1856 "<ulink url=\"info:automake\">automake info documentation</ulink>. "
1860 #: C/anjuta-manual.xml:539(title)
1861 msgid "Project properties"
1862 msgstr "Propiedades del proyecto"
1864 #: C/anjuta-manual.xml:546(para)
1866 "Set project name, version and URL in <guibutton>General</guibutton> page. "
1867 "Configure variables can also be use in these fields. The URL is the bug "
1868 "report URL for the project."
1871 #: C/anjuta-manual.xml:553(para)
1873 "Add and remove dependencies for your project in <guibutton>Packages</"
1874 "guibutton> page. See below for details."
1877 #: C/anjuta-manual.xml:559(para)
1879 "Create more configure variables in <guibutton>Variables</guibutton> page to "
1880 "use in group and target properties."
1883 #: C/anjuta-manual.xml:540(para)
1885 "Project properties dialog can be only brought by choosing "
1886 "<menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
1887 "guimenuitem></menuchoice>. You can: <placeholder-1/>"
1890 #: C/anjuta-manual.xml:574(title) C/anjuta-manual.xml:576(screeninfo)
1891 msgid "Project properties dialog"
1894 #: C/anjuta-manual.xml:566(para)
1896 "Dependencies are external packages that the project uses and hence required "
1897 "to build it. Only packages installed using <ulink url=\"info:pkg-config"
1898 "\">pkg-config</ulink> can be added from this interface. For others, the "
1899 "configure.ac file can be edited manually. <placeholder-1/>"
1902 #: C/anjuta-manual.xml:581(para)
1904 "External package dependencies are grouped into <emphasis>modules</emphasis>, "
1905 "so that their combined build flags can be conviniently added to different "
1906 "targets. <emphasis>Modules</emphasis> are just arbitrary names given to "
1907 "group the packages and can be named anything (only alphanumeric and _ are "
1908 "allowed in module name). Usually, they follow the name of targets they would "
1909 "be use in. Consequently, for small projects with single targets, just one "
1910 "module to hold all dependencies is enough."
1913 #: C/anjuta-manual.xml:590(para)
1915 "Each package exports a set of <emphasis>compiler flags</emphasis> and "
1916 "<emphasis>libraries</emphasis>. They are aggregated together for all "
1917 "packages under a module and configure variables <emphasis>$(module_CFLAGS)</"
1918 "emphasis> and <emphasis>$(module_LIBS)</emphasis> are defined. These "
1919 "variables can then be used in <link linkend=\"group-properties\">Group "
1920 "properties</link> and <link linkend=\"target-properties\">Target properties</"
1924 #: C/anjuta-manual.xml:603(para)
1926 "Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
1927 "guimenuitem></menuchoice> to bring up project properties dialog."
1930 #: C/anjuta-manual.xml:610(para)
1931 msgid "Select the tab <guibutton>Packages</guibutton> to bring up packages page."
1934 #: C/anjuta-manual.xml:614(para)
1936 "Select the <emphasis>module</emphasis> to add the package to. If there is no "
1937 "module created yet or there is no appropriate module, create one by clicking "
1938 "<guibutton>Add module</guibutton>. Give a sensible name to the module, "
1939 "preferably in UPPERCASE to match with rest of configure variables (only use "
1940 "alphanumeric and '_' characters) and press <keycap>Enter</keycap> to create "
1944 #: C/anjuta-manual.xml:624(para)
1946 "Click <guibutton>Add package</guibutton> to bring up package selection "
1950 #: C/anjuta-manual.xml:627(para)
1951 msgid "Select the package to add and click <guibutton>Add</guibutton>."
1954 #: C/anjuta-manual.xml:630(para)
1955 msgid "Click <guibutton>Close</guibutton> to close the properties dialog."
1956 msgstr "Pulse <guibutton>Cerrar</guibutton> para cerrar el diálogo de propiedades."
1958 #: C/anjuta-manual.xml:599(para)
1959 msgid "To add a package dependency: <placeholder-1/>"
1962 #: C/anjuta-manual.xml:637(title)
1963 msgid "Group properties"
1964 msgstr "Propiedades del grupo"
1966 #: C/anjuta-manual.xml:638(para)
1968 "To set group properties, select it in the <interface>Project View</"
1969 "interface> and active it. You can also bring it by selecting "
1970 "<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
1971 "guimenuitem></menuchoice>"
1974 #: C/anjuta-manual.xml:654(para)
1976 "<emphasis>Includes</emphasis>: Set your $(module_CFLAGS) variables and other "
1977 "include directories for your c and c++ targets. You need to provide the full "
1978 "include options of the compiler here, e.g. -I/usr/include/blah. The include "
1979 "paths will be use to find the include files in your source files. You can "
1980 "also add other sort of compiler flags here, but they are prefered to be set "
1981 "in their respective compiler flags properties (see below)."
1984 #: C/anjuta-manual.xml:664(para)
1986 "Usually your configure script would also make some automatically determined "
1987 "compiler flags. The variables usually end with _CFLAGS, e.g "
1988 "$(PACKAGE_CFLAGS). They are also set here. See setting <link linkend="
1989 "\"project-properties\">Project properties</link> for more details on these "
1993 #: C/anjuta-manual.xml:674(para) C/anjuta-manual.xml:715(para)
1995 "<emphasis>Compiler settings</emphasis>: Set your compiler specific flags "
1996 "here. There are different fields for different compiler categories. Flags "
1997 "that can be set here depend on the actual compiler used. The default "
1998 "compiler use for c/c++ is gcc/g++ (gnu c compiler). Check out <ulink url="
1999 "\"info:gcc\">gcc info documentation</ulink> for more details."
2002 #: C/anjuta-manual.xml:684(para)
2004 "<emphasis>Install directories</emphasis>: Targets in the group that require "
2005 "installation directories would each get a field to enter the installation "
2006 "directory. Set their installation directories as relative to one of the many "
2007 "automake directory variables, such as $(prefix), $(bindir), $(libdir), "
2011 #: C/anjuta-manual.xml:645(para)
2013 "<emphasis>Group Properties</emphasis> set to a group applies to all the "
2014 "targets under it. So any compiler or linker flags set there would be "
2015 "automatically be part of all the targets in it (in addition the targets "
2016 "individual properties). Folowing flags are available in group properties. "
2020 #: C/anjuta-manual.xml:699(title)
2021 msgid "Target properties"
2022 msgstr "Propiedades del destino"
2024 #: C/anjuta-manual.xml:700(para)
2026 "To set target properties, select it in the <interface>Project View</"
2027 "interface> and active it. You can also bring it by selecting "
2028 "<menuchoice><guimenu>Operation menu</guimenu><guimenuitem>Properties</"
2029 "guimenuitem></menuchoice>"
2032 #: C/anjuta-manual.xml:725(para)
2034 "<emphasis>Linker flags</emphasis>: Set linker flags that should be used when "
2035 "linking the target. It applies only to Program and library targets. See "
2036 "<ulink url=\"info:ld\">ld info documentation</ulink> for available linker "
2040 #: C/anjuta-manual.xml:733(para)
2042 "<emphasis>Libraries</emphasis>: Set the libraries that the target depends "
2043 "on. Usually they are the $(module_LIBS) configure variables. See setting "
2044 "<link linkend=\"project-properties\">Project properties</link> for more "
2045 "details on these variables."
2048 #: C/anjuta-manual.xml:707(para)
2050 "<emphasis>Target Properties</emphasis> set to a target applies to that "
2051 "target. So any compiler or linker flags set there would be just part of it "
2052 "(in addition the its group properties). Folowing flags are available in "
2053 "target properties. <placeholder-1/>"
2056 #: C/anjuta-manual.xml:748(title)
2057 msgid "Compiling and Building"
2060 #: C/anjuta-manual.xml:750(title)
2062 msgstr "Vista general"
2064 #: C/anjuta-manual.xml:751(para)
2065 msgid "An executable for a project is generated in two steps:"
2068 #: C/anjuta-manual.xml:756(para)
2072 #: C/anjuta-manual.xml:757(para)
2076 #: C/anjuta-manual.xml:760(para)
2078 "These steps are collectively known as <emphasis>Building</emphasis>. Some "
2079 "other steps may also be involved in the build process, but for the sake of "
2080 "simplicity, we will only look at these two steps."
2083 #: C/anjuta-manual.xml:765(para)
2085 "<emphasis>Compiling</emphasis> is the step in which object files are "
2086 "generated from their corresponding source files. For instance, a source file "
2087 "<filename>hello.c</filename> will generate <filename>hello.o</filename> "
2088 "after compilation. Usually you do not need to worry about these object files "
2089 "— just think of them as intermediate files involved in creating the final "
2093 #: C/anjuta-manual.xml:772(para)
2095 "Once the object files (<filename>*.o</filename> files) are ready, they are "
2096 "all linked together (along with any libraries) to generate the final "
2097 "executable. This step is called <emphasis>Linking</emphasis>."
2100 #: C/anjuta-manual.xml:779(title)
2101 msgid "Compiling the source"
2102 msgstr "Compilar los fuentes"
2104 #: C/anjuta-manual.xml:780(para)
2106 "In a project, the individual source files can be compiled separately into "
2107 "objects (<filename>*.o</filename> files). Although you do not have to worry "
2108 "about these object files, sometimes it is handy to compile a file first (for "
2109 "example, to make sure there are no syntax errors). Building a whole project "
2110 "can take a lot of time, especially in the case of larger and more complex "
2111 "applications. Therefore, you will probably go through a series of edit-"
2112 "compile-edit-compile-.... loops while a developing the project."
2115 #: C/anjuta-manual.xml:788(para)
2117 "To compile a file, choose the menu item <menuchoice><guisubmenu>Build</"
2118 "guisubmenu><guimenuitem>Compile</guimenuitem></menuchoice> or press "
2119 "<keycap>F11</keycap>. This will compile the active file."
2122 #: C/anjuta-manual.xml:795(title)
2123 msgid "Building an executable"
2124 msgstr "Construir un ejecutable"
2126 #: C/anjuta-manual.xml:796(para)
2128 "<application>Anjuta</application> has no separate link command, simply "
2129 "because it is not necessary. The build process will compile all the source "
2130 "files and link them together along with the libraries. The build command "
2131 "will note recompile those files which are already up-to-date (this is called "
2132 "the <emphasis>dependency check</emphasis>). If you have already compiled all "
2133 "of the files individually, then the only thing the build step performs is "
2134 "the link. If you have already built the project and no dependent file has "
2135 "been modified, even the link stage will be skipped."
2138 #: C/anjuta-manual.xml:805(para)
2140 "So how exactly does the dependency check influence the project development? "
2141 "If you have modified a file, then all of the source files that depend on the "
2142 "modified file are recompiled. All files (not only the object files and "
2143 "executable) in the project are checked for these dependencies during the "
2144 "build process. If it is found that a particular file is dependent on some "
2145 "other file which has been modified, then that file will be re-generated."
2148 #: C/anjuta-manual.xml:813(para)
2150 "Since you have now got a rough understanding of the value of the dependency "
2151 "check, can you imagine how your life (as a programmer) would be if it had "
2152 "not been there? If you cannot answer just yet, then will find out when you "
2153 "start developing big projects!"
2156 #: C/anjuta-manual.xml:818(para)
2158 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></"
2159 "menuchoice> will build all of the files in the <filename class=\"directory"
2160 "\">src</filename> (source) directory, and generate the executable. "
2161 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build All</"
2162 "guimenuitem></menuchoice> will build the whole project — all of the "
2163 "subdirectories (including <filename class=\"directory\">src</filename>), are "
2164 "built recursively."
2167 #: C/anjuta-manual.xml:828(title)
2168 msgid "Creating a distribution package"
2169 msgstr "Crear un paquete de distribución"
2171 #: C/anjuta-manual.xml:829(para)
2173 "To build the tarball distribution of the project choose "
2174 "<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Tarball</"
2175 "guimenuitem></menuchoice>. This will create a tarball (<filename>*.tar.gz</"
2176 "filename>) and put it in the top level project directory. Copy the file to a "
2177 "safe place for distribution."
2180 #: C/anjuta-manual.xml:837(title)
2182 msgstr "Instalación"
2184 #: C/anjuta-manual.xml:838(para)
2186 "Choosing the menu item <menuchoice><guisubmenu>Build</"
2187 "guisubmenu><guimenuitem>Install</guimenuitem></menuchoice> will install the "
2188 "generated application on your system."
2191 #: C/anjuta-manual.xml:844(title)
2192 msgid "System wide installation"
2195 #: C/anjuta-manual.xml:845(para)
2197 "You must be logged in as root to perform a system-wide install. Also note "
2198 "that for a GNOME application to use the pixmaps in the project, it must be "
2199 "installed as a system-wide application. Otherwise, when the application is "
2200 "executed in your project, there will be lots of \"pixmap not found\" errors. "
2201 "You can configure anjuta to use <command>sudo</command> or <command>su</"
2202 "command> before installing the project in the build preferences."
2205 #: C/anjuta-manual.xml:855(title)
2209 #: C/anjuta-manual.xml:856(para)
2211 "To run the <filename>configure</filename> script found in the top level "
2212 "project directory, choose the menu item <menuchoice><guisubmenu>Build</"
2213 "guisubmenu><guimenuitem>Configure</guimenuitem></menuchoice>. The script "
2214 "will determine the system configuration and create some of the files "
2215 "required to perform a build (such as <filename>Makefile</filename> and "
2216 "<filename>config.h</filename>). This is necessary because the application "
2217 "may depend on specific configuration of some of these options."
2220 #: C/anjuta-manual.xml:865(title)
2221 msgid "When to configure"
2224 #: C/anjuta-manual.xml:866(para)
2226 "Until you run <filename>configure</filename>, you cannot start building the "
2230 #: C/anjuta-manual.xml:871(para)
2232 "The <filename>configure</filename> script is (usually) run only once at the "
2233 "beginning of the first build process — for example, just after you have "
2234 "extracted a source tarball of a project distribution. After that, "
2235 "configuration is automatically handled by the subsequent build processes. If "
2236 "you have used the <emphasis>Application Wizard</emphasis> to create the "
2237 "application, then you will not need to run <filename>configure</filename> "
2238 "separately: the wizard will run it as a part of the project generation "
2242 #: C/anjuta-manual.xml:879(para)
2244 "You can also supply additional options to the configuration script. After "
2245 "choosing the <guimenuitem>Configure</guimenuitem> menu item, a dialog will "
2246 "appear to prompt for additional options."
2249 #: C/anjuta-manual.xml:885(title) C/anjuta-manual.xml:887(screeninfo)
2250 msgid "Configure options dialog"
2253 #: C/anjuta-manual.xml:891(para)
2255 "Enter any options (or leave it blank to accept the defaults) and click "
2256 "<guibutton>OK</guibutton>. To find out the options available to the "
2257 "<filename>configure</filename> script, enter <userinput>--help</userinput> "
2258 "in the option entry box and click <guibutton>OK</guibutton>. The options "
2259 "will be displayed in the <interface>Message window</interface>."
2262 #: C/anjuta-manual.xml:898(para)
2264 "There is no requirement to run <filename>configure</filename> only once. It "
2265 "can be run at any time, usually when the configuration options need to be "
2266 "changed. One thing to note is that, if the <filename>config.h</filename> "
2267 "file in the top level directory is changed, running <filename>configure</"
2268 "filename> again will not overwrite it."
2271 #: C/anjuta-manual.xml:906(title)
2272 msgid "Auto generate"
2275 #: C/anjuta-manual.xml:907(para)
2277 "Auto generation consists of two steps: running <application>automake</"
2278 "application> and then running <application>autoconf</application>. If an "
2279 "executable <filename>autogen.sh</filename> script is found in the top level "
2280 "project directory, this file will be executed instead of the two steps. Like "
2281 "<emphasis>configuration</emphasis>, auto generation is automatically handled "
2282 "by the build process. It can also be run in cases where it is difficult to "
2283 "configure the project (such as lots of errors reported due to mis-"
2284 "synchronization after modifying lots of build files)."
2287 #: C/anjuta-manual.xml:918(title)
2288 msgid "When to autogen.sh"
2291 #: C/anjuta-manual.xml:919(para)
2293 "Unlike configuration, auto generation does not need to be run even once — in "
2294 "fact, it does not need to be run at all! The option is available because it "
2295 "can be handy in some circumstances."
2298 #: C/anjuta-manual.xml:925(para)
2300 "Choose the menu item <menuchoice><guisubmenu>Build</"
2301 "guisubmenu><guimenuitem>Auto generate</guimenuitem></menuchoice> to auto "
2302 "generate the project."
2305 #: C/anjuta-manual.xml:929(para)
2307 "Read the info pages of <ulink type=\"info\" url=\"info:automake"
2308 "\"><application>automake</application></ulink> and <ulink type=\"info\" url="
2309 "\"info:autoconf\"><application>autoconf</application></ulink> for more "
2310 "details on how these tools work."
2313 #: C/anjuta-manual.xml:936(title)
2317 #: C/anjuta-manual.xml:937(para)
2319 "This option cleans the project and leaves it in a state that requires "
2320 "<guimenuitem>Build All</guimenuitem> to be performed. It deletes all of the "
2321 "files generated by the build process, including all object files "
2322 "(<filename>*.o</filename> files) and the executable(s) in the <filename "
2323 "class=\"directory\">src</filename> directory (and other directories)."
2326 #: C/anjuta-manual.xml:944(para)
2328 "Choose the menu item <menuchoice><guisubmenu>Build</"
2329 "guisubmenu><guimenuitem>Clean</guimenuitem></menuchoice> to clean the "
2333 #: C/anjuta-manual.xml:950(title)
2337 #: C/anjuta-manual.xml:951(para)
2339 "There is not a great deal to say about <guimenuitem>Clean All</guimenuitem> "
2340 "(which might also be called <emphasis>Clean distribution</emphasis>, or "
2341 "<emphasis>clean dist</emphasis> for short). It cleans the project and leaves "
2342 "it in a state that requires <guimenuitem>Configure</guimenuitem> and "
2343 "<guimenuitem>Build All</guimenuitem> to be performed. It deletes all of the "
2344 "files generated by the build processes, including all the object files "
2345 "(<filename>*.o</filename> files), executable(s) and Makefiles. In other "
2346 "words, it leaves the project as though it has just been extracted from a "
2347 "distribution tarball."
2350 #: C/anjuta-manual.xml:961(para)
2352 "Choose the menu item <menuchoice><guisubmenu>Build</"
2353 "guisubmenu><guimenuitem>Clean All</guimenuitem></menuchoice> to completely "
2354 "clean the project."
2357 #: C/anjuta-manual.xml:968(title)
2358 msgid "Executing program"
2361 #: C/anjuta-manual.xml:969(para)
2363 "Once an executable is ready after the build, you can execute it by choosing "
2364 "the menu item <menuchoice><guisubmenu>Build</"
2365 "guisubmenu><guimenuitem>Execute</guimenuitem></menuchoice>, or pressing "
2366 "<keycap>F3</keycap>. You can specify which executable you want to use in "
2367 "case your project provides more than one and specify command line arguments."
2370 #: C/anjuta-manual.xml:976(title)
2371 msgid "Dependencies"
2374 #: C/anjuta-manual.xml:977(para)
2376 "Unlike the build stage, execution doesn't check for dependencies (at least "
2377 "for the time being). In other words, it does not check if the executable is "
2378 "up-to-date before it executes the program. So, <emphasis>you must take care "
2379 "of that yourself.</emphasis>"
2382 #: C/anjuta-manual.xml:987(title)
2383 msgid "Choose executable and set program parameters"
2386 #: C/anjuta-manual.xml:989(screeninfo)
2387 msgid "Setting program parameters"
2390 #: C/anjuta-manual.xml:3(title)
2394 #: C/anjuta-manual.xml:5(emphasis)
2395 msgid "To debug is human. To fix it is divine..."
2398 #: C/anjuta-manual.xml:7(para)
2400 "Well, the <emphasis>human</emphasis> part is what this section is about. The "
2401 "<emphasis>divine</emphasis> part is up to you!"
2404 #: C/anjuta-manual.xml:11(para)
2406 "When a program does not behave in the way it is supposed to, we say the "
2407 "program contains a bug or bugs. This does not refer to compilation errors — "
2408 "those are simply errors and they are relatively easy to clear, because the "
2409 "compiler tells you where the problems are. On the other hand, "
2410 "<emphasis>bugs</emphasis> are errors that happen during the execution of the "
2411 "program and they can be hard (sometimes very hard!) to detect."
2414 #: C/anjuta-manual.xml:19(para)
2416 "Any program that you think is bug-free is never completely bug-free. All we "
2417 "can try to do is to reduce the number of bugs contained in the program. The "
2418 "process of removing bugs is known as <emphasis>debugging</emphasis>, and the "
2419 "tool that is used for debugging is called the <emphasis>debugger</emphasis>. "
2420 "<application>Anjuta</application> provides a very user-friendly and powerful "
2421 "debugging environment (actually, a GUI wrapper over <application>gdb</"
2422 "application>, a powerful command line debugging tool and standard on Linux)."
2425 #: C/anjuta-manual.xml:27(para)
2427 "A debugger tracks and traces the execution of the program and provides "
2428 "various views of information needed to study the execution of the program."
2431 #: C/anjuta-manual.xml:33(para)
2433 "The debugger has been heavily changed since anjuta 2.0.2. Some features have "
2434 "been dropped but will be reenabled, a few have been added."
2437 #: C/anjuta-manual.xml:42(title)
2438 msgid "Start and stop"
2441 #: C/anjuta-manual.xml:47(emphasis) C/anjuta-manual.xml:53(title)
2442 msgid "Running an executable"
2445 #: C/anjuta-manual.xml:48(emphasis)
2446 msgid "Attaching to a process"
2449 #: C/anjuta-manual.xml:44(para)
2450 msgid "There are two ways to start the debugger: <placeholder-1/>"
2453 #: C/anjuta-manual.xml:54(para)
2455 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2456 "guisubmenu><guimenuitem>Run Target…</guimenuitem></menuchoice> to display a "
2457 "dialog box where you can select the executable that you want to debug, the "
2458 "command line parameters and if you want a terminal or not. The popup menu of "
2459 "the target combo box is already filled with all executables of the current "
2460 "project, so you can easily select one of them. But it is not mandatory, you "
2461 "can select any other executable. The debugger accepts libtool executable, I "
2462 "mean script wrapping the real executable generated by libtool. When you have "
2463 "set everything you can click on <guibutton>Execute</guibutton> to start the "
2464 "debugger, load your program and stop at its beginning."
2467 #: C/anjuta-manual.xml:68(para)
2469 "In order to better user the debugger, it is recommended to debug program "
2470 "with debugging information (-g for gcc) and no optimization (-O0 for gcc)."
2473 #: C/anjuta-manual.xml:76(title)
2474 msgid "Attaching to a Process"
2477 #: C/anjuta-manual.xml:77(para)
2479 "It is also possible to attach to a running process for debugging. Choose the "
2480 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Attach to "
2481 "Process …</guimenuitem></menuchoice>. A list of all the process running on "
2482 "the system will appear."
2485 #: C/anjuta-manual.xml:84(title) C/anjuta-manual.xml:86(screeninfo)
2486 msgid "Attach to Process dialog"
2489 #: C/anjuta-manual.xml:90(para)
2490 msgid "Select the process to attach to and click <guibutton>OK</guibutton>."
2493 #: C/anjuta-manual.xml:94(para)
2495 "It is currently not possible to load symbol information for the attached "
2499 #: C/anjuta-manual.xml:102(title)
2500 msgid "Restarting an executable"
2503 #: C/anjuta-manual.xml:103(para)
2505 "After running a executable at least one time, you can choose the menu item "
2506 "<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Restart Target</"
2507 "guimenuitem></menuchoice> to restart your program. It is just a shortcut "
2508 "that will stop the debugger if it is currently running and restart it with "
2509 "the last executable."
2512 #: C/anjuta-manual.xml:113(title)
2513 msgid "Stopping the Debugger"
2516 #: C/anjuta-manual.xml:114(para)
2518 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2519 "guisubmenu><guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the "
2520 "debugger. This option will kill the program which is being debugged. If the "
2521 "debugger has been attached to a running process, it will just detach from it "
2522 "without killing it. You will get a confirmation box if a program is "
2523 "currently attached or running."
2526 #: C/anjuta-manual.xml:128(title)
2530 #: C/anjuta-manual.xml:129(para)
2532 "Execution of a program in the debugger can be finely controlled. The program "
2533 "can be executed in single steps, or allowed to continue until it encounters "
2534 "a breakpoint. Executing like this is essential for tracking program "
2535 "behaviour. Like a video editing session, the program can be executed in "
2536 "<emphasis>slow motion</emphasis> with the ability to go forward, pause, "
2540 #: C/anjuta-manual.xml:136(para)
2542 "The methods that can be used to execute a program in the debugger are "
2543 "described in the next few sections."
2546 #: C/anjuta-manual.xml:142(title)
2547 msgid "Single stepping (step in)"
2550 #: C/anjuta-manual.xml:143(para)
2552 "Single stepping executes only one statement of the program (from the place "
2553 "where it has stopped) and then returns control. If the statement that is "
2554 "executed contains one or more functions, the debugger tries to step inside "
2555 "the functions (in the sequence in which the functions are executed). Once "
2556 "the statement is executed and control is passed back, it is possible to "
2557 "study the various program parameters."
2560 #: C/anjuta-manual.xml:150(para)
2561 msgid "If the program need to been started to use single stepping."
2564 #: C/anjuta-manual.xml:153(para)
2566 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2567 "guisubmenu><guimenuitem>Step In</guimenuitem></menuchoice> or click on the "
2568 "<guibutton>Step In</guibutton> icon in the <interface>Debug toolbar</"
2569 "interface> to step into a program."
2572 #: C/anjuta-manual.xml:162(title)
2573 msgid "Single stepping (step over)"
2576 #: C/anjuta-manual.xml:163(para)
2578 "<emphasis>Step over</emphasis> is similar to <emphasis>step in</emphasis>, "
2579 "except that it does not step inside any function in the statement being "
2580 "executed. The statement will be executed in one go."
2583 #: C/anjuta-manual.xml:168(para)
2585 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2586 "guisubmenu><guimenuitem>Step Over</guimenuitem></menuchoice> or click on the "
2587 "<guibutton>Step Over</guibutton> icon in the <interface>Debug toolbar</"
2588 "interface> to step over statements in a program."
2591 #: C/anjuta-manual.xml:175(para)
2593 "If a dynamic library is loaded during the step, the program will not stop at "
2594 "the end of the step. But it will run until it finds a breakpoint or you stop "
2598 #: C/anjuta-manual.xml:184(title)
2599 msgid "Single stepping (step out)"
2602 #: C/anjuta-manual.xml:185(para)
2604 "<emphasis>Step out</emphasis> will execute the current function until it "
2605 "returns. The program will be stopped once it exits from the function. Step "
2606 "out is not really single stepping, because it does not only execute a single "
2607 "statement — it executes the whole function until that function returns to "
2608 "the calling function."
2611 #: C/anjuta-manual.xml:192(para)
2613 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2614 "guisubmenu><guimenuitem>Step Out</guimenuitem></menuchoice> or click on the "
2615 "<guibutton>Step Out</guibutton> icon in the <interface>Debug toolbar</"
2616 "interface> to step out in a program."
2619 #: C/anjuta-manual.xml:201(title)
2620 msgid "Run/Continue"
2621 msgstr "Ejecutar/Seguir"
2623 #: C/anjuta-manual.xml:202(para)
2625 "This option will continue the execution of the program until a breakpoint is "
2626 "encountered, or the program exits."
2629 #: C/anjuta-manual.xml:206(para)
2631 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2632 "guisubmenu><guimenuitem>Run/Continue</guimenuitem></menuchoice> or click on "
2633 "the <guibutton>Run/Continue</guibutton> icon in the <interface>Debug "
2634 "toolbar</interface> to continue the execution of a program."
2637 #: C/anjuta-manual.xml:215(title)
2641 #: C/anjuta-manual.xml:216(para)
2643 "This option will continue the execution of the program until the line where "
2644 "cursor is is reached."
2647 #: C/anjuta-manual.xml:220(para)
2649 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2650 "guisubmenu><guimenuitem>Run to Cursor</guimenuitem></menuchoice> or click on "
2651 "the <guibutton>Run to Cursor</guibutton> icon in the <interface>Debug "
2652 "toolbar</interface> to run until the line at cursor is reached."
2655 #: C/anjuta-manual.xml:229(title)
2656 msgid "Stop Program"
2659 #: C/anjuta-manual.xml:230(para)
2661 "While the program is running and has control, no debugging tasks can be "
2662 "performed. To obtain control while the program is running, choose the menu "
2663 "item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Interrupt "
2664 "Program</guimenuitem></menuchoice> or click on the <guibutton>Stop Program</"
2665 "guibutton> icon in the <interface>Debug toolbar</interface>. This will "
2666 "interrupt the program and return control to the debugger."
2669 #: C/anjuta-manual.xml:245(title)
2671 msgstr "Puntos de parada"
2673 #: C/anjuta-manual.xml:246(para)
2675 "When debugging a program, it is useful to be able to stop the execution of "
2676 "the program at a particular point, so that the state of the program can be "
2677 "examined at that location. Breakpoints enable this to happen. Breakpoints "
2678 "can be set at different locations in a source file, and then the program is "
2679 "allowed to run. When a breakpoint is encountered, the execution of the "
2680 "program is suspended, enabling expressions to be evaluated, variables to be "
2681 "inspected, the stack trace to be studied, and so on."
2684 #: C/anjuta-manual.xml:256(title)
2685 msgid "Listing Breakpoints"
2688 #: C/anjuta-manual.xml:257(para)
2690 "The <interface>Breakpoint list window</interface> can be opened by choosing "
2691 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Breakpoints</"
2692 "guimenuitem></menuchoice>"
2695 #: C/anjuta-manual.xml:264(title) C/anjuta-manual.xml:266(screeninfo)
2696 msgid "Breakpoint view"
2699 #: C/anjuta-manual.xml:271(para)
2701 "<emphasis>Location</emphasis>, refers to the location of the code in the "
2702 "source file. <emphasis>Location</emphasis> can be specified in any of the "
2703 "following formats:"
2706 #: C/anjuta-manual.xml:278(para)
2707 msgid "File_name:Line_number"
2710 #: C/anjuta-manual.xml:279(para)
2711 msgid "Function_name"
2714 #: C/anjuta-manual.xml:280(para)
2715 msgid "File:Function_name"
2718 #: C/anjuta-manual.xml:283(para)
2720 "The first one is obvious — The location refers to the line number "
2721 "<emphasis>Line_number</emphasis> in the source file <emphasis>File</"
2722 "emphasis>. The second refers to the first line of the function "
2723 "<emphasis>Function_name</emphasis>. The third is similar to the second, "
2724 "except that this notation is used where there is more than one function with "
2725 "the name <emphasis>Function_name</emphasis> in the program. It is possible "
2726 "to differentiate between them by providing the <emphasis>File</emphasis>, so "
2727 "the notation refers to the function <emphasis>Function_name</emphasis> in "
2728 "the file <emphasis>File</emphasis>."
2731 #: C/anjuta-manual.xml:297(para)
2732 msgid "Break condition"
2733 msgstr "Condición de parada"
2735 #: C/anjuta-manual.xml:298(para)
2737 msgstr "Conteo de pasadas"
2739 #: C/anjuta-manual.xml:294(para)
2740 msgid "Two parameters can be associated with each breakpoint: <placeholder-1/>"
2741 msgstr "Se pueden asociar dos parámetros con cada punto de parada: <placeholder-1/>"
2743 #: C/anjuta-manual.xml:301(para)
2745 "The <emphasis>Break condition</emphasis> is a valid C expression which "
2746 "should evaluate to a Boolean value — that is, the evaluation of the "
2747 "expression should result in either TRUE(1) or FALSE(0). If the final "
2748 "evaluation value is not a Boolean value, then it will be appropriately type "
2749 "casted to a Boolean."
2752 #: C/anjuta-manual.xml:308(para)
2754 "Every time the breakpoint is encountered during the execution, the break "
2755 "condition will be evaluated. The debugger will break the execution only if "
2756 "the evaluation results in a TRUE value, otherwise it will continue the "
2757 "execution as though there had been no breakpoint."
2760 #: C/anjuta-manual.xml:314(para)
2762 "The default value of <emphasis>Break condition</emphasis> is always TRUE. "
2763 "The debugger will break the execution at the breakpoint location."
2765 "El valor predeterminado de la <emphasis>Condición de parada</emphasis> es "
2766 "siempre TRUE. El depurador parará la ejecución en la posición del punto de "
2769 #: C/anjuta-manual.xml:318(para)
2771 "The <emphasis>Pass count</emphasis> is an integer (unsigned) value which "
2772 "tells the debugger to skip the breakpoint that number of times before it is "
2773 "considered. <emphasis>Pass count</emphasis> has a higher priority than the "
2774 "<emphasis>Break condition</emphasis>. Only when the <emphasis>Pass count</"
2775 "emphasis> reaches zero will the debugger evaluate the <emphasis>Break "
2776 "condition</emphasis> (if any condition is present). If there is no "
2777 "condition, the debugger will break the execution once the <emphasis>Pass "
2778 "count</emphasis> counts down to zero."
2781 #: C/anjuta-manual.xml:328(para)
2783 "The default value of the <emphasis>Pass count</emphasis> is zero. The "
2784 "breakpoint will be considered when it is first encountered."
2786 "El valor predeterminado del <emphasis>Conteo de pasadas<emphasis> es cero. "
2787 "El punto de parada se considerará cuando se encuentre por primera vez."
2789 #: C/anjuta-manual.xml:333(para)
2791 "All breakpoints are kept across anjuta session even if they correspond to a "
2792 "non existing place. The interface try to set them each time the program is "
2793 "started or a new dynamic library is loaded."
2796 #: C/anjuta-manual.xml:342(title)
2797 msgid "Adding or Setting Breakpoints"
2798 msgstr "Añadir o establecer puntos de parada"
2800 #: C/anjuta-manual.xml:343(para)
2802 "Choose the menu item <menuchoice><guisubmenu>Debug</"
2803 "guisubmenu><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> or "
2804 "<menuchoice><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> in the "
2805 "breakpoint list popup menu to open the add breakpoint dialog."
2808 #: C/anjuta-manual.xml:351(title) C/anjuta-manual.xml:353(screeninfo)
2809 msgid "Breakpoint add dialog"
2810 msgstr "Diálogo de adición de punto de parada"
2812 #: C/anjuta-manual.xml:358(para)
2814 "Enter the location at which to set the breakpoint. Optionally, enter the "
2815 "<emphasis>Break condition</emphasis> and the <emphasis>Pass count</emphasis> "
2816 "in the appropriate entry boxes. Click <guibutton>OK</guibutton> to set the "
2820 #: C/anjuta-manual.xml:364(para)
2822 "A breakpoint may also be by selecting a line in the editor and choosing the "
2823 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Toggle "
2824 "Breakpoint</guimenuitem></menuchoice>, the editor popup menu item "
2825 "<menuchoice><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice> or the "
2826 "<guibutton>Toggle Breakpoint</guibutton> icon in the <interface>Debug "
2827 "toolbar</interface>."
2830 #: C/anjuta-manual.xml:374(para)
2832 "Breakpoints can be added even if the debugger is not started or in dynamic "
2833 "library not loaded yet. But they cannot be added while a program is running "
2834 "under control of the debugger."
2837 #: C/anjuta-manual.xml:383(title)
2838 msgid "Editing Breakpoints"
2839 msgstr "Editar puntos de parada"
2841 #: C/anjuta-manual.xml:384(para)
2843 "It is possible to change the condition of a breakpoint of the pass count by "
2844 "selecting the breakpoint to edit in the breakpoint list and click in the "
2845 "popup menu item <menuchoice><guimenuitem>Edit Breakpoint</guimenuitem></"
2849 #: C/anjuta-manual.xml:389(para)
2851 "Edit the entries as required and click on <guibutton>OK</guibutton> to "
2852 "commit the changes."
2854 "Edite las entradas como se requiere y pulse <guibutton>Aceptar</guibutton> "
2855 "para efectuar los cambios."
2857 #: C/anjuta-manual.xml:396(title)
2858 msgid "Deleting Breakpoints"
2859 msgstr "Borrar puntos de parada"
2861 #: C/anjuta-manual.xml:397(para)
2863 "Select the breakpoint to delete in the breakpoint list view and click on "
2864 "<menuchoice><guimenuitem>Remove Breakpoint</guimenuitem></menuchoice>."
2867 #: C/anjuta-manual.xml:401(para)
2869 "A existing breakpoint may also be deleted by selecting the line in the "
2870 "editor and choosing the menu item <menuchoice><guisubmenu>Debug</"
2871 "guisubmenu><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice>, the "
2872 "editor popup menu item <menuchoice><guimenuitem>Toggle Breakpoint</"
2873 "guimenuitem></menuchoice> or the <guibutton>Toggle Breakpoint</guibutton> "
2874 "icon in the <interface>Debug toolbar</interface>."
2877 #: C/anjuta-manual.xml:413(title)
2878 msgid "Enabling or Disabling Breakpoints"
2881 #: C/anjuta-manual.xml:414(para)
2883 "Click on the Enable column of the <interface>Breakpoint list window</"
2884 "interface> or in the menu item <menuchoice><guimenuitem>Enable Breakpoint</"
2885 "guimenuitem></menuchoice> to enable or disable the selected breakpoint. The "
2886 "breakpoint will be enabled or disabled, depending on the current state."
2889 #: C/anjuta-manual.xml:420(para)
2891 "To disable all breakpoints, click on <menuchoice><guisubmenu>Debug</"
2892 "guisubmenu><guimenuitem>Disable All Breakpoints</guimenuitem></menuchoice> "
2893 "or on <menuchoice><guimenuitem>Disable All Breakpoints</guimenuitem></"
2894 "menuchoice> in the breakpoint list popup menu."
2897 #: C/anjuta-manual.xml:431(title)
2901 #: C/anjuta-manual.xml:434(title)
2902 msgid "Listing local variable"
2905 #: C/anjuta-manual.xml:435(para)
2907 "When a program is running under the control of the debugger, the "
2908 "<interface>Locals list window</interface> can be opened by choosing "
2909 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Locals</guimenuitem></"
2913 #: C/anjuta-manual.xml:449(title) C/anjuta-manual.xml:451(screeninfo)
2914 msgid "Local variables"
2917 #: C/anjuta-manual.xml:441(para)
2919 "Local variables of the current frame (the current funtion in which the "
2920 "program control is present) are displayed in the <interface>Locals list "
2921 "window</interface>. During execution of the program (eg. during single "
2922 "stepping), local variables will be updated. If any varialble value was "
2923 "changed in the last debugging step, its value will be highlight in red. The "
2924 "variables are presented in a tree form for easy view. <placeholder-1/>"
2927 #: C/anjuta-manual.xml:456(para)
2929 "The value of a local variable can be modified by selecting it and clicking "
2930 "in the value column."
2933 #: C/anjuta-manual.xml:461(para)
2935 "Gdb is more and more often used as a back end for a graphical front end. It "
2936 "has been improved recently in this area. It is recommanded to use the latest "
2937 "version (6.6) of gdb. On older version, gdb can crash when the front end ask "
2938 "for an pointer with an invalid (but not used) value."
2941 #: C/anjuta-manual.xml:471(title)
2942 msgid "Listing watched expressions"
2945 #: C/anjuta-manual.xml:472(para)
2947 "Inspecting or evaluating an expression provides the result only once. To "
2948 "continuously monitor some variables or expressions, use <emphasis>expression "
2952 #: C/anjuta-manual.xml:476(para)
2954 "Choose the menu item <menuchoice><guisubmenu>View</"
2955 "guisubmenu><guimenuitem>Watch Window</guimenuitem></menuchoice> to display "
2956 "the <interface>expression watch window</interface>."
2959 #: C/anjuta-manual.xml:483(title)
2960 msgid "Adding an expression to watch"
2963 #: C/anjuta-manual.xml:484(para)
2965 "Right-click on the <interface>expression watch window</interface> to open "
2966 "the <interface>Operation menu</interface>. Choose the menu item "
2967 "<guimenuitem>Add Watch…</guimenuitem>. Alternatively, you can use "
2968 "<menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Add Watch…</"
2969 "guimenuitem></menuchoice> A dialog prompting for the expression will appear. "
2970 "Enter the expression and click <guibutton>OK</guibutton>."
2973 #: C/anjuta-manual.xml:493(para)
2975 "By default watch expression are updated automatically each time the program "
2976 "is stopped. This can be changed in the add watch dialog or later using the "
2977 "<guimenuitem>Automatic update</guimenuitem> menu item in the "
2978 "<interface>expression watch window</interface> popup menu. A watched "
2979 "expression can be update manually by choosing <guimenuitem>Update Watch</"
2980 "guimenuitem> or <guimenuitem>Update All</guimenuitem> in the previous menu."
2983 #: C/anjuta-manual.xml:502(para)
2985 "It is not necessary to have the debugger running to add a new watch "
2986 "expression. If the debugger is not running or the corresponding expression "
2987 "cannot be found, the front end will try to create the watch expression, each "
2988 "time the program is stopped."
2991 #: C/anjuta-manual.xml:511(title)
2992 msgid "Removing an expression from watch"
2995 #: C/anjuta-manual.xml:512(para)
2997 "Select the watch expression that you want to remove in the "
2998 "<interface>expression watch window</interface>, then open the "
2999 "<interface>Operation menu</interface>, clicking with the right mouse button, "
3000 "and choose the menu item <guimenuitem>Remove</guimenuitem> to remove it."
3003 #: C/anjuta-manual.xml:518(para)
3005 "All watch can be removed by choosing <guimenuitem>Remove All</guimenuitem> "
3006 "in the popup menu of the <interface>expression watch window</interface>."
3009 #: C/anjuta-manual.xml:525(title)
3010 msgid "Evaluating expressions"
3013 #: C/anjuta-manual.xml:526(para)
3015 "When control is returned from a program — possibly at a breakpoint — it is "
3016 "possible to evaluate expressions or inspect the values of variables in the "
3017 "program. Choose the menu item <menuchoice><guisubmenu>Debug</"
3018 "guisubmenu><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice>, "
3019 "<menuchoice><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice> in "
3020 "the popup menu of the editor or click the <guibutton>Inspect</guibutton> "
3021 "button on the <interface>Debug Toolbar</interface>."
3024 #: C/anjuta-manual.xml:535(para)
3025 msgid "A window will appear showing the result of the evaluation."
3028 #: C/anjuta-manual.xml:538(para)
3030 "If an expression is highlighted in the editor, it is already displayed else "
3031 "the window is empty. In both cases, you an select a new expression by "
3032 "clicking on the name column and writing the new expression."
3035 #: C/anjuta-manual.xml:543(para)
3037 "The expression can be added directly in the list of watched expressions by "
3038 "clicking on <guibutton>Add</guibutton> button."
3041 #: C/anjuta-manual.xml:553(title)
3042 msgid "Stack Trace and Thread"
3045 #: C/anjuta-manual.xml:556(title)
3046 msgid "Stack Window"
3047 msgstr "Ventana de pila"
3049 #: C/anjuta-manual.xml:557(para)
3051 "The <interface>Stack trace window</interface> shows the contents of the "
3052 "program stack. It lists all of the functions and their arguments in the "
3053 "sequence they were called. There is also a number representing each call. "
3054 "This number is called the <emphasis>Frame</emphasis>. Each call in the trace "
3055 "exists in a different frame. This starts from frame 0 (the last function "
3056 "called) and grows higher as the function nesting become deeper."
3059 #: C/anjuta-manual.xml:565(para)
3061 "Choose the menu item <menuchoice><guisubmenu>View</"
3062 "guisubmenu><guimenuitem>Program Stack</guimenuitem></menuchoice>, to open "
3063 "the stack trace for the program being debugged."
3066 #: C/anjuta-manual.xml:572(title) C/anjuta-manual.xml:574(screeninfo)
3067 msgid "Stack trace window"
3070 #: C/anjuta-manual.xml:579(para)
3072 "A small arrow points to the currently selected frame in the stack trace. By "
3073 "default, this will be frame 0, the last function called. All of the "
3074 "evaluation and inspection of expressions or variables will be with reference "
3075 "to this selected frame. The scope of the variables or expressions being "
3076 "evaluated will be limited to the selected frame only. The same applies for "
3077 "new expressions only in the watch."
3080 #: C/anjuta-manual.xml:589(title)
3081 msgid "Setting the current frame"
3084 #: C/anjuta-manual.xml:590(para)
3086 "Double-clicking on any frame in the stack trace will set that frame as the "
3087 "currently selected frame (the arrow will point to the frame, indicating that "
3088 "it has been selected as the current frame). Alternatively, open the "
3089 "<interface>Operation menu</interface> by right-clicking on the "
3090 "<interface>Stack trace window</interface>, and choose the menu item "
3091 "<guimenuitem>Set frame</guimenuitem> to set the frame."
3094 #: C/anjuta-manual.xml:598(para)
3096 "Changing the stack frame will change the <interface>Locals list window</"
3097 "interface> content, but not the <interface>expression watch window</"
3098 "interface> as each expression is evaluated in the frame used when it was "
3102 #: C/anjuta-manual.xml:606(title)
3103 msgid "Thread Window"
3106 #: C/anjuta-manual.xml:607(para)
3108 "The <interface>Thread window</interface> show all threads used by the "
3109 "program and display the current thread. Choose the menu item "
3110 "<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Thread</guimenuitem></"
3111 "menuchoice>, to open this window."
3114 #: C/anjuta-manual.xml:612(para)
3116 "A small arrow points to the current thread. When the programm is stopped, it "
3117 "correspond to the thread which has been interrupted. Each thread has its own "
3118 "stack frame,so changing the current thread will change the current stack "
3122 #: C/anjuta-manual.xml:621(title)
3123 msgid "Setting the current thread"
3126 #: C/anjuta-manual.xml:622(para)
3128 "Double-clicking on any thread in the thread list will set that thread as the "
3129 "currently selected thread (the arrow will point to the thread, indicating "
3130 "that it has been selected as the current thread). Alternatively, open the "
3131 "<interface>Operation menu</interface> by right-clicking on the "
3132 "<interface>Thread list window</interface>, and choose the menu item "
3133 "<guimenuitem>Set thread</guimenuitem> to set the thread."
3136 #: C/anjuta-manual.xml:630(para)
3138 "Changing the thread will change the value of CPU registers and the current "
3139 "stack frame, so the <interface>Locals list window</interface> will change "
3143 #: C/anjuta-manual.xml:639(title)
3147 #: C/anjuta-manual.xml:642(title)
3148 msgid "Register window"
3149 msgstr "Ventana de registros"
3151 #: C/anjuta-manual.xml:643(para)
3153 "It is possible to examine the contents of the internal registers of the CPU "
3154 "(microprocessor). Choose the menu item <menuchoice><guisubmenu>View</"
3155 "guisubmenu><guimenuitem>Registers</guimenuitem></menuchoice>. A window "
3156 "listing all of the available registers in the microprocessor and their "
3157 "corresponding contents will appear."
3159 "Es posible examinar el contenido de los registros internos de la CPU "
3160 "(microprocesador). Elija el elemento del menú <menuchoice><guisubmenu>Ver</"
3161 "guisubmenu><guimenuitem>Registros</guimenuitem></menuchoice>. Aparecerá una "
3162 "ventana listando todos los registros disponibles en el microprocesador y su "
3163 "correspondiente contenido."
3165 #: C/anjuta-manual.xml:650(para)
3167 "If any register value was changed in the last debugging step, its value will "
3168 "be highlight in red. It is possible to change one register value by "
3169 "selecting it and clicking in the value column."
3171 "Si cualquier valor de un registro se cambió en el último paso de depuración, "
3172 "su valor se resaltará en rojo. Es posible cambiar el valor de un registro "
3173 "seleccionándolo y pulsando en la columna de valor."
3175 #: C/anjuta-manual.xml:658(title)
3176 msgid "Memory window"
3177 msgstr "Ventana de memoria"
3179 #: C/anjuta-manual.xml:659(para)
3181 "Choose the menu item <menuchoice><guisubmenu>View</"
3182 "guisubmenu><guimenuitem>Memory </guimenuitem></menuchoice>, to open the "
3183 "<interface>memory window</interface> for the program being debugged. This "
3184 "window shows the contents of all memory."
3186 "Elija el elemento del menú <menuchoice><guisubmenu>Ver</"
3187 "guisubmenu><guimenuitem>Memoria</guimenuitem></menuchoice> para abrir la "
3188 "<interface>ventana de memoria</interface> para el programa que se está "
3189 "depurando. Esta ventana muestra el contenido de toda la memoria."
3191 #: C/anjuta-manual.xml:664(para)
3193 "The first is the memory address in hexadecimal, the second is the memory "
3194 "content in hexadecimal too and the last column is the memory content in "
3197 "Lo primero son las direcciones de memoria en hexadecimal, lo segundo es el "
3198 "contenido de la memoria en hexadecimal y la última columna es el contenido "
3199 "de la memoria en ASCII."
3201 #: C/anjuta-manual.xml:668(para)
3203 "The addressing space of even a 32 bits microprocessor is quite big(4 Giga "
3204 "bytes), so it is very difficult to go to a particular address with the "
3205 "scrollbar. But you can click on the right mouse button, get a new menu and "
3206 "select <menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to "
3207 "get a small edit box where you can enter an address in hexadecimal."
3210 #: C/anjuta-manual.xml:678(title)
3211 msgid "Disassembly window"
3214 #: C/anjuta-manual.xml:679(para)
3216 "Choose the menu item <menuchoice><guisubmenu>View</"
3217 "guisubmenu><guimenuitem>Disassembly </guimenuitem></menuchoice>, to open the "
3218 "<interface>disassembly window</interface> for the program being debugged. "
3222 #: C/anjuta-manual.xml:685(para)
3224 "The first column is the address in hexadecimal. In the second column, you "
3225 "can have a label starting at the beginning of the line and ended with a "
3226 "colon or a assembler instruction starting after 4 space characters."
3229 #: C/anjuta-manual.xml:690(para)
3231 "Again, as the addressing space is very big, the scrollbar is quite useless. "
3232 "You can click on the right mouse button, get a new menu and select "
3233 "<menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> to get a "
3234 "small edit box where you can enter an address in hexadecimal. The position "
3235 "in the disassembly window will be changed to the program counter value when "
3236 "the program is stopped."
3239 #: C/anjuta-manual.xml:703(title)
3243 #: C/anjuta-manual.xml:705(para)
3245 "There are a number of other debugger features used less frequently and not "
3246 "very well integrated in the new front end but which are still working."
3248 "Existe cierto número de características del depurador que se no se usan tan "
3249 "frecuentemente y no están muy bien integradas en el nuevo front-end pero se "
3250 "está trabajando en ello."
3252 #: C/anjuta-manual.xml:711(title)
3253 msgid "Dynamically loaded Libraries"
3254 msgstr "Bibliotecas cargadas dinámicamente"
3256 #: C/anjuta-manual.xml:712(para)
3258 "To obtain a list of the dynamic libraries used by the program, choose the "
3259 "menu item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
3260 "guisubmenu><guimenuitem>Shared Libraries</guimenuitem></menuchoice>. This "
3261 "will bring open a window which will list all the shared libraries the "
3262 "program has loaded and their locations in the memory. It also shows whether "
3263 "the symbol table is loaded or not (Yes/No)."
3265 "Para obtener una lista de las bibliotecas usadas dinámicamente por el "
3266 "programa, elija el elemento del menú <menuchoice><guisubmenu>Depurar</"
3267 "guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Bibliotecas "
3268 "compartidas</guimenuitem></menuchoice>. Esto abrirá una nueva ventana que "
3269 "listará todas las bibliotecas compartidas que el programa ha cargado y sus "
3270 "ubicaciones en la memoria. También muestra si la tabla de símbolos se ha "
3271 "cargado o no (Sí/No)."
3273 #: C/anjuta-manual.xml:722(title) C/anjuta-manual.xml:724(screeninfo)
3274 msgid "Shared Libraries window"
3275 msgstr "Ventana de bibliotecas compartidas."
3277 #: C/anjuta-manual.xml:732(title)
3278 msgid "Kernel Signals"
3279 msgstr "Señales del núcleo"
3281 #: C/anjuta-manual.xml:733(para)
3283 "Kernel signals are a way of signaling between processes in Linux. The list "
3284 "of signals available for a program can be displayed by choosing the menu "
3285 "item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
3286 "guisubmenu><guimenuitem>Kernel Signals</guimenuitem></menuchoice>. A window "
3287 "will open which lists all of the signals available in the system along with "
3288 "a brief description of each signal."
3290 "Las señales del núcleo son una forma de señalizar procesos en Linux. La "
3291 "lista de señales disponibles para un programa se puede mostrar eligiendo el "
3292 "elemento del menú <menuchoice><guisubmenu>Depurar</"
3293 "guisubmenu><guisubmenu>Información<menuchoice><guisubmenu>Señales del "
3294 "núcleo</guisubmenu><guisubmenu>. Se abrirá una ventana listando todas las "
3295 "señales disponibles en el sistema junto con una breve descripción de cada "
3298 #: C/anjuta-manual.xml:742(title) C/anjuta-manual.xml:744(screeninfo)
3299 msgid "Kernel Signals window"
3300 msgstr "Ventana de señales del núcleo"
3302 #: C/anjuta-manual.xml:749(para)
3303 msgid "There are three columns which specify what to do when the signal is received:"
3304 msgstr "Existen tres columnas que especifican qué hacer cuando se recibe una señal:"
3306 #: C/anjuta-manual.xml:755(para)
3308 "<emphasis>Stop</emphasis> — this tells the debugger whether to stop the "
3309 "program execution (and return control) when the program receives this signal."
3311 "<emphasis>Parar</emphasis>; esto le dice al depurador si debe parar la "
3312 "ejecución del programa (y devolver el control) cuando el programa recibe "
3315 #: C/anjuta-manual.xml:761(para)
3317 "<emphasis>Print</emphasis> — this tells the debugger whether to display the "
3320 "<emphasis>Imprimir</emphasis>; esto de dice al depurador si debe mostrar la "
3323 #: C/anjuta-manual.xml:766(para)
3325 "<emphasis>Pass</emphasis> — this tells the debugger whether to pass the "
3326 "signal to the program."
3328 "<emphasis>Pasar</emphasis>; esto le dice al depurador si debe pasar la señal "
3331 #: C/anjuta-manual.xml:772(para)
3333 "The popup menu that is displayed when you click on the right mouse button "
3334 "has all its item disabled because the corresponding functions are not "
3337 "El menú emergente que se muestra al pulsar con el botón derecho del ratón "
3338 "tiene todos sus elementos desactivados porque las funciones correspondientes "
3339 "no están aún implementadas."
3341 #: C/anjuta-manual.xml:781(title)
3342 msgid "Information about used files"
3343 msgstr "Información acerca de archivos usados"
3345 #: C/anjuta-manual.xml:782(para)
3347 "It is possible to get some information about the files used by the debugged "
3348 "program. by choosing the menu item <menuchoice><guisubmenu>Debug</"
3349 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Target files</"
3350 "guimenuitem></menuchoice>. A window will open displaying all informations."
3352 "Es posible obtener alguna información acerca de los archivos usados por el "
3353 "programa depurado, eligiendo el elemento del menú "
3354 "<menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</"
3355 "guisubmenu><guimenuitem>Información de archivos objetivo</guimenuitem></"
3356 "menuchoice>. Se abrirá una ventana mostrando toda la información."
3358 #: C/anjuta-manual.xml:791(title)
3359 msgid "Information about debugged program"
3360 msgstr "Información acerca del programa depurado"
3362 #: C/anjuta-manual.xml:792(para)
3364 "It is possible to get some information about the debugged program by "
3365 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3366 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Program</"
3367 "guimenuitem></menuchoice>. A window will open displaying all informations."
3369 "Es posible obtener alguna información acerca del programa depurado eligiendo "
3370 "el elemento del menú <menuchoice><guisubmenu>Depurar</"
3371 "guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Programa</"
3372 "guimenuitem></menuchoice>. Se abrirá una ventana mostrando toda la "
3375 #: C/anjuta-manual.xml:801(title)
3376 msgid "Information about kernel structure"
3377 msgstr "Información acerca de la estructura del núcleo"
3379 #: C/anjuta-manual.xml:802(para)
3381 "It is possible to get some information kernel data on the current process by "
3382 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3383 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Kernel user "
3384 "struct</guimenuitem></menuchoice>. A window will open displaying all "
3387 "Es posible obtener alguna información de los datos del núcleo acerca de los "
3388 "procesos actuales eligiendo el elemento del menú "
3389 "<menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</"
3390 "guisubmenu><guimenuitem>Información del user struct del núcleo</"
3391 "guimenuitem></menuchoice>. Se abrirá una ventana mostrando toda la "
3394 #: C/anjuta-manual.xml:811(title)
3395 msgid "Information about global variables"
3396 msgstr "Información acerca de las variables globales"
3398 #: C/anjuta-manual.xml:812(para)
3400 "It is possible to list all global variables by choosing the menu item "
3401 "<menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Information</"
3402 "guisubmenu><guimenuitem>Info Global Variable</guimenuitem></menuchoice>. A "
3403 "window will open listing all global variables."
3405 "Es posible listar todas las variables globales eligiendo el elemento del "
3406 "menú <menuchoice><guisubmenu>Depurar</guisubmenu><guisubmenu>Información</"
3407 "guisubmenu><guimenuitem>Info variables globales</guimenuitem></menuchoice>. "
3408 "Se abrirá una ventana listando todas las variables globales."
3410 #: C/anjuta-manual.xml:821(title)
3411 msgid "Information about the current frame"
3412 msgstr "Información acerca del marco actual"
3414 #: C/anjuta-manual.xml:822(para)
3416 "It is possible to obtain information about the currently selected frame by "
3417 "choosing the menu item <menuchoice><guisubmenu>Debug</"
3418 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Info Current "
3419 "Frame</guimenuitem></menuchoice>. A window will open describing the current "
3422 "Es posible obtener información acerca del marco actualmente seleccionado "
3423 "eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</"
3424 "guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Marco actual</"
3425 "guimenuitem></menuchoice>. Se abrirá una ventana describiendo el marco "
3428 #: C/anjuta-manual.xml:831(title)
3429 msgid "Information about the current function arguments"
3430 msgstr "Información acerca de los argumentos actuales de la función"
3432 #: C/anjuta-manual.xml:832(para)
3434 "It is possible to obtain information about the arguments of the current "
3435 "function by choosing the menu item <menuchoice><guisubmenu>Debug</"
3436 "guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Arguments</"
3437 "guimenuitem></menuchoice>. A window will open describing the arguments."
3439 "Es posible obtener información acerca de los argumentos de la función actual "
3440 "eligiendo el elemento del menú <menuchoice><guisubmenu>Depurar</"
3441 "guisubmenu><guisubmenu>Información</guisubmenu><guimenuitem>Argumentos</"
3442 "guimenuitem></menuchoice>. Se abrirá una ventana describiendo los argumentos."
3444 #: C/anjuta-manual.xml:841(title)
3445 msgid "User command"
3446 msgstr "Comando de usuario"
3448 #: C/anjuta-manual.xml:842(para)
3450 "To send directly a command to the back end choose the menu item "
3451 "<menuchoice><guimenu>Debug</guimenu><guimenuitem>Debugger command</"
3452 "guimenuitem></menuchoice>. This will bring a small dialog where you can "
3453 "enter commands that will be send to the debugger when you press "
3454 "<keycap>Return</keycap>."
3456 "Para enviar directamente un comando al «backend» elija el elemento del menú "
3457 "<menuchoice><guimenu>Depurar</guimenu><guimenuitem>Comando del depurador</"
3458 "guimenuitem></menuchoice>. Se mostrará un pequeño diálogo donde podrá "
3459 "introducir los comandos que se enviarán al depurador cuando pulse "
3460 "<keycap>Intro</keycap>."
3462 #: C/anjuta-manual.xml:850(para)
3464 "The front end sends this command directly to the back end without doing any "
3465 "check. By example if you set a breakpoint like this, it will not appear in "
3466 "the <interface>breakpoint list window</interface>. It is better to avoid "
3467 "using this command unless you know exactly what you are doing."
3469 "El «frontend» envía este comando directamente al «backend» sin ninguna "
3470 "comprobación. Por ejemplo, si establece un punto de parada como este, no "
3471 "aparecerá en la <interface>ventana de lista de puntos de parada</interface>. "
3472 "Es mejor evitar el uso de este comando a no ser que sepa exactamente qué "
3475 #: C/anjuta-manual.xml:3(title)
3477 msgstr "Preferencias"
3479 #: C/anjuta-manual.xml:4(para)
3481 "Preferences are ways to customize <application>anjuta</application> to suit "
3482 "your tastes. Activate <menuchoice><guimenu>Settings</"
3483 "guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> to bring up the "
3484 "preferences dialog. If you want to reset the preferences to their default "
3485 "values, it can be done from <menuchoice><guimenu>Settings</"
3486 "guimenu><guimenuitem> Set Default Preferences</guimenuitem></menuchoice>. "
3487 "Some are explained below."
3489 "Las preferencias siempre son personalizables para que <application>Anjuta</"
3490 "application> se ajuste a sus gustos. Active <menuchoice><guimenu>Opciones</"
3491 "guimenu><guimenuitem>Preferencias</guimenuitem></menuchoice> para mostrar el "
3492 "diálogo de preferencias. Si quiere restablecer las preferencias a los "
3493 "valores predeterminados, puede hacerlo desde <menuchoice><guimenu>Opciones</"
3494 "guimenu><guimenuitem>Preferencias predeterminadas</guimenuitem></"
3495 "menuchoice>. Algunas se explican debajo."
3497 #: C/anjuta-manual.xml:11(title)
3501 #: C/anjuta-manual.xml:13(para)
3503 "<emphasis>Project Directory</emphasis> is the path where you plan to put all "
3504 "your projects. Application wizard creates new projects in this directory "
3505 "only. The default project directory is ~/Projects and generally, this is "
3506 "just fine for most people. Also, when Open project is activated, this is the "
3507 "base directory where the file selectior will start."
3509 "<emphasis>Directorio del proyecto:</emphasis> Es la ruta donde planea poner "
3510 "todos sus proyectos. El asistente de aplicación crea los nuevos proyectos "
3511 "sólo en este directorio. El directorio de proyecto predeterminado es ~/"
3512 "Projects y generalmente es suficiente para la mayoría de las personas. "
3513 "Además, cuando Abrir proyecto está activado, es el directorio base donde el "
3514 "selector de archivos comenzará."
3516 #: C/anjuta-manual.xml:20(para)
3518 "<emphasis>User Info:</emphasis> Provide your correct Name and Email address "
3519 "here. They are not used to do software registration (pun), rather they are "
3520 "used to create ChangeLog entries and other insert text bits."
3522 "<emphasis>Información del usuario:</emphasis> Proporciona su nombre y "
3523 "dirección de correo electrónico. No se utilizan para registrar el software, "
3524 "sino para crear entradas en el archivo ChangeLog e insertar otros bits de "
3527 #: C/anjuta-manual.xml:27(title)
3528 msgid "File Manager"
3529 msgstr "Gestor de archivos"
3531 #: C/anjuta-manual.xml:29(para)
3533 "<emphasis>Root directory if no project is open</emphasis> is the path where "
3534 "the root of the file manager points to if no project is currently open."
3536 "<emphasis>Directorio raíz si no hay un proyecto abierto</emphasis> es la "
3537 "ruta donde apunta la raíz del gestor de archivos si actualmente no hay "
3538 "ningún proyecto abierto."
3540 #: C/anjuta-manual.xml:34(para)
3542 "<emphasis>File Filter:</emphasis> It is possible to filter out some file "
3543 "from the file tree, for example hidden files or files that are ignored by "
3544 "the version control system which usually means they are generated at build "
3545 "time and should not be changed."
3547 "<emphasis>Filtro de archivos:</emphasis> Es posible filtrar algunos archivos "
3548 "del árbol de archivos, por ejemplo los archivos ocultos o los archivos "
3549 "ignorados por el sistema de control de versiones que generalmente significa "
3550 "que se general durante la compilación y no se deberían cambiar."
3552 #: C/anjuta-manual.xml:3(title)
3553 msgid "User-defined Tools"
3554 msgstr "Herramientas definidas por el usuario"
3556 #: C/anjuta-manual.xml:7(para)
3558 "Often, you'll find the inbuilt functionality provided by Anjuta to be "
3559 "insufficient. In these cases, you might be tempted to either add the feature "
3560 "yourself to the Anjuta codebase or submit a feature request to implement the "
3561 "feature. However, both approaches are likely to be slow and problematic, "
3562 "especially if your tool is a specialized one. In these circumstances, it is "
3563 "advisable to use the Anjuta tools framework instead."
3565 "A menudo encontrará que las funcionalidades propias proporcionadas por "
3566 "Anjuta son insuficientes. En estos casos, puede que esté tentado a añadir la "
3567 "característica al código fuente de Anjuta usted mismo o enviar una petición "
3568 "de implementación de característica. No obstante, ambos casos suelen ser "
3569 "lentos y problemáticos, especialmente si su herramienta es especializada. "
3570 "Bajo estas circunstancias, es mejor usar el entorno de trabajo de las "
3571 "herramientas de Anjuta."
3573 #: C/anjuta-manual.xml:16(para)
3575 "Anjuta provides a powerful framework for defining user-defined tools for "
3576 "extending it's functionality. Tools have access to almost all features of "
3577 "the IDE through the use of variables. You can add tools under any menu item, "
3578 "specify input, output and error redirection within the GUI framework and "
3579 "supply command line parameters to the tool."
3581 "Anjuta proporciona un potente entorno de trabajo para definir herramientas "
3582 "definidas por el usuario para extender su funcionalidad. Las herramientas "
3583 "acceden a casi todas las características del EID a través del uso de "
3584 "variables. Puede añadir herramientas bajo cualquier elemento del menú, "
3585 "entradas específicas, salidas y redirecciones de errores dentro del entorno "
3586 "de trabajo del IGU así como proporcionar parámetros de la línea de comandos "
3589 #: C/anjuta-manual.xml:24(para)
3590 msgid "The tools plugin has to be enabled to use this feature!"
3592 "El complemento de herramientas debe estar activado para usar esta "
3595 #: C/anjuta-manual.xml:31(title)
3596 msgid "Tools Examples"
3597 msgstr "Ejemplos de herramientas"
3599 #: C/anjuta-manual.xml:32(para)
3601 "This is a simple example how to use the tools plugin to integrate the GNOME "
3602 "ChangeLog generation script"
3604 "Este es un simple ejemplo de cómo usar el complemento de herramientas para "
3605 "integrar el script generador de registro de cambios de GNOME."
3607 #: C/anjuta-manual.xml:38(title) C/anjuta-manual.xml:40(screeninfo)
3608 msgid "The tool editor"
3609 msgstr "La herramienta de edición"
3611 #: C/anjuta-manual.xml:2(title)
3615 #: C/anjuta-manual.xml:3(para)
3617 "The <application>Anjuta</application> project was founded by Naba Kumar. "
3618 "Please visit <ulink type=\"http\" url=\"http://anjuta.org?page=authors/"
3619 "\">this online list</ulink> to know all Anjuta contributors."
3621 "Naba Kumar fundó el proyecto <application>Anjuta</application>. Visite "
3622 "<ulink type=\"http\" url=\"http://anjuta.org?page=authors/\">esta lista en "
3623 "línea</ulink> para conocer todos los contribuidores de Anjuta."
3625 #: C/anjuta-manual.xml:10(para)
3627 "For more information on <application>Anjuta</application>, please visit the "
3628 "project website at <ulink type=\"http\" url=\"http://anjuta.org/\">http://"
3629 "anjuta.org</ulink>. Bug reports should be made using the Bug Tracker at the "
3630 "project development site <ulink type=\"http\" url=\"http://www.sourceforge."
3631 "net/projects/anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>"
3633 "Para obtener más información acerca de <application>Anjuta</application>, "
3634 "visite la página web del proyecto en <ulink type=\"http\" url=\"http://"
3635 "anjuta.org/\">http://anjuta.orghttp://anjuta.org. Los informes de error se "
3636 "deben rellenar usando Bug Tracker en la página web de desarrollo del "
3637 "proyecto en <ulink type=\"http\" url=\"http://www.sourceforge.net/projects/"
3638 "anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>."
3640 #: C/anjuta-manual.xml:18(para)
3642 "This manual was written by Naba Kumar and Andy Piper. Please send all "
3643 "comments and suggestions regarding this manual to Anjuta Devel list "
3644 "<email>anjuta-devel@list.sourceforge.net</email>. Comments may also be "
3645 "submitted via the project trackers at SourceForge."
3647 "Naba Kumar y Andy Piper escribieron este manual. Envíe cualquier comentario "
3648 "y sugerencia acerca de este manual a la lista de desarrollo de Anjuta "
3649 "<email>anjuta-devel@list.sourceforge.net</email>. También se pueden enviar "
3650 "comentarios a traes de la página del proyecto en SourceForge."
3652 #: C/anjuta-manual.xml:2(title)
3656 #: C/anjuta-manual.xml:3(para)
3658 "This program is free software; you can redistribute it and/or modify it "
3659 "under the terms of the <ulink type=\"ghelp\" url=\"gnome-help:gpl\">GNU "
3660 "General Public License</ulink> as published by the Free Software Foundation; "
3661 "either version 2 of the License, or (at your option) any later version."
3663 "Este programa es software libre; puede redistribuirlo y/o modificarlo bajo "
3664 "los términos de la <ulink type=\"ghelp\" url=\"gnome-help:gpl\">Licencia "
3665 "Pública General GNU</ulink> tal como la publica la Free Software Foundation; "
3666 "tanto en la versión 2 de la Licencia, o (a su opción) cualquier otra versión "
3669 #: C/anjuta-manual.xml:10(para)
3671 "This program is distributed in the hope that it will be useful, but WITHOUT "
3672 "ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or "
3673 "FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public "
3674 "License</citetitle> for more details."
3676 "Este programa se distribuye con la esperanza de que le sea útil, pero SIN "
3677 "NINGUNA GARANTÍA; sin incluso la garantía implícita de MERCANTILIDAD o "
3678 "IDONEIDAD PARA UN PROPÓSITO PARTICULAR. Vea la <citetitle>Licencia Pública "
3679 "General GNU</citetitle> para más detalles."
3681 #: C/anjuta-manual.xml:16(para)
3683 "A copy of the <citetitle>GNU General Public License</citetitle> is included "
3684 "as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also "
3685 "obtain a copy of the <citetitle>GNU General Public License</citetitle> from "
3686 "the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://"
3687 "www.fsf.org\"> their Web site</ulink> or by writing to <address> Free "
3688 "Software Foundation, Inc. <street>51 Franklin Street</street> Fifth Floor "
3689 "<city>Boston</city>, <state>MA</state><postcode>02110-1301</"
3690 "postcode><country>USA</country></address>"
3692 "Una copia de la <citetitle>Licencia Pública General GNU</citetitle> está "
3693 "incluidacomo un apéndice de la <citetitle>Guía del usuario de GNOME</"
3694 "citetitle>. También puede obtener una copia de la <citetitle>Licencia "
3695 "Pública General GNU</citetitle> a través de la Free Software Foundation "
3696 "visitando <ulink type=\"http\" url=\"http://www.fsf.org\">su página web</"
3697 "ulink> o escribiendo a la <address> Free Software Foundation, Inc. "
3698 "<street>51 Franklin Street</street> Fifth Floor <city>Boston</city>, "
3699 "<state>MA</state><postcode>02110-1301</postcode><country>EE. UU.</country></"
3702 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
3703 #: C/anjuta-manual.xml:0(None)
3704 msgid "translator-credits"
3705 msgstr "Jorge González <jorgegonz@svn.gnome.org>, 2007"