msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2022-02-11 12:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Put one translator per line, in the form NAME , YEAR1, YEAR2 msgctxt "_" msgid "translator-credits" msgstr "" #. (itstool) path: info/desc #: C/index.page:8 msgid "Help for Anjuta DevStudio." msgstr "" #. (itstool) path: info/title #: C/index.page:9 msgctxt "link" msgid "Anjuta" msgstr "" #. (itstool) path: info/title #: C/index.page:10 msgctxt "text" msgid "Anjuta DevStudio" msgstr "" #. (itstool) path: credit/name #: C/index.page:14 #: C/anjuta-code-assist.page:13 #: C/anjuta-code-help.page:14 #: C/anjuta-code-indentation.page:14 #: C/anjuta-code-symbols.page:13 msgid "Johannes Schmid" msgstr "" #. (itstool) path: media/span #: C/index.page:24 msgid "Anjuta logo" msgstr "" #. (itstool) path: page/title #: C/index.page:23 msgid "<_:media-1/> Anjuta DevStudio" msgstr "" #. (itstool) path: section/title #: C/index.page:29 msgid "Project Management" msgstr "" #. (itstool) path: section/title #: C/index.page:33 msgid "Coding and code navigation" msgstr "" #. (itstool) path: section/title #: C/index.page:37 msgid "Building Project" msgstr "" #. (itstool) path: section/title #: C/index.page:41 msgid "Debugging Program" msgstr "" #. (itstool) path: section/title #: C/index.page:51 msgid "Reference" msgstr "" #. (itstool) path: info/desc #: C/anjuta-code-assist.page:9 msgid "Configure and use the integrated editor features" msgstr "" #. (itstool) path: page/title #: C/anjuta-code-assist.page:18 msgid "Autocompletion and calltips" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-assist.page:21 msgid "Autocompletion" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-assist.page:22 msgid "Autocompletion automatically suggests functions and other code symbols after you start typing by trying to match existing symbols with the first characters typed. It will popup a drop-down menu where you can select a match by using the Enter key. Normally this happens automatically after you typed the third (non-whitespace) character but you can also force it by using the EditAuto-Complete menu item." msgstr "" #. (itstool) path: note/p #: C/anjuta-code-assist.page:31 msgid "Anjuta supports autocompletion for code written in C/C++, Vala, Javascript and Python. Note that autocompletion can only work if anjuta knows about the symbols used. If you are using C/C++ libraries that are not configured using pkg-config and/or not added to the project configuration, anjuta won't be able to find those symbols and autocompletion might not work." msgstr "" #. (itstool) path: note/p #: C/anjuta-code-assist.page:38 msgid "In addition some syntax might be too complex for the integrated parser and it might not be able to detect which completion is required" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-assist.page:44 msgid "Effective coding using calltips" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-assist.page:46 msgid "As it is usually quite hard to remember the signature of every method or function used in a project, the editor will automatically display a small tooltip whenever you type '(' after a function name and show you the signature." msgstr "" #. (itstool) path: info/desc #: C/anjuta-code-help.page:9 msgid "Quickly find the information you need in the API documentation" msgstr "" #. (itstool) path: page/title #: C/anjuta-code-help.page:19 msgid "Using the API reference" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-help.page:22 msgid "Browsing the API reference" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-help.page:24 msgid "For a quick access to the API reference of libraries, anjuta features an integrated API browser. If not already done it can be activated in the preferences (EditPreferences) in GeneralPlugins by choosing the DevHelp plugin." msgstr "" #. (itstool) path: section/p #: C/anjuta-code-help.page:30 msgid "The API reference has two windows, one for searching for a specific symbol and the browser for viewing the help documents." msgstr "" #. (itstool) path: section/title #: C/anjuta-code-help.page:36 msgid "Jump to the API reference using shortcuts in the editor" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-help.page:38 msgid "In case you are unsure how a specific function used in existing code works, simply place the cursor on the function name and use ShiftF1 (or HelpContext-Help) to jump to the documentation." msgstr "" #. (itstool) path: info/desc #: C/anjuta-code-indentation.page:9 msgid "Configure and use automatic indentation for a consistent coding style" msgstr "" #. (itstool) path: page/title #: C/anjuta-code-indentation.page:19 msgid "Auto-indentation" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-indentation.page:22 msgid "Configuring and using auto-indentation" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-indentation.page:25 msgid "Manual configuration" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-indentation.page:27 msgid "Automatic indentation is configured in the preferences (EditPreferences) in the tab corresponding to the used programming language. The indentation width for several types of statements can be set there." msgstr "" #. (itstool) path: section/p #: C/anjuta-code-indentation.page:32 msgid "The big disadvantage of manually configuring indentation is that all developers working on a project must use the same settings or it will result if different styles used in the same files. For a better solution, see the next section." msgstr "" #. (itstool) path: note/p #: C/anjuta-code-indentation.page:38 msgid "Unless explicitly changed in the preferences the indentation settings found in the Modeline of a file will be used instead of the configured settings to keep the file consistent." msgstr "" #. (itstool) path: section/title #: C/anjuta-code-indentation.page:45 msgid "Modelines" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-indentation.page:47 msgid "Modelines are used to help editors to automatically detect the indentation mode which should be used for a particular file. They are especially useful if many developers work on the same project and use different environments." msgstr "" #. (itstool) path: section/p #: C/anjuta-code-indentation.page:51 msgid "Anjuta supports modelines in the two formats used by Vim and Emacs." msgstr "" #. (itstool) path: section/title #: C/anjuta-code-indentation.page:59 msgid "Indenting blocks of code" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-indentation.page:61 msgid "Normally new lines are appropriately indented automatically but you can indent existing lines or all selected code with the EditAuto-Indent menu item." msgstr "" #. (itstool) path: info/desc #: C/anjuta-code-symbols.page:9 msgid "Efficient ways to navigate through source code" msgstr "" #. (itstool) path: page/title #: C/anjuta-code-symbols.page:18 msgid "Code navigation using the symbol browser" msgstr "" #. (itstool) path: section/title #: C/anjuta-code-symbols.page:21 msgid "Using the symbol browser" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-symbols.page:22 msgid "The symbol browser allows you to get an overview over the symbols used in your project. Symbols refers to variables, functions/methods and classes here and the exact definition depends on the programming language used." msgstr "" #. (itstool) path: section/p #: C/anjuta-code-symbols.page:26 msgid "The symbol browser has three tabs:" msgstr "" #. (itstool) path: item/p #: C/anjuta-code-symbols.page:28 msgid "File shows the symbols of the current file in the editor" msgstr "" #. (itstool) path: item/p #: C/anjuta-code-symbols.page:29 msgid "Project shows all symbols of the project" msgstr "" #. (itstool) path: item/p #: C/anjuta-code-symbols.page:30 msgid "Search lets you search the symbols in the project (use CtrlL to jump directly to the search box)" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-symbols.page:34 msgid "Double click on jumps to the definition of the symbol in the editor." msgstr "" #. (itstool) path: section/title #: C/anjuta-code-symbols.page:38 msgid "Navigating in the editor" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-symbols.page:39 msgid "In the Goto popup-menu of the editor there two items that help you to quickly navigate through the source code:" msgstr "" #. (itstool) path: item/p #: C/anjuta-code-symbols.page:43 msgid "Symbol definition" msgstr "" #. (itstool) path: item/p #: C/anjuta-code-symbols.page:44 msgid "Symbol declaration" msgstr "" #. (itstool) path: section/p #: C/anjuta-code-symbols.page:47 msgid "If you want to go back to the position in the editor where you used the shown items in the Goto menu you can use the Previous history (and Next history) items in the same menu." msgstr "" #. (itstool) path: info/desc #: C/autotools-project-backend.page:8 msgid "Autotools project backend." msgstr "" #. (itstool) path: credit/name #: C/autotools-project-backend.page:12 #: C/autotools-project-folder-edit.page:13 #: C/autotools-project-root-edit.page:14 #: C/autotools-project-target-edit.page:13 #: C/autotools-project-target-type.page:12 #: C/autotools-build-build.page:15 #: C/autotools-build-clean.page:15 #: C/autotools-build-compile.page:15 #: C/autotools-build-configure-dialog.page:15 #: C/autotools-build-configure.page:15 #: C/autotools-build-distribute.page:15 #: C/autotools-build-install.page:15 #: C/autotools-build-plugin.page:12 #: C/autotools-build-preferences-dialog.page:14 #: C/debug-breakpoint-dialog.page:14 #: C/debug-breakpoint.page:13 #: C/debug-cpu.page:13 #: C/debug-custom.page:13 #: C/debug-data.page:13 #: C/debug-execute.page:13 #: C/debug-expression.page:13 #: C/debug-information.page:13 #: C/debug-local.page:13 #: C/debug-process-dialog.page:13 #: C/debug-run.page:15 #: C/debug-stack.page:13 #: C/debug-step.page:13 #: C/debug-tips.page:13 #: C/debug-watch.page:13 #: C/directory-project-backend.page:12 #: C/language-support-cpp-modelines-emacs.page:13 #: C/language-support-cpp-modelines-vim.page:13 #: C/makefile-project-backend.page:12 #: C/project-import.page:15 #: C/project-manager-folder-add.page:13 #: C/project-manager-folder.page:15 #: C/project-manager-folder-remove.page:13 #: C/project-manager-library-add.page:14 #: C/project-manager-library.page:17 #: C/project-manager-library-remove.page:14 #: C/project-manager-module-add.page:14 #: C/project-manager-module-new.page:16 #: C/project-manager-module-remove.page:14 #: C/project-manager-package-remove.page:13 #: C/project-manager.page:12 #: C/project-manager-root.page:16 #: C/project-manager-source-add.page:13 #: C/project-manager-source.page:16 #: C/project-manager-source-remove.page:13 #: C/project-manager-target-add.page:13 #: C/project-manager-target.page:16 #: C/project-manager-target-remove.page:13 #: C/project-manager-treeview.page:12 #: C/project-wizard-create.page:14 #: C/project-wizard-template.page:13 #: C/run-parameters-dialog.page:15 #: C/run-run.page:15 #: C/widget-index.page:11 msgid "Sébastien Granjoux" msgstr "" #. (itstool) path: credit/name #: C/autotools-project-backend.page:16 #: C/autotools-build-build.page:19 #: C/debug-breakpoint-dialog.page:18 #: C/debug-breakpoint.page:17 #: C/debug-cpu.page:17 #: C/debug-custom.page:17 #: C/debug-expression.page:17 #: C/debug-information.page:17 #: C/debug-local.page:17 #: C/debug-process-dialog.page:17 #: C/debug-run.page:19 #: C/debug-stack.page:17 #: C/debug-step.page:17 #: C/debug-tips.page:17 #: C/debug-watch.page:17 #: C/directory-project-backend.page:16 #: C/full-index.page:11 #: C/makefile-project-backend.page:16 #: C/project-import.page:19 #: C/project-manager-library-add.page:18 #: C/project-manager-library-remove.page:18 #: C/project-manager-module-add.page:18 #: C/project-manager-module-new.page:20 #: C/project-manager-module-remove.page:18 #: C/project-manager-package-remove.page:17 #: C/project-manager.page:16 #: C/project-manager-source-add.page:17 #: C/project-manager-source-remove.page:17 #: C/project-manager-target-add.page:17 #: C/project-manager-target-remove.page:17 #: C/project-wizard-create.page:18 #: C/project-wizard-template.page:17 #: C/run-run.page:19 msgid "Philip Chimento" msgstr "" #. (itstool) path: page/title #: C/autotools-project-backend.page:21 msgid "GNU Autotools project backend plugin" msgstr "" #. (itstool) path: page/p #: C/autotools-project-backend.page:23 msgid "This is the most common project format on Linux. It has been designed to distribute source code packages on a wide range of Unix-like systems. If you have ever installed a program using configure, make and make install, you probably have already used it as a user." msgstr "" #. (itstool) path: page/p #: C/autotools-project-backend.page:31 msgid "It is typically a bit more difficult to use as a developer. However, it is the default backend for Anjuta, which has features that make it easier to use. All the project manager's features are enabled when using it. You should be able to maintain a project using the Autotools backend without writing a line in configure.ac or any Makefile.am files." msgstr "" #. (itstool) path: note/p #: C/autotools-project-backend.page:41 msgid "Autotools files give more information than a makefile, but the backend does not support all the possible tricks. If you find a project that cannot be read correctly, filing a bug report will be appreciated. In the meantime, as a workaround, you can use the directory project backend instead. It is much more limited but should find all source files." msgstr "" #. (itstool) path: info/desc #: C/autotools-project-folder-edit.page:9 msgid "Edit autotools folder properties." msgstr "" #. (itstool) path: page/title #: C/autotools-project-folder-edit.page:18 msgid "Edit an Autotools Folder" msgstr "" #. (itstool) path: page/p #: C/autotools-project-folder-edit.page:20 msgid "These properties allows you to define common properties for all targets belonging to this folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:25 #: C/autotools-project-target-edit.page:30 msgid "C compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:26 msgid "The flags to pass to the C compiler if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:30 #: C/autotools-project-target-edit.page:35 msgid "C preprocessor flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:31 msgid "These flags are passed to every compilation that invokes the C preprocessor. This value is ignored if these flags are defined for the target." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:36 #: C/autotools-project-target-edit.page:41 msgid "C++ compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:37 msgid "The flags to pass to the C++ compiler flags if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:41 #: C/autotools-project-target-edit.page:58 msgid "Fortran compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:42 msgid "The flags to pass to the Fortran 9x compiler if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:46 msgid "Installation directories" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:47 msgid "This defines installation directories. It is needed if you want to install files in custom directories." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:51 #: C/autotools-project-target-edit.page:76 msgid "Java compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:52 msgid "The flags to pass to the Java compiler if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:56 #: C/autotools-project-target-edit.page:87 msgid "Lex/Flex compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:57 msgid "The flags to pass to the scanner generator Lex or Flex if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:61 #: C/autotools-project-target-edit.page:100 msgid "Linker flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:62 msgid "The flags to pass to the linker if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:65 #: C/autotools-project-target-edit.page:111 msgid "Objective C compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:66 msgid "The flags to pass to the Objective C compiler if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:70 #: C/autotools-project-target-edit.page:117 msgid "Vala compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:71 msgid "The flags to pass to the Vala compiler if a per target value is not defined." msgstr "" #. (itstool) path: item/title #: C/autotools-project-folder-edit.page:75 #: C/autotools-project-target-edit.page:123 msgid "Yacc/Bison compiler flags" msgstr "" #. (itstool) path: item/p #: C/autotools-project-folder-edit.page:76 msgid "The flags to pass to the parser generator Bison or Yacc if a per target value is not defined." msgstr "" #. (itstool) path: info/desc #: C/autotools-project-root-edit.page:10 msgid "Edit autotools project properties." msgstr "" #. (itstool) path: page/title #: C/autotools-project-root-edit.page:19 msgid "Edit Autotools Project Properties" msgstr "" #. (itstool) path: page/p #: C/autotools-project-root-edit.page:21 msgid "These are the properties of the root item." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:25 msgid "Backend" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:26 msgid "This the project backend used by the project: Autotools. Another backend can be selected by clicking on this button. It can be useful if the current backend has some troubles to parse your project files." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:32 msgid "Name" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:33 msgid "The name of your project. It can contains space." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:36 msgid "Version" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:37 msgid "This is the project version." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:40 msgid "Bug report URL" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:41 msgid "This is an URL allowing to send bug report, by example an email address or a link to a bug tracker. It is optional." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:45 msgid "Package name" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:46 msgid "This is the name of distribution package, it shouldn't contain spaces. It is optional." msgstr "" #. (itstool) path: item/title #: C/autotools-project-root-edit.page:50 msgid "URL" msgstr "" #. (itstool) path: item/p #: C/autotools-project-root-edit.page:51 msgid "This is the home page of the project. It is optional." msgstr "" #. (itstool) path: page/p #: C/autotools-project-root-edit.page:55 msgid "In addition, the root item works as a folder and has all its properties. See to see the list." msgstr "" #. (itstool) path: info/desc #: C/autotools-project-target-edit.page:9 msgid "Edit autotools target properties." msgstr "" #. (itstool) path: page/title #: C/autotools-project-target-edit.page:18 msgid "Edit an Autotools Target" msgstr "" #. (itstool) path: page/p #: C/autotools-project-target-edit.page:20 msgid "Here is a list of all target properties used in autotools project. Some of them are not available on all targets." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:25 msgid "Build for check only" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:26 msgid "If checked, this target is not installed and has to be built only when running checks." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:31 msgid "The flags to pass to the C compiler when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:36 msgid "These flags are passed to every compilation that invokes the C preprocessor. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:42 msgid "The flags to pass to the C++ compiler flags when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:47 msgid "Do not install" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:48 msgid "If checked, this target is not installed. It can be used for utilities used to build other target or programs used only by developers." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:53 msgid "Do not use prefix" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:54 msgid "If checked, do not add prefix to manual page and executable. Such prefix are used to provide alternative of system tools." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:59 msgid "The flags to pass to the Fortran 9x compiler when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:64 msgid "Include in distribution" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:65 msgid "If checked, include the target in the distribution package." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:68 msgid "Installation directory" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:69 msgid "It defines where the target is installed. It is not directly the directory where the files are installed but the name of one of the standard directory variable (bindir, sbindir, libdir, libexecdir, datadir, pkgdatadir, pkglibexecdir, includedir, mandir, infodir, docdir) or a custom variable defined in the folder properties." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:77 msgid "The flags to pass to the Java compiler when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:82 msgid "Keep target path" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:83 msgid "If checked, keep the hierarchy of the project directory when installing files." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:88 msgid "The flags to pass to the scanner generator Lex or Flex when generating target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:93 msgid "Libraries" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:94 msgid "Specify additional libraries used by the target. Useful for adding non package libraries. See Add non-packaged libraries page for more details." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:101 msgid "The flags to pass to the linker when linking the target. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-edit.page:105 msgid "Manual section" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:106 msgid "Specify the section of the manual where to add man page. Valid section name are the digits ‘0’ through ‘9’, and the letters ‘l’ and ‘n’." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:112 msgid "The flags to pass to the Objective C compiler when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:118 msgid "The flags to pass to the Vala compiler when compiling target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-edit.page:124 msgid "The flags to pass to the parser generator Bison or Yacc when generating target source files. This value overrides the one eventually defined in the parent folder." msgstr "" #. (itstool) path: info/desc #: C/autotools-project-target-type.page:8 msgid "Autotools target type." msgstr "" #. (itstool) path: page/title #: C/autotools-project-target-type.page:17 msgid "Autotools project type" msgstr "" #. (itstool) path: page/p #: C/autotools-project-target-type.page:19 msgid "There are different types of target available." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:23 msgid "Shared Library (Libtool)" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:24 msgid "It represents a library shared by several programs which is linked at run time. It is the most common kind of libraries on Linux. It is called dynamic link library on Windows." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:27 msgid "It uses the Libtool package. Its name must start with 'lib' and has the '.la' extension." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:31 msgid "Module (Libtool)" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:32 msgid "It represents a library, often named a plugin, linked at run time explicitly by the program itself. It is used to only load the code corresponding to the used features." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:35 msgid "It uses the Libtool package. Its name does not need the 'lib' prefix but must have the '.la' extension." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:39 msgid "Static Library (Libtool)" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:40 msgid "It represents a library linked with the program at compile time. Only the function used are kept inside the generated executable." msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:42 msgid "It uses the Libtool package. Its name must start with 'lib' and has the '.a' extension." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:46 msgid "Program" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:47 msgid "It represents compiled program by example from C source files. All children represent the source files compiled to generate the program." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:52 msgid "Python module" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:53 msgid "It represents a program written in Python." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:56 msgid "Java module" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:57 msgid "It represents a program written in Java." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:60 msgid "LISP module" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:61 msgid "It represents a program written in LISP." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:64 msgid "Header files" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:65 msgid "This target allows you to group header files and define where they have to be installed." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:69 msgid "Man documentation" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:70 msgid "It groups man pages needed by the project." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:73 msgid "Info documentation" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:74 msgid "It groups info page needed by the project." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:77 msgid "Miscellaneous Data" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:78 msgid "It groups data files which needed by the project like pictures, ui description, settings files..." msgstr "" #. (itstool) path: item/title #: C/autotools-project-target-type.page:82 msgid "Script" msgstr "" #. (itstool) path: item/p #: C/autotools-project-target-type.page:83 msgid "It represents program those are scripts. Those scripts are only installed in the specified directory. If scripts are generated additional rules are needed." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-build.page:11 msgid "Build targets or project." msgstr "" #. (itstool) path: page/title #: C/autotools-build-build.page:24 msgid "Build targets" msgstr "" #. (itstool) path: page/p #: C/autotools-build-build.page:25 msgid "A target is a file created from source files. Typically, it is a program or a library, but it could also be documentation if the documentation needs processing, for example." msgstr "" #. (itstool) path: page/p #: C/autotools-build-build.page:30 msgid "The build command compiles all needed source files, and possibly links them with some other files, like libraries, in order to create the target. If some source files are already compiled and haven't been modified, they are not be recompiled, in order to save time. There are several ways to trigger a build." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:39 msgid "From the main menu, select Build Build or press F7 to build all targets in the same directory as the currently opened file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:48 msgid "From the main menu, select Build Build Project or press ShiftF7 to build the complete project. All subdirectories are built recursively." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:57 #: C/autotools-build-clean.page:45 #: C/autotools-build-install.page:50 msgid "From the file manager pane, select a file or a directory." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:62 msgid "Click on the right mouse button to make the file manager context menu appear and select BuildBuild to build all targets in the directory currently selected or the parent directory of the currently selected file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:72 #: C/autotools-build-clean.page:60 #: C/autotools-build-install.page:65 msgid "From the project manager pane, select a source file or a target." msgstr "" #. (itstool) path: item/p #: C/autotools-build-build.page:77 msgid "Click on the right mouse button to make the project manager context menu appear and select BuildBuild to build all targets in the directory containing the currently selected file or target." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-clean.page:11 msgid "Remove built files." msgstr "" #. (itstool) path: page/title #: C/autotools-build-clean.page:20 msgid "Clean targets" msgstr "" #. (itstool) path: page/p #: C/autotools-build-clean.page:22 msgid "It can be useful to delete all files created by the build process. For example, if all dependencies are not taken into account and a modified file does not trigger a recompiling as it should, deleting all files will fix this. There are several ways to do this" msgstr "" #. (itstool) path: item/p #: C/autotools-build-clean.page:28 msgid "From the main menu, select Build Clean to delete all files built in the same directory as the current edited file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-clean.page:37 msgid "From the main menu, select Build Clean Project to delete all project built files," msgstr "" #. (itstool) path: item/p #: C/autotools-build-clean.page:50 msgid "Click on the right mouse button to make the file manager context menu appears and select BuildClean to delete all files built in the directory currently selected or the parent directory of the currently selected file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-clean.page:65 msgid "Click on the right mouse button to make the project manager context menu appears and select BuildClean to delete all built files in the directory containing the currently selected file or target." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-compile.page:11 msgid "Compile files." msgstr "" #. (itstool) path: page/title #: C/autotools-build-compile.page:20 msgid "Compile files" msgstr "" #. (itstool) path: page/p #: C/autotools-build-compile.page:22 msgid "Most programming languages allow you to compile an individual source file. It reads the file, checks for errors and convert into an intermediate object file. Most errors happens in this step, so it is useful to compile a file after modifying it to check for errors. There are several ways to do it." msgstr "" #. (itstool) path: item/p #: C/autotools-build-compile.page:30 msgid "From the main menu, select Build Compile or press F9 to compile the current edited file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-compile.page:39 msgid "From the file manager pane, select a file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-compile.page:44 msgid "Click on the right mouse button to make the file manager context menu appears and select BuildCompile to compile the file currently selected in the file manager pane." msgstr "" #. (itstool) path: item/p #: C/autotools-build-compile.page:53 msgid "From the project manager pane, select a source file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-compile.page:58 msgid "Click on the right mouse button to make the project manager context menu appears and select BuildCompile to compile the file currently selected in the project manager pane." msgstr "" #. (itstool) path: note/p #: C/autotools-build-compile.page:66 msgid "You do not need to save your file before compiling it, it will be done automatically by Anjuta if needed." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-configure-dialog.page:11 msgid "Autotools configure dialog" msgstr "" #. (itstool) path: page/title #: C/autotools-build-configure-dialog.page:20 msgid "Autotools Configure Dialog" msgstr "" #. (itstool) path: page/p #: C/autotools-build-configure-dialog.page:22 msgid "The Configure dialog allows you to set the following options and configure the project." msgstr "" #. (itstool) path: item/title #: C/autotools-build-configure-dialog.page:29 msgid "Regenerate Project" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure-dialog.page:30 msgid "If checked, the project will be completely regenerated, else only the configure step is done. Anjuta automatically checks this check box when needed so you can leave it in its current state." msgstr "" #. (itstool) path: item/title #: C/autotools-build-configure-dialog.page:37 msgid "Configuration" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure-dialog.page:38 msgid "You can have several configurations having their own options and build directory, this text box allows to name them. Typically you have already defined a Default configuration, a Debug configuration making programs easier to debug (keeping intermediate variables and code ordering) and an Optimized configuration generating faster programs but increasing build time. You can define additional custom configurations." msgstr "" #. (itstool) path: item/title #: C/autotools-build-configure-dialog.page:49 msgid "Build Directory" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure-dialog.page:50 msgid "Select here the build directory. It can be the project directory or a subdirectory. This is particularly useful when switching between different configurations to avoid rebuilding the whole project." msgstr "" #. (itstool) path: note/p #: C/autotools-build-configure-dialog.page:56 msgid "With autotools, you cannot have one configuration using a different directory if you already have one configuration using the project directory. You need to remove it first." msgstr "" #. (itstool) path: note/p #: C/autotools-build-configure-dialog.page:63 msgid "Some autotools project cannot be built outside the project directory. You can still use different configurations but they all have to use the project directory and everything will be recompiled on each change of the configuration." msgstr "" #. (itstool) path: item/title #: C/autotools-build-configure-dialog.page:72 msgid "Configure Options" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure-dialog.page:73 msgid "This text box list all command line arguments used by the configure step. All arguments are separated by spaces and must be quoted if they contains a space. Each configuration fills this text box with default values that you can modify." msgstr "" #. (itstool) path: note/p #: C/autotools-build-configure-dialog.page:80 msgid "Each autotools project supports a common list of arguments but can have specify arguments. You can have a list of all accepted arguments by running configure --help on the command line. You need to have configured your project at least one time to have the configure script." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-configure.page:11 msgid "Configure an autotools project and manage configurations." msgstr "" #. (itstool) path: page/title #: C/autotools-build-configure.page:20 msgid "Configure a project" msgstr "" #. (itstool) path: page/p #: C/autotools-build-configure.page:22 msgid "Before compiling and building files, an autotools project has to be configured. This step is needed to set global options, to check that all required libraries and programs are installed on your system and to generate appropriate build scripts." msgstr "" #. (itstool) path: section/title #: C/autotools-build-configure.page:30 msgid "Configure the project" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure.page:34 msgid "From the main menu, select Build Configure Project...." msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure.page:40 msgid "Keep the default configuration, select a new configuration or create a new one. You can inspect and modify all configuration options. See for more information." msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure.page:47 msgid "Click on Execute to configure the project." msgstr "" #. (itstool) path: section/p #: C/autotools-build-configure.page:53 msgid "The configuration could fail if some libraries or programs are not installed or do not have the right version. The error message tell you what is missing." msgstr "" #. (itstool) path: section/title #: C/autotools-build-configure.page:60 msgid "Change the configuration" msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure.page:64 msgid "From the main menu, select Build Select ConfigurationAnother configuration." msgstr "" #. (itstool) path: section/p #: C/autotools-build-configure.page:71 msgid "If the project has not been already configured, it will be automatically configured before building any file." msgstr "" #. (itstool) path: section/title #: C/autotools-build-configure.page:79 msgid "Remove configuration" msgstr "" #. (itstool) path: section/p #: C/autotools-build-configure.page:81 msgid "It is a like cleaning the project but it removes even more files. You need to re-configure your project to build it afterward." msgstr "" #. (itstool) path: item/p #: C/autotools-build-configure.page:88 msgid "From the main menu, select Build Remove Configuration." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-distribute.page:11 msgid "Create a distribution package." msgstr "" #. (itstool) path: page/title #: C/autotools-build-distribute.page:20 msgid "Create a distribution package" msgstr "" #. (itstool) path: page/p #: C/autotools-build-distribute.page:22 msgid "The standard way to distribute a autotools project is as a compressed tar archive containing all source files. The user will have to decompress it, then compile and install it on his system using the command sequence configure, make and make install." msgstr "" #. (itstool) path: item/p #: C/autotools-build-distribute.page:30 msgid "From the main menu, select Build Build Tarball to create a source distribution package." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-install.page:11 msgid "Install targets or project." msgstr "" #. (itstool) path: page/title #: C/autotools-build-install.page:20 msgid "Install targets" msgstr "" #. (itstool) path: page/p #: C/autotools-build-install.page:22 msgid "Unless your project is very simple, it needs some data files like user interface description files. These files are typically copied in standard directories and read from there. It means that you cannot run your program from the build directory. You need to install it in order to copy all these files in the final place, by example in a subdirectory of /usr/local." msgstr "" #. (itstool) path: page/p #: C/autotools-build-install.page:29 msgid "There are several possibilities to install targets or a project." msgstr "" #. (itstool) path: item/p #: C/autotools-build-install.page:33 msgid "From the main menu, select Build Install to install all files in the same directory as the current edited file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-install.page:42 msgid "From the main menu, select Build Install Project to install all project files," msgstr "" #. (itstool) path: item/p #: C/autotools-build-install.page:55 msgid "Click on the right mouse button to make the file manager context menu appears and select BuildInstall to install all files in the directory currently selected or the parent directory of the currently selected file." msgstr "" #. (itstool) path: item/p #: C/autotools-build-install.page:70 msgid "Click on the right mouse button to make the project manager context menu appears and select BuildInstall to install all files in the directory containing the currently selected file or target." msgstr "" #. (itstool) path: note/p #: C/autotools-build-install.page:79 msgid "If you install the program in a system directory, you can have to use su or sudo to have enough right. See for more information." msgstr "" #. (itstool) path: info/desc #. (itstool) path: page/title #: C/autotools-build-plugin.page:8 #: C/autotools-build-plugin.page:17 msgid "Autotools build plugin" msgstr "" #. (itstool) path: page/p #: C/autotools-build-plugin.page:19 msgid "This plugin is targeted at autotools projects but as they use make it is useful for other kind of projects using make." msgstr "" #. (itstool) path: section/title #: C/autotools-build-plugin.page:25 msgid "Make command used" msgstr "" #. (itstool) path: section/p #: C/autotools-build-plugin.page:26 msgid "Here is a list of the targets used by the plugin. They are implemented in all autotools projects but you need to implement them if you use a custom makefile." msgstr "" #. (itstool) path: item/title #: C/autotools-build-plugin.page:31 msgid "make object_file_name" msgstr "" #. (itstool) path: item/p #: C/autotools-build-plugin.page:32 msgid "Use to compile an source file. The object file name is found by replacing the source file extension with the corresponding object extension." msgstr "" #. (itstool) path: item/title #: C/autotools-build-plugin.page:36 msgid "make" msgstr "" #. (itstool) path: item/p #: C/autotools-build-plugin.page:37 msgid "Use to build all targets in a directory." msgstr "" #. (itstool) path: item/title #: C/autotools-build-plugin.page:40 msgid "make install" msgstr "" #. (itstool) path: item/p #: C/autotools-build-plugin.page:41 msgid "Use to install all targets in a directory." msgstr "" #. (itstool) path: item/title #: C/autotools-build-plugin.page:44 msgid "make clean" msgstr "" #. (itstool) path: item/p #: C/autotools-build-plugin.page:45 msgid "Use to delete all file built in a directory." msgstr "" #. (itstool) path: item/title #: C/autotools-build-plugin.page:48 msgid "make dist" msgstr "" #. (itstool) path: item/p #: C/autotools-build-plugin.page:49 msgid "Use to build a distribution package, called only in the project directory." msgstr "" #. (itstool) path: note/p #: C/autotools-build-plugin.page:54 msgid "As make comes with default rules allowing it to compile and link a C program without needing a makefile. You can compile a C program from a single source file without a makefile nor a project." msgstr "" #. (itstool) path: info/desc #: C/autotools-build-preferences-dialog.page:10 msgid "Autotools build preferences dialog." msgstr "" #. (itstool) path: page/title #: C/autotools-build-preferences-dialog.page:19 msgid "Autotools Build Preferences Dialog" msgstr "" #. (itstool) path: page/p #: C/autotools-build-preferences-dialog.page:21 msgid "The dialog allows you to set global options for building files." msgstr "" #. (itstool) path: item/title #: C/autotools-build-preferences-dialog.page:27 msgid "Run several commands at a time" msgstr "" #. (itstool) path: item/p #: C/autotools-build-preferences-dialog.page:28 msgid "make is able to run several compilations at the same time. It decreases build time when having a multi-core processor but could trigger some issues so this can be enabled or disabled with this check box." msgstr "" #. (itstool) path: item/title #: C/autotools-build-preferences-dialog.page:33 msgid "Continue on errors" msgstr "" #. (itstool) path: item/p #: C/autotools-build-preferences-dialog.page:34 msgid "By default make stops as soon as it gets an error, it can be faster to continue and get errors for all files in one step. You have to check this check box to get this behavior." msgstr "" #. (itstool) path: item/title #: C/autotools-build-preferences-dialog.page:39 msgid "Translate messages" msgstr "" #. (itstool) path: item/p #: C/autotools-build-preferences-dialog.page:40 msgid "By default errors and warnings message are translated. It has two drawbacks though. In order to recognize errors and warnings the translation of Anjuta and the compiler should perfectly match. Moreover, it is often more difficult to find help on the internet when searching translated messages as they are much less common. Unchecking this check box allows to disable translation." msgstr "" #. (itstool) path: item/title #: C/autotools-build-preferences-dialog.page:48 msgid "Highlight build warnings and errors in editor" msgstr "" #. (itstool) path: item/p #: C/autotools-build-preferences-dialog.page:49 msgid "Errors and warnings during the build are displayed and highlighted in the message window. By checking this option, they are highlighted in the editor too." msgstr "" #. (itstool) path: item/title #: C/autotools-build-preferences-dialog.page:54 msgid "Install as root" msgstr "" #. (itstool) path: item/p #: C/autotools-build-preferences-dialog.page:55 msgid "Installing a program needs to copy files into system directories which are often not writable by users. If this check box is checked, you can choose to use sudo or su before installing the files to acquire enough right to do it." msgstr "" #. (itstool) path: info/desc #: C/debug-breakpoint-dialog.page:10 msgid "Used to create or edit a breakpoint" msgstr "" #. (itstool) path: page/title #: C/debug-breakpoint-dialog.page:23 msgid "Breakpoint Dialog" msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint-dialog.page:27 msgid "Location" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:28 msgid "This is the position of the breakpoint. For an existing breakpoint, you cannot change this. You can set a breakpoint at a certain line number, or at the beginning of a function. Use one of the following formats:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:33 msgid "file_name:line_number" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:34 msgid "function_name" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:35 msgid "file_name:function_name" msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint-dialog.page:39 msgid "Condition" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:40 msgid "The break condition is an expression which should evaluate to a boolean value TRUE (1) or FALSE (0). Every time the breakpoint is encountered during your program's execution, the break condition will be evaluated. The debugger will break the execution only if the result of the evaluation is TRUE." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:45 msgid "If you leave this field blank the condition is always considered TRUE." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint-dialog.page:49 msgid "Pass Count" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:50 msgid "The debugger can also skip the breakpoint a certain number of times before breaking. If the pass count is not zero, then the debugger will have to encounter the breakpoint this number of times before breaking." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint-dialog.page:53 msgid "The pass count has a higher priority than the condition. Only when the pass count has been reached will the debugger evaluate the condition if it is present and break the program's execution." msgstr "" #. (itstool) path: info/desc #: C/debug-breakpoint.page:9 msgid "Managing breakpoints." msgstr "" #. (itstool) path: page/title #: C/debug-breakpoint.page:22 msgid "Breakpoints" msgstr "" #. (itstool) path: page/p #: C/debug-breakpoint.page:24 msgid "Breakpoints are used to stop the execution of the program at a particular point so that the state of the program can be examined at those locations." msgstr "" #. (itstool) path: section/title #: C/debug-breakpoint.page:28 msgid "Listing breakpoints" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:32 msgid "From the main menu, select View Breakpoints to open the Breakpoint window." msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:38 msgid "This view has the following columns:" msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:42 msgid "Location" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:43 msgid "This is the position of the breakpoint in the source file. When the breakpoint is set by the debugger, you can get additional information such as the function containing the breakpoint." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:48 #: C/debug-stack.page:79 msgid "Address" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:49 msgid "This field is filled with the address of the breakpoint when it is set by the debugger." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:53 #: C/debug-local.page:55 #: C/debug-watch.page:53 msgid "Type" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:54 msgid "This always displays breakpoint. It will be used in a future release supporting different kinds of breakpoints." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:58 msgid "Condition" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:59 msgid "This is the breakpoint condition. It is empty if no condition is defined." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:63 msgid "Pass count" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:64 msgid "When the debugger is not running, this column displays the pass count of the breakpoint, or zero if it is not defined." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:66 msgid "When the debugger is running, if the pass count is zero, this column displays the number of times this breakpoint has been triggered. If the pass count is not zero, both numbers are displayed. The pass count is the second number." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:72 msgid "State" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:73 msgid "This is the state of the breakpoint. It may be" msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:75 msgid "Pending:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:75 msgid "the breakpoint is not set in your program." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:76 msgid "Permanent:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:76 msgid "the breakpoint is set (its id number is displayed in parentheses)." msgstr "" #. (itstool) path: item/title #: C/debug-breakpoint.page:77 msgid "Temporary:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:77 msgid "the breakpoint is set but will be deleted if reached." msgstr "" #. (itstool) path: note/p #: C/debug-breakpoint.page:83 msgid "All breakpoints are kept across Anjuta sessions even if they correspond to a non-existing locations, for example in a source file of a shared library not loaded yet. In this case their states are set as pending." msgstr "" #. (itstool) path: section/title #: C/debug-breakpoint.page:90 msgid "Setting breakpoints" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:94 msgid "From the main menu, select Debug Add Breakpoint... or right click in the Breakpoint window and select Add Breakpoint...." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:100 msgid "Fill in the Location, which is the position of the breakpoint, and the other fields if desired. If a file is currently opened in the editor, the Location defaults to the current line. See for more information." msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:108 msgid "Another solution is to use the toggle breakpoint function. If there is no breakpoint on the current line, it will add one. Otherwise, it will remove it." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:114 msgid "From the main menu, select Debug Toggle Breakpoint or right click in the Editor window and select Toggle Breakpoint." msgstr "" #. (itstool) path: section/title #: C/debug-breakpoint.page:125 msgid "Editing breakpoints" msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:127 msgid "You can't change the location of a breakpoint; create a new breakpoint instead. However, you can change the break condition or the pass count. To edit a breakpoint:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:133 #: C/debug-breakpoint.page:160 msgid "Select a breakpoint in the Breakpoint window." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:136 msgid "Right click in the Breakpoint window and select Edit Breakpoint...." msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:141 msgid "Change the Condition or Pass Count fields and click on OK when you are done. See for more information." msgstr "" #. (itstool) path: section/title #: C/debug-breakpoint.page:151 msgid "Removing breakpoints" msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:153 msgid "You can remove a breakpoint using the toggle breakpoint function described above. However, if you want to remove more than one breakpoint or the breakpoint is in a different file than the one you are editing, you can use the breakpoint window:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:163 msgid "Right click in the Breakpoint window and select Remove Breakpoint." msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:169 msgid "To remove all breakpoints:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:173 msgid "From the main menu, select Debug Remove All Breakpoints or right-click in the Breakpoint window and select Remove All Breakpoints." msgstr "" #. (itstool) path: section/title #: C/debug-breakpoint.page:184 msgid "Enabling and disabling breakpoints" msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:186 msgid "Sometimes you might want to disable a breakpoint temporarily instead of deleting it altogether. To disable or re-enable a breakpoint:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:191 msgid "Click on the Enable checkmark in the Breakpoint window or right click in the Breakpoint window and select Enable Breakpoint or Disable Breakpoint." msgstr "" #. (itstool) path: section/p #: C/debug-breakpoint.page:197 msgid "You can disable all breakpoints using:" msgstr "" #. (itstool) path: item/p #: C/debug-breakpoint.page:201 msgid "From the main menu, select Debug Disable All Breakpoints or right-click in the Breakpoint window and select Disable All Breakpoints." msgstr "" #. (itstool) path: info/desc #: C/debug-cpu.page:9 msgid "Examine CPU information." msgstr "" #. (itstool) path: page/title #: C/debug-cpu.page:22 msgid "CPU" msgstr "" #. (itstool) path: section/title #: C/debug-cpu.page:25 msgid "View CPU registers" msgstr "" #. (itstool) path: item/p #: C/debug-cpu.page:29 msgid "From the main menu, select View Registers to open the Register window." msgstr "" #. (itstool) path: section/p #: C/debug-cpu.page:35 msgid "Registers whose values have changed since the last stop are in red. It is possible to change the value of any register by clicking in the value column and entering a new value." msgstr "" #. (itstool) path: section/title #: C/debug-cpu.page:42 msgid "View memory" msgstr "" #. (itstool) path: item/p #: C/debug-cpu.page:46 msgid "From the main menu, select View Memory to open the Memory window." msgstr "" #. (itstool) path: section/p #: C/debug-cpu.page:52 msgid "The first column displays memory addresses in hexadecimal, the second displays memory contents in hexadecimal and the last column shows memory contents in ASCII." msgstr "" #. (itstool) path: section/p #: C/debug-cpu.page:55 #: C/debug-cpu.page:82 msgid "The addressing space of even a 32-bit microprocessor is very large (4 gigabytes), so it is very difficult to go to a particular address with the scrollbar. But you can click the right mouse button and select Go to address to get a small edit box where you can enter an address in hexadecimal." msgstr "" #. (itstool) path: section/title #: C/debug-cpu.page:64 msgid "View Disassembly" msgstr "" #. (itstool) path: item/p #: C/debug-cpu.page:69 msgid "From the main menu, select View Disassembly to open the Disassembly window." msgstr "" #. (itstool) path: section/p #: C/debug-cpu.page:75 msgid "The first column displays addresses in hexadecimal. In the second column, you can have a label starting at the beginning of the line and ending with a colon or a assembly-language instruction indented by 4 space characters." msgstr "" #. (itstool) path: section/p #: C/debug-cpu.page:79 msgid "The position in the disassembly window will be changed to the program counter value when the program is stopped." msgstr "" #. (itstool) path: info/desc #: C/debug-custom.page:9 msgid "Use custom debugger command." msgstr "" #. (itstool) path: page/title #: C/debug-custom.page:22 msgid "Custom command" msgstr "" #. (itstool) path: page/p #: C/debug-custom.page:24 msgid "You can send a custom command to the debugger like this:" msgstr "" #. (itstool) path: item/p #: C/debug-custom.page:28 msgid "From the main menu, select Debug Debugger Command." msgstr "" #. (itstool) path: item/p #: C/debug-custom.page:32 msgid "Enter your command." msgstr "" #. (itstool) path: page/p #: C/debug-custom.page:36 msgid "The output of the command is displayed in the message window used by the debugger." msgstr "" #. (itstool) path: note/p #: C/debug-custom.page:40 msgid "The command is sent directly to the debugger without performing any checks. For example, if you set a breakpoint like this, it will not appear in the Breakpoint window. It is better to avoid using this command unless you know exactly what you are doing." msgstr "" #. (itstool) path: info/desc #: C/debug-data.page:9 msgid "Examine program Data." msgstr "" #. (itstool) path: page/title #: C/debug-data.page:18 msgid "Examine data" msgstr "" #. (itstool) path: info/desc #: C/debug-execute.page:9 msgid "Control program execution." msgstr "" #. (itstool) path: page/title #: C/debug-execute.page:18 msgid "Control execution" msgstr "" #. (itstool) path: info/desc #: C/debug-expression.page:9 msgid "Evaluate expressions and modify variables." msgstr "" #. (itstool) path: page/title #: C/debug-expression.page:22 msgid "Examine expressions" msgstr "" #. (itstool) path: section/title #: C/debug-expression.page:25 msgid "Inspect an expression and modify a variable" msgstr "" #. (itstool) path: section/p #: C/debug-expression.page:27 msgid "While you are debugging a program, you can find out the value of an expression or variable while the program is paused. It is also sometimes useful to change the value of a variable." msgstr "" #. (itstool) path: item/p #: C/debug-expression.page:33 msgid "From the main menu, select Debug Inspect/Evaluate... or right click in the Editor window and select Inspect/Evaluate...." msgstr "" #. (itstool) path: item/p #: C/debug-expression.page:38 msgid "If the expression is a variable name, you can change its value by clicking on the Value column and entering a new value." msgstr "" #. (itstool) path: info/desc #: C/debug-information.page:9 msgid "Examine additional program information." msgstr "" #. (itstool) path: page/title #: C/debug-information.page:22 msgid "Miscellaneous information" msgstr "" #. (itstool) path: page/p #: C/debug-information.page:24 msgid "The debugger can tell you various information about the program while it is running." msgstr "" #. (itstool) path: section/title #: C/debug-information.page:28 msgid "View shared libraries" msgstr "" #. (itstool) path: item/p #: C/debug-information.page:32 msgid "From the main menu, select Debug InfoShared Libraries." msgstr "" #. (itstool) path: section/p #: C/debug-information.page:37 msgid "This opens a window which will list all shared libraries the program has loaded and their locations in memory. It also shows whether each library's symbol table is loaded or not." msgstr "" #. (itstool) path: section/title #: C/debug-information.page:44 msgid "View signals" msgstr "" #. (itstool) path: item/p #: C/debug-information.page:48 msgid "From the main menu, select Debug InfoKernel signals." msgstr "" #. (itstool) path: section/p #: C/debug-information.page:53 msgid "This lists all available signals with a small description and three columns to specify what to do when a signal is received:" msgstr "" #. (itstool) path: item/title #: C/debug-information.page:58 msgid "Stop" msgstr "" #. (itstool) path: item/p #: C/debug-information.page:59 msgid "The debugger stops the program execution when the program receives this signal." msgstr "" #. (itstool) path: item/title #: C/debug-information.page:63 msgid "Print" msgstr "" #. (itstool) path: item/p #: C/debug-information.page:64 msgid "The debugger displays the received signal." msgstr "" #. (itstool) path: item/title #: C/debug-information.page:67 msgid "Pass" msgstr "" #. (itstool) path: item/p #: C/debug-information.page:68 msgid "The debugger passes the signal to the program." msgstr "" #. (itstool) path: note/p #: C/debug-information.page:73 msgid "The context menu that is displayed when you click the right mouse button has all its items disabled because the corresponding functions are not implemented yet." msgstr "" #. (itstool) path: info/desc #: C/debug-local.page:9 msgid "Examine local variables." msgstr "" #. (itstool) path: page/title #: C/debug-local.page:22 msgid "Local variables" msgstr "" #. (itstool) path: page/p #: C/debug-local.page:24 msgid "Local variables of the current frame (the current function in which the program control is present) are displayed in the Locals window. During execution of the program (e.g. during single stepping), local variables will be updated. If any variable value was changed in the last debugging step, its value will be highlighted in red. Variables are presented in a tree form for easy view." msgstr "" #. (itstool) path: section/title #: C/debug-local.page:32 msgid "Listing local variables" msgstr "" #. (itstool) path: item/p #: C/debug-local.page:36 msgid "From the main menu, select View Locals to open the Locals window." msgstr "" #. (itstool) path: section/p #: C/debug-local.page:42 msgid "All local variables are displayed in a tree view with children used to represent structure or array members." msgstr "" #. (itstool) path: item/title #: C/debug-local.page:47 #: C/debug-watch.page:45 msgid "Variable" msgstr "" #. (itstool) path: item/p #: C/debug-local.page:48 msgid "The name of the variable." msgstr "" #. (itstool) path: item/title #: C/debug-local.page:51 #: C/debug-watch.page:49 msgid "Value" msgstr "" #. (itstool) path: item/p #: C/debug-local.page:52 msgid "The variable value." msgstr "" #. (itstool) path: item/p #: C/debug-local.page:56 msgid "The type of the variable." msgstr "" #. (itstool) path: section/title #: C/debug-local.page:62 #: C/debug-watch.page:153 msgid "Changing the value of a variable" msgstr "" #. (itstool) path: item/p #: C/debug-local.page:66 msgid "In the Locals window, select the variable you want to edit and double click in the Value column." msgstr "" #. (itstool) path: item/p #: C/debug-local.page:70 msgid "Type the new value." msgstr "" #. (itstool) path: info/desc #: C/debug-process-dialog.page:9 msgid "Attach to process dialog" msgstr "" #. (itstool) path: page/title #: C/debug-process-dialog.page:22 msgid "Attach to Process Dialog" msgstr "" #. (itstool) path: page/p #: C/debug-process-dialog.page:24 msgid "The Attach to process dialog allows you to select a currently running process." msgstr "" #. (itstool) path: item/title #: C/debug-process-dialog.page:28 msgid "Hide paths" msgstr "" #. (itstool) path: item/p #: C/debug-process-dialog.page:29 msgid "This hides command paths in the process list if checked." msgstr "" #. (itstool) path: item/title #: C/debug-process-dialog.page:32 msgid "Hide process parameters" msgstr "" #. (itstool) path: item/p #: C/debug-process-dialog.page:33 msgid "This hides the command line arguments in the process list if checked." msgstr "" #. (itstool) path: item/title #: C/debug-process-dialog.page:36 msgid "Display process tree" msgstr "" #. (itstool) path: item/p #: C/debug-process-dialog.page:37 msgid "If unchecked, the processes are displayed in a list. If checked, the processes are displayed in a tree." msgstr "" #. (itstool) path: info/desc #: C/debug-run.page:11 msgid "Start a program with the debugger." msgstr "" #. (itstool) path: page/title #: C/debug-run.page:24 msgid "Debug a program" msgstr "" #. (itstool) path: section/title #: C/debug-run.page:27 msgid "Start a program in the debugger" msgstr "" #. (itstool) path: section/p #: C/debug-run.page:29 msgid "The current program is defined in the Program Parameters dialog. See for more information. This program can be started in the debugger like this:" msgstr "" #. (itstool) path: item/p #: C/debug-run.page:35 msgid "From the main menu, select Run Debug Program or press ShiftF12" msgstr "" #. (itstool) path: note/p #: C/debug-run.page:41 msgid "A program can be more difficult to debug if it is highly optimized or if debugging information is missing. Whether optimization and debugging information are enabled, is defined in the configure step. Normally, there is a Debug configuration available, that turns off optimization and includes all debugging information. Anjuta displays a warning if this configuration is not used. See for more information." msgstr "" #. (itstool) path: section/title #: C/debug-run.page:52 msgid "Debug an already running application" msgstr "" #. (itstool) path: section/p #: C/debug-run.page:54 msgid "The debugger can be used on an already running application." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:58 msgid "From the main menu, select Run Debug Process... to get a dialog listing all currently running processes." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:63 msgid "Select a process in the Attach to process dialog and click on Attach to start the debugger on this process. See for more details." msgstr "" #. (itstool) path: section/title #: C/debug-run.page:71 msgid "Debug a remote application" msgstr "" #. (itstool) path: section/p #: C/debug-run.page:73 msgid "The debugger can be used to debug an application running on another computer connected through a TCP or serial connection." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:78 msgid "From the main menu, select Run Debug Remote..." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:82 msgid "Select the type of the connection to the remote application, Serial Line Connection or TCP/IP Connection." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:86 msgid "For a TCP connection, fill in the Address and Port fields." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:88 msgid "For a serial connection, fill in the text box below with the serial device name, for example /dev/ttyb." msgstr "" #. (itstool) path: item/p #: C/debug-run.page:92 msgid "Click on Connect to start the debugger and connect to the remote target." msgstr "" #. (itstool) path: section/title #: C/debug-run.page:100 msgid "Stop the debugger" msgstr "" #. (itstool) path: section/p #: C/debug-run.page:102 msgid "The debugger and the program can be stopped at any time like this:" msgstr "" #. (itstool) path: item/p #: C/debug-run.page:106 msgid "From the main menu, select Run Stop Debugger." msgstr "" #. (itstool) path: info/desc #: C/debug-stack.page:9 msgid "Examine the stack." msgstr "" #. (itstool) path: page/title #: C/debug-stack.page:22 msgid "Stack" msgstr "" #. (itstool) path: section/title #: C/debug-stack.page:25 msgid "List stack frames" msgstr "" #. (itstool) path: section/p #: C/debug-stack.page:27 msgid "A stack frame is the area of the stack associated to each function call. It lists all functions and their arguments in the sequence they were called. Each stack frame is numbered starting from 0 for the current function. You can only view the stack frames while the debugger is running." msgstr "" #. (itstool) path: section/p #: C/debug-stack.page:32 msgid "Moreover, a program can be composed of several threads. Each thread is executed independently and has its own registers, stack and local variables, but shares all global variables." msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:38 msgid "From the main menu, select View Stack to open the Stack window." msgstr "" #. (itstool) path: section/p #: C/debug-stack.page:44 msgid "The stacks are displayed in a tree view having their corresponding thread as parent and displaying the following information:" msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:49 msgid "Active" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:50 msgid "This contains a yellow arrow to represent the active stack frame. By default it is frame 0, the current function. All evaluations and local variables are relative to this active frame. You can change the active stack frame to examine local variables in other functions." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:56 msgid "Thread" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:57 msgid "This is a number corresponding to each thread." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:60 msgid "Frame" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:61 msgid "This is the frame number starting from 0 for the current function. The first function of your program, for example main() in a C program, has the highest number." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:66 msgid "File" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:67 msgid "The name of the file containing the function corresponding to this frame." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:71 msgid "Line" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:72 msgid "The line number of the function corresponding to this frame." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:75 msgid "Function" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:76 msgid "The name of the function corresponding to this frame." msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:80 msgid "The address of the function corresponding to this frame." msgstr "" #. (itstool) path: item/title #: C/debug-stack.page:83 msgid "Arguments" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:84 msgid "The function arguments." msgstr "" #. (itstool) path: section/title #: C/debug-stack.page:92 msgid "Change the current stack frame or thread" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:96 #: C/debug-stack.page:116 msgid "In the Stack window, select the frame you want." msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:99 msgid "Right-click and select Set current frame." msgstr "" #. (itstool) path: section/p #: C/debug-stack.page:103 msgid "Clicking on a stack frame in the same thread changes only the stack frame, allowing to see other local variables. But doing it in another thread will change both the stack frame and the thread. The register values will be different and the debugger will restart in the selected thread." msgstr "" #. (itstool) path: section/title #: C/debug-stack.page:112 msgid "View the current function" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:119 msgid "Double-click, or right-click and select View Source." msgstr "" #. (itstool) path: section/title #: C/debug-stack.page:126 msgid "Get a stack trace" msgstr "" #. (itstool) path: item/p #: C/debug-stack.page:130 msgid "In the Stack window, right-click and select Get stack trace." msgstr "" #. (itstool) path: info/desc #: C/debug-step.page:9 msgid "Stopping and continuing." msgstr "" #. (itstool) path: page/title #: C/debug-step.page:22 msgid "Stop and step" msgstr "" #. (itstool) path: page/p #: C/debug-step.page:24 msgid "Like a video editing session, the program can be executed in slow motion with the ability to go forward, pause, stop, and so on. This is essential for tracking program behavior. You cannot go backward yet, though." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:30 msgid "Step in" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:34 msgid "From the main menu, select Debug Step In or press F5 or click on the Step In icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:40 msgid "Single stepping executes only one statement of the program (from the place where it has stopped) and then returns control. If the statement that is executed contains one function, the debugger tries to step inside the functions (in the sequence in which the functions are executed). Once the statement is executed and control is passed back, you can study your program's state." msgstr "" #. (itstool) path: note/p #: C/debug-step.page:48 msgid "If the Disassembly window has the focus when this command is selected, it executes only one assembler instruction." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:55 msgid "Step over" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:59 msgid "From the main menu, select Debug Step Over or press F6 or click on the Step Over icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:65 msgid "Stepping over is similar to stepping except that it does not stop inside any function in the statement being executed." msgstr "" #. (itstool) path: note/p #: C/debug-step.page:69 msgid "If the Disassembly window has the focus when this command is selected, it executes only one assembler instruction, except if that instruction is a call to a subroutine, in which case the program stops when the subroutine is completed." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:78 msgid "Step out" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:82 msgid "From the main menu, select Debug Step Out or press ShiftF5 or click on the Step Out icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:88 msgid "Stepping out executes the current function until it returns to the calling function." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:94 msgid "Run and continue" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:98 msgid "From the main menu, select Debug Run/Continue or press F4 or click on the Continue icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:104 msgid "This command restarts the program and lets it run until a breakpoint is encountered or the program exits." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:109 msgid "Run To" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:113 msgid "From the main menu, select Debug Run to Cursor or press F8 or click on the Run to icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:119 msgid "This restarts the program and lets it run until the line or the address (if the Disassembly window has the focus) at the cursor is reached." msgstr "" #. (itstool) path: section/title #: C/debug-step.page:125 msgid "Stopping the Program" msgstr "" #. (itstool) path: item/p #: C/debug-step.page:129 msgid "From the main menu, select Debug Pause Program or click on the Pause icon in the toolbar." msgstr "" #. (itstool) path: section/p #: C/debug-step.page:135 msgid "This interrupts the program and returns control to the debugger, allowing you to perform debugging tasks, like inspecting data or adding breakpoints." msgstr "" #. (itstool) path: info/desc #: C/debug-tips.page:9 msgid "Debugging tips and tricks." msgstr "" #. (itstool) path: page/title #: C/debug-tips.page:22 msgid "Debugging tips" msgstr "" #. (itstool) path: section/title #: C/debug-tips.page:25 msgid "Fixing GLib/GTK+ critical errors" msgstr "" #. (itstool) path: section/p #: C/debug-tips.page:27 msgid "Sometimes it can be difficult to track down where GLib critical errors are occurring, since they do not stop the program. You can set the program to stop as soon as it gets a GLib critical error, by setting the environment variable G_DEBUG to the value fatal_criticals." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:35 msgid "Open the by selecting RunProgram Parameters... from the main menu." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:40 msgid "Click the plus sign next to Environment Variables to expand the list of environment variables." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:44 msgid "Click New to add a new entry to the list." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:47 msgid "Fill in Name with G_DEBUG and Value with fatal_criticals." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:51 msgid "Click Apply to confirm the changes." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:54 msgid "Run the program with the debugger by selecting RunDebug Program from the main menu." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:58 msgid "Use the program until the critical error occurs." msgstr "" #. (itstool) path: item/p #: C/debug-tips.page:61 msgid "When the debugger stops your program, look at the to check where this error comes from." msgstr "" #. (itstool) path: section/p #: C/debug-tips.page:66 msgid "The top function with frame number 0 is in GLib, so you have to look down in the stack. Typically the error originates from the topmost function that belongs to your program." msgstr "" #. (itstool) path: info/desc #: C/debug-watch.page:9 msgid "Monitor expressions and variables." msgstr "" #. (itstool) path: page/title #: C/debug-watch.page:22 msgid "Watch expressions" msgstr "" #. (itstool) path: page/p #: C/debug-watch.page:24 msgid "Watch expressions, or watches for short, are expressions that the debugger evaluates and prints the result of every time the program is stopped; for example, after every single-step through the program." msgstr "" #. (itstool) path: section/title #: C/debug-watch.page:30 msgid "List watched expressions" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:34 msgid "From the main menu, select View Watches to open the Watches window." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:40 msgid "Like local variables, all watch expressions are displayed in a tree with children used to represent structure or array members." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:46 msgid "The name of the variable or the expression." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:50 msgid "The variable or expression value." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:54 msgid "The type of the variable or of the expression result." msgstr "" #. (itstool) path: section/title #: C/debug-watch.page:60 msgid "Update watches" msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:62 msgid "Watch expressions can be updated automatically as soon as the program is stopped or on user request." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:65 msgid "To set a watch expression to update automatically:" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:69 msgid "In the Watches window, select the watch you want to update automatically. Right-click and check that Automatic Update if checked. If not, select it." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:75 msgid "To update a watch expression manually:" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:79 msgid "In the Watches window, right click and select Update Watch to update the selected watch." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:84 msgid "To update all watch expressions manually at once:" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:88 msgid "In the Watches window, right click and select Update all to update all watches at the same time." msgstr "" #. (itstool) path: section/title #: C/debug-watch.page:97 msgid "Add a watch on an expression" msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:99 msgid "To add an expression to the watch list:" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:103 msgid "From the main menu, select Debug Add Watch... or in the Watches window, right-click and select Add Watch...." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:108 msgid "Enter the expression to watch. Check Automatic Update if you want the expression to be evaluated each time the program is stopped." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:114 msgid "An expression can be evaluated and then added as a watch like this:" msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:118 msgid "From the main menu, select Debug Inspect/Evaluate or right click in the Editor window and select Inspect/Evaluate." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:123 msgid "Click on Add button to add this expression to the watches list." msgstr "" #. (itstool) path: section/title #: C/debug-watch.page:131 msgid "Remove a watch" msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:133 msgid "You can remove an expression from the watches list." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:137 msgid "In the Watches window, select the watch you want to remove, then right-click and select Remove Watch." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:142 msgid "All watches can be removed at the same time." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:146 msgid "In the Watches window, right-click and select Remove all." msgstr "" #. (itstool) path: section/p #: C/debug-watch.page:155 msgid "If a watch expression corresponds to a variable, you can change its value." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:160 msgid "In the Watches window, select the variable you want to edit and double click in the Value column." msgstr "" #. (itstool) path: item/p #: C/debug-watch.page:164 msgid "Enter the new value." msgstr "" #. (itstool) path: info/desc #: C/directory-project-backend.page:8 msgid "Directory project backend." msgstr "" #. (itstool) path: page/title #: C/directory-project-backend.page:21 msgid "Directory project backend plugin" msgstr "" #. (itstool) path: page/p #: C/directory-project-backend.page:23 msgid "This is the simplest project backend. There is no project file. It works like a file viewer, considering all files matching typical source extensions (for example .c, .py) to be source files. Directories are kept in order to group source files but there is no target." msgstr "" #. (itstool) path: page/p #: C/directory-project-backend.page:32 msgid "This backend is a useful workaround if your project does not have a corresponding backend in Anjuta or if the appropriate backend does not fully support your project." msgstr "" #. (itstool) path: page/p #: C/directory-project-backend.page:38 msgid "It is not possible to add or change anything with a project using this backend. But if you create a source file in the project directory, with the right extension, it will be added automatically." msgstr "" #. (itstool) path: info/desc #: C/full-index.page:8 msgid "All help topics." msgstr "" #. (itstool) path: page/title #: C/full-index.page:16 msgid "Index" msgstr "" #. (itstool) path: info/title #. (itstool) path: page/title #: C/introduction.page:7 #: C/introduction.page:12 msgid "Introduction" msgstr "" #. (itstool) path: info/desc #: C/introduction.page:8 msgid "Introduction to Anjuta Integrated Development Environment" msgstr "" #. (itstool) path: page/p #: C/introduction.page:14 msgid "Anjuta is a versatile Integrated Development Environment (IDE) for the GNOME desktop. It features a number of advanced programming facilities including project management, application wizards, interactive debugging, integrated Glade UI designer, integrated Devhelp API help, class generator, powerful source editor, symbols browsing, Git support, C/C++, Python and Vala support and more." msgstr "" #. (itstool) path: page/p #: C/introduction.page:23 msgid "Anjuta has a flexible and advanced docking system that allows you to lay out all the views in whatever way you like. You can drag and drop the views using drag bars and rearrange the layout." msgstr "" #. (itstool) path: page/p #: C/introduction.page:29 msgid "Anjuta has been designed to be simple to operate yet powerful enough to fulfill all your programming needs. We have added many new features to Anjuta over the course of its development. Our focus is on delivering power and usability at the same time and making your software development enjoyable without overloading your senses. We intend to continue improving and stabilizing Anjuta to give you the best IDE experience possible." msgstr "" #. (itstool) path: page/p #: C/introduction.page:39 msgid "We hope you will have a good time using Anjuta. If not, please help us make it better by reporting bugs and suggestions - this will help to improve the software, as well as helping the open source community." msgstr "" #. (itstool) path: page/p #: C/introduction.page:45 msgid "The following screenshot illustrates some of the things you will find in Anjuta." msgstr "" #. (itstool) path: figure/title #: C/introduction.page:51 msgid "Anjuta in action" msgstr "" #. (itstool) path: figure/desc #. (itstool) path: media/p #: C/introduction.page:52 #: C/introduction.page:54 msgid "Anjuta main window" msgstr "" #. (itstool) path: figure/media #. This is a reference to an external file such as an image or video. When #. the file changes, the md5 hash will change to let you know you need to #. update your localized copy. The msgstr is not used at all. Set it to #. whatever you like once you have updated your copy of the file. #: C/introduction.page:53 msgctxt "_" msgid "external ref='figures/anjuta-in-action.png' md5='a31f1c85a4a14032fcd30ab6f6d6b3c0'" msgstr "" #. (itstool) path: info/desc #: C/language-support-cpp-modelines-emacs.page:9 msgid "Supported Emacs modelines features." msgstr "" #. (itstool) path: page/title #: C/language-support-cpp-modelines-emacs.page:18 msgid "Emacs modelines" msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-emacs.page:20 msgid "Such modeline is a comment in the first line of the file or the second one if the first contains a shebang (#!). It is composed by a list of variable names followed by : and a value, separated by ; and surrounded by -*-." msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-emacs.page:25 msgid "A typical Emacs modeline looks like this:" msgstr "" #. (itstool) path: page/code #: C/language-support-cpp-modelines-emacs.page:27 #, no-wrap msgid "" "\n" "/* -*- Mode: C; indent-tabs-mode: t; c-basic-offset: 4; tab-width: 4 -*- */\n" " " msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-emacs.page:31 msgid "Anjuta supports only the following variables." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-emacs.page:35 msgid "indent-tabs-mode" msgstr "" #. (itstool) path: item/p #: C/language-support-cpp-modelines-emacs.page:36 msgid "Set to t to use tabulation for indentation or nil to use spaces." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-emacs.page:40 msgid "tab-width" msgstr "" #. (itstool) path: item/p #: C/language-support-cpp-modelines-emacs.page:41 #: C/language-support-cpp-modelines-vim.page:48 msgid "Number of space characters corresponding to one tabulation character." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-emacs.page:44 msgid "c-basic-offset" msgstr "" #. (itstool) path: item/p #: C/language-support-cpp-modelines-emacs.page:45 #: C/language-support-cpp-modelines-vim.page:53 msgid "Number of space characters used to indent C code." msgstr "" #. (itstool) path: info/desc #: C/language-support-cpp-modelines-vim.page:9 msgid "Supported Vim modelines features." msgstr "" #. (itstool) path: page/title #: C/language-support-cpp-modelines-vim.page:18 msgid "Vim modelines" msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-vim.page:20 msgid "This modeline is a line in the 5 first of the 5 last of the file containing vim: followed by at least one space and a list of variable names with an optional value after = separated by space or :." msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-vim.page:25 msgid "A typical Vim modeline looks like this:" msgstr "" #. (itstool) path: page/code #: C/language-support-cpp-modelines-vim.page:27 #, no-wrap msgid "" "\n" "/* vim: set noet ts=4 sw=4: */" msgstr "" #. (itstool) path: page/p #: C/language-support-cpp-modelines-vim.page:30 msgid "Anjuta support only the following variables." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:34 msgid "expandtab" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:35 msgid "et" msgstr "" #. (itstool) path: item/p #: C/language-support-cpp-modelines-vim.page:36 msgid "Use spaces for indentation." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:39 msgid "noexpandtab" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:40 msgid "noet" msgstr "" #. (itstool) path: item/p #: C/language-support-cpp-modelines-vim.page:41 msgid "Use tabulation for indentation." msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:44 msgid "softtabstop" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:45 msgid "sts" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:46 msgid "tabstop" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:47 msgid "ts" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:51 msgid "shiftwidth" msgstr "" #. (itstool) path: item/title #: C/language-support-cpp-modelines-vim.page:52 msgid "sw" msgstr "" #. (itstool) path: info/desc #: C/makefile-project-backend.page:8 msgid "Makefile project backend." msgstr "" #. (itstool) path: page/title #: C/makefile-project-backend.page:21 msgid "Makefile project backend plugin" msgstr "" #. (itstool) path: page/p #: C/makefile-project-backend.page:23 msgid "A makefile is probably the most common way to build software on all kinds of platforms. A makefile contains a list or rules describing which commands have to be run in order to generate a target from a list of dependencies. When building a program, the target is an object file and the dependencies are the source files. The target of one rule can be a dependency of another one, allowing several rules to be chained in order to make a final target." msgstr "" #. (itstool) path: page/p #: C/makefile-project-backend.page:33 msgid "It is a low-level, general tool, making it difficult to find all source files and targets of a project. So Anjuta has limited support for makefiles, reading only one makefile in the top project directory and extracting source files and targets." msgstr "" #. (itstool) path: note/p #: C/makefile-project-backend.page:42 msgid "If the project backend is not able to find all the source files, you can try to use the directory backend instead. It does not recognize any targets but should get all source files." msgstr "" #. (itstool) path: page/p #: C/makefile-project-backend.page:49 msgid "Changing properties, or adding or removing targets and source files are disabled with this backend, as automatically editing the makefile is not implemented. It has to be changed by hand using the text editor. When the makefile is saved, it is automatically reloaded though." msgstr "" #. (itstool) path: info/desc #: C/project-import.page:11 msgid "Import an existing project." msgstr "" #. (itstool) path: page/title #: C/project-import.page:24 msgid "Import a Project" msgstr "" #. (itstool) path: page/p #: C/project-import.page:26 msgid "Anjuta does not have its own project format. It loads projects using already existing formats, like makefile or autotools, and does not require that other developers use it. Anjuta's own settings are stored in a file with the .anjuta extension and a hidden directory created in the project directory. To use a project in Anjuta and create these settings files, you will need to import the project. This will not modify any project files." msgstr "" #. (itstool) path: item/p #: C/project-import.page:38 msgid "From the main menu, select File NewProject from Existing Sources or Project from Existing Sources from the drop-down list of the New button in the top tool bar to start the project wizard." msgstr "" #. (itstool) path: item/p #: C/project-import.page:47 msgid "Select Import from folder if the project is already present on your computer, then select the project directory." msgstr "" #. (itstool) path: item/p #: C/project-import.page:51 msgid "Or Select Import from version control system if the project needs to be checked out from a server. Then select the version control system, the server address and the destination directory on your computer." msgstr "" #. (itstool) path: item/p #: C/project-import.page:59 msgid "After selecting an existing project, the Project name text box should be filled with the name of the project's directory, but you can change it. When it's done, click on the Import button to download the project if needed and create the files needed by Anjuta." msgstr "" #. (itstool) path: item/p #: C/project-import.page:68 msgid "Anjuta tries to automatically find the project backend used by your project. But if several backends are possible, you will get a dialog asking you to choose a project backend plugin. Read the project backend description to find out which one to choose." msgstr "" #. (itstool) path: info/desc #: C/project-manager-folder-add.page:9 msgid "Add a folder to a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-folder-add.page:18 msgid "Add a Folder" msgstr "" #. (itstool) path: page/p #: C/project-manager-folder-add.page:20 msgid "A folder allows you to group several target allowing to set common properties for all of them. It often corresponds to a directory." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-add.page:25 msgid "Select the group or the project where you want to add the new group in the project view, click on the right mouse button to make the project context menu appear and select Add Group." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-add.page:29 msgid "Or from the main menu, select Project Add Group." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-add.page:33 msgid "Enter a new group name." msgstr "" #. (itstool) path: note/p #: C/project-manager-folder-add.page:35 msgid "Groups names are typically restricted to letters, digits and the underscore, so it's safer to avoid other characters." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-add.page:40 msgid "You can select another group in the bottom group tree view." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-add.page:43 msgid "When you have chosen the parent and enter the name, click on the Add button to add the group to your project." msgstr "" #. (itstool) path: info/desc #: C/project-manager-folder.page:11 msgid "Add, edit or remove folders from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-folder.page:20 msgid "Manage Folders" msgstr "" #. (itstool) path: info/desc #: C/project-manager-folder-remove.page:9 msgid "Remove folders from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-folder-remove.page:18 msgid "Remove Folder" msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-remove.page:22 msgid "Select the folder you want to remove in the project view, click on the right mouse button to make the project context menu appear and select Remove." msgstr "" #. (itstool) path: item/p #: C/project-manager-folder-remove.page:28 msgid "Confirm the removal. This will only remove the folder from the project files without removing any files or directories from your disk." msgstr "" #. (itstool) path: info/desc #: C/project-manager-library-add.page:10 msgid "Add a custom library to a target." msgstr "" #. (itstool) path: page/title #: C/project-manager-library-add.page:23 msgid "Add a Custom Library" msgstr "" #. (itstool) path: page/p #: C/project-manager-library-add.page:25 msgid "It is easier to use a packaged library, which is common on Linux, so check if it is the case here. But else you can still use the library as explained below." msgstr "" #. (itstool) path: page/p #: C/project-manager-library-add.page:29 msgid "In order to use a library in C, you need to tell the compiler where the header files are, and tell the linker where to find the needed libraries. The issue is that your program will not compile on another computer if the header and the libraries are elsewhere." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:36 msgid "Select the directory containing the program where you want to add the library in the project view, click on the right mouse button to make the project context menu appear and select Properties." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:41 #: C/project-manager-library-add.page:65 msgid "Or from the main menu, select Project Properties. By default, it edits the properties of the currently selected item in the project view. You can select a different item in the drop-down list button." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:47 msgid "If the header files are installed in a standard location (/usr/include) you don't have to set this. If not, you need to add -Iinclude_path in the C preprocessor flags property if you are using gcc as your compiler. You can add several paths separated with spaces. These options will be used for all targets inside this directory." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:55 msgid "You might have to expand the More options button to see this. Click on the Apply button when you are done." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:59 msgid "Next, you need to add the library to a target. Select the target where you want to add the library in the project view, click on the right mouse button to make the project context menu appear and select Properties." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:71 msgid "You need to set the Linker flags property, adding -llibrary_name if your compiler is gcc. library_name is the name of the library file without the lib prefix and without the .a or .so extension." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-add.page:77 msgid "If the library is in not in a standard directory, gcc can look in additional directories with the option -Llibrary_path." msgstr "" #. (itstool) path: info/desc #: C/project-manager-library.page:13 msgid "Add or remove libraries to project targets." msgstr "" #. (itstool) path: page/title #: C/project-manager-library.page:22 msgid "Manage Libraries" msgstr "" #. (itstool) path: info/desc #: C/project-manager-library-remove.page:10 msgid "Remove a custom library from a target." msgstr "" #. (itstool) path: page/title #: C/project-manager-library-remove.page:23 msgid "Remove a Custom Library" msgstr "" #. (itstool) path: item/p #: C/project-manager-library-remove.page:27 msgid "Select the target that has the library you want to remove in the project view, click on the right mouse button to make the project context menu appear and select Properties." msgstr "" #. (itstool) path: item/p #: C/project-manager-library-remove.page:33 msgid "Remove the library from the C preprocessor flags and Linker flags properties. Click on the Apply button to write the changes to the project files." msgstr "" #. (itstool) path: info/desc #: C/project-manager-module-add.page:10 msgid "Add a set of libraries to a target." msgstr "" #. (itstool) path: page/title #: C/project-manager-module-add.page:23 msgid "Add packaged libraries" msgstr "" #. (itstool) path: page/p #: C/project-manager-module-add.page:25 msgid "On Linux, most libraries are distributed with additional data stored in a pkg-config file. This file contains information like the other libraries needed, the C compiler and the linker flags needed to use that library. This file, the header files and the library files themselves is called a package." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:33 msgid "Select the program where you want to add the new library in the project view, click on the right mouse button to make the project context menu appear and select Add Library." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:37 #: C/project-manager-module-new.page:35 msgid "Or from the main menu, select Project Add Library...." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:41 msgid "You need to select the target where you want to add the library in the target button above." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:45 msgid "A library cannot be added directly to a target. You can add only a module displayed in the module view below. If you select a library inside a module, the parent module will be added." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:50 msgid "If the library you want is not displayed in the module view, you need to add it as a module first. Click on the button New Library and follow the explanation here." msgstr "" #. (itstool) path: note/p #: C/project-manager-module-add.page:55 msgid "After creating a new module, you have to wait a few seconds while the project files are reloaded to see the new module in the list." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-add.page:60 msgid "When you are done, click on the Add button to add the selected module to the target." msgstr "" #. (itstool) path: info/desc #: C/project-manager-module-new.page:12 msgid "Groups libraries in a module." msgstr "" #. (itstool) path: page/title #: C/project-manager-module-new.page:25 msgid "Add a Module" msgstr "" #. (itstool) path: page/p #: C/project-manager-module-new.page:27 msgid "Packages cannot be added directly to a program but have to be grouped in a module." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:32 msgid "Select a program in the project view, click on the right mouse button to make the project context menu appear, and select Add Library." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:39 msgid "On the Add Library dialog, click on the New Library button." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:43 msgid "You will get a list of all the packaged libraries installed on your system. You can check one or more libraries." msgstr "" #. (itstool) path: note/p #: C/project-manager-module-new.page:46 msgid "If the library you want does not appear here:" msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:49 msgid "Perhaps it is not installed on your system. Launch the application you use to install new programs and search for the library name. The package you need often has a \"dev\" or \"devel\" suffix and should include header files and a pkg-config file with a .pc extension." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:57 msgid "It could be that the library is not packaged, it is often the case for libraries not developed on Linux. See the chapter explaining how to use them." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:66 msgid "After selecting one library, a module name will be automatically generated but you can change it. You can select an already existing module name to add a new library to it and to all targets already using it." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-new.page:72 msgid "When you are done, click on the Add button to create the new module with the selected libraries. You need to add a new module to at least one target to really use it." msgstr "" #. (itstool) path: info/desc #: C/project-manager-module-remove.page:10 msgid "Remove a set of libraries from a target." msgstr "" #. (itstool) path: page/title #: C/project-manager-module-remove.page:23 msgid "Remove a Module" msgstr "" #. (itstool) path: item/p #: C/project-manager-module-remove.page:27 msgid "Select the library you want to remove in the project view, click on the right mouse button to make the project context menu appear, and select Remove." msgstr "" #. (itstool) path: item/p #: C/project-manager-module-remove.page:33 msgid "Confirm the removal. This library will be removed from the target." msgstr "" #. (itstool) path: info/desc #: C/project-manager-package-remove.page:9 msgid "Remove a library from a module." msgstr "" #. (itstool) path: page/title #: C/project-manager-package-remove.page:22 msgid "Remove a Package" msgstr "" #. (itstool) path: item/p #: C/project-manager-package-remove.page:26 msgid "Select the package you want to remove in the project view , click on the right mouse button to make the project context menu appear and select Remove." msgstr "" #. (itstool) path: item/p #: C/project-manager-package-remove.page:32 msgid "Confirm the removal. This package will be removed from the project file." msgstr "" #. (itstool) path: info/desc #: C/project-manager.page:8 msgid "Project manager." msgstr "" #. (itstool) path: page/title #: C/project-manager.page:21 msgid "Project manager plugin" msgstr "" #. (itstool) path: page/p #: C/project-manager.page:23 msgid "Anjuta supports several already existing project formats through plugin backends. The main one is the autotools format commonly used on Linux." msgstr "" #. (itstool) path: page/p #: C/project-manager.page:29 msgid "The project backend to use is chosen when creating or importing a new project in Anjuta. It is displayed in the properties of the project root node and can be changed at any time." msgstr "" #. (itstool) path: page/p #: C/project-manager.page:35 msgid "Whatever the underlying backend, the graphical interface is the same but some functions might be disabled." msgstr "" #. (itstool) path: section/title #: C/project-manager.page:41 msgid "Project Backend Plugin" msgstr "" #. (itstool) path: info/desc #: C/project-manager-root.page:12 msgid "Edit project properties." msgstr "" #. (itstool) path: page/title #: C/project-manager-root.page:21 msgid "Edit a Project" msgstr "" #. (itstool) path: info/desc #: C/project-manager-source-add.page:9 msgid "Add existing files to a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-source-add.page:22 msgid "Add Files" msgstr "" #. (itstool) path: item/p #: C/project-manager-source-add.page:26 msgid "Select the target where you want to add the new source files in the project view, click on the right mouse button to make the project context menu appear and select Add Source File." msgstr "" #. (itstool) path: item/p #: C/project-manager-source-add.page:31 msgid "Or from the main menu, select Project Add Source File..." msgstr "" #. (itstool) path: item/p #: C/project-manager-source-add.page:35 msgid "You can select another target in the top target chooser button." msgstr "" #. (itstool) path: item/p #: C/project-manager-source-add.page:39 msgid "In the file chooser below, select the files you want to add. Then click on the Add button to add those files to your project. You can select several files at the same time keeping Ctrl key pressed or using the Shift to select a range of files." msgstr "" #. (itstool) path: note/p #: C/project-manager-source-add.page:48 msgid "You can add files in sub-directories of the project. Most project formats require the files to be under the project directory. Added source files outside the project directory are automatically copied inside to fulfill this requirement." msgstr "" #. (itstool) path: info/desc #: C/project-manager-source.page:12 msgid "Add or remove files from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-source.page:21 msgid "Manage Files" msgstr "" #. (itstool) path: info/desc #: C/project-manager-source-remove.page:9 msgid "Remove files from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-source-remove.page:22 msgid "Remove Files" msgstr "" #. (itstool) path: item/p #: C/project-manager-source-remove.page:26 msgid "Select the file you want to remove in the project view, click on the right mouse button to make the project context menu appear and select Remove." msgstr "" #. (itstool) path: item/p #: C/project-manager-source-remove.page:32 msgid "Confirm the removal. The file will only be removed from the project, not from your disk." msgstr "" #. (itstool) path: note/p #: C/project-manager-source-remove.page:38 msgid "You can select several files at the same time by keeping the Ctrl key pressed or select a range using the Shift key." msgstr "" #. (itstool) path: info/desc #: C/project-manager-target-add.page:9 msgid "Add a target to a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-target-add.page:22 msgid "Add a Target" msgstr "" #. (itstool) path: page/p #: C/project-manager-target-add.page:24 msgid "A target groups files together and defines their use. It is used to represent a program, with all its source files as its children or only group data files those should be installed at the same place." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-add.page:30 msgid "Select the directory where you want to add the new target in the project view, click on the right mouse button to make the project context menu appear and select New Target." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-add.page:34 msgid "Or from the main menu, select Project New Target...." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-add.page:38 msgid "You can select another directory in the bottom directory tree view." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-add.page:40 msgid "Enter a target name and select the type of the target in the drop-down list below. Depending on your project backend, various types of target are possible, see at the bottom." msgstr "" #. (itstool) path: note/p #: C/project-manager-target-add.page:45 msgid "Target names are typically restricted to letters, digits and the underscore, so it's safer to avoid other characters." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-add.page:50 msgid "When you have chosen the target name, type and parent, click on the Add button to create this new target." msgstr "" #. (itstool) path: info/desc #: C/project-manager-target.page:12 msgid "Add, edit or remove targets from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-target.page:21 msgid "Manage Targets" msgstr "" #. (itstool) path: info/desc #: C/project-manager-target-remove.page:9 msgid "Remove a target from a project." msgstr "" #. (itstool) path: page/title #: C/project-manager-target-remove.page:22 msgid "Remove a Target" msgstr "" #. (itstool) path: item/p #: C/project-manager-target-remove.page:26 msgid "Select the target you want to remove in the project view, click on the right mouse button to make the project context menu appear and select Remove." msgstr "" #. (itstool) path: item/p #: C/project-manager-target-remove.page:32 msgid "Confirm the removal. The target and all its properties will be removed from the project file. All its files stay untouched on your hard disk." msgstr "" #. (itstool) path: info/desc #: C/project-manager-treeview.page:8 msgid "Display project's content." msgstr "" #. (itstool) path: page/title #: C/project-manager-treeview.page:17 msgid "View a Project" msgstr "" #. (itstool) path: page/p #: C/project-manager-treeview.page:19 msgid "A project is represented by a tree, the root item corresponds to the project while children represent programs, libraries, directories and source files. Each item can have properties allowing to set more details like project version, compiler flags or installation directories. These item are divided in several categories, depending on the backend not all are available:" msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:28 msgid "Root" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:29 msgid "There is only one node of this kind. It represents the project itself. It is the place where you can set project wide properties like the project name or the project version." msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:34 msgid "Module" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:35 msgid "This is a set of packages used in autotools project. They appear as children of the root node to represent all modules defined and as children of each target using them. For more details, see ." msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:41 msgid "Package" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:42 msgid "This is a packaged library used in autotools project. They appear as children of each module. For more details, see ." msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:47 msgid "Folder" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:48 msgid "This is used to group targets allowing to set common properties. They are often implemented by sub directories. For more details, see ." msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:53 msgid "Target" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:54 msgid "It groups files and define how they are used. There are several kinds of targets, by example program, library or data, corresponding to different use of the child files. They often represent generated project files like compiled programs or libraries. For more details see ." msgstr "" #. (itstool) path: note/p #: C/project-manager-treeview.page:61 msgid "You can drag and drop targets at the beginning of the project tree view to create a shortcut allowing to access them more easily. By default all program targets are already put here." msgstr "" #. (itstool) path: item/title #: C/project-manager-treeview.page:68 msgid "Source" msgstr "" #. (itstool) path: item/p #: C/project-manager-treeview.page:69 msgid "Each source file is represented by a item in the project view. The use of each file depends on its parent target. All children of a program target are compiled to generate it. While children of a data target are only copied to a directory when the project is installed. For more details see ." msgstr "" #. (itstool) path: info/desc #: C/project-wizard-create.page:10 msgid "Create a new project from scratch." msgstr "" #. (itstool) path: page/title #: C/project-wizard-create.page:23 msgid "Create a Project" msgstr "" #. (itstool) path: page/p #: C/project-wizard-create.page:25 msgid "New projects are created from templates. Anjuta will ask you for various information, like the type of the project, its name and more." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:32 msgid "From the main menu, select File NewProject." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:36 msgid "Or from the drop-down list of the New button in the top tool bar, select Project to start the project wizard." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:44 msgid "Select the icon representing the type of the project you want to create and click on Forward." msgstr "" #. (itstool) path: note/p #: C/project-wizard-create.page:49 msgid "Leave the mouse over a project icon for a second and a small pop-up message will appear showing more information about this type of project." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:57 msgid "Depending on the selected project type, you will have to enter different information. When you are done, click on Forward." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:61 msgid "All informations are grouped in pages, typically you will have to fill two or three pages. You can go back at any time using the button Back." msgstr "" #. (itstool) path: note/p #: C/project-wizard-create.page:67 msgid "Keep the mouse over the button or typing area for a second to get a small pop-up message with more details about the corresponding setting." msgstr "" #. (itstool) path: item/p #: C/project-wizard-create.page:75 msgid "After filling out all the information pages, you will get a summary page listing the main information about your project. Nothing has been written to your disk yet at this point. Click on Apply to save the project and open it in Anjuta." msgstr "" #. (itstool) path: note/p #: C/project-wizard-create.page:85 msgid "Each project type corresponds to a template. Anjuta already includes several templates but you can add custom ones and even write your own." msgstr "" #. (itstool) path: info/desc #: C/project-wizard-template.page:9 msgid "Project wizard template." msgstr "" #. (itstool) path: page/title #: C/project-wizard-template.page:22 msgid "Project wizard template" msgstr "" #. (itstool) path: page/p #: C/project-wizard-template.page:24 msgid "A project template is composed of a bunch of files which can be processed by a powerful template processing engine called autogen. A project template file has a .wiz extension, and describes all the project properties and files needed." msgstr "" #. (itstool) path: page/p #: C/project-wizard-template.page:31 msgid "This .wiz file looks like a XML file and is documented here." msgstr "" #. (itstool) path: info/desc #: C/run-parameters-dialog.page:11 msgid "Run parameters dialog" msgstr "" #. (itstool) path: page/title #: C/run-parameters-dialog.page:20 msgid "Run Parameters Dialog" msgstr "" #. (itstool) path: page/p #: C/run-parameters-dialog.page:22 msgid "The run parameter dialog allows you to define the current program and several parameters." msgstr "" #. (itstool) path: item/title #: C/run-parameters-dialog.page:27 msgid "Program" msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:28 msgid "This is the program that will be executed if you run a program with or without the debugger. The drop-down list allows you to select programs created by the current project, but you can click on the Browse button to choose any other program." msgstr "" #. (itstool) path: item/title #: C/run-parameters-dialog.page:34 msgid "Arguments" msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:35 msgid "These are the command line arguments used by your program. The drop-down list keeps an history of the last arguments used." msgstr "" #. (itstool) path: item/title #: C/run-parameters-dialog.page:40 msgid "Working Directory" msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:41 msgid "The working directory is the current directory when your program will be run." msgstr "" #. (itstool) path: item/title #: C/run-parameters-dialog.page:45 msgid "Environment Variables" msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:46 msgid "You can click on the drop-down section, to display all environment variables that will be accessible by your program. By default, it includes all the current environment variables, they are displayed in light gray." msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:50 msgid "You can click on the New button to add a new environment variable." msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:52 msgid "You can click on the Edit button to change the value of the selected environment variable." msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:54 msgid "You can click on the Delete button to remove the selected environment variable." msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:56 msgid "When a variable has not the same value as in the current environment, it is displayed in black." msgstr "" #. (itstool) path: item/title #: C/run-parameters-dialog.page:60 msgid "Run in Terminal" msgstr "" #. (itstool) path: item/p #: C/run-parameters-dialog.page:61 msgid "This has to be checked to run the program in a terminal allowing you to provide inputs and see its outputs using the standard Unix streams. It is not necessary for programs having a graphical interface." msgstr "" #. (itstool) path: info/desc #: C/run-run.page:11 msgid "Start a program without the debugger." msgstr "" #. (itstool) path: page/title #: C/run-run.page:24 msgid "Run a program" msgstr "" #. (itstool) path: page/p #: C/run-run.page:26 msgid "If Anjuta is used to start a program it checks that it is up to date and builds it if needed." msgstr "" #. (itstool) path: item/p #: C/run-run.page:31 msgid "From the main menu, select Run Run or press F3 to execute the current program." msgstr "" #. (itstool) path: page/p #: C/run-run.page:37 msgid "The current program and several parameters can be set on the parameter dialog. See for more information." msgstr "" #. (itstool) path: item/p #: C/run-run.page:42 msgid "From the main menu, select Run Program Parameters... to display the dialog." msgstr "" #. (itstool) path: note/p #: C/run-run.page:49 msgid "If your program needs data files, you probably have to install it at least one time before running it. See for more information." msgstr "" #. (itstool) path: info/desc #: C/widget-index.page:8 msgid "All windows and dialogs." msgstr "" #. (itstool) path: page/title #: C/widget-index.page:16 msgid "Windows and dialogs" msgstr ""