[anjuta] Updated Swedish translation

From: Damned-Lies <translations src gnome org>
To: commits-list gnome org
Cc:
Subject: [anjuta] Updated Swedish translation
Date: Sat, 7 Mar 2015 23:26:23 +0000 (UTC)
commit 90e2ebbdc084ea6aef9ef5559d537f4a4597bc89
Author: Josef Andersson <josef andersson gmail com>
Date:   Sat Mar 7 23:26:17 2015 +0000

    Updated Swedish translation

 manuals/anjuta-manual/sv/sv.po | 4796 +++++++++++++++++++++++++++++++++++-----
 1 files changed, 4213 insertions(+), 583 deletions(-)
---
diff --git a/manuals/anjuta-manual/sv/sv.po b/manuals/anjuta-manual/sv/sv.po
index 66e973b..31209ec 100644
--- a/manuals/anjuta-manual/sv/sv.po
+++ b/manuals/anjuta-manual/sv/sv.po
@@ -1,1057 +1,4687 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: anjuta manual\n"
-"POT-Creation-Date: 2007-02-07 01:33+0100\n"
+"POT-Creation-Date: 2015-02-26 15:47+0000\n"
 "PO-Revision-Date: 2007-02-07 01:44+0100\n"
 "Last-Translator: Daniel Nylander <po danielnylander se>\n"
 "Language-Team: Swedish <tp-sv listor tp-sv se>\n"
+"Language: sv\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: C/tools.xml:3(title)
-msgid "User-defined Tools"
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+#, fuzzy
+#| msgid "translator-credits"
+msgctxt "_"
+msgid "translator-credits"
+msgstr "Daniel Nylander <po danielnylander se>, 2007"
+
+#. (itstool) path: info/desc
+#: C/index.page:8
+msgid "Help for Anjuta DevStudio."
 msgstr ""
 
-#: C/tools.xml:6(title)
-#: C/introduction.xml:3(title)
-msgid "Introduction"
+#. (itstool) path: info/title
+#: C/index.page:9
+#, fuzzy
+#| msgid "Anjuta Team"
+msgctxt "link"
+msgid "Anjuta"
+msgstr "Anjuta-teamet"
+
+#. (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 "Johannes Schmid"
+
+#. (itstool) path: media/span
+#: C/index.page:24
+#, fuzzy
+#| msgid "Anjuta Team"
+msgid "Anjuta logo"
+msgstr "Anjuta-teamet"
+
+#. (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 "Projekthantering"
+
+#. (itstool) path: section/title
+#: C/index.page:33
+msgid "Coding and code navigation"
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/index.page:37
+#, fuzzy
+#| msgid "Project"
+msgid "Building Project"
+msgstr "Projekt"
+
+#. (itstool) path: section/title
+#: C/index.page:41
+#, fuzzy
+#| msgid "Debugging"
+msgid "Debugging Program"
+msgstr "Felsökning"
+
+#. (itstool) path: section/title
+#: C/index.page:51
+#, fuzzy
+#| msgid "Preferences"
+msgid "Reference"
+msgstr "Inställningar"
+
+#. (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 <key>Enter</key> key. Normally this happens automaticly "
+"after you typed the third (non-whitespace) character but you can also force "
+"it by using the <guiseq><gui>Edit</gui><gui>Auto-Complete</gui></guiseq> "
+"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 "
+"<cmd>pkg-config</cmd> 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 (<guiseq><gui>Edit</gui><gui>Preferences</gui></guiseq>) in "
+"<guiseq><gui>General</gui><gui>Plugins</gui></guiseq> by choosing the "
+"<app>DevHelp</app> 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 <keyseq><key>Shift</"
+"key><key>F1</key></keyseq> (or <guiseq><gui>Help</gui><gui>Context-Help</"
+"gui></guiseq>) 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 (<guiseq><gui>Edit</"
+"gui><gui>Preferences</gui></guiseq>) 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 explicitely 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 <app>Vim</app> and "
+"<app>Emacs</app>."
+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 approprietely indented automatically but you can "
+"indent existing lines or all selected code with the <guiseq><gui>Edit</"
+"gui><gui>Auto-Indent</gui></guiseq> 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 "<gui>File</gui> shows the symbols of the current file in the editor"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:29
+msgid "<gui>Project</gui> shows all symbols of the project"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:30
+msgid ""
+"<gui>Search</gui> lets you search the symbols in the project (use "
+"<keyseq><key>Ctrl</key><key>L</key></keyseq> 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 <gui>Goto</gui> 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 "<gui>Symbol definition</gui>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:44
+msgid "<gui>Symbol declaration</gui>"
+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 <gui>Goto</gui> menu you can use the <gui>Previous "
+"history</gui> (and <gui>Next history</gui>) 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 <cmd>configure</cmd>, <cmd>make</cmd> "
+"and <cmd>make install</cmd>, 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 <app>Anjuta</app>, 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 <file>configure.ac</file> or any <file>Makefile.am</file> "
+"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 <link href=\"https://bugzilla.gnome.org/browse.cgi?";
+"product=anjuta\">bug report</link> 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 "<gui>C compiler flags</gui>"
+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 "<gui>C preprocessor flags</gui>"
+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 "<gui>C++ compiler flags</gui>"
+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 "<gui>Fortran compiler flags</gui>"
+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 "<gui>Installation directories</gui>"
+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 "<gui>Java compiler flags</gui>"
+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 "<gui>Lex/Flex compiler flags</gui>"
+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 "<gui>Linker flags</gui>"
+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 "<gui>Objective C compiler flags</gui>"
+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 "<gui>Vala compiler flags</gui>"
+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 "<gui>Yacc/Bison compiler flags</gui>"
+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 "<gui>Backend</gui>"
+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 "<gui>Name</gui>"
+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 "<gui>Version</gui>"
+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 "<gui>Bug report URL</gui>"
+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 "<gui>Package name</gui>"
+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 "<gui>URL</gui>"
+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 "
+"<link xref=\"autotools-project-folder-edit\"/> 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 "<gui>Build for check only</gui>"
+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 "<gui>Do not install</gui>"
+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 "<gui>Do not use prefix</gui>"
+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 "<gui>Include in distribution</gui>"
+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 "<gui>Installation directory</gui>"
+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 "<gui>Keep target path</gui>"
+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 "<gui>Libraries</gui>"
+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 <link xref=\"project-manager-library\">Add non-"
+"packaged libraries</link> 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 "<gui>Manual section</gui>"
+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 "
+"explicitely 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 souces 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 progran 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 progran 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
+#, fuzzy
+#| msgid "Introduction"
+msgid "Info documentation"
 msgstr "Introduktion"
 
-#: C/tools.xml:7(para)
-msgid "Often, you'll find the inbuilt functionality provided by Anjuta to be insufficient. In these cases, 
you might be tempted to either add the feature yourself to the Anjuta codebase or submit a feature request to 
implement the feature. However, both approaches are likely to be slow and problematic, especially if your 
tool is a specialized one. In these circumstances, it is advisable to use the Anjuta tools framework instead."
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:74
+msgid "It groups info page needed by the project."
 msgstr ""
 
-#: C/tools.xml:16(para)
-msgid "Anjuta provides a powerful framework for defining user-defined tools for extending it's 
functionality. Tools have access to almost all features of the IDE through the use of variables. You can add 
tools under any menu item, specify input, output and error redirection within the GUI framework and supply 
command line parameters to the tool."
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:77
+msgid "Miscellaneous Data"
 msgstr ""
 
-#: C/tools.xml:24(para)
-msgid "The tools plugin has to be enabled to use this feature!"
+#. (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 ""
 
-#: C/tools.xml:31(title)
-msgid "Tools Examples"
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:82
+msgid "Script"
 msgstr ""
 
-#: C/tools.xml:32(para)
-msgid "This is a simple example how to use the tools plugin to integrate the GNOME ChangeLog generation 
script"
+#. (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 ""
 
-#: C/tools.xml:38(title)
-#: C/tools.xml:40(screeninfo)
-msgid "The tool editor"
+#. (itstool) path: info/desc
+#: C/autotools-build-build.page:11
+msgid "Build targets or project."
 msgstr ""
 
-#: C/template.xml:3(title)
-msgid "new chapter"
+#. (itstool) path: page/title
+#: C/autotools-build-build.page:24
+msgid "Build targets"
 msgstr ""
 
-#: C/template.xml:4(para)
-msgid "to be written"
+#. (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 ""
 
-#: C/projects.xml:3(title)
-msgid "Project Management"
-msgstr "Projekthantering"
+#. (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 ""
 
-#: C/projects.xml:6(title)
-msgid "Introduction to managing projects"
-msgstr "Introduktion till projekthantering"
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:39
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Build</"
+"gui></guiseq> or press <key>F7</key> to build all targets in the same "
+"directory as the currently opened file."
+msgstr ""
 
-#: C/projects.xml:7(para)
-msgid "If the program or application you are developing is a small one, and it is only going to be run on 
your computer, then a single source file will often serve the purpose. If the application is more complex, 
with multiple source files, it is useful to be able to keep track of your program and its resources. Such a 
<emphasis>program</emphasis> becomes a <emphasis>project</emphasis>."
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:48
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Build "
+"Project</gui></guiseq> or press <keyseq><key>Shift</key><key>F7</key></"
+"keyseq> to build the complete project. All subdirectories are built "
+"recursively."
 msgstr ""
 
-#: C/projects.xml:16(para)
-msgid "Many command-line tools are available to maintain and manage a project, and each tool has its own 
specific rules and capabilities. Do not worry Anjuta will take care of everything. It is still possible to 
make use of other tools, which has the added advantage of making your project more flexible and more 
adaptable. However, before you start editing all those makefiles, bear in mind the files that Anjuta manages. 
These files will all be overwritten. If you do not want to get involved with manually editing project files, 
just relax and let Anjuta do it all. Creating a New Project Choose the menu item FileNew Project to start the 
application wizard. Read the first page carefully. Click on Next to proceed. Select the type of application 
you want to create in the second page. Click on Next to proceed. On the next pages, enter all the necessary 
details for your project. You cannot change these settings later. No white spaces or any non-alphanumeric 
characters, except unders
 core (_) and dash (-), are allowed in any of the entry boxes in this page (except the Author text box). You 
can also specify whether your project will have internationalization support using gettext (read the gettext 
info page for more details). This gives your project multilingual support for different regional languages 
such as English, French, Dutch etc.. The rest of the options are for setting whether the GNU copyright 
statement should appear in the comments at the top of each file, and enabling GNOME desktop menu information 
if necessary. The final step is to verify the information you have just supplied. Click on Finish to start 
generating the project. Once project generation is over, you can try it out by building the project and 
executing it. Loading and Saving Projects Loading Projects To open a project, choose the menu item File Open 
. Select the project file (*.anjuta) in the dialog and click OK. If the project has recently been opened, 
then you will find it liste
 d in the menu FileRecent. Choose the project file from the list, and the project will be opened. As soon as 
a project is opened, Anjuta will enter Project mode. There are three panes in the project window. The first 
is the project pane and lists the project files organized in file types. The second is the symbol browser, 
which has already been discussed in section Symbol Browser and tags Brwoser. The third pane is the file view 
of the project and is more or less similar to a mini file-manager. In file view, all the files present in the 
project tree is visible. Right clicking on these files will pop up the file operation submenu. If the project 
is also a CVS tree, then corrosponing file revision numbers are also listing on the right of file names in 
the file view pane. Importing Projects The import project feature is used to import an already existing 
project and convert it into anjuta projcect. Activate the import project wizard from FileNew Project from 
existing sources and
  follow instructions dictated by the wizard. Once the project is imported, it could be opened in anjuta 
subsequently just like any other anjuta project. The import project features only works if your existing 
project is using autoconf/automake. Saving Projects The project is automatically saved when you close because 
all changes are made directly in the Makefile.am. Adding and Removing Files There are various different types 
of file that Anjuta will manage for you in the project: Source files Document files Pixmap files Help files 
Data files PO files Each of these different types exist in their own specific directories inside the project. 
Adding Files Choose the corresponding menu item from the Project Add Source file submenu. Select the file you 
want to add and the target you want to add it to in the dialog and click OK. If the file you choose has 
already been added to the project, then Anjuta will not add it again. It will also give you a warning that 
the file is already a
 dded. If the file you choose is not in the directory corresponding to the type you have selected, you will 
be asked to confirm that you wish to copy the file into that directory. Anjuta cannot add files which are 
outside of their correct directories. Removing Files To remove a file from the project, select the file you 
want to remove from the Project Listing, right-click to open the Operation popup menu and choose Remove. A 
confirmation dialog will appear, and the file will be removed from the project. The file is not deleted! The 
file is not deleted from the filesystem. It still exists, and you can add it back again later if you so wish. 
The file is only removed from the project listing, and will not take part in any of the project operations 
such as compiling, building, distribution etc.. Project Configuration Choose Project Properties to change the 
project configuration. You can add and remove depencies for your project there. Project properties dialog 
Project properties 
 dialog Managing Project Files Anjuta manages all Makefile.am (or Makefile, in case of a Makefile based 
project) files for you. A tree of the scanned files is shown in the Project window. You can use Project Add 
Target to add a new target (executable, library, ...) to the project. To add files to the new target see 
Adding and Removing Files above. To add a new group to your project, use Project Add Groups. In most project 
backends (Automake, Makefile) group simply means directory. After you created a group you can add targets to 
that group. Compiling, Building and Executing a Project Overview An executable for a project is generated in 
two steps: Compiling Linking These steps are collectively known as Building. Some other steps may also be 
involved in the build process, but for the sake of simplicity, we will only look at these two steps. 
Compiling is the step in which object files are generated from their corresponding source files. For 
instance, a source file hello.c will g
 enerate hello.o after compilation. Usually you do not need to worry about these object files just think of 
them as intermediate files involved in creating the final executable. Once the object files (*.o files) are 
ready, they are all linked together (along with any libraries) to generate the final executable. This step is 
called Linking. Compiling the source In a project, the individual source files can be compiled separately 
into objects (*.o files). Although you do not have to worry about these object files, sometimes it is handy 
to compile a file first (for example, to make sure there are no syntax errors). Building a whole project can 
take a lot of time, especially in the case of larger and more complex applications. Therefore, you will 
probably go through a series of edit-compile-edit-compile-.... loops while a developing the project. To 
compile a file, choose the menu item Build Compile or click on the Compile icon on the extended toolbar. This 
will compile the active
  file. Building an executable Anjuta has no separate link command, simply because it is not necessary. The 
build process will compile all the source files and link them together along with the libraries. The build 
command will note recompile those files which are already up-to-date (this is called the dependency check). 
If you have already compiled all of the files individually, then the only thing the build step performs is 
the link. If you have already built the project and no dependent file has been modified, even the link stage 
will be skipped. So how exactly does the dependency check influence the project development? If you have 
modified a file, then all of the source files that depend on the modified file are recompiled. All files (not 
only the object files and executable) in the project are checked for these dependencies during the build 
process. If it is found that a particular file is dependent on some other file which has been modified, then 
that file will be re-g
 enerated. Since you have now got a rough understanding of the value of the dependency check, can you imagine 
how your life (as a programmer) would be if it had not been there? If you cannot answer just yet, then will 
find out when you start developing big projects! BuildBuild will build all of the files in the src (source) 
directory, and generate the executable. Build Build All will build the whole project all of the 
subdirectories (including src), are built recursively. Creating a distribution package To build the tarball 
distribution of the project choose Build Build Tarball. This will create a tarball (*.tar.gz) and put it in 
the top level project directory. Copy the file to a safe place for distribution. Install Choosing the menu 
item Build Install will install the generated application on your system. System wide installation You must 
be logged in as root to perform a system-wide install. Also note that for a GNOME application to use the 
pixmaps in the project, it must 
 be installed as a system-wide application. Otherwise, when the application is executed in your project, 
there will be lots of pixmap not found errors. You can configure anjuta to use sudo or su before installing 
the project in the build preferences. Configure To run the configure script found in the top level project 
directory, choose the menu item Build Configure. The script will determine the system configuration and 
create some of the files required to perform a build (such as Makefile and config.h). This is necessary 
because the application may depend on specific configuration of some of these options. When to configure 
Until you run configure, you cannot start building the project. The configure script is (usually) run only 
once at the beginning of the first build process for example, just after you have extracted a source tarball 
of a project distribution. After that, configuration is automatically handled by the subsequent build 
processes. If you have used the Applica
 tion Wizard to create the application, then you will not need to run configure separately: the wizard will 
run it as a part of the project generation process. You can also supply additional options to the 
configuration script. After choosing the Configure menu item, a dialog will appear to prompt for additional 
options. Configure options dialog Configure options dialog Enter any options (or leave it blank to accept the 
defaults) and click OK. To find out the options available to the configure script, enter --help in the option 
entry box and click OK. The options will be displayed in the Message window. There is no requirement to run 
configure only once. It can be run at any time, usually when the configuration options need to be changed. 
One thing to note is that, if the config.h file in the top level directory is changed, running configure 
again will not overwrite it. Auto generate Auto generation consists of two steps: running automake and then 
running autoconf. If an exec
 utable autogen.sh script is found in the top level project directory, this file will be executed instead of 
the two steps. Like configuration, auto generation is automatically handled by the build process. It can also 
be run in cases where it is difficult to configure the project (such as lots of errors reported due to 
mis-synchronization after modifying lots of build files). When to autogen.sh Unlike configuration, auto 
generation does not need to be run even once in fact, it does not need to be run at all! The option is 
available because it can be handy in some circumstances. Choose the menu item Build Auto generate to auto 
generate the project. Read the info pages of automake and autoconf for more details on how these tools work. 
Clean This option cleans the project and leaves it in a state that requires Build All to be performed. It 
deletes all of the files generated by the build process, including all object files (*.o files) and the 
executable(s) in the src directory (
 and other directories). Choose the menu item Build Clean to clean the project. Clean All There is not a 
great deal to say about Clean All (which might also be called Clean distribution, or clean dist for short). 
It cleans the project and leaves it in a state that requires Configure and Build All to be performed. It 
deletes all of the files generated by the build processes, including all the object files (*.o files), 
executable(s) and Makefiles. In other words, it leaves the project as though it has just been extracted from 
a distribution tarball. Choose the menu item Build Clean All to completely clean the project."
+#. (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 <gui>file manager pane</gui>, select a file or a directory."
 msgstr ""
 
-#: C/preferences.xml:3(title)
-msgid "Preferences"
-msgstr "Inställningar"
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:62
+msgid ""
+"Click on the right mouse button to make the <gui>file manager context menu</"
+"gui> appear and select <guiseq><gui>Build</gui><gui>Build</gui></guiseq> to "
+"build all targets in the directory currently selected or the parent "
+"directory of the currently selected file."
+msgstr ""
 
-#: C/preferences.xml:4(para)
-msgid "Preferences are ways to customize <application>anjuta</application> to suit your tastes. Activate 
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> to bring up the 
preferences dialog. If you want to reset the preferences to their default values, it can be done from 
<menuchoice><guimenu>Settings</guimenu><guimenuitem> Set Default Preferences</guimenuitem></menuchoice>. Some 
are explained below."
+#. (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 <gui>project manager pane</gui>, select a source file or a target."
 msgstr ""
 
-#: C/preferences.xml:11(title)
-msgid "General"
-msgstr "Allmänt"
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:77
+msgid ""
+"Click on the right mouse button to make the <gui>project manager context "
+"menu</gui> appear and select <guiseq><gui>Build</gui><gui>Build</gui></"
+"guiseq> to build all targets in the directory containing the currently "
+"selected file or target."
+msgstr ""
 
-#: C/preferences.xml:13(para)
-msgid "<emphasis>Project Directory</emphasis> is the path where you plan to put all your projects. 
Application wizard creates new projects in this directory only. The default project directory is ~/Projects 
and generally, this is just fine for most people. Also, when Open project is activated, this is the base 
directory where the file selectior will start."
+#. (itstool) path: info/desc
+#: C/autotools-build-clean.page:11
+msgid "Remove built files."
 msgstr ""
 
-#: C/preferences.xml:20(para)
-msgid "<emphasis>User Info:</emphasis> Provide your correct Name and Email address here. They are not used 
to do software registration (pun), rather they are used to create ChangeLog entries and other insert text 
bits."
+#. (itstool) path: page/title
+#: C/autotools-build-clean.page:20
+msgid "Clean targets"
 msgstr ""
 
-#: C/preferences.xml:27(title)
-msgid "File Manager"
-msgstr "Filhanterare"
+#. (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 ""
 
-#: C/preferences.xml:29(para)
-msgid "<emphasis>Root directory if no project is open</emphasis> is the path where the root of the file 
manager points to if no project is currently open."
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:28
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Clean</"
+"gui></guiseq> to delete all files built in the same directory as the current "
+"edited file."
 msgstr ""
 
-#: C/preferences.xml:34(para)
-msgid "<emphasis>File Filter:</emphasis> It is possible to filter out some file from the file tree, for 
example hidden files or files that are ignored by the version control system which usually means they are 
generated at build time and should not be changed."
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:37
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Clean "
+"Project</gui></guiseq> to delete all project built files,"
 msgstr ""
 
-#: C/license.xml:2(title)
-msgid "License"
-msgstr "Licens"
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:50
+msgid ""
+"Click on the right mouse button to make the <gui>file manager context menu</"
+"gui> appears and select <guiseq><gui>Build</gui><gui>Clean</gui></guiseq> to "
+"delete all files built in the directory currently selected or the parent "
+"directory of the currently selected file."
+msgstr ""
 
-#: C/license.xml:3(para)
-msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink 
type=\"ghelp\" url=\"gnome-help:gpl\">GNU General Public License</ulink> as published by the Free Software 
Foundation; either version 2 of the License, or (at your option) any later version."
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:65
+msgid ""
+"Click on the right mouse button to make the <gui>project manager context "
+"menu</gui> appears and select <guiseq><gui>Build</gui><gui>Clean</gui></"
+"guiseq> to delete all built files in the directory containing the currently "
+"selected file or target."
 msgstr ""
 
-#: C/license.xml:10(para)
-msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without 
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU 
General Public License</citetitle> for more details."
+#. (itstool) path: info/desc
+#: C/autotools-build-compile.page:11
+msgid "Compile files."
 msgstr ""
 
-#: C/license.xml:16(para)
-msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the 
<citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public 
License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" 
url=\"http://www.fsf.org\";> their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. 
<street>59 Temple Place</street> - Suite 330 <city>Boston</city>, 
<state>MA</state><postcode>02110-1301</postcode><country>USA</country></address>"
+#. (itstool) path: page/title
+#: C/autotools-build-compile.page:20
+msgid "Compile files"
 msgstr ""
 
-#: C/legal.xml:2(para)
-msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free 
Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with 
no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this 
<ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual."
-msgstr "Tillstånd att kopiera, distribuera och/eller modifiera detta dokument ges under villkoren i GNU Free 
Documentation License (GFDL), version 1.1 eller senare, utgivet av Free Software Foundation utan 
standardavsnitt och omslagstexter.  En kopia av GFDL finns att hämta på denna <ulink type=\"help\" 
url=\"ghelp:fdl\">länk</ulink> eller i filen COPYING-DOCS som medföljer denna handbok."
+#. (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 ""
 
-#: C/legal.xml:12(para)
-msgid "This manual is part of a collection of GNOME manuals distributed under the GFDL. If you want to 
distribute this manual separately from the collection, you can do so by adding a copy of the license to the 
manual, as described in section 6 of the license."
-msgstr "Denna handbok utgör en av flera GNOME-handböcker som distribueras under villkoren i GFDL.  Om du 
vill distribuera denna handbok separat från övriga handböcker kan du göra detta genom att lägga till en kopia 
av licensavtalet i handboken enligt instruktionerna i avsnitt 6 i licensavtalet."
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:30
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Compile</"
+"gui></guiseq> or press <key>F9</key> to compile the current edited file."
+msgstr ""
 
-#: C/legal.xml:19(para)
-msgid "Many of the names used by companies to distinguish their products and services are claimed as 
trademarks. Where those names appear in any GNOME documentation, and the members of the GNOME Documentation 
Project are made aware of those trademarks, then the names are in capital letters or initial capital letters."
-msgstr "Flera namn på produkter och tjänster är registrerade varumärken. I de fall dessa namn förekommer i 
GNOME-dokumentation - och medlemmarna i GNOME-dokumentationsprojektet är medvetna om dessa varumärken - är de 
skrivna med versaler eller med inledande versal."
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:39
+msgid "From the <gui>file manager pane</gui>, select a file."
+msgstr ""
 
-#: C/legal.xml:35(para)
-msgid "DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR 
IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS 
FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE 
QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD 
ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY 
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY 
CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS 
AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
-msgstr "DOKUMENTET TILLHANDAHÅLLS I \"BEFINTLIGT SKICK\" UTAN NÅGRA SOM HELST GARANTIER, VARE SIG 
UTTRYCKLIGA ELLER UNDERFÖRSTÅDDA, INKLUSIVE, MEN INTE BEGRÄNSAT TILL, GARANTIER ATT DOKUMENTET ELLER EN 
MODIFIERAD VERSION AV DOKUMENTET INTE INNEHÅLLER NÅGRA FELAKTIGHETER, ÄR LÄMPLIGT FÖR ETT VISST ÄNDAMÅL ELLER 
INTE STRIDER MOT LAG. HELA RISKEN VAD GÄLLER KVALITET, EXAKTHET OCH UTFÖRANDE AV DOKUMENTET OCH MODIFIERADE 
VERSIONER AV DOKUMENTET LIGGER HELT OCH HÅLLET PÅ ANVÄNDAREN. OM ETT DOKUMENT ELLER EN MODIFIERAD VERSION AV 
ETT DOKUMENT SKULLE VISA SIG INNEHÅLLA FELAKTIGHETER I NÅGOT HÄNSEENDE ÄR DET DU (INTE DEN URSPRUNGLIGA 
SKRIBENTEN, FÖRFATTAREN ELLER NÅGON ANNAN MEDARBETARE) SOM FÅR STÅ FÖR ALLA EVENTUELLA KOSTNADER FÖR SERVICE, 
REPARATIONER ELLER KORRIGERINGAR. DENNA GARANTIFRISKRIVNING UTGÖR EN VÄSENTLIG DEL AV DETTA LICENSAVTAL. 
DETTA INNEBÄR ATT ALL ANVÄNDNING AV ETT DOKUMENT ELLER EN MODIFIERAD VERSION AV ETT DOKUMENT BEVILJAS ENDAST U
 NDER DENNA ANSVARSFRISKRIVNING; OCH"
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:44
+msgid ""
+"Click on the right mouse button to make the <gui>file manager context menu</"
+"gui> appears and select <guiseq><gui>Build</gui><gui>Compile</gui></guiseq> "
+"to compile the file currently selected in the <gui>file manager pane</gui>."
+msgstr ""
 
-#: C/legal.xml:55(para)
-msgid "UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, 
OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR 
MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY 
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT 
LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL 
OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE 
DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES."
-msgstr "UNDER INGA OMSTÄNDIGHETER ELLER INOM RAMEN FÖR NÅGON LAGSTIFTNING, OAVSETT OM DET GÄLLER KRÄNKNING 
(INKLUSIVE VÅRDSLÖSHET), KONTRAKT ELLER DYLIKT, SKA FÖRFATTAREN, DEN URSPRUNGLIGA SKRIBENTEN ELLER ANNAN 
MEDARBETARE ELLER ÅTERFÖRSÄLJARE AV DOKUMENTET ELLER AV EN MODIFIERAD VERSION AV DOKUMENTET ELLER NÅGON 
LEVERANTÖR TILL NÅGON AV NÄMNDA PARTER STÄLLAS ANSVARIG GENTEMOT NÅGON FÖR NÅGRA DIREKTA, INDIREKTA, 
SÄRSKILDA ELLER OFÖRUTSEDDA SKADOR ELLER FÖLJDSKADOR AV NÅGOT SLAG, INKLUSIVE, MEN INTE BEGRÄNSAT TILL, 
SKADOR BETRÄFFANDE FÖRLORAD GOODWILL, HINDER I ARBETET, DATORHAVERI ELLER NÅGRA ANDRA TÄNKBARA SKADOR ELLER 
FÖRLUSTER SOM KAN UPPKOMMA PÅ GRUND AV ELLER RELATERAT TILL ANVÄNDNINGEN AV DOKUMENTET ELLER MODIFIERADE 
VERSIONER AV DOKUMENTET, ÄVEN OM PART SKA HA BLIVIT INFORMERAD OM MÖJLIGHETEN TILL SÅDANA SKADOR."
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:53
+msgid "From the <gui>project manager pane</gui>, select a source file."
+msgstr ""
 
-#: C/legal.xml:28(para)
-msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE 
DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>"
-msgstr "DOKUMENTET OCH MODIFIERADE VERSIONER AV DOKUMENTET TILLHANDAHÅLLS UNDER VILLKOREN I GNU FREE 
DOCUMENTATION LICENSE ENDAST UNDER FÖLJANDE FÖRUTSÄTTNINGAR: <placeholder-1/>"
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:58
+msgid ""
+"Click on the right mouse button to make the <gui>project manager context "
+"menu</gui> appears and select <guiseq><gui>Build</gui><gui>Compile</gui></"
+"guiseq> to compile the file currently selected in the <gui>project manager "
+"pane</gui>."
+msgstr ""
 
-#: C/introduction.xml:4(para)
-msgid "<application>Anjuta</application> is a versatile Integrated Development Environment (IDE) for C and 
C++. It has been written for GTK+/GNOME, and features a number of advanced programming facilities. It is a 
graphical interface to the collection of command line programming tools available for Linux and UNIX systems. 
These are usually run via a text console, and can be unfriendly to use."
+#. (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 <app>Anjuta</app> if needed."
 msgstr ""
 
-#: C/introduction.xml:12(para)
-msgid "<application>Anjuta</application> is an effort to marry the flexibility and power of command line 
tools with the ease-of-use of the GNOME graphical user interface. It has been made as user-friendly as 
possible."
+#. (itstool) path: info/desc
+#: C/autotools-build-configure-dialog.page:11
+msgid "Autotools configure dialog"
 msgstr ""
 
-#: C/introduction.xml:20(title)
-#: C/introduction.xml:22(screeninfo)
-msgid "Anjuta in action"
+#. (itstool) path: page/title
+#: C/autotools-build-configure-dialog.page:20
+msgid "Autotools Configure Dialog"
 msgstr ""
 
-#: C/introduction.xml:28(para)
-msgid "Please report any problems with <application>Anjuta</application> - this will help to improve the 
software, as well as helping the Open Source community."
+#. (itstool) path: page/p
+#: C/autotools-build-configure-dialog.page:22
+msgid ""
+"The <gui>Configure</gui> dialog allows you to set the following options and "
+"configure the project."
 msgstr ""
 
-#: C/interface.xml:2(title)
-msgid "Getting Familiar with Anjuta"
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:29
+msgid "<gui>Regenerate Project</gui>"
 msgstr ""
 
-#: C/interface.xml:5(title)
-msgid "Starting Anjuta"
-msgstr "Starta Anjuta"
+#. (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. <app>Anjuta</app> automatically checks this check "
+"box when needed so you can leave it in its current state."
+msgstr ""
 
-#: C/interface.xml:6(para)
-msgid "To start <application>Anjuta</application>, open the GNOME <guimenu>Main Menu</guimenu>. 
<application>Anjuta</application> is found on the <guisubmenu>Development</guisubmenu> submenu. In RedHat 8.0 
or later anjuta can be found in <guisubmenu>Extra</guisubmenu> submenu and then 
<guisubmenu>Programming</guisubmenu> submenu."
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:37
+msgid "<gui>Configuration</gui>"
 msgstr ""
 
-#: C/interface.xml:13(title)
-msgid "Anjuta application icon"
+#. (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 ""
 
-#: C/interface.xml:15(screeninfo)
-msgid "Anjuta application icon on the Development menu"
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:49
+msgid "<gui>Build Directory</gui>"
 msgstr ""
 
-#: C/interface.xml:19(para)
-msgid "Click on the <application>Anjuta</application> icon to start. The IDE (<emphasis>Integrated 
Development Environment</emphasis>) will open. Alternatively, <application>anjuta</application> can be 
started from a terminal by issuing the command <command>anjuta</command>. If 
<application>anjuta</application> us started for the first time, it will greet you with a welcome message."
+#. (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 ""
 
-#: C/interface.xml:28(title)
-msgid "Menus"
-msgstr "Menyer"
+#. (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 ""
 
-#: C/interface.xml:29(para)
-msgid "At the top of the <application>Anjuta</application> main window is the menubar. Almost all of the 
functions are available by activating the appropriate menu item. The functions have been grouped according to 
their type. For example, the file operations have been grouped into the <guisubmenu>File</guisubmenu> menu."
+#. (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 ""
 
-#: C/interface.xml:38(title)
-msgid "Menubar"
-msgstr "Menyrad"
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:72
+msgid "<gui>Configure Options</gui>"
+msgstr ""
 
-#: C/interface.xml:40(screeninfo)
-msgid "Anjuta menubar"
+#. (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 ""
 
-#: C/interface.xml:45(para)
-msgid "Most of the menus and submenus can be detached. Click on the detach bar (the dashed line just above 
the first menu item). Once the menu is detached, it will become an independent window."
+#. (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 "
+"<cmd>configure --help</cmd> on the command line. You need to have configured "
+"your project at least one time to have the <cmd>configure</cmd> script."
 msgstr ""
 
-#: C/interface.xml:52(title)
-#: C/interface.xml:54(screeninfo)
-msgid "File menu"
+#. (itstool) path: info/desc
+#: C/autotools-build-configure.page:11
+msgid "Configure an autotools project and manage configurations."
 msgstr ""
 
-#: C/interface.xml:59(para)
-msgid "Shortcut keys are available for many of the menu options. All of the shortcut keys are shown 
alongside the corresponding menu items. A useful reference to the shortcut keys which are not directly 
attachted with the menu is also available in the next section."
+#. (itstool) path: page/title
+#: C/autotools-build-configure.page:20
+msgid "Configure a project"
 msgstr ""
 
-#: C/interface.xml:69(title)
-msgid "Useful Shortcuts"
-msgstr "Användbara genvägar"
+#. (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 ""
 
-#: C/interface.xml:73(para)
-msgid "<emphasis>Switch Editor page:</emphasis> CTRL-TAB (forward) and CTRL-SHIFT-TAB (backward) -- The 
pages could also be switched by right clicking on the notebook tabs and selecting an editor tab (useful when 
all the tabs in the editor are not visible at once). Some desktop configuration may already have these 
shortcut keys assigned. In that case, you will need to reconfigure them (not in anjuta, because they are 
fixed) if you want to avail these shortcuts."
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:30
+msgid "Configure the project"
 msgstr ""
 
-#: C/interface.xml:82(para)
-msgid "<emphasis>Context Help:</emphasis> CTRL-H -- Keep the cursor on the word (for example, the function 
name) for which you want to get the API help and press the shortcut. Context help only works if you have 
<application>DevHelp</application> installed. If you do not have <application>DevHelp</application> 
installed, the context help menu and toolbar button will be inactive. You can get it from 
<application>DevHelp</application> website. You will also have to install the related 
<application>DevHelp</application> books."
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:34
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> "
+"<gui>Configure Project...</gui></guiseq>."
 msgstr ""
 
-#: C/interface.xml:92(para)
-msgid "<emphasis>Auto complete:</emphasis> CTRL-ENTER -- Press the shortcut with the cursor placed at the 
end of incomplete word and a list of words matching the remaining part will appear. Scroll and select the 
right word from the list if you find one."
+#. (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 <link xref="
+"\"autotools-build-configure-dialog\"/> for more information."
 msgstr ""
 
-#: C/interface.xml:99(para)
-msgid "<emphasis>More shortcus:</emphasis> Look for the shortcut keys displayed on right side of the menu 
item labels. They could also be changed as explained in the tip below."
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:47
+msgid "Click on <gui>Execute</gui> to configure the project."
 msgstr ""
 
-#: C/interface.xml:106(title)
-msgid "Customize shortcuts"
-msgstr "Anpassning av genvägar"
+#. (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 ""
 
-#: C/interface.xml:107(para)
-msgid "You can change the default shortcuts by using 
<menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Customize shortcuts</guimenuitem></menuchoice>."
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:60
+msgid "Change the configuration"
 msgstr ""
 
-#: C/interface.xml:116(title)
-msgid "Toolbars"
-msgstr "Verktygsrader"
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:64
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Select "
+"Configuration</gui><gui>Another configuration</gui></guiseq>."
+msgstr ""
 
-#: C/interface.xml:117(para)
-msgid "The operations which used most often are made available from the toolbars. There are five toolbars on 
the main window."
+#. (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 ""
 
-#: C/interface.xml:124(para)
-msgid "<interface>Main Toolbar</interface> - file and editing functions"
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:79
+msgid "Remove configuration"
 msgstr ""
 
-#: C/interface.xml:125(para)
-msgid "<interface>Browser Toolbar</interface> - browse bookmarks and function tags"
+#. (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 ""
 
-#: C/interface.xml:130(title)
-#: C/interface.xml:132(screeninfo)
-msgid "Main toolbar"
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:88
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Remove "
+"Configuration</gui></guiseq>."
 msgstr ""
 
-#: C/interface.xml:137(para)
-msgid "Move the mouse pointer over any toolbar button. A tooltip describing the function of the button will 
appear."
+#. (itstool) path: info/desc
+#: C/autotools-build-distribute.page:11
+msgid "Create a distribution package."
 msgstr ""
 
-#: C/interface.xml:141(para)
-msgid "There are some drop-down combination boxes on the toolbars. These are explained in later sections of 
the manual."
+#. (itstool) path: page/title
+#: C/autotools-build-distribute.page:20
+msgid "Create a distribution package"
 msgstr ""
 
-#: C/interface.xml:150(title)
-msgid "Main Window"
-msgstr "Huvudfönster"
+#. (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 "
+"<cmd>configure</cmd>, <cmd>make</cmd> and <cmd>make install</cmd>."
+msgstr ""
 
-#: C/interface.xml:151(para)
-msgid "In the main window, there are several frames which can be attached/detached and reordered by clicking 
on the title bar:"
+#. (itstool) path: item/p
+#: C/autotools-build-distribute.page:30
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Build "
+"Tarball</gui></guiseq> to create a source distribution package."
 msgstr ""
 
-#: C/interface.xml:160(interface)
-msgid "Documents"
-msgstr "Dokument"
+#. (itstool) path: info/desc
+#: C/autotools-build-install.page:11
+msgid "Install targets or project."
+msgstr ""
 
-#: C/interface.xml:165(interface)
-msgid "Project"
-msgstr "Projekt"
+#. (itstool) path: page/title
+#: C/autotools-build-install.page:20
+msgid "Install targets"
+msgstr ""
 
-#: C/interface.xml:170(interface)
-msgid "Files"
-msgstr "Filer"
+#. (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 <file>/usr/local</"
+"file>."
+msgstr ""
 
-#: C/interface.xml:175(interface)
-msgid "Symbols"
-msgstr "Symboler"
+#. (itstool) path: page/p
+#: C/autotools-build-install.page:29
+msgid "There are several possibilities to install targets or a project."
+msgstr ""
 
-#: C/interface.xml:180(interface)
-msgid "Messages"
-msgstr "Meddelanden"
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:33
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Install</"
+"gui></guiseq> to install all files in the same directory as the current "
+"edited file."
+msgstr ""
 
-#: C/interface.xml:185(interface)
-msgid "Terminal"
-msgstr "Terminal"
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:42
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Install "
+"Project</gui></guiseq> to install all project files,"
+msgstr ""
 
-#: C/interface.xml:193(para)
-msgid "The <interface>Documents window</interface> will have one document active at a time (if there are any 
files opened). All of the file commands will apply to this active document. You can switch to any page by 
clicking on the page tab. You can do the same by right-clicking on the page tabs and choosing the document 
from the pop-up menu that will appear. This is especially useful when you have a lot of files opened, but not 
all of them are visible in the page tab area."
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:55
+msgid ""
+"Click on the right mouse button to make the <gui>file manager context menu</"
+"gui> appears and select <guiseq><gui>Build</gui><gui>Install</gui></guiseq> "
+"to install all files in the directory currently selected or the parent "
+"directory of the currently selected file."
 msgstr ""
 
-#: C/interface.xml:204(para)
-msgid "The <interface>Project window</interface> shows a tree of the project files if you have a project 
opened. Otherwise, the <interface>Project window</interface> is usually hidden. Double-clicking on any item 
in the <interface>Project window</interface> will open that file."
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:70
+msgid ""
+"Click on the right mouse button to make the <gui>project manager context "
+"menu</gui> appears and select <guiseq><gui>Build</gui><gui>Install</gui></"
+"guiseq> to install all files in the directory containing the currently "
+"selected file or target."
 msgstr ""
 
-#: C/interface.xml:212(para)
-msgid "The <interface>Files window</interface> shows a file tree. If no project is open, the file tree 
usually points to the file system root but you can change it in the preferences. If a project is open it 
shows all files inside the project. Double clicking opens a file in the appropriate application as configured 
in the gnome mime preferences. Richt click opens a popup-menu which gives you choices how to open the file."
+#. (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 "
+"<cmd>su</cmd> or <cmd>sudo</cmd> to have enough right. See <link xref="
+"\"autotools-build-preferences-dialog\"/> for more information."
 msgstr ""
 
-#: C/interface.xml:221(para)
-msgid "The <interface>Symbols window</interface> shows shows a tree of availible symbols in the project 
generated from ctags parser. Double clicking opens an editor window with the corresponding file and line."
+#. (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 ""
 
-#: C/interface.xml:226(para)
-msgid "There is also a <interface>Search tab</interface> in the Symbols window where you can search for 
symbols."
+#. (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 "<cmd>make <var>object_file_name</var></cmd>"
+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 "<cmd>make</cmd>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:37
+msgid "Use to build all targets in a directory."
 msgstr ""
 
-#: C/interface.xml:232(para)
-msgid "The <interface>Message window</interface> will list all the messages (both 
<filename>stdout</filename> and <filename>stderr</filename> outputs) when an external command is executed. 
The <interface>Message window</interface> is usually hidden, but appears as soon as an external command is 
executed, such as during file or project compilation, debugging sessions, searches, and many other 
operations. <application>Anjuta</application> also adds its own messages here when necessary."
+#. (itstool) path: item/title
+#: C/autotools-build-plugin.page:40
+msgid "<cmd>make install</cmd>"
 msgstr ""
 
-#: C/interface.xml:240(para)
-msgid "The colors used to display the messages are important. Messages displayed in the standard foreground 
color (usually Black) are normal messages. Those displayed in Blue are important messages such as errors or 
other information. Messages shown in Red are <emphasis>Hot Linked</emphasis>. Double-clicking on such a 
message will take you to the particular file and line number specified in the message."
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:41
+msgid "Use to install all targets in a directory."
 msgstr ""
 
-#: C/interface.xml:248(para)
-msgid "For example, when you compile a file which contains bugs, some red messages will appear showing what 
the problems are, and where they occur. Double-clicking on such messages will open the file and highlight the 
line containing the error."
+#. (itstool) path: item/title
+#: C/autotools-build-plugin.page:44
+msgid "<cmd>make clean</cmd>"
 msgstr ""
 
-#: C/interface.xml:256(para)
-msgid "The <interface>Terminal window</interface> is a terminal emulation where you can type commands just 
like in the gnome-terminal."
+#. (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 "<cmd>make dist</cmd>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:49
+msgid ""
+"Use to build a distributation package, called only in the project directory."
 msgstr ""
 
-#: C/interface.xml:264(title)
-msgid "Session management"
-msgstr "Sessionshantering"
+#. (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 ""
 
-#: C/interface.xml:265(para)
-msgid "All of the settings, including the window sizes and window positions, are saved when you exit 
<application>Anjuta</application>. Session management is still under development, so you should not exit 
<application>Anjuta</application> with any unsaved documents. <application>Anjuta</application> will display 
a warning if you try to exit with unsaved documents still open."
+#. (itstool) path: info/desc
+#: C/autotools-build-preferences-dialog.page:10
+msgid "Autotools build preferences dialog."
 msgstr ""
 
-#: C/fileoperations.xml:2(title)
-msgid "File Operations"
+#. (itstool) path: page/title
+#: C/autotools-build-preferences-dialog.page:19
+msgid "Autotools Build Preferences Dialog"
 msgstr ""
 
-#: C/fileoperations.xml:6(title)
-msgid "Creating a New File and inserting texts"
+#. (itstool) path: page/p
+#: C/autotools-build-preferences-dialog.page:21
+msgid "The dialog allows you to set global options for building files."
 msgstr ""
 
-#: C/fileoperations.xml:8(title)
-msgid "Creating New File"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:27
+msgid "<gui>Run several commands at a time</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:9(para)
-msgid "To create a new file, choose 
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>New</guimenuitem></menuchoice> from the menubar, or 
click on the <guibutton>New File</guibutton> button on the toolbar. A new page will appear in the editor (or 
a new window if the parent document is windowed). This new document will be named 
<filename>newfile#1</filename>, <filename>newfile#2</filename>, <filename>newfile#3</filename> and so on."
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:28
+msgid ""
+"<app>make</app> 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 ""
 
-#: C/fileoperations.xml:20(title)
-msgid "File Wizard"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:33
+msgid "<gui>Continue on errors</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:31(title)
-msgid "New File Wizard"
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:34
+msgid ""
+"By default <app>make</app> 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 ""
 
-#: C/fileoperations.xml:33(screeninfo)
-#: C/fileoperations.xml:154(screeninfo)
-msgid "The Open File dialog"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:39
+msgid "<gui>Translate messages</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:21(para)
-msgid "A wizard can also be used to create a new file.To create a new file, choose 
<menuchoice><guisubmenu>File</guisubmenu><guisubmenu>New</guisubmenu><guimenuitem>File</guimenuitem></menuchoice>
 from the menubar. This will open the New File Wizard dialog. Select the file type. Enter the File name. The 
suffix will be automatically added. You can add a license information (according to your license choice) and 
a header. In case of C-C++ header file, you can also add an header template. Click <guibutton>OK</guibutton> 
to validate the creation. <placeholder-1/>"
+#. (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 "
+"<app>Anjuta</app> 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 ""
 
-#: C/fileoperations.xml:38(para)
-msgid "<application>Anjuta</application> occatinally also creates new files during some operations. For 
example, some CVS operations, such as diff, file log, file status etc, create new files and add the output 
there. These could be saved in real file just like normal new files."
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:48
+msgid "<gui>Highlight build warnings and errors in editor</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:46(title)
-msgid "Inserting Macros"
+#. (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 ""
 
-#: C/fileoperations.xml:47(para)
-msgid "Macros can be used to quickly edit repetitive sequences of text."
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:54
+msgid "<gui>Install as root</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:51(para)
-msgid "Macro plugin must be activated."
+#. (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 <cmd>sudo</cmd> or <cmd>su</cmd> before installing the files to acquire "
+"enough right to do it."
 msgstr ""
 
-#: C/fileoperations.xml:56(title)
-msgid "Inserting"
+#. (itstool) path: info/desc
+#: C/debug-breakpoint-dialog.page:10
+msgid "Used to create or edit a breakpoint"
 msgstr ""
 
-#: C/fileoperations.xml:57(para)
-msgid "Two types of macros are available: Anjuta macros and User macros (My macros). Anjuta macros are not 
modifiable by the user. On the other hand, User macros can be defined and modified by the user."
+#. (itstool) path: page/title
+#: C/debug-breakpoint-dialog.page:23
+msgid "Breakpoint Dialog"
 msgstr ""
 
-#: C/fileoperations.xml:62(para)
-msgid "To insert macro, move the cursor at the desired place. Select 
<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>.
 The dialog window appears. Select the wanted macro in the list. The result of the macro expansion is 
displayed in the window and a summary is shown in the dialog window. Choose <guibutton>Insert</guibutton>. 
The expanded macro text is inserted at the cursor position."
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:27
+msgid "<gui>Location</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:75(title)
-msgid "Macro"
-msgstr "Makro"
+#. (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 ""
 
-#: C/fileoperations.xml:77(screeninfo)
-msgid "The Macro dialog"
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:33
+msgid "<var>file_name</var>:<var>line_number</var>"
 msgstr ""
 
-#: C/fileoperations.xml:70(para)
-msgid "Another possibility to insert macro is to select 
<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</guisubmenu><guimenuitem>Insert 
Macro...</guimenuitem></menuchoice>, then to press the wanted macro shortcut. <placeholder-1/>"
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:34
+msgid "<var>function_name</var>"
 msgstr ""
 
-#: C/fileoperations.xml:84(title)
-msgid "Defining Macros"
-msgstr "Definiera makron"
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:35
+msgid "<var>file_name</var>:<var>function_name</var>"
+msgstr ""
 
-#: C/fileoperations.xml:85(para)
-msgid "From the Insert-Macro window, choose <guibutton>Add</guibutton> or select 
<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</guisubmenu><guimenuitem>Add Macro... 
</guimenuitem></menuchoice>. The Add/Edit window appears. Enter the macro name, choose or define a category 
and enter a shortcut. Then edit text relative to your macro. The character ' | ' will indicate the cursor 
position after the macro insertion. Choose <guibutton>OK</guibutton>. The macro is added to the list."
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:39
+msgid "<gui>Condition</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:93(para)
-msgid "The user can also erase a macro by selecting it in the list (only My Macros) then by choosing 
<guibutton>Remove</guibutton>."
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:40
+msgid ""
+"The break condition is an expression which should evaluate to a boolean "
+"value <code>TRUE</code> (1) or <code>FALSE</code> (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 <code>TRUE</code>."
 msgstr ""
 
-#: C/fileoperations.xml:101(title)
-msgid "Add/Edit Macro"
-msgstr "Lägg till/Redigera makro"
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:45
+msgid ""
+"If you leave this field blank the condition is always considered <code>TRUE</"
+"code>."
+msgstr ""
 
-#: C/fileoperations.xml:103(screeninfo)
-msgid "Add Edit dialog"
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:49
+msgid "<gui>Pass Count</gui>"
 msgstr ""
 
-#: C/fileoperations.xml:97(para)
-msgid "Same manner, macro can be edited and modified by selecting it in the list then by choosing 
<guibutton>Edit</guibutton>. <placeholder-1/>"
+#. (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 ""
 
-#: C/fileoperations.xml:110(title)
-msgid "Macro Keywords"
+#. (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 ""
 
-#: C/fileoperations.xml:111(para)
-msgid "Macros Keywords are available. They can be integrated in the macro definitions. The names of these 
macro Keywords start and finish by the character ' @ '."
+#. (itstool) path: info/desc
+#: C/debug-breakpoint.page:9
+msgid "Managing breakpoints."
 msgstr ""
 
-#: C/fileoperations.xml:119(title)
-msgid "Keyword Macro"
+#. (itstool) path: page/title
+#: C/debug-breakpoint.page:22
+msgid "Breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:121(screeninfo)
-msgid "The Keyword macro"
+#. (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 ""
 
-#: C/fileoperations.xml:115(para)
-msgid "Available macro keywords are : @DATE_TIME@, @DATE_YMD@, @DATE_Y@, @USER_NAME@, @FILE_NAME@, 
@FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, @TABSIZE@, @INDENTSIZE@, @USETABS   <placeholder-1/>"
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:28
+msgid "Listing breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:130(title)
-msgid "Save file"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:32
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Breakpoints</gui></guiseq> to open the <gui>Breakpoint</gui> window."
 msgstr ""
 
-#: C/fileoperations.xml:131(para)
-msgid "You should save new documents as soon as possible to avoid any data loss in case of a crash."
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:38
+msgid "This view has the following columns:"
 msgstr ""
 
-#: C/fileoperations.xml:140(title)
-msgid "Opening and Saving Files"
-msgstr "Öppna och spara filer"
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:42
+#, fuzzy
+#| msgid "Introduction"
+msgid "Location"
+msgstr "Introduktion"
 
-#: C/fileoperations.xml:152(title)
-msgid "Open File dialog"
+#. (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 ""
 
-#: C/fileoperations.xml:144(para)
-msgid "<emphasis>Opening a file:</emphasis> To open an existing file, choose 
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Open</guimenuitem></menuchoice> from the menubar, click 
on the <guibutton>Open</guibutton> button on the toolbar, or press 
<keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo>. This will display the <interface>Open 
File</interface> dialog. <placeholder-1/> Select or enter the file you want to open, then click 
<guibutton>Open</guibutton>. To open more than one file at once, select multiple files to open by first 
pressing CTRL and clicking the files in the list and press <guibutton>Open</guibutton>. If you change your 
mind, click <guibutton>Cancel</guibutton> to dismiss the dialog without opening the file."
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:48 C/debug-stack.page:79
+msgid "Address"
 msgstr ""
 
-#: C/fileoperations.xml:173(title)
-msgid "Open Multiple File dialog"
+#. (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 ""
 
-#: C/fileoperations.xml:175(screeninfo)
-msgid "The Open File dialog in multiple-select mode"
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:53 C/debug-local.page:55 C/debug-watch.page:53
+msgid "Type"
 msgstr ""
 
-#: C/fileoperations.xml:165(para)
-msgid "For selecting multiple files at once, select a file in the dialog and press CTRL once. This will 
bring the file selection dialog in multiple-select mode and multiple files could be selected from the list. 
Multiple file select mode is simlar to single file select mode, except that the file operation (for which the 
file selection was being done) will be performed for all the selected files. <placeholder-1/>"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:54
+msgid ""
+"This always displays <gui>breakpoint</gui>. It will be used in a future "
+"release supporting different kinds of breakpoints."
 msgstr ""
 
-#: C/fileoperations.xml:180(para)
-msgid "The <bold>Show Hidden</bold>, if switched on (Click right), will make the hidden files (files 
starting with \".\"; visible in the file list. Depress it to make them hide. 
<application>Anjuta</application> fileselection dialog also has inbuild file type filter. Select the 
appropiate file type filter in the dialog and the file list will be limited to the files of the selected type 
only."
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:58
+msgid "Condition"
 msgstr ""
 
-#: C/fileoperations.xml:200(screeninfo)
-msgid "The Save As File"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:59
+msgid ""
+"This is the breakpoint condition. It is empty if no condition is defined."
 msgstr ""
 
-#: C/fileoperations.xml:190(para)
-msgid "<emphasis>Saving a file:</emphasis> To save a file, choose 
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save</guimenuitem></menuchoice> from the menubar, click 
on the <guibutton>Save</guibutton> button on the toolbar, or press 
<keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>. This will save the file. If the file is new, a 
<interface>Save As</interface> dialog will appear. Enter a filename and click <guibutton>Save</guibutton> to 
save the new file with the name supplied. <placeholder-1/>"
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:63
+msgid "Pass count"
 msgstr ""
 
-#: C/fileoperations.xml:207(para)
-msgid "<emphasis>Saving a file with a different name:</emphasis> You can explicitly save a file with a new 
filename. To do this, choose <menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save 
As</guimenuitem></menuchoice> from the menubar. A <interface>Save As</interface> dialog will appear prompting 
you to enter the new filename. Enter the name and click <guibutton>Save</guibutton>."
+#. (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 ""
 
-#: C/fileoperations.xml:215(title)
-msgid "File save as overwrite"
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:72
+msgid "State"
 msgstr ""
 
-#: C/fileoperations.xml:216(para)
-msgid "When you use <guimenuitem>Save As</guimenuitem> with an existing file, the original is not deleted. 
It is left unchanged since the last save. If a file with the new filename already exists, a confirmation 
dialog will appear, to ensure that you want to overwrite it. Clicking <guibutton>Yes</guibutton> will 
overwrite the file with the file you are saving."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:73
+msgid "This is the state of the breakpoint. It may be"
 msgstr ""
 
-#: C/fileoperations.xml:228(para)
-msgid "<emphasis>Closing a file:</emphasis> To close a file, choose 
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Close</guimenuitem></menuchoice> from the menubar, or 
click on the <guibutton>Close</guibutton> button on the toolbar. The file could also be closed by clicking 
the <guibutton>cross</guibutton> in the filename tab. This will close the current file. If the file is not 
saved, or is a new file, then <application>Anjuta</application> will prompt you to save the file before 
closing it."
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:75
+msgid "Pending:"
 msgstr ""
 
-#: C/fileoperations.xml:242(title)
-msgid "File auto save"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:75
+msgid "the breakpoint is not set in your program."
 msgstr ""
 
-#: C/fileoperations.xml:243(para)
-msgid "If you have enabled auto-save, it will not auto-save any new files. You must first save them 
manually. The same applies to the <guimenuitem>Save All</guimenuitem> option: it will not save new files, if 
you haven't saved them first manually. <emphasis>You must save a file manually before auto-save or 
<guimenuitem>Save All</guimenuitem> will work with it.</emphasis>"
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:76
+msgid "Permanent:"
 msgstr ""
 
-#: C/fileoperations.xml:255(title)
-msgid "Editing Files"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:76
+msgid "the breakpoint is set (its id number is displayed in parentheses)."
 msgstr ""
 
-#: C/fileoperations.xml:256(para)
-msgid "<application>Anjuta</application> has a number of helpful features which aid in editing and working 
with source files. The following sections describe how to use some of the interesting features available."
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:77
+msgid "Temporary:"
 msgstr ""
 
-#: C/fileoperations.xml:262(title)
-#: C/fileoperations.xml:271(title)
-msgid "Editor Margins"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:77
+msgid "the breakpoint is set but will be deleted if reached."
 msgstr ""
 
-#: C/fileoperations.xml:273(screeninfo)
-#: C/fileoperations.xml:321(screeninfo)
-#: C/fileoperations.xml:423(screeninfo)
-msgid "The Tags toolbar"
+#. (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 ""
 
-#: C/fileoperations.xml:263(para)
-msgid "<emphasis>Editor Margins:</emphasis> Editor margins are the small area on the left of the editor for 
some special purposes. There are three editor margins available and all of them may not be available when you 
first start <application>anjuta</application>. They are Line numbers margin, Markers margin and Code fold 
margin. By default (that is, when you run <application>anjuta</application> for the first time) only the code 
fold margin witll be visible. The rest could be made visible from 
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. <placeholder-1/>"
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:90
+msgid "Setting breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:278(para)
-msgid "The <emphasis>Line Numbers Margin</emphasis> is largest of all the three margins (and slightly darker 
then rest) and displays the document's line numbers. <emphasis>Line Number Margin</emphasis> could be made 
visible or invisible by toggling 
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Line Numbers 
Margin</guimenuitem></menuchoice>. Single left clicking on this margin will select the whole line (including 
the last newline, if present). You can set the font properties for line number margin in the preferences."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:94
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Add "
+"Breakpoint...</gui></guiseq> or right click in the <gui>Breakpoint</gui> "
+"window and select <gui>Add Breakpoint...</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:287(para)
-msgid "<emphasis>Markers Margin</emphasis> is the next margin which can be made visible or invisible by 
selecting <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Markers 
Margin</guimenuitem></menuchoice>. This margin displays graphical icons to mark the give line. The markers 
which will be displayed in this margin are Bookmark marker (rectangular blue colored icon), Breakpoint marker 
(circular red colored) and Line indicator (pointed arrow yellow colored). Bookmark marker is used to indicate 
bookmaked lines which could be toggled from 
<menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</guisubmenu><guimenuitem> Toggle 
Bookmark</guimenuitem></menuchoice> with the cursor placed in that line. The breakpoint marker is used in 
debugger to mark the line with debugging breakpoints (see debugging section for more details). The line 
indicator marker is used to indicate a line when we do a jump from another part, for example when navigating 
the bookm
 arks and during single stepping in debugger."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:100
+msgid ""
+"Fill in the <gui>Location</gui>, which is the position of the breakpoint, "
+"and the other fields if desired. If a file is currently opened in the "
+"editor, the <gui>Location</gui> defaults to the current line. See <link xref="
+"\"debug-breakpoint-dialog\"/> for more information."
 msgstr ""
 
-#: C/fileoperations.xml:300(para)
-msgid "<emphasis>Code folding margin</emphasis> is where the folding tree is visisble. Clicking on these 
folding tree nodes will fold or unfold the code blocks. An underline will also be drawn below the folded line 
to make it more obvious that a block of code has been folded below the line. For more details on code 
folding, see the section <emphasis>Code Folding</emphasis> below."
+#. (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 ""
 
-#: C/fileoperations.xml:308(title)
-msgid "Invisible margin marker"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:114
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Toggle "
+"Breakpoint</gui></guiseq> or right click in the <gui>Editor</gui> window and "
+"select <gui>Toggle Breakpoint</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:319(title)
-msgid "Editor markes when markers margin is invisible"
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:125
+msgid "Editing breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:309(para)
-msgid "If the marker margin is not visible, the markers will be displayed by changing the background color 
of the line. For example, if there a breakpoint marker is set in a line and the marker margin is not visible, 
that line will be displayed with red background. Similarly, for bookmark marker and line indicatior marker, 
the background color of the line will be sky blue and yellow, respectively. If you do not like this (perhaps 
due to some contrasting themes), enable the <emphasis>Markers Margins</emphasis> from 
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Markers 
Margin</guimenuitem></menuchoice>. <placeholder-1/>"
+#. (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 ""
 
-#: C/fileoperations.xml:329(title)
-msgid "Editor Guides"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:133 C/debug-breakpoint.page:160
+msgid "Select a breakpoint in the <gui>Breakpoint</gui> window."
 msgstr ""
 
-#: C/fileoperations.xml:330(para)
-msgid "The editor could be made to make certain document information, which otherwise are normally not 
visible. <emphasis>Indentation guides, white spaces and line end characters</emphasis> are such information 
which could be made visible for editing comfort. They could be make visible or invisible by toggling the menu 
items in <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. Indentation guides 
are the small dotted lines drawn to connect the matching braces in the source code. When the cursor is over 
one such maching braces, the dotted indentation guide is highlighted to give a visual region of the 
indentation."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:136
+msgid ""
+"Right click in the <gui>Breakpoint</gui> window and select <gui>Edit "
+"Breakpoint...</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:340(title)
-#: C/fileoperations.xml:342(screeninfo)
-msgid "Editor with guides"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:141
+msgid ""
+"Change the <gui>Condition</gui> or <gui>Pass Count</gui> fields and click on "
+"<gui>OK</gui> when you are done. See <link xref=\"debug-breakpoint-dialog\"/"
+"> for more information."
 msgstr ""
 
-#: C/fileoperations.xml:348(title)
-msgid "Syntax highlighting"
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:151
+msgid "Removing breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:349(para)
-msgid "<application>Anjuta</application> can highlight many different languages. This is usually done 
automatically by determining the type of the file from the file extension. If 
<application>Anjuta</application> cannot determine the type of the file, there will be no syntax 
highlighting. You can explicitly force a particular highlight style by selecting the style from the menu 
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu><guisubmenu> Highlight 
Mode</guisubmenu></menuchoice>."
+#. (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 ""
 
-#: C/fileoperations.xml:360(title)
-msgid "Code folding"
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:163
+msgid ""
+"Right click in the <gui>Breakpoint</gui> window and select <gui>Remove "
+"Breakpoint</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:361(para)
-msgid "Source files which have block coding properties (such as C, C++, Pascal, Java etc.), have the 
advantage of working with <emphasis>code folds</emphasis>. All of the code blocks in the source file can be 
folded or unfolded by clicking on the fold points in the fold margin of the <interface>Editor 
window</interface> (usually a +/- symbol or up/down arrow). These fold points automatically appear for source 
files which use code blocks."
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:169
+msgid "To remove all breakpoints:"
 msgstr ""
 
-#: C/fileoperations.xml:369(para)
-msgid "Code folding is especially useful when editing big source files that run to thousands of lines. Once 
the folds are closed, the document appears to become smaller, facilitating easy browsing and editing of the 
file."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:173
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Remove "
+"All Breakpoints</gui></guiseq> or right-click in the <gui>Breakpoint</gui> "
+"window and select <gui>Remove All Breakpoints</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:376(para)
-msgid "Please note that code folding and editor guides are only avalible in the scintilla based editor."
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:184
+msgid "Enabling and disabling breakpoints"
 msgstr ""
 
-#: C/fileoperations.xml:381(title)
-msgid "Auto-formatting source code"
+#. (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 ""
 
-#: C/fileoperations.xml:382(para)
-msgid "If the current file is a C or C++ source or header file, then it is possible to automatically indent 
(auto-format) the file. This gives a clean look to the source code, increases legibility, reduces the 
likelihood of syntax errors, and above all it saves time. This can be performed by choosing 
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Auto-format 
</guimenuitem></menuchoice> on the menubar. Change the style of formatting by customizing the choices in the 
preferences."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:191
+msgid ""
+"Click on the <gui>Enable</gui> checkmark in the <gui>Breakpoint</gui> window "
+"or right click in the <gui>Breakpoint</gui> window and select <gui>Enable "
+"Breakpoint</gui> or <gui>Disable Breakpoint</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:392(title)
-msgid "indent"
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:197
+msgid "You can disable all breakpoints using:"
 msgstr ""
 
-#: C/fileoperations.xml:393(para)
-msgid "You will need to have the <application>indent</application> utility installed in order to use this 
feature. Read the <ulink type=\"info\" url=\"info:indent\">info page for 
<application>indent</application></ulink> for further details."
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:201
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Disable "
+"All Breakpoints</gui></guiseq> or right-click in the <gui>Breakpoint</gui> "
+"window and select <gui>Disable All Breakpoints</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:404(title)
-msgid "Symbol browser and Browsing Files"
+#. (itstool) path: info/desc
+#: C/debug-cpu.page:9
+msgid "Examine CPU information."
 msgstr ""
 
-#: C/fileoperations.xml:405(para)
-msgid "All C and C++ source and header files can be browsed using the tags in the files. All of the open C 
and C++ source and header files are scanned for available tags (a \"tag\" refers to a function definition, 
structure, macro, etc.). Please note that Tag and Symbol is used synonymously in this manual, except when 
refering to Tags browser and Symbol browser, which two different interfaces."
+#. (itstool) path: page/title
+#: C/debug-cpu.page:22
+msgid "CPU"
 msgstr ""
 
-#: C/fileoperations.xml:421(title)
-#: C/fileoperations.xml:444(title)
-msgid "Tags toolbar"
+#. (itstool) path: section/title
+#: C/debug-cpu.page:25
+msgid "View CPU registers"
 msgstr ""
 
-#: C/fileoperations.xml:427(title)
-msgid "Function symbols"
-msgstr "Funktionssymboler"
+#. (itstool) path: item/p
+#: C/debug-cpu.page:29
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Registers</gui></guiseq> to open the <gui>Register</gui> window."
+msgstr ""
 
-#: C/fileoperations.xml:428(para)
-msgid "Function prototype and definition, if present in the same file, can be usually distinguished from the 
corrosponding line numbers. Prototypes usually comes before the definition, so they are likely to have 
smaller line numbers."
+#. (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 ""
 
-#: C/fileoperations.xml:414(para)
-msgid "<emphasis>Tags Browser:</emphasis> Tags browser is available on the Browser toolbar. It shows a list 
of tags available in the currently active file (souce file). If there is no tags (or sysmbols) available in 
the file, the tags list will be invisible and a \"No Tags\" will be displayed instead. The tags in this list 
are shown along with the line numbers where they are found. If there are multiple symbols with the same name, 
they will be shown with different line numbers. <placeholder-1/><placeholder-2/>"
+#. (itstool) path: section/title
+#: C/debug-cpu.page:42
+msgid "View memory"
 msgstr ""
 
-#: C/fileoperations.xml:446(screeninfo)
-msgid "Symbol browser"
+#. (itstool) path: item/p
+#: C/debug-cpu.page:46
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Memory</"
+"gui></guiseq> to open the <gui>Memory</gui> window."
 msgstr ""
 
-#: C/fileoperations.xml:436(para)
-msgid "<emphasis>Symbol Browser:</emphasis> If there is a project open, <application>Anjuta</application> 
will scan for tags in all of the source and header files of the project. This way it is possible to go to any 
function definition, structure definition, class definition etc. without manually opening the file. You don't 
even have to know which file that tag is found in (except in the case of function definitions). The symbol 
browser lists all the available symbols in the project. <placeholder-1/>"
+#. (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 ""
 
-#: C/fileoperations.xml:454(title)
-msgid "Tags synchronization"
+#. (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 <gui>Go to "
+"address</gui> to get a small edit box where you can enter an address in "
+"hexadecimal."
 msgstr ""
 
-#: C/fileoperations.xml:455(para)
-msgid "You don't have to worry about the synchronization and update of the tag database. 
<application>Anjuta</application> will take care of everything. You just have to decide which tag you want to 
go to!"
+#. (itstool) path: section/title
+#: C/debug-cpu.page:64
+msgid "View Disassembly"
 msgstr ""
 
-#: C/fileoperations.xml:466(title)
-msgid "Searching for and Replacing text in files"
+#. (itstool) path: item/p
+#: C/debug-cpu.page:69
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Disassembly</gui></guiseq> to open the <gui>Disassembly</gui> window."
 msgstr ""
 
-#: C/fileoperations.xml:468(title)
-msgid "Searching"
+#. (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 ""
 
-#: C/fileoperations.xml:469(para)
-msgid "To search for a <emphasis>text</emphasis> or <emphasis>regular expression</emphasis> string in the 
current file, choose 
<menuchoice><guimenu>Edit</guimenu><guisubmenu>Search</guisubmenu><guimenuitem>Find</guimenuitem></menuchoice>
 or press <keycombo><keycap>Ctrl</keycap><keycap>F</keycap></keycombo>. This will open the 
<interface>Find</interface> dialog."
+#. (itstool) path: info/desc
+#: C/debug-custom.page:9
+msgid "Use custom debugger command."
 msgstr ""
 
-#: C/fileoperations.xml:476(para)
-msgid "Use the text box to specify the string to search for, and select whether it is a normal string or a 
regular expression (RegExp). It is also possible to specify the direction of search, whether the search is 
case-sensitive or not, and the scope of the search. Click <guibutton>Search</guibutton> to start searching."
+#. (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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Debugger "
+"Command</gui></guiseq>."
+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 ""
 
-#: C/fileoperations.xml:482(para)
-msgid "If the search is successful, the matched text in the document will be highlighted, marked... 
(according to the search action choice). If the search is not successful, a <emphasis>match not 
found</emphasis> message will be displayed."
+#. (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 "
+"<gui>Breakpoint</gui> window. It is better to avoid using this command "
+"unless you know exactly what you are doing."
 msgstr ""
 
-#: C/fileoperations.xml:487(para)
-msgid "If you want to search again, click on the <guibutton>Search</guibutton> button on the main toolbar or 
press <keycombo><keycap>Ctrl</keycap><keycap>G</keycap></keycombo>. This will find the next match 
(<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>G</keycap></keycombo> for the previous match). 
You can even change the search text when you do this. Enter the new string in the <guilabel>Search 
Expression</guilabel> text box in the main toolbar."
+#. (itstool) path: info/desc
+#: C/debug-data.page:9
+msgid "Examine program Data."
 msgstr ""
 
-#: C/fileoperations.xml:496(title)
-msgid "Search Text dialog"
+#. (itstool) path: page/title
+#: C/debug-data.page:18
+msgid "Examine data"
 msgstr ""
 
-#: C/fileoperations.xml:501(para)
-msgid "To stop a long research, choose <guibutton>Stop</guibutton> button."
+#. (itstool) path: info/desc
+#: C/debug-execute.page:9
+msgid "Control program execution."
 msgstr ""
 
-#: C/fileoperations.xml:504(para)
-msgid "If the \"Basic Search and Replace\" option is selected in the Setting window, the search direction 
can be choosen from the Expression window."
+#. (itstool) path: page/title
+#: C/debug-execute.page:18
+#, fuzzy
+#| msgid "Introduction"
+msgid "Control execution"
+msgstr "Introduktion"
+
+#. (itstool) path: info/desc
+#: C/debug-expression.page:9
+msgid "Evaluate expressions and modify variables."
 msgstr ""
 
-#: C/fileoperations.xml:509(title)
-msgid "Basic Search Text dialog"
+#. (itstool) path: page/title
+#: C/debug-expression.page:22
+msgid "Examine expressions"
 msgstr ""
 
-#: C/fileoperations.xml:516(title)
-msgid "Specifying Search Range"
+#. (itstool) path: section/title
+#: C/debug-expression.page:25
+msgid "Inspect an expression and modify a variable"
 msgstr ""
 
-#: C/fileoperations.xml:517(para)
-msgid "In the \"Search Target dialog\", define the search location and the action to be done in case of 
search success."
+#. (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 ""
 
-#: C/fileoperations.xml:521(para)
-msgid "The maximum number actions can be defined by User."
+#. (itstool) path: item/p
+#: C/debug-expression.page:33
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Inspect/"
+"Evaluate...</gui></guiseq> or right click in the <gui>Editor</gui> window "
+"and select <gui>Inspect/Evaluate...</gui>."
 msgstr ""
 
-#: C/fileoperations.xml:525(title)
-msgid "Search Target dialog"
+#. (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 <gui>Value</gui> column and entering a new value."
 msgstr ""
 
-#: C/fileoperations.xml:530(para)
-msgid "The user can select where the text will be searched."
+#. (itstool) path: info/desc
+#: C/debug-information.page:9
+msgid "Examine additional program information."
 msgstr ""
 
-#: C/fileoperations.xml:534(title)
-msgid "Search Target In choice"
+#. (itstool) path: page/title
+#: C/debug-information.page:22
+msgid "Miscellaneous information"
 msgstr ""
 
-#: C/fileoperations.xml:540(title)
-msgid "Searching in Files"
+#. (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 ""
 
-#: C/fileoperations.xml:541(para)
-msgid "To find text in your project, select \"search in\" <menuchoice><guimenu> All Project 
Files</guimenu></menuchoice>."
+#. (itstool) path: section/title
+#: C/debug-information.page:28
+msgid "View shared libraries"
 msgstr ""
 
-#: C/fileoperations.xml:545(para)
-#: C/fileoperations.xml:576(para)
-msgid "Enter the text you want to search and specify search options (case-sensitive, complete words ...). 
Click <guibutton>Search</guibutton> to start searching."
+#. (itstool) path: item/p
+#: C/debug-information.page:32
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Info</"
+"gui><gui>Shared Libraries</gui></guiseq>."
 msgstr ""
 
-#: C/fileoperations.xml:550(para)
-msgid "To find text in File list, select \"search in\" <menuchoice><guimenu> Specifying File 
List</guimenu></menuchoice>. Define the Search variables. Click <guibutton>Search</guibutton> to start 
searching."
+#. (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 ""
 
-#: C/fileoperations.xml:557(title)
-msgid "Search File List"
+#. (itstool) path: section/title
+#: C/debug-information.page:44
+msgid "View signals"
 msgstr ""
 
-#: C/fileoperations.xml:565(title)
-msgid "Specifying File Patterns"
+#. (itstool) path: item/p
+#: C/debug-information.page:48
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Info</"
+"gui><gui>Kernel signals</gui></guiseq>."
 msgstr ""
 
-#: C/fileoperations.xml:566(para)
-msgid "To find in files and/or folders, select \"search in\" <menuchoice><guimenu> Specify File 
Patterns</guimenu></menuchoice>, choose the file types and/or folders you want to search."
+#. (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 ""
 
-#: C/fileoperations.xml:571(para)
-msgid "Remember, directories are searched recursively. All of the files under the directory, and the files 
under all the subdirectories, and the files under all of the sub-subdirectories (and so on) are all included 
in the search."
+#. (itstool) path: item/title
+#: C/debug-information.page:58
+msgid "Stop"
 msgstr ""
 
-#: C/fileoperations.xml:582(title)
-msgid "Search File Pattern"
+#. (itstool) path: item/p
+#: C/debug-information.page:59
+msgid ""
+"The debugger stops the program execution when the program receives this "
+"signal."
 msgstr ""
 
-#: C/fileoperations.xml:592(title)
-msgid "Specifying Search Action"
+#. (itstool) path: item/title
+#: C/debug-information.page:63
+msgid "Print"
 msgstr ""
 
-#: C/fileoperations.xml:593(para)
-msgid "The user selects which action will be done in case of search success."
+#. (itstool) path: item/p
+#: C/debug-information.page:64
+msgid "The debugger displays the received signal."
 msgstr ""
 
-#: C/fileoperations.xml:596(para)
-msgid "According to the previous selections (Search in, Search direction ...), some actions coul be 
unavailable."
+#. (itstool) path: item/title
+#: C/debug-information.page:67
+msgid "Pass"
 msgstr ""
 
-#: C/fileoperations.xml:601(title)
-msgid "Search Target Action choice"
+#. (itstool) path: item/p
+#: C/debug-information.page:68
+msgid "The debugger passes the signal to the program."
 msgstr ""
 
-#: C/fileoperations.xml:609(title)
-#: C/fileoperations.xml:617(title)
-msgid "Replacing"
+#. (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 ""
 
-#: C/fileoperations.xml:610(para)
-msgid "Search and replace is similar to just finding text, except that you also specify the replace text in 
the <guilabel>Replace Text</guilabel> text box, and whether or not you want to be prompted before the replace 
takes place (Replace First Match or Replace All Matches)."
+#. (itstool) path: info/desc
+#: C/debug-local.page:9
+msgid "Examine local variables."
 msgstr ""
 
-#: C/fileoperations.xml:622(para)
-msgid "Choose <guibutton>Replace</guibutton> to replace the matched text or <guibutton>Forward</guibutton> 
to jump to the next matched text."
+#. (itstool) path: page/title
+#: C/debug-local.page:22
+msgid "Local variables"
 msgstr ""
 
-#: C/fileoperations.xml:629(title)
-msgid "Search Setting"
+#. (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 <gui>Locals</gui> 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 ""
 
-#: C/fileoperations.xml:630(para)
-msgid "The user has the possibility of saving the setting of his search options."
+#. (itstool) path: section/title
+#: C/debug-local.page:32
+msgid "Listing local variables"
 msgstr ""
 
-#: C/fileoperations.xml:633(para)
-msgid "Item highlighted in red is the active item. Item by defaultt is the search setting which is loaded at 
Anjuta launching."
+#. (itstool) path: item/p
+#: C/debug-local.page:36
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Locals</"
+"gui></guiseq> to open the <gui>Locals</gui> window."
 msgstr ""
 
-#: C/fileoperations.xml:638(title)
-msgid "Search Setting dialog"
+#. (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 ""
 
-#: C/fileoperations.xml:649(title)
-msgid "Printing a file"
+#. (itstool) path: item/title
+#: C/debug-local.page:47 C/debug-watch.page:45
+msgid "Variable"
 msgstr ""
 
-#: C/fileoperations.xml:659(title)
-msgid "Print preview of a C file"
+#. (itstool) path: item/p
+#: C/debug-local.page:48
+msgid "The name of the variable."
 msgstr ""
 
-#: C/fileoperations.xml:661(screeninfo)
-msgid "Print preview"
+#. (itstool) path: item/title
+#: C/debug-local.page:51 C/debug-watch.page:49
+msgid "Value"
 msgstr ""
 
-#: C/fileoperations.xml:650(para)
-msgid "Print preview could be taken by selecting <menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print 
Preview</guimenuitem></menuchoice>. It will render the current file and present a preview of the print. 
Source codes which are hilighted in the editor are also highlighted similarly in the print (or preview). 
Addtional options are available to print with the line numbers, wrapped lines and/or headers in the Editor 
printing preferences from <menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Preferences. 
</guimenuitem></menuchoice><placeholder-1/>"
+#. (itstool) path: item/p
+#: C/debug-local.page:52
+msgid "The variable value."
 msgstr ""
 
-#: C/fileoperations.xml:668(title)
-msgid "Print Preferences"
+#. (itstool) path: item/p
+#: C/debug-local.page:56
+msgid "The type of the variable."
 msgstr ""
 
-#: C/fileoperations.xml:670(screeninfo)
-msgid "Print preferences"
+#. (itstool) path: section/title
+#: C/debug-local.page:62 C/debug-watch.page:153
+msgid "Changing the value of a variable"
 msgstr ""
 
-#: C/fileoperations.xml:675(para)
-msgid "When you are ready to print and satisfied with the preview, select 
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print</guimenuitem></menuchoice> or 
<guibutton>Print</guibutton> from the print preview window. This will bring up the actual print dialog as 
shown below. Select the appropriate print parameters and print the file with <guibutton>Print</guibutton> on 
it."
+#. (itstool) path: item/p
+#: C/debug-local.page:66
+msgid ""
+"In the <gui>Locals</gui> window, select the variable you want to edit and "
+"double click in the <gui>Value</gui> column."
 msgstr ""
 
-#: C/fileoperations.xml:687(title)
-msgid "Print Dialog"
+#. (itstool) path: item/p
+#: C/debug-local.page:70
+msgid "Type the new value."
 msgstr ""
 
-#: C/fileoperations.xml:689(screeninfo)
-msgid "Print dialog"
+#. (itstool) path: info/desc
+#: C/debug-process-dialog.page:9
+msgid "Attach to process dialog"
 msgstr ""
 
-#: C/fileoperations.xml:682(para)
-msgid "Landscaped or portrait page layout, paper size, page orientation and paper type could also be set. 
Remember to set them up properly according to your printer, otherwise printing may not come up properly. 
<placeholder-1/>"
+#. (itstool) path: page/title
+#: C/debug-process-dialog.page:22
+msgid "Attach to Process Dialog"
 msgstr ""
 
-#: C/execute.xml:3(title)
-msgid "Running and Testing"
+#. (itstool) path: page/p
+#: C/debug-process-dialog.page:24
+msgid ""
+"The <gui>Attach to process</gui> dialog allows you to select a currently "
+"running process."
 msgstr ""
 
-#: C/execute.xml:5(title)
-msgid "Executing the program"
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:28
+msgid "<gui>Hide paths</gui>"
 msgstr ""
 
-#: C/execute.xml:6(para)
-msgid "Once your executable is ready after the build, you can execute it by choosing the menu item 
<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Execute</guimenuitem></menuchoice>, or pressing 
<keycap>F3</keycap>. You can specify which executable you want to use in case your project provides more than 
one and specify command line arguments."
+#. (itstool) path: item/p
+#: C/debug-process-dialog.page:29
+msgid "This hides command paths in the process list if checked."
 msgstr ""
 
-#: C/execute.xml:13(title)
-msgid "Dependencies"
-msgstr "Beroenden"
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:32
+msgid "<gui>Hide process parameters</gui>"
+msgstr ""
 
-#: C/execute.xml:14(para)
-msgid "Unlike the build stage, execution doesn't check for dependencies (at least for the time being). In 
other words, it does not check if the executable is up-to-date before it executes the program. So, 
<emphasis>you must take care of that yourself.</emphasis>"
+#. (itstool) path: item/p
+#: C/debug-process-dialog.page:33
+msgid "This hides the command line arguments in the process list if checked."
 msgstr ""
 
-#: C/execute.xml:24(title)
-msgid "Choose executable and set program parameters"
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:36
+msgid "<gui>Display process tree</gui>"
 msgstr ""
 
-#: C/execute.xml:26(screeninfo)
-msgid "Setting program parameters"
+#. (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 <gui>Program Parameters</gui> dialog. "
+"See <link xref=\"run-parameters-dialog\"/> 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 <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Debug "
+"Program</gui></guiseq> or press <keyseq><key>Shift</key><key>F12</key></"
+"keyseq>"
+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 <link xref=\"autotools-build-configure\"/> 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 <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Debug "
+"Process...</gui></guiseq> 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 <gui>Attach to process</gui> dialog and click on "
+"<gui>Attach</gui> to start the debugger on this process. See <link xref="
+"\"debug-process-dialog\"/> 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 <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Debug "
+"Remote...</gui></guiseq>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-run.page:82
+msgid ""
+"Select the type of the connection to the remote application, <gui>Serial "
+"Line Connection</gui> or <gui>TCP/IP Connection</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-run.page:86
+msgid ""
+"For a TCP connection, fill in the <gui>Address</gui> and <gui>Port</gui> "
+"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 <cmd>/dev/ttyb</cmd>."
 msgstr ""
 
-#: C/debugger.xml:3(title)
-msgid "Debugging"
+#. (itstool) path: item/p
+#: C/debug-run.page:92
+msgid ""
+"Click on <gui>Connect</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Stop "
+"Debugger</gui></guiseq>."
+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 <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Stack</"
+"gui></guiseq> to open the <gui>Stack</gui> 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 <code>main()</code> in a C program, "
+"has the highest number."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-stack.page:66
+#, fuzzy
+#| msgid "Files"
+msgid "File"
+msgstr "Filer"
+
+#. (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
+#, fuzzy
+#| msgid "Function symbols"
+msgid "Function"
+msgstr "Funktionssymboler"
+
+#. (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
+#, fuzzy
+#| msgid "Documents"
+msgid "Arguments"
+msgstr "Dokument"
+
+#. (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 <gui>Stack</gui> window, select the frame you want."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-stack.page:99
+msgid "Right-click and select <gui>Set current frame</gui>."
+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 <gui>View Source</gui>."
+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 <gui>Stack</gui> window, right-click and select <gui>Get stack trace</"
+"gui>."
+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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Step In</"
+"gui></guiseq> or press <key>F5</key> or click on the <gui>Step In</gui> 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 <gui>Disassembly window</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Step "
+"Over</gui></guiseq> or press <key>F6</key> or click on the <gui>Step Over</"
+"gui> 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 <gui>Disassembly window</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Step "
+"Out</gui></guiseq> or press <keyseq><key>Shift</key><key>F5</key></keyseq> "
+"or click on the <gui>Step Out</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Run/"
+"Continue</gui></guiseq> or press <key>F4</key> or click on the "
+"<gui>Continue</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Run to "
+"Cursor</gui></guiseq> or press <key>F8</key> or click on the <gui>Run to</"
+"gui> 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 <gui>Disassembly window</gui> 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 <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Pause "
+"Program</gui></guiseq> or click on the <gui>Pause</gui> 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
+#, fuzzy
+#| msgid "Debugging"
+msgid "Debugging tips"
 msgstr "Felsökning"
 
-#: C/debugger.xml:6(para)
-msgid "We are working on a new and improved debugger. The current is buggy and the information provided in 
this chapter might not be up-to-date!"
+#. (itstool) path: section/title
+#: C/debug-tips.page:25
+msgid "Fixing GLib/GTK+ critical errors"
 msgstr ""
 
-#: C/debugger.xml:13(title)
-msgid "Introduction to debugging"
-msgstr "Introduktion till felsökning"
+#. (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 <sys>G_DEBUG</sys> to the value <sys>fatal_criticals</sys>."
+msgstr ""
 
-#: C/debugger.xml:15(emphasis)
-msgid "To debug is human. To fix it is divine..."
+#. (itstool) path: item/p
+#: C/debug-tips.page:35
+msgid ""
+"Open the <link xref=\"run-parameters-dialog\"/> by selecting "
+"<guiseq><gui>Run</gui><gui>Program Parameters...</gui></guiseq> from the "
+"main menu."
 msgstr ""
 
-#: C/debugger.xml:17(para)
-msgid "Well, the <emphasis>human</emphasis> part is what this section is about. The 
<emphasis>divine</emphasis> part is up to you!"
+#. (itstool) path: item/p
+#: C/debug-tips.page:40
+msgid ""
+"Click the plus sign next to <gui>Environment Variables</gui> to expand the "
+"list of environment variables."
 msgstr ""
 
-#: C/debugger.xml:21(para)
-msgid "When a program does not behave in the way it is supposed to, we say the program contains a bug or 
bugs. This does not refer to compilation errors those are simply errors and they are relatively easy to 
clear, because the compiler tells you where the problems are. On the other hand, bugs are errors that happen 
during the execution of the program and they can be hard (sometimes very hard!) to detect. Any program that 
you think is bug-free is never completely bug-free. All we can try to do is to reduce the number of bugs 
contained in the program. The process of removing bugs is known as debugging, and the tool that is used for 
debugging is called the debugger. Anjuta provides a very user-friendly and powerful debugging environment 
(actually, a GUI wrapper over gdb, a powerful command line debugging tool). A debugger tracks and traces the 
execution of the program and provides various views of information needed to study the execution of the 
program. Debugger Targets Befor
 e debugging, it is important to understand what debugging targets are. Debugging targets refer to those 
entities with which the debugger interacts during operation. There are four types of debugging targets: 
Executable Symbol table Core file Process There can be only one target active for each of the four types of 
targets at any give time. All of the targets do not need to be active for the debugger to work, although 
certain combinations are required active for a useful debugging session. Example combinations may be [ 
executable, symbol table, and process ] or [ executable, symbol table and core file ]. The target Executable 
becomes active when an executable file is loaded into the debugger. The target Symbol table is automatically 
loaded from the executable file, therefore it does not have to be handled separately. The symbol table is 
necessary for the debugger to identify the various symbols in the source code of the program. The information 
is included in the executable d
 uring the compilation (as long as the program is compiled with the Debug option enabled The target Core file 
becomes active when the core file is loaded into the debugger. A core file is the memory image of the program 
which was dumped by the kernel, usually because it had performed an illegal operation. The core file can 
provide information such as variable contents, register values, and stack trace of the program at the time of 
the error. By studying the core file it is possible to find out which part of the program has misbehaved and 
resulted in the core dump. The target Process becomes active when the program is executed under the debugger 
or when you attach to an already running process. Starting and Stopping the Debugger To start the debugger, 
choose the menu item DebugStart Debugger. This will start the debugger with the executable of the current 
project. If there is no project open, then it will load the executable of the currently active file. If there 
is no project
  open, and no active file, the debugger will start, but no executable will be loaded. The executable will 
have to be loaded manually. Once the debugger is started, a debugging session will be entered. When debugging 
is complete, exit the debugging session by choosing the menu item DebugStop Debugger. Loading Executables The 
debugger will automatically load an executable if a project or a file is currently open. To load a different 
executable, choose the menu item Debug Load Executable . A file selection dialog will open. Select the 
executable to debug and click on OK. Attaching to a Process It is possible to attach to a running process for 
debugging. Choose the menu item Debug Attach to Process . A list of all the process running on the system 
will appear. Attach to Process dialog Attach to Process dialog Select the process to attach to and click OK. 
Ensure that the executable (and hence the symbol table) have already been loaded into the debugger. If lots 
of question marks 
 (??) appear during the debugging session, then the attached process and the executable do not match. Loading 
a Core file Choose the menu item Debug Load Core file to load the core file. Select the core file in the file 
selection dialog and click OK. When loading a core file, ensure that the executable file (and hence the 
symbol table) has already been loaded otherwise, debugging may be tricky! If lots of question marks (??) 
appear during the debugging session, then the core file and the executable do not match. Execution Execution 
of a program in the debugger can be finely controlled. The program can be executed in single steps, or 
allowed to continue until it encounters a breakpoint. Executing like this is essential for tracking program 
behaviour. Like a video editing session, the program can be executed in slow motion with the ability to go 
forward, pause, stop, and so on. The methods that can be used to execute a program in the debugger are 
described in the next few secti
 ons. Single stepping (step in) Single stepping executes only one statement of the program (from the place 
where it has stopped) and then returns control. If the statement that is executed contains one or more 
functions, the debugger tries to step inside the functions (in the sequence in which the functions are 
executed). Once the statement is executed and control is passed back, it is possible to study the various 
program parameters. If the program has not been started at the time single stepping is started, the program 
will be started and will be stopped at the first statement of the program (the first statement in the 
function main()). Choose the menu item Debug ExecutionStep In or click on the Step In icon in the Debug 
toolbar to step into a program. Single stepping (step over) Step over is similar to step in, except that it 
does not step inside any function in the statement being executed. The statement will be executed in one go. 
Choose the menu item Debug ExecutionStep
  Over or click on the Step Over icon in the Debug toolbar to step over statements in a program. Single 
stepping (step out) Step out will execute the current function until it returns. The program will be stopped 
once it exits from the function. Step out is not really single stepping, because it does not only execute a 
single statement it executes the whole function until that function returns to the calling function. Choose 
the menu item Debug ExecutionStep Out or click on the Step Out icon in the Debug toolbar to step out in a 
program. Run/Continue This option will continue the execution of the program until a breakpoint is 
encountered, or the program exits. If the program is not yet started, then the program will be started and 
executed until a breakpoint or program termination is reached. Choose the menu item Debug 
ExecutionRun/Continue or click on the Run/Continue icon in the Debug toolbar to continue the execution of a 
program. Stop Program This option will kill the pro
 gram which is being debugged. Note that it is not possible to stop an attached process. Choose the menu item 
Debug Stop Program or click on the Stop Program icon in the Debug toolbar to terminate the execution of a 
program. Restart Program This option will stop the program and then restart it. All of the breakpoints will 
remain in effect. Note that it is not possible to restart an attached process. Choose the menu item Debug 
Restart Program to restart the execution of a program. Breakpoints When debugging a program, it is useful to 
be able to stop the execution of the program at a particular point, so that the state of the program can be 
examined at that location. Breakpoints enable this to happen. Breakpoints can be set at different locations 
in a source file, and then the program is allowed to run. When a breakpoint is encountered, the execution of 
the program is suspended, enabling expressions to be evaluated, variables to be inspected, the stack trace to 
be studied, and 
 so on. Breakpoint dialog Breakpoint dialog Location, refers to the location of the code in the source file. 
Location can be specified in any of the following formats: File_name:Line_number Function_name 
File:Function_name The first one is obvious The location refers to the line number Line_number in the source 
file File. The second refers to the first line of the function Function_name. The third is similar to the 
second, except that this notation is used where there is more than one function with the name Function_name 
in the program. It is possible to differentiate between them by providing the File, so the notation refers to 
the function Function_name in the file File. Two parameters can be associated with each breakpoint: Break 
condition Pass count The Break condition is a valid C expression which should evaluate to a Boolean value 
that is, the evaluation of the expression should result in either TRUE(1) or FALSE(0). If the final 
evaluation value is not a Boolean value, 
 then it will be appropriately type casted to a Boolean. Every time the breakpoint is encountered during the 
execution, the break condition will be evaluated. The debugger will break the execution only if the 
evaluation results in a TRUE value, otherwise it will continue the execution as though there had been no 
breakpoint. The default value of Break condition is always TRUE. The debugger will break the execution at the 
breakpoint location. The Pass count is an integer (unsigned) value which tells the debugger to skip the 
breakpoint that number of times before it is considered. Pass count has a higher priority than the Break 
condition. Only when the Pass count reaches zero will the debugger evaluate the Break condition (if any 
condition is present). If there is no condition, the debugger will break the execution once the Pass count 
counts down to zero. The default value of the Pass count is zero. The breakpoint will be considered when it 
is first encountered. Adding or Settin
 g Breakpoints The Breakpoint editing window can be opened by choosing View Breakpoints or DebugBreakpoints 
Breakpoints . Click on Add. A dialog will appear. Breakpoint add dialog Breakpoint add dialog Enter the 
location at which to set the breakpoint. Optionally, enter the Break condition and the Pass count in the 
appropriate entry boxes. Click OK to set the breakpoint. A breakpoint may also be by highlighting the 
function name in the editor and choosing the menu item Debug BreakpointsSet Breakpoint (or by clicking on the 
Toggle breakpoint at cursor button on the Debug Toolbar). Editing Breakpoints Open the Breakpoint editing 
window by choosing the menu item View Breakpoints or DebugBreakpoints Breakpoints . Select the breakpoint to 
edit and click on Edit. A dialog will appear. Breakpoint edit dialog Breakpoint edit dialog Edit the entries 
as required and click on OK to commit the changes. Deleting Breakpoints Open the Breakpoint editing window by 
choosing the menu item View
  Breakpoints or DebugBreakpoints Breakpoints . Select the breakpoint to delete and click on Delete. The 
breakpoint will be deleted. To delete all breakpoints, click on Delete All. Enabling or Disabling Breakpoints 
Open the Breakpoint editing window by choosing the menu item View Breakpoints or DebugBreakpoints Breakpoints 
. Select the breakpoint to enable or disable and click on Toggle Enable. The breakpoint will be enabled or 
disabled, depending on the current state. To enable all or disable all breakpoints, click on Enable All or 
Disable All. Note When the debugger is started, all breakpoints will be set. Any old breakpoints (where the 
source file is more recent than the breakpoint) will be disabled. Working with Expressions FIXME: Evaluating 
expressions When control is returned from a program possibly at a breakpoint it is possible to evaluate 
expressions or inspect the values of variables in the program. Choose the menu item Debug Inspect/Evaluate , 
or click the Inspect 
 button on the Debug Toolbar. A dialog prompting for the expression will appear. Supply a valid C expression, 
or a variable name, and click on OK. Inspect/Evaluate dialog Inspect/Evaluate dialog A window will appear 
showing the result of the evaluation. Evaluation result Evaluation result Alternatively, it is possible to 
highlight the expression in the editor and perform the above steps. This will save typing the expression in 
the Inspect dialog. The expression may be any valid C expression and may include function calls from the 
program, library calls, system calls, etc.. Expression Watch Inspecting or evaluating an expression provides 
the result only once. To continuously monitor some variables or expressions, use expression watch. Add all 
the expressions and variables to monitor in the watch. These values will be automatically updated and shown 
in the expression watch window. Expression Watch window Evaluation watch Adding an expression to watch Choose 
the menu item ViewWa
 tch Window. Right-click on the expression watch window to open the Operation menu. Choose the menu item Add. 
A dialog prompting for the expression will appear. Enter the expression and click OK. Add Expression dialog 
Add Expression dialog If the expression was selected in the editor prior to the addition, it will 
automatically appear in the dialog. Removing an expression from watch Choose the menu item ViewWatch Window. 
Right-click on the expression watch window to open the Operation menu. Choose the menu item Remove to remove 
the entry. Clearing the watch Choose the menu item ViewWatch Window. Right-click on the expression watch 
window to open the Operation menu. Choose the menu item Clear to update or clear. Local varables Local 
variables of the current frame (the current funtion in which the program control is present), displayed and 
updated in the Locals pane of the message manager. During execution of the program (eg. during single 
stepping), local variables will be upd
 ated. If any varialble value was changed in the last debugging step, its value will be highlight in red. The 
variables are presented in a tree form for easy view. Local variables Local variables Varables tips Variable 
tips is a quick way to find out the value of a variable. Hover the mouse cursor over the variable name whose 
value you would like to have and wait for a couple of seconds. The value of the variable (if availabe with 
the debugger) will be displayed as a tip. variable-tip Variable tip Stack Trace Stack Window The Stack trace 
window shows the contents of the program stack. It lists all of the functions and their arguments in the 
sequence they were called. There is also a number representing each call. This number is called the Frame. 
Each call in the trace exists in a different frame. This starts from frame 0 (the last function called) and 
grows higher as the function nesting become deeper. Choose the menu item ViewProgram Stack, to open the stack 
trace for the pr
 ogram being debugged. Stack trace window Stack trace window A small arrow points to the currently selected 
frame in the stack trace. By default, this will be frame 0, the last function called. All of the evaluation 
and inspection of expressions or variables will be with reference to this selected frame. The scope of the 
variables or expressions being evaluated will be limited to the selected frame only. The same applies for 
expressions in the watch. Setting the current frame Double-clicking on any frame in the stack trace will set 
that frame as the currently selected frame (the arrow will point to the frame, indicating that it has been 
selected as the current frame). Alternatively, open the Operation menu by right-clicking on the Stack trace 
window, and choose the menu item Set frame to set the frame. Information about the current frame It is 
possible to obtain information about the currently selected frame by choosing the menu item Debug 
InformationInfo Current Frame. A win
 dow will open describing the current frame. Current Frame Information Current Frame Information Updating 
Stack trace Choose the menu item Update from the Operation menu (right-click on the Stack trace window) to 
refresh the Stack trace window. Others There are a number of other debugger features which are used less 
frequently, but are nevertheless handy. Kernel Signals Kernel signals are a way of signaling between 
processes in Linux. The list of signals available for a program can be displayed by choosing the menu item 
ViewKernel Signals. A window will open which lists all of the signals available in the system along with a 
brief description of each signal. Kernel Signals window Kernel Signals window There are three columns which 
specify what to do when the signal is received: Stop this tells the debugger whether to stop the program 
execution (and return control) when the program receives this signal. Print this tells the debugger whether 
to display the received signal. Pass
  this tells the debugger whether to pass the signal to the program. Changing behaviour on signals To change 
the way debugger behaves when a particular signal is received, select the signal in the list. Right-click to 
open the Operation menu. Choose Modify Signal. This will open a dialog. Set the three behaviours and click OK 
to commit the change. Modify Kernel Signal dialog Modify Kernel Signal dialog Sending the signal to the 
program To explicitly sent the signal to the program being debugged, select the signal in the given list. 
Right-click to open the Operation menu. Choose the menu item Send to process. A confirmation dialog will 
appear. Click OK to confirm and send the signal to the program. Updating the signal list Choose the menu item 
Update from the Operation menu (right-click in the Kernal Signals window to open) to refresh the Kernel 
Signals window. CPU registers It is possible to examine the contents of the internal registers of the CPU 
(microprocessor). Choose th
 e menu item View Registers. A window listing all of the available registers in the microprocessor and their 
corrosponding contents will appear. CPU Registers window CPU Registers window Dynamically loaded Libraries To 
obtain a list of the dynamic libraries used by the program, choose the menu item View Shared Libraries. This 
will bring open a window which will list all the shared libraries the program has loaded and their locations 
in the memory. It also shows whether the symbol table is loaded or not (Yes/No). Shared Libraries window 
Shared Libraries window Interrupting the program While the program is running and has control, no debugging 
tasks can be performed. To obtain control while the program is running, choose the menu item Debug Interrupt 
Program. This will interrupt the program and return control to the debugger. For interruption to work 
properly, set the debugger behaviour for the interrupt signal (SIGINT) to the value [ Stop:Yes, Print:Yes, 
Pass:No ]. This is the
  default value."
+#. (itstool) path: item/p
+#: C/debug-tips.page:44
+msgid "Click <gui>New</gui> to add a new entry to the list."
 msgstr ""
 
-#: C/compileopts.xml:4(title)
-msgid "Setting Compiler Options"
+#. (itstool) path: item/p
+#: C/debug-tips.page:47
+msgid ""
+"Fill in <gui>Name</gui> with <input>G_DEBUG</input> and <gui>Value</gui> "
+"with <input>fatal_criticals</input>."
 msgstr ""
 
-#: C/compileopts.xml:5(para)
-msgid "You can customize the the way the compiler will compile your file or project. Remember, each project 
will have its own set of compiler settings. If the options are modified when there is no project open, the 
settings are saved separately and will be used when compiling and building single files only. These are all 
transparent to the user: <application>Anjuta</application> handles them automatically."
+#. (itstool) path: item/p
+#: C/debug-tips.page:51
+msgid "Click <gui>Apply</gui> to confirm the changes."
 msgstr ""
 
-#: C/compileopts.xml:15(title)
-msgid "Support for your program"
+#. (itstool) path: item/p
+#: C/debug-tips.page:54
+msgid ""
+"Run the program with the debugger by selecting <guiseq><gui>Run</"
+"gui><gui>Debug Program</gui></guiseq> from the main menu."
 msgstr ""
 
-#: C/compileopts.xml:17(para)
-msgid "You have have seen in the previous sections how to specify basic compile options (such as include and 
library paths, linker settings, and so on). This process can be cumbersome when you want to use some of the 
more standard or popular libraries GTK and GNOME, for example. To enable easy implementation of these 
libraries and to avoid and inconsistencies, the developers of such libraries usually supply a configuration 
program (usually called *-config) along with their libraries. Well, that's the theory. Now for the practical 
part. Anjuta will do the difficult parts for you, so you do not need to worry about the configuration 
programs for these libraries just add the particular support to your project. To add support for a library to 
your program: Choose the menu item Settings Compiler and Linker Settings and click on the Supports tab in the 
Compiler Options dialog. Select the supports for your program by double-clicking on them. Double-clicking 
again on any selected sup
 ports will unselect them. Supports dialog Supports dialog This will automatically set all the include paths 
and the libraries necessary for the options chosen. There will be no need to set the include paths and 
libraries manually. Available supports Currently, Anjuta has only a few library support options Glib, GTK, 
GNOME and Bonobo. Some of these are not yet fully supported. Compiler options for supports Once basic library 
supports have been specified, there is no need to manually set the basic compiler options usually required 
for these libraries. Any other libraries may still need compiler settings to be changed. Include Paths To set 
include paths for your program: Choose the menu item Settings Compiler and Linker Settings and click on the 
Include Paths tab in the Compiler Options dialog. Enter each of the paths one by one and click on the Add 
button for each entry. To remove an entry, select the entry in the list and click on Remove. To edit an 
entry, select the entry, m
 odify it in the text box and click on Update To clear all of the entries, click on Clear. Include Paths 
dialog Include Paths dialog Absolute or Relative include paths? If the settings are for a project, then all 
include paths should be relative to the source directory of the project. Avoid using absolute paths 
otherwise, when you distribute the source code, other people will have problems trying to build the program. 
If the settings are are made outside of a project, then it doesn't matter whether the paths are absolute or 
relative the settings will be local to your machine only. Library Paths When your program links to external 
libraries (specified via the Libraries settings in the next section), the linker will search for those 
libraries in the library search paths. Anjuta will automatically use system library paths, but you should add 
any additional search paths to your project. To set library paths for your program: Choose the menu item 
Settings Compiler and Linker Setti
 ngs and click on the Library Paths tab in the Compiler Options dialog. Enter each of the paths one by one 
and click on the Add button for each entry. To remove an entry, select the entry in the list and click on 
Remove. To edit an entry, select the entry, modify it in the text box and click on Update To clear all of the 
entries, click on Clear. Library Paths dialog Library Paths dialog Absolute or Relative include paths? If the 
settings are for a project, then all library paths should be relative to the source directory of the project. 
Avoid using absolute paths otherwise, when you distribute the source code, other people will have problems 
trying to build the program. If the settings are are made outside of a project, then it doesn't matter 
whether the paths are absolute or relative the settings will be local to your machine only. Libraries to link 
Libraries are external modules that must be linked with your program at the final stage of the build, to 
produce another librar
 y or an executable. The linker is passed the list of libraries to link with to construct the final target. 
It is also possible to provide the names of object modules (*.o files) along with the libraries to link 
against. Object modules are specified by a special flag (asterisk *) at the start of the object module name 
(so that Anjuta can differentiate them from the library modules). Object modules must be listed with their 
full paths (absolute or relative, depending upon the context), because they will not be searched for on the 
library search path. Example: in the screenshot below, the first entry \"scintilla\" is a library, while 
those starting with \"*\" are object modules. Libraries dialog Libraries dialog Libraries follow the naming 
format: libXXX.a. When specifying libraries in the list, the prefix \"lib\" and the suffix \".a\" are 
skipped, and only the library name \"XXX\" is given in the entry. To set libraries for your program: Choose 
the menu item Settings Compiler 
 and Linker Settings and click on the Libraries tab in the Compiler Options dialog. Enter each of the library 
names (and object names, if required) and click on the Add button for each entry. Libraries can also be 
selected from the list shown in the right pane of the dialog. Not all libraries will be available in this 
list. Object module paths Object modules must be specified with an explicit path and must start with an 
asterisk (*). Explicit path means the path should be relative path of the object from the source dir and the 
filename should be complete (eg. ../../lib/diagram.o). To remove an entry, select the entry in the list and 
click on Remove. To disable an entry, double-click on the entry in the list. To re-enable it, double-click 
again. Entries that are disabled are not included in the the linking process. To edit an entry, select the 
entry, modify it in the text box and click on Update To clear all of the entries, click on Clear. Defining 
Macros To define macros for 
 your program: Choose the menu item Settings Compiler and Linker Settings and click on the Defines tab in the 
Compiler Options dialog. Enter each macro to define one by one and click on the Add button for each entry. To 
remove an entry, select the entry in the list and click on Remove. To edit an entry, select the entry, modify 
it in the text box and click on Update To clear all of the entries, click on Clear. Defines dialog Defines 
dialog Compiler Warnings It is possible to tell the compiler how to respond to each different type of 
warning. Choose the menu item Settings Compiler and Linker Settings and click on the Warnings tab in the 
Compiler Options dialog. Select the warnings you want to see in the Message window when you compile or build 
your file or project. Selecting No Warnings will disable all warnings. Similarly, selecting All Warnings will 
enable all warnings. Warnings dialog Warnings dialog Code Optimization To set the level of Optimization for 
code compilation: C
 hoose the menu item Settings Compiler and Linker Settings and click on the Optimization tab in the Compiler 
Options dialog. Select the level of optimization required. Optimization dialog Optimization dialog Note that 
it is not a good idea to enable any sort of optimization if you have also enabled debugging. It will not do 
any harm to do so, but it will make life much more difficult when debugging the program. With optimization 
enabled, the compiler will modify your code to improve performance. This sometimes creates confusion during 
debugging, as the line number that the debugger refers to will not always correspond to the actual line 
number in the source file. Code optimization takes place during the compilation stage only, and does not 
affect the source code in the file. Other compiler settings To set miscellaneous compiler settings: Choose 
the menu item Settings Compiler and Linker Settings and click on the Others tab in the Compiler Options 
dialog. Various options for c
 ompiling are set on this tabbed section. Other Compiler Settings dialog Other Compiler Settings dialog The 
first is the Enable Debugging option. This option tells the compiler to add extra debug information (such as 
the symbol table), which is necessary for stepping through the code. This makes the program slightly larger. 
This option will be most useful during the development of your program. When the code is ready for the 
release, disable this option and build the program again. The project should be cleaned first before the 
rebuild otherwise, due to automatic dependency checking, not all of the files may be built with this option 
disabled. Note that it is not a good idea to enable any sort of optimization if you have also enabled 
debugging. It will not do any harm to do so, but it will make life much more difficult when debugging the 
program. With optimization enabled, the compiler will modify your code to improve performance. This sometimes 
creates confusion during debug
 ging, as the line number that the debugger refers to will not always correspond to the actual line number in 
the source file. The second option Enable Profiling is similar to the Enable Debugging option, except that it 
builds your program with profiling information. Profiling is not yet implemented in Anjuta. For the time 
being, you can use gprof, a console-based profiler; or MemProf, which is a GUI (GTK) application. Read the 
gprof manual page to learn how to profile your program. Enabling profiling will make a progam run very 
slowly, so it should only be used for debugging. Additional options to pass to the compiler and linker can be 
entered into the text boxes on this tabbed section."
+#. (itstool) path: item/p
+#: C/debug-tips.page:58
+msgid "Use the program until the critical error occurs."
 msgstr ""
 
-#: C/build.xml:3(title)
-msgid "Compiling and Building"
+#. (itstool) path: item/p
+#: C/debug-tips.page:61
+msgid ""
+"When the debugger stops your program, look at the <link xref=\"debug-stack\"/"
+"> to check where this error comes from."
 msgstr ""
 
-#: C/build.xml:5(title)
-msgid "Compiling and building programs"
+#. (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 ""
 
-#: C/build.xml:6(para)
-msgid "Once you have written a program, you will probably want to build and run it. To compile the current 
file, click choose the menu item 
<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Compile</guimenuitem></menuchoice>, or press 
<keycap>F9</keycap>. The <interface>Message window</interface> will appear and list all the messages 
including any compilation errors. You can double-click on the error lines (displayed in red) to go to the 
particular line where the error occurred. You can define macros, specify include paths, and set the compiler 
options if you so wish. Compiling a file will save it first, then it will be compiled."
+#. (itstool) path: info/desc
+#: C/debug-watch.page:9
+msgid "Monitor expressions and variables."
 msgstr ""
 
-#: C/build.xml:15(para)
-msgid "Compiling a file does not build an executable. It simply generates an object 
(<filename>*.o</filename>) file which is later linked to build the executable."
+#. (itstool) path: page/title
+#: C/debug-watch.page:22
+msgid "Watch expressions"
 msgstr ""
 
-#: C/build.xml:19(para)
-msgid "To build a file, choose the menu item 
<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></menuchoice>, or press 
<keycap>F11</keycap>. This will again display the <interface>Message window</interface> listing all the 
messages that are encountered during the build. The build process will link your object file with libraries 
and generate the executable."
+#. (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 <link xref=\"debug-step\">single-step</link> through "
+"the program."
 msgstr ""
 
-#: C/build.xml:27(title)
-msgid "Build dependencies"
+#. (itstool) path: section/title
+#: C/debug-watch.page:30
+msgid "List watched expressions"
 msgstr ""
 
-#: C/build.xml:28(para)
-msgid "The build process will compile your file first if the object file is not up-to-date or it has not yet 
been generated. This means that you can build a file without first compiling it. However, when you are 
dealing with a project rather then a single file, compiling and building are entirely different concepts."
+#. (itstool) path: item/p
+#: C/debug-watch.page:34
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Watches</"
+"gui></guiseq> to open the <gui>Watches</gui> window."
 msgstr ""
 
-#: C/authors.xml:2(title)
-msgid "Authors"
-msgstr "Upphovsmän"
+#. (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 ""
 
-#: C/authors.xml:3(para)
-msgid "The <application>Anjuta</application> project was founded by Naba Kumar. Please visit <ulink 
type=\"http\" url=\"http://anjuta.org?page=authors/\";>this online list</ulink> to know all Anjuta 
contributors."
+#. (itstool) path: item/p
+#: C/debug-watch.page:46
+msgid "The name of the variable or the expression."
 msgstr ""
 
-#: C/authors.xml:10(para)
-msgid "For more information on <application>Anjuta</application>, please visit the project website at <ulink 
type=\"http\" url=\"http://anjuta.org/\";>http://anjuta.org</ulink>. Bug reports should be made using the Bug 
Tracker at the project development site <ulink type=\"http\" 
url=\"http://www.sourceforge.net/projects/anjuta\";> http://www.sourceforge.net/projects/anjuta</ulink>"
+#. (itstool) path: item/p
+#: C/debug-watch.page:50
+msgid "The variable or expression value."
 msgstr ""
 
-#: C/authors.xml:18(para)
-msgid "This manual was written by Naba Kumar and Andy Piper. Please send all comments and suggestions 
regarding this manual to Anjuta Devel list <email>anjuta-devel list sourceforge net</email>. Comments may 
also be submitted via the project trackers at SourceForge."
+#. (itstool) path: item/p
+#: C/debug-watch.page:54
+msgid "The type of the variable or of the expression result."
 msgstr ""
 
-#: C/anjuta-manual.xml:27(title)
-msgid "Anjuta IDE Manual"
+#. (itstool) path: section/title
+#: C/debug-watch.page:60
+msgid "Update watches"
 msgstr ""
 
-#: C/anjuta-manual.xml:28(edition)
-msgid "v1.0.0"
-msgstr "v1.0.0"
+#. (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 ""
 
-#: C/anjuta-manual.xml:30(para)
-msgid "Manual for the Anjuta IDE"
+#. (itstool) path: section/p
+#: C/debug-watch.page:65
+msgid "To set a watch expression to update automatically:"
 msgstr ""
 
-#: C/anjuta-manual.xml:34(firstname)
-msgid "Naba"
-msgstr "Naba"
+#. (itstool) path: item/p
+#: C/debug-watch.page:69
+msgid ""
+"In the <gui>Watches</gui> window, select the watch you want to update "
+"automatically. Right-click and check that <gui>Automatic Update</gui> if "
+"checked. If not, select it."
+msgstr ""
 
-#: C/anjuta-manual.xml:35(surname)
-msgid "Kumar"
-msgstr "Kumar"
+#. (itstool) path: section/p
+#: C/debug-watch.page:75
+msgid "To update a watch expression manually:"
+msgstr ""
 
-#: C/anjuta-manual.xml:38(firstname)
-msgid "Andy"
-msgstr "Andy"
+#. (itstool) path: item/p
+#: C/debug-watch.page:79
+msgid ""
+"In the <gui>Watches</gui> window, right click and select <gui>Update Watch</"
+"gui> to update the selected watch."
+msgstr ""
 
-#: C/anjuta-manual.xml:39(surname)
-msgid "Piper"
-msgstr "Piper"
+#. (itstool) path: section/p
+#: C/debug-watch.page:84
+msgid "To update all watch expressions manually at once:"
+msgstr ""
 
-#: C/anjuta-manual.xml:42(firstname)
-msgid "Biswapesh"
-msgstr "Biswapesh"
+#. (itstool) path: item/p
+#: C/debug-watch.page:88
+msgid ""
+"In the <gui>Watches</gui> window, right click and select <gui>Update all</"
+"gui> to update all watches at the same time."
+msgstr ""
 
-#: C/anjuta-manual.xml:43(surname)
-msgid "Chattopadhyayr"
-msgstr "Chattopadhyayr"
+#. (itstool) path: section/title
+#: C/debug-watch.page:97
+msgid "Add a watch on an expression"
+msgstr ""
 
-#: C/anjuta-manual.xml:46(firstname)
-msgid "Johannes"
-msgstr "Johannes"
+#. (itstool) path: section/p
+#: C/debug-watch.page:99
+msgid "To add an expression to the watch list:"
+msgstr ""
 
-#: C/anjuta-manual.xml:47(surname)
-msgid "Schmid"
-msgstr "Schmid"
+#. (itstool) path: item/p
+#: C/debug-watch.page:103
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Add "
+"Watch...</gui></guiseq> or in the <gui>Watches</gui> window, right-click and "
+"select <gui>Add Watch...</gui>."
+msgstr ""
 
-#: C/anjuta-manual.xml:51(year)
-msgid "2001-2002"
-msgstr "2001-2002"
+#. (itstool) path: item/p
+#: C/debug-watch.page:108
+msgid ""
+"Enter the expression to watch. Check <gui>Automatic Update</gui> if you want "
+"the expression to be evaluated each time the program is stopped."
+msgstr ""
 
-#: C/anjuta-manual.xml:52(year)
-msgid "2006"
-msgstr "2006"
+#. (itstool) path: section/p
+#: C/debug-watch.page:114
+msgid "An expression can be evaluated and then added as a watch like this:"
+msgstr ""
 
-#: C/anjuta-manual.xml:53(holder)
-msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
-msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
+#. (itstool) path: item/p
+#: C/debug-watch.page:118
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Inspect/"
+"Evaluate</gui></guiseq> or right click in the <gui>Editor</gui> window and "
+"select <gui>Inspect/Evaluate</gui>."
+msgstr ""
 
-#: C/anjuta-manual.xml:54(holder)
-msgid "Johannes Schmid"
-msgstr "Johannes Schmid"
+#. (itstool) path: item/p
+#: C/debug-watch.page:123
+msgid ""
+"Click on <gui>Add</gui> button to add this expression to the watches list."
+msgstr ""
 
-#: C/anjuta-manual.xml:58(para)
-msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the 
<citetitle>GNU Free Documentation License</citetitle>, Version 1.1 or any later version published by the Free 
Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain 
a copy of the <citetitle>GNU Free Documentation License</citetitle> from the Free Software Foundation by 
visiting <ulink type=\"http\" url=\"http://www.fsf.org\";>their Web site</ulink> or by writing to: Free 
Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA."
+#. (itstool) path: section/title
+#: C/debug-watch.page:131
+msgid "Remove a watch"
 msgstr ""
 
-#: C/anjuta-manual.xml:70(para)
-msgid "Many of the names used by companies to distinguish their products and services are claimed as 
trademarks. Where those names appear in any GNOME documentation, and those trademarks are made aware to the 
members of the GNOME Documentation Project, the names have been printed in caps or initial caps."
+#. (itstool) path: section/p
+#: C/debug-watch.page:133
+msgid "You can remove an expression from the watches list."
 msgstr ""
 
-#: C/anjuta-manual.xml:81(revnumber)
-msgid "Anjuta Manual 2.1.0"
-msgstr "Handbok för Anjuta 2.1.0"
+#. (itstool) path: item/p
+#: C/debug-watch.page:137
+msgid ""
+"In the <gui>Watches</gui> window, select the watch you want to remove, then "
+"right-click and select <gui>Remove Watch</gui>."
+msgstr ""
 
-#: C/anjuta-manual.xml:82(date)
-msgid "2007"
-msgstr "2007"
+#. (itstool) path: section/p
+#: C/debug-watch.page:142
+msgid "All watches can be removed at the same time."
+msgstr ""
 
-#: C/anjuta-manual.xml:84(para)
-msgid "Johannes Schmid<email>jhs gnome org</email>"
-msgstr "Johannes Schmid<email>jhs gnome org</email>"
+#. (itstool) path: item/p
+#: C/debug-watch.page:146
+msgid ""
+"In the <gui>Watches</gui> window, right-click and select <gui>Remove all</"
+"gui>."
+msgstr ""
 
-#: C/anjuta-manual.xml:86(para)
-msgid "Anjuta Team"
-msgstr "Anjuta-teamet"
+#. (itstool) path: section/p
+#: C/debug-watch.page:155
+msgid ""
+"If a watch expression corresponds to a variable, you can change its value."
+msgstr ""
 
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: C/anjuta-manual.xml:0(None)
-msgid "translator-credits"
-msgstr "Daniel Nylander <po danielnylander se>, 2007"
+#. (itstool) path: item/p
+#: C/debug-watch.page:160
+msgid ""
+"In the <gui>Watches</gui> window, select the variable you want to edit and "
+"double click in the <gui>Value</gui> 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 <file>.c</file>, <file>.py</file>) 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 <app>Anjuta</app> 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: 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/title
+#. (itstool) path: page/title
+#: C/introduction.page:7 C/introduction.page:12
+msgid "Introduction"
+msgstr "Introduktion"
+
+#. (itstool) path: info/desc
+#: C/introduction.page:8
+msgid "Introduction to <app>Anjuta</app> Integrated Development Environment"
+msgstr ""
+
+#. (itstool) path: page/p
+#: C/introduction.page:14
+msgid ""
+"<app>Anjuta</app> 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 ""
+"<app>Anjuta</app> 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 ""
+"<app>Anjuta</app> has been designed to be simple to operate yet powerful "
+"enough to fulfill all your programming needs. We have added many new "
+"features to <app>Anjuta</app> 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 <app>Anjuta</app> 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 <app>Anjuta</app>. 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 "
+"<app>Anjuta</app>."
+msgstr ""
+
+#. (itstool) path: figure/title
+#: C/introduction.page:51
+msgid "<app>Anjuta</app> in action"
+msgstr ""
+
+#. (itstool) path: figure/desc
+#. (itstool) path: media/p
+#: C/introduction.page:52 C/introduction.page:54
+msgid "<app>Anjuta</app> main window"
+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 <code>:</code> and a value, separated by <code>;</code> "
+"and surrounded by <code>-*-</code>."
+msgstr ""
+
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-emacs.page:25
+msgid "A typical <app>Emacs</app> 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 "<code>indent-tabs-mode</code>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/language-support-cpp-modelines-emacs.page:36
+msgid ""
+"Set to <code>t</code> to use tabulation for indentation or <code>nil</code> "
+"to use spaces."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-emacs.page:40
+msgid "<code>tab-width</code>"
+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 "<code>c-basic-offset</code>"
+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 "
+"<code>vim:</code> followed by at least one space and a list of variable "
+"names with an optional value after <code>=</code> separated by space or "
+"<code>:</code>."
+msgstr ""
+
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-vim.page:25
+msgid "A typical <app>Vim</app> 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 "<code>expandtab</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:35
+msgid "<code>et</code>"
+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 "<code>noexpandtab</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:40
+msgid "<code>noet</code>"
+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 "<code>softtabstop</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:45
+msgid "<code>sts</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:46
+msgid "<code>tabstop</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:47
+msgid "<code>ts</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:51
+msgid "<code>shiftwidth</code>"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:52
+msgid "<code>sw</code>"
+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 <app>Anjuta</app> 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
+#, fuzzy
+#| msgid "Project"
+msgid "Import a Project"
+msgstr "Projekt"
+
+#. (itstool) path: page/p
+#: C/project-import.page:26
+msgid ""
+"<app>Anjuta</app> 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 <file>.anjuta</file> extension and a hidden directory created "
+"in the project directory. To use a project in <app>Anjuta</app> 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 <gui>main menu</gui>, select <guiseq><gui>File</gui> <gui>New</"
+"gui><gui>Project from Existing Sources</gui></guiseq> or <gui>Project from "
+"Existing Sources</gui> from the drop-down list of the <gui>New</gui> button "
+"in the <gui>top tool bar</gui> to start the project wizard."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-import.page:47
+msgid ""
+"Select <gui>Import from folder</gui> 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 <gui>Import from version control system</gui> 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 <gui>Project name</gui> 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 <gui>Import</gui> button to download "
+"the project if needed and create the files needed by <app>Anjuta</app>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-import.page:68
+msgid ""
+"<app>Anjuta</app> 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 "
+"<gui>project view</gui>, click on the right mouse button to make the "
+"<gui>project context menu</gui> appear and select <gui>Add Group</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-folder-add.page:29
+msgid ""
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>Add "
+"Group</gui></guiseq>."
+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 <gui>group tree view</gui>."
+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 <gui>Add</"
+"gui> 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 <gui>project view</gui>, click "
+"on the right mouse button to make the <gui>project context menu</gui> appear "
+"and select <gui>Remove</gui>."
+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 <link xref=\"project-manager-module-new\">here</link>. 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 <gui>project view</gui>, click on the right mouse button to "
+"make the <gui>project context menu</gui> appear and select <gui>Properties</"
+"gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:41 C/project-manager-library-add.page:65
+msgid ""
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> "
+"<gui>Properties</gui></guiseq>. 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 (<file>/usr/"
+"include</file>) you don't have to set this. If not, you need to add <input>-"
+"I<var>include_path</var></input> in the <gui>C preprocessor flags</gui> "
+"property if you are using <app>gcc</app> 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 <gui>More options</gui> button to see this. "
+"Click on the <gui>Apply</gui> 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 <gui>project view</gui>, click on the right "
+"mouse button to make the <gui>project context menu</gui> appear and select "
+"<gui>Properties</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:71
+msgid ""
+"You need to set the <gui>Linker flags</gui> property, adding <input>-"
+"l<var>library_name</var></input> if your compiler is <app>gcc</app>. "
+"<var>library_name</var> is the name of the library file without the "
+"<file>lib</file> prefix and without the <file>.a</file> or <file>.so</file> "
+"extension."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:77
+msgid ""
+"If the library is in not in a standard directory, <app>gcc</app> can look in "
+"additional directories with the option <input>-L<var>library_path</var></"
+"input>."
+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 "
+"<gui>project view</gui>, click on the right mouse button to make the "
+"<gui>project context menu</gui> appear and select <gui>Properties</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-library-remove.page:33
+msgid ""
+"Remove the library from the <gui>C preprocessor flags</gui> and <gui>Linker "
+"flags</gui> properties. Click on the <gui>Apply</gui> 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 "
+"<app>pkg-config</app> 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 <gui>project "
+"view</gui>, click on the right mouse button to make the <gui>project context "
+"menu</gui> appear and select <gui>Add Library</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-module-add.page:37 C/project-manager-module-new.page:35
+msgid ""
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>Add "
+"Library...</gui></guiseq>."
+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 "
+"<gui>target button</gui> 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 <gui>module view</gui> 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 <gui>module view</gui>, you "
+"need to add it as a module first. Click on the button <gui>New Library</gui> "
+"and follow the explanation <link xref=\"project-manager-module-new\">here</"
+"link>."
+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 <gui>Add</gui> 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 <gui>project view</gui>, click on the right mouse "
+"button to make the <gui>project context menu</gui> appear, and select "
+"<gui>Add Library</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:39
+msgid ""
+"On the <gui>Add Library</gui> dialog, click on the <gui>New Library</gui> "
+"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 <app>pkg-config</app> file with a <file>.pc</file> 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 developped on Linux. See the chapter <link xref=\"project-"
+"manager-library-add\"/> 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 <gui>Add</gui> 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 <gui>project view</gui>, click "
+"on the right mouse button to make the <gui>project context menu</gui> "
+"appear, and select <gui>Remove</gui>."
+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 <gui>project view</gui> , click "
+"on the right mouse button to make the <gui>project context menu</gui> appear "
+"and select <gui>Remove</gui>."
+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
+#, fuzzy
+#| msgid "Project Management"
+msgid "Project manager."
+msgstr "Projekthantering"
+
+#. (itstool) path: page/title
+#: C/project-manager.page:21
+#, fuzzy
+#| msgid "Project Management"
+msgid "Project manager plugin"
+msgstr "Projekthantering"
+
+#. (itstool) path: page/p
+#: C/project-manager.page:23
+msgid ""
+"<app>Anjuta</app> 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 choosen when creating or importing a new "
+"project in <app>Anjuta</app>. 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
+#, fuzzy
+#| msgid "Project Management"
+msgid "Project Backend Plugin"
+msgstr "Projekthantering"
+
+#. (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
+#, fuzzy
+#| msgid "Project"
+msgid "Edit a Project"
+msgstr "Projekt"
+
+#. (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
+#, fuzzy
+#| msgid "Files"
+msgid "Add Files"
+msgstr "Filer"
+
+#. (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 "
+"<gui>project view</gui>, click on the right mouse button to make the "
+"<gui>project context menu</gui> appear and select <gui>Add Source File</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:31
+msgid ""
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>Add "
+"Source File...</gui></guiseq>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:35
+msgid ""
+"You can select another target in the top <gui>target chooser button</gui>."
+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 <gui>Add</gui> button to add those files to your project. You can select "
+"several files at the same time keeping <key>Ctrl</key> key pressed or using "
+"the <key>Shift</key> 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 <gui>project view</gui>, click on "
+"the right mouse button to make the <gui>project context menu</gui> appear "
+"and select <gui>Remove</gui>."
+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 <key>Ctrl</key> "
+"key pressed or select a range using the <key>Shift</key> 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 "
+"<gui>project view</gui>, click on the right mouse button to make the "
+"<gui>project context menu</gui> appear and select <gui>New Target</gui>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:34
+msgid ""
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>New "
+"Target...</gui></guiseq>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:38
+msgid ""
+"You can select another directory in the bottom <gui>directory tree view</"
+"gui>."
+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 "
+"<gui>Add</gui> 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 <gui>project view</gui>, click "
+"on the right mouse button to make the <gui>project context menu</gui> appear "
+"and select <gui>Remove</gui>."
+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
+#, fuzzy
+#| msgid "Project"
+msgid "View a Project"
+msgstr "Projekt"
+
+#. (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 <link xref=\"project-manager-module-"
+"new\"/>."
+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 <link xref=\"project-manager-"
+"library\"/>."
+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 <link xref="
+"\"project-manager-folder\"/>."
+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 <link xref=\"project-"
+"manager-target\"/>."
+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 <link xref="
+"\"project-manager-source\"/>."
+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
+#, fuzzy
+#| msgid "Project"
+msgid "Create a Project"
+msgstr "Projekt"
+
+#. (itstool) path: page/p
+#: C/project-wizard-create.page:25
+msgid ""
+"New projects are created from templates. <app>Anjuta</app> 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 <gui>main menu</gui>, select <guiseq><gui>File</gui> <gui>New</"
+"gui><gui>Project</gui></guiseq>."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/project-wizard-create.page:36
+msgid ""
+"Or from the drop-down list of the <gui>New</gui> button in the <gui>top tool "
+"bar</gui>, select <gui>Project</gui> 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 <gui>Forward</gui>."
+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 <gui>Forward</gui>."
+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 <gui>Back</gui>."
+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 <gui>Apply</gui> to save the project "
+"and open it in <app>Anjuta</app>."
+msgstr ""
+
+#. (itstool) path: note/p
+#: C/project-wizard-create.page:85
+msgid ""
+"Each project type corresponds to a template. <app>Anjuta</app> 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 <app>autogen</app>. A project "
+"template file has a <file>.wiz</file> extension, and describes all the "
+"project properties and files needed."
+msgstr ""
+
+#. (itstool) path: page/p
+#: C/project-wizard-template.page:31
+msgid ""
+"This <file>.wiz</file> file looks like a XML file and is documented <link "
+"href=\"http://library.gnome.org/devel/libanjuta/stable/project-wizard-format.";
+"html\">here</link>."
+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 <gui>run parameter</gui> dialog allows you to define the current program "
+"and several parameters."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:27
+msgid "<gui>Program</gui>"
+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 <gui>Browse</gui> "
+"button to choose any other program."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:34
+msgid "<gui>Arguments</gui>"
+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 "<gui>Working Directory</gui>"
+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 "<gui>Environment Variables</gui>"
+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 <gui>New</gui> button to add a new environment variable."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:52
+msgid ""
+"You can click on the <gui>Edit</gui> 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 <gui>Delete</gui> 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 "<gui>Run in Terminal</gui>"
+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 <app>Anjuta</app> 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 <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Run</gui></"
+"guiseq> or press <key>F3</key> 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 <gui>parameter</"
+"gui> dialog. See <link xref=\"run-parameters-dialog\"/> for more information."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/run-run.page:42
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Program "
+"Parameters...</gui></guiseq> 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 <link xref=\"autotools-build-install\"/> 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 ""
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]