[anjuta/gnome-3-28] Update Ukrainian translation



commit 0958ca7666b30cfd8fcebdcf83c7b39c0b74a073
Author: Yuri Chornoivan <yurchor ukr net>
Date:   Mon Jun 29 14:36:57 2020 +0000

    Update Ukrainian translation

 manuals/anjuta-manual/uk/uk.po | 6662 ++++++++++++++++++++++------------------
 1 file changed, 3603 insertions(+), 3059 deletions(-)
---
diff --git a/manuals/anjuta-manual/uk/uk.po b/manuals/anjuta-manual/uk/uk.po
index 9a604173a..80b72199a 100644
--- a/manuals/anjuta-manual/uk/uk.po
+++ b/manuals/anjuta-manual/uk/uk.po
@@ -1,4163 +1,4707 @@
 # Ukrainian translation of anjuta.
 # Copyright (C) 2009 Free Software Foundation Inc.
 # This file is distributed under the same license as the anjuta package.
-# Maxim V. Dziumanenko <dziumanenko gmail com>, 2009.
 #
+# Maxim V. Dziumanenko <dziumanenko gmail com>, 2009.
+# Yuri Chornoivan <yurchor ukr net>, 2020.
 msgid ""
 msgstr ""
 "Project-Id-Version: anjuta master\n"
-"POT-Creation-Date: 2009-05-27 23:35+0000\n"
-"PO-Revision-Date: 2009-05-29 15:23+0300\n"
-"Last-Translator: Maxim V. Dziumanenko <dziumanenko gmail com>\n"
+"POT-Creation-Date: 2020-05-29 18:47+0000\n"
+"PO-Revision-Date: 2020-06-29 17:34+0300\n"
+"Last-Translator: Yuri Chornoivan <yurchor ukr net>\n"
 "Language-Team: Ukrainian <uk li org>\n"
+"Language: uk\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<"
+"=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+"X-Generator: Lokalize 20.07.70\n"
 
-#: C/anjuta-manual.xml:27(title)
-msgid "Anjuta IDE Manual"
-msgstr "Посібник користувача Anjuta IDE"
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+msgctxt "_"
+msgid "translator-credits"
+msgstr ""
+"Юрій Сирота <rasta cvs gnome org>\n"
+"Максим Дзюманенко <mvd mylinux com ua>"
 
-#: C/anjuta-manual.xml:28(edition)
-msgid "v1.0.0"
-msgstr "v1.0.0"
+#. (itstool) path: info/desc
+#: C/index.page:8
+msgid "Help for Anjuta DevStudio."
+msgstr ""
 
-#: C/anjuta-manual.xml:30(para)
-msgid "Manual for the Anjuta IDE"
-msgstr "Довідка з програми Anjuta IDE"
+#. (itstool) path: info/title
+#: C/index.page:9
+#| msgid "Anjuta Team"
+msgctxt "link"
+msgid "Anjuta"
+msgstr "Anjuta"
 
-#: C/anjuta-manual.xml:34(firstname)
-msgid "Naba"
-msgstr "Naba"
+#. (itstool) path: info/title
+#: C/index.page:10
+#| msgid "Anjuta in action"
+msgctxt "text"
+msgid "Anjuta DevStudio"
+msgstr "Anjuta DevStudio"
 
-#: C/anjuta-manual.xml:35(surname)
-msgid "Kumar"
-msgstr "Kumar"
+#. (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"
 
-#: C/anjuta-manual.xml:38(firstname)
-msgid "Andy"
-msgstr "Andy"
+#. (itstool) path: media/span
+#: C/index.page:24
+#| msgid "Anjuta Team"
+msgid "Anjuta logo"
+msgstr "Логотип Anjuta"
 
-#: C/anjuta-manual.xml:39(surname)
-msgid "Piper"
-msgstr "Piper"
+#. (itstool) path: page/title
+#: C/index.page:23
+msgid "<_:media-1/> Anjuta DevStudio"
+msgstr ""
 
-#: C/anjuta-manual.xml:42(firstname)
-msgid "Biswapesh"
-msgstr "Biswapesh"
+#. (itstool) path: section/title
+#: C/index.page:29
+msgid "Project Management"
+msgstr "Керування проєктом"
 
-#: C/anjuta-manual.xml:43(surname)
-msgid "Chattopadhyayr"
-msgstr "Chattopadhyayr"
+#. (itstool) path: section/title
+#: C/index.page:33
+msgid "Coding and code navigation"
+msgstr "Написання коду та навігація кодом"
 
-#: C/anjuta-manual.xml:46(firstname)
-msgid "Johannes"
-msgstr "Johannes"
+#. (itstool) path: section/title
+#: C/index.page:37
+msgid "Building Project"
+msgstr "Збирання проєкту"
 
-#: C/anjuta-manual.xml:47(surname)
-msgid "Schmid"
-msgstr "Schmid"
+#. (itstool) path: section/title
+#: C/index.page:41
+msgid "Debugging Program"
+msgstr "Діагностика програми"
 
-#: C/anjuta-manual.xml:51(year)
-msgid "2001-2002"
-msgstr "2001-2002"
+#. (itstool) path: section/title
+#: C/index.page:51
+msgid "Reference"
+msgstr "Довідник"
 
-#: C/anjuta-manual.xml:52(year)
-msgid "2006-2008"
-msgstr "2006-2008"
+#. (itstool) path: info/desc
+#: C/anjuta-code-assist.page:9
+msgid "Configure and use the integrated editor features"
+msgstr ""
 
-#: C/anjuta-manual.xml:53(holder)
-msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
-msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
+#. (itstool) path: page/title
+#: C/anjuta-code-assist.page:18
+msgid "Autocompletion and calltips"
+msgstr ""
 
-#: C/anjuta-manual.xml:54(holder)
-msgid "Johannes Schmid"
-msgstr "Johannes Schmid"
+#. (itstool) path: section/title
+#: C/anjuta-code-assist.page:21
+msgid "Autocompletion"
+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."
-msgstr ""
-"Дозволяється копіювати, розповсюджувати та/або змінювати цей документ на "
-"умовах <citetitle>GNU Free Documentation License</citetitle>, версії 1.1 або "
-"будь-якої старшої версії, що видана Free Software Foundation без Invariant "
-"Sections, без Front-Cover Texts, та без Back-Cover Texts. Ви можете отримати "
-"копію <citetitle>GNU Free Documentation License</citetitle> у Free Software "
-"Foundation відвідавши <ulink type=\"http\" url=\"http://www.fsf.org\";>їх веб-"
-"сайт</ulink> або написавши до: Free Software Foundation, Inc., 51 Franklin "
-"Street, Fifth Floor, Boston, MA 02110-1301, USA."
-
-#: 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."
-msgstr ""
-"Велика кількість що назв використовуються компаніями для їх продуктів чи "
-"служб є торговельними марками. Якщо такі назви зустрічаються у документації "
-"GNOME, та учасникам проекту документування GNOME відомо, що вони є "
-"торговельними марками, тоді ці назви вказуються у лапках."
-
-#: C/anjuta-manual.xml:81(revnumber)
-msgid "Anjuta Manual 2.1.0"
-msgstr "Посібник з Anjuta Manual версії 2.1.0"
-
-#: C/anjuta-manual.xml:82(date)
-msgid "2007"
-msgstr "2007"
-
-#: C/anjuta-manual.xml:84(para)
-msgid "Johannes Schmid<email>jhs gnome org</email>"
-msgstr "Johannes Schmid<email>jhs gnome org</email>"
-
-#: C/anjuta-manual.xml:86(para)
-msgid "Anjuta Team"
-msgstr "Команда Anjuta"
-
-#: C/anjuta-manual.xml:3(title) C/anjuta-manual.xml:6(title)
-msgid "Introduction"
-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 automatically "
+"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 ""
 
-#: C/anjuta-manual.xml:4(para)
+#. (itstool) path: note/p
+#: C/anjuta-code-assist.page:31
 msgid ""
-"<application>Anjuta</application> is a versatile Integrated Development "
-"Environment (IDE) for the GNOME desktop. It features a number of advanced "
-"programming facilities includes project management, application wizards, an "
-"interactive debugger, an integrated Glade UI designer, integrated Devhelp "
-"API help, an integrated Valgrind memory profiler, an integrated gprof "
-"performance profiler, a class generator, a powerful source editor, source "
-"browsing, and more."
+"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 ""
-"<application>Anjuta</application> - універсальне інтегроване середовище "
-"розробки (IDE) для робочого столу GNOME. Воно містить багато розвинених "
-"можливостей програмування, включаючи керування проектами, помічники "
-"створення програм, інтерактивне налагодження, інтегрований засіб дизайну "
-"інтерфейсу Glade, інтегровану довідку Devhelp API, інтегроване профілювання "
-"пам'яті Valgrind, інтегроване профілювання швидкодії, генератор класів, "
-"потужний редактор тексту програми, перегляд тексту, та інше."
-
-#: C/anjuta-manual.xml:14(para)
-msgid ""
-"Anjuta DevStudio has been designed to be simple to operate yet powerful "
-"enough to fulfill all your programming needs. We've added many new features "
-"to Anjuta over the course of its development. Our focus is on delivering "
-"power and usability at the same time and making your software development "
-"enjoyable without overloading your senses. We intend to continue improving "
-"and stabilizing Anjuta to give you the best IDE experience possible. We hope "
-"you will have a good time using Anjuta. If not, please help us make it "
-"better by reporting bugs and suggestions."
-msgstr ""
-"Anjuta DevStudio розроблено простим у використанні та водночас досить "
-"потужним для потреб програмістів. Протягом історії розробки ми додали до "
-"Anjuta багато нових функцій. Ми намагались досягнути потужності та зручності у використанні, "
-"та водночас зробити розробку програм для вас задоволенням без надмірного укладення. "
-"Ми намагаємося постійно вдосконалювати та стабілізувати "
-"Anjuta, щоб надати вам найкращу IDE. Ми сподіваємося ви отримаєте задоволення від "
-"використання Anjuta. Якщо ні, будь ласка, допоможіть нам покращити програму, сповіщайте про  "
-"усі помилки та висловлюйте пропозиції."
 
-#: C/anjuta-manual.xml:25(para)
+#. (itstool) path: note/p
+#: C/anjuta-code-assist.page:38
 msgid ""
-"The following screenshot illustrates some of the things you will find in "
-"Anjuta."
-msgstr ""
-"Наступний знімок ілюструє деякі елементи, які ви знайдете у Anjuta."
-
-#: C/anjuta-manual.xml:31(title) C/anjuta-manual.xml:33(screeninfo)
-msgid "Anjuta in action"
-msgstr "Anjuta у дії"
-
-#: C/anjuta-manual.xml:39(para)
-msgid ""
-"Anjuta has a flexible and advanced docking system that allows you to lay out "
-"all views in whatever way you like. You can drag and drop the views using "
-"drag bars and rearrange the layout. The layouts are persistent for each "
-"project so you can maintain different layouts for different projects. All "
-"dock views are minimizable to avoid clutter in the main window. Minimized "
-"views appear as icons on the left side of the main window. You can configure "
-"all menu actions either by typing when the cursor is over a menu item (the "
-"usual GNOME way) or through a dedicated shortcut configuration user "
-"interface."
-msgstr ""
-"Anjuta має гнучку та розвинену систему панелей, що дозволяє їх розташовувати "
-"як ви захочете. Ви можете перетягувати панелі та впорядковувати їх розташування. "
-"Розташування запам'ятовується для кожного проекту, тож ви "
-"по різному розташовувати панелі у різних проектах. Усі панелі мінімізуються "
-"для уникання безладу у головному вікні. Мінімізовані "
-"панелі показуються у вигляді значків з лівого боку головного вікна. Ви можете налаштувати "
-"дії усіх меню або вводячи комбінацію клавіш коли курсор знаходиться над пунктом меню (звичайний спосіб для "
-"GNOME) або через окремий інтерфейс налаштовування комбінацій клавіш."
-
-#: C/anjuta-manual.xml:50(para)
-msgid ""
-"Please report any problems with <application>Anjuta</application> - this "
-"will help to improve the software, as well as helping the open source "
-"community."
-msgstr ""
-"Будь ласка, сповіщайте про проблеми у <application>Anjuta</application> - це допоможе "
-"вдосконалити програму, а також допоможе спільноті open source."
-
-#: C/anjuta-manual.xml:2(title)
-msgid "Getting Familiar with Anjuta"
-msgstr "Починаємо роботу з Anjuta"
-
-#: C/anjuta-manual.xml:5(title)
-msgid "Menus and shortcuts"
-msgstr "Меню та комбінації клавіш"
-
-#: C/anjuta-manual.xml:6(para)
-msgid ""
-"At the top of the <application>Anjuta</application> main window is the menu "
-"bar. You can access almost all of Anjuta's functionality through menu items. "
-"Operations have been grouped according to their type. For example, file "
-"operations have been grouped into the <guisubmenu>File</guisubmenu> menu."
-msgstr ""
-"Вгорі головного вікна <application>Anjuta</application> є панель меню. "
-"З меню можна отримати доступ до майже усіх функцій Anjuta. "
-"Операгії згруповано відповідно до їх типу. Наприклад, операції з файлами "
-"згруповано у меню <guisubmenu>Файло</guisubmenu>."
-
-#: C/anjuta-manual.xml:15(title)
-msgid "Menubar"
-msgstr "Панель меню"
-
-#: C/anjuta-manual.xml:17(screeninfo)
-msgid "Anjuta menubar"
-msgstr "Панель меню Anjuta"
-
-#: C/anjuta-manual.xml:23(title) C/anjuta-manual.xml:25(screeninfo)
-msgid "File menu"
-msgstr "Меню Файл"
-
-#: C/anjuta-manual.xml:30(para)
-msgid ""
-"Shortcut keys are available for many menu items. All shortcut keys are shown "
-"alongside the corresponding menu items. Some other useful shortcuts are "
-"listed here."
-msgstr ""
-"Для багатьох пунктів меню призначено комбінації клавіш. Усі комбінації клавіш "
-"показуються у відповідних пунктах меню. Нижче перелічено деякі корисні комбінації."
-
-#: C/anjuta-manual.xml:38(para)
-msgid ""
-"<emphasis>Switch Editor Page:</emphasis><keycombo><keycap>Ctrl</"
-"keycap><keycap>Alt</keycap><keycap>Page Up</keycap></keycombo> (forward) and "
-"<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Page Down</"
-"keycap></keycombo> (backward). You can also switch pages by right-clicking "
-"on the notebook tabs and selecting a filename from the pop-up menu (useful "
-"when all the tabs in the editor are not visible at once). Some desktop "
-"configurations 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 use these shortcuts."
-msgstr ""
-"<emphasis>Перемикання сторінки редагування:</emphasis><keycombo><keycap>Ctrl</"
-"keycap><keycap>Alt</keycap><keycap>Page Up</keycap></keycombo> (вперед) та "
-"<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Page Down</"
-"keycap></keycombo> (назад). Також можна перемикати сторінки клацнувши правою кнопкою "
-"на вкладках та обирати назву файлу з розкривного списку (корисно "
-"коли усі вкладки у редакторі не показуються одночасно). У деяких випадках "
-"такі комбінації клавіш вже використовуються робочим столом. Тоді, що користуватись ними, "
-"їх треба змінити у параметрах робочого столу (не у Anjuta, оскільки вони фіксовані)."
-
-#: C/anjuta-manual.xml:49(para)
-msgid ""
-"<emphasis>Context Help:</emphasis><keycombo><keycap>Shift</"
-"keycap><keycap>F1</keycap></keycombo>. Place the cursor on the word (for "
-"example, the function name) for which you want to get API help and type this "
-"shortcut. Context help only works if you have <application>Devhelp</"
-"application> installed; otherwise, the context help menu and toolbar button "
-"will be inactive. You can get Devhelp from the <application>Devhelp</"
-"application> website. You will also have to install the related "
-"<application>Devhelp</application> books."
-msgstr ""
-"<emphasis>Контекстна довідка:</emphasis><keycombo><keycap>Shift</"
-"keycap><keycap>F1</keycap></keycombo>. Розмістіть курсор у слові (наприклад, "
-"назві функції) яке хочете знайти у довідці з API та натисніть ці клавіші. "
-"Контекстна довідка працює лише якщо у системі встановлено програму <application>Devhelp</"
-"application>; у іншому разі меню та кнопка на панелі контекстної довідки будуть неактивні. "
-"Програму Devhelp можна отримати з веб-сайту <application>Devhelp</"
-"application>. Також треба встановити відповідні книжки  "
-"<application>Devhelp</application>."
-
-#: C/anjuta-manual.xml:60(para)
-msgid ""
-"<emphasis>Autocomplete:</emphasis><keycombo><keycap>Ctrl</"
-"keycap><keycap>Enter</keycap></keycombo>. Type this shortcut with the cursor "
-"placed at the end of an incomplete word and a list of words matching the "
-"remaining part will appear. Scroll and select the right word from the list "
-"if you find one."
-msgstr ""
-"<emphasis>Автодоповнення:</emphasis><keycombo><keycap>Ctrl</"
-"keycap><keycap>Enter</keycap></keycombo>. Введіть цю комбінацію, коли курсор "
-"розташовано наприкінці неповного слова і з'явиться список слів, що відповідають введеній частині слова. "
-"Прокрутіть список та виберіть потрібне слово зі списку."
-
-#: C/anjuta-manual.xml:68(para)
-msgid ""
-"<emphasis>More shortcuts:</emphasis> Look for the shortcut keys displayed on "
-"the right side of menu item labels. Shortcuts can also be changed as "
-"explained in the tip below."
-msgstr ""
-"<emphasis>Інші комбінації клавіш:</emphasis> Подивіться на комбінації, що показані "
-"праворуч від позначок. Їх також можна змінити, описаним нижче способом."
-
-#: C/anjuta-manual.xml:75(title)
-msgid "Customize shortcuts"
-msgstr "Налаштовування комбінації клавіш"
-
-#: C/anjuta-manual.xml:76(para)
-msgid ""
-"You can change the default shortcuts by choosing "
-"<menuchoice><guisubmenu>Edit</guisubmenu><guimenuitem>Preferences</"
-"guimenuitem></menuchoice> and selecting the <interface> Shortcuts</"
-"interface> tab."
-msgstr ""
-"Комбінацію клавіш можна змінити обравши "
-"<menuchoice><guisubmenu>Правка</guisubmenu><guimenuitem>Параметри</"
-"guimenuitem></menuchoice> та обрати вкладку <interface> Комбінації клавіш</"
-"interface>."
-
-#: C/anjuta-manual.xml:87(title)
-msgid "Main Window"
-msgstr "Головне вікно"
-
-#: C/anjuta-manual.xml:88(para)
-msgid ""
-"The main window contains several view windows which can be rearranged by "
-"dragging on their title bars. They can also be minimized by clicking on the "
-"minimize buttons on the left of title bars."
-msgstr ""
-"У головному вікні містяться декілька панелей які можна впорядковувати перетягуванням. "
-"Також їх можна мінімізувати клацнувши на кнопці мінімізації з лівого боку заголовку панелі."
-
-#: C/anjuta-manual.xml:97(para)
-msgid ""
-"The <interface>Documents window</interface> will have one document active at "
-"a time (if there are any files opened). All file commands will apply to this "
-"active document. You can switch to any document by clicking on its tab. You "
-"can do the same by right-clicking on the page tabs and choosing the document "
-"from the pop-up menu that will appear. This is especially useful when you "
-"have a lot of files opened, but not all of them are visible in the page tab "
-"area."
-msgstr ""
-"У вікні <interface>Вікно документу</interface> одночасно може бути активним лише один документ "
-"(якщо відкриті якісь файли). Усі команди роботи з файлами застосовуються до "
-"цього активного документу. Можна перейти до іншого документу, клацнувши на його вкладці. Те ж саме "
-"можна зробити клацанням правою кнопкою на вкладках сторінки та обираючи документ "
-"з розкривного меню, що з'явиться. Це особливо зручно якщо ви відкрили багато файлів, "
-"але не всі з них показані у області вкладок сторінки."
-
-#: C/anjuta-manual.xml:108(para)
-msgid ""
-"The <interface>Project window</interface> shows a tree of project files if "
-"you have a project opened. Otherwise, the <interface>Project window</"
-"interface> is usually hidden. Double-clicking on any item in the "
-"<interface>Project window</interface> will open that file."
-msgstr ""
-"У вікні <interface>Вікно проекту</interface> показано дерево файлів проекту, якщо проект відкритою. "
-"У іншому випадку <interface>Вікно проекту</"
-"interface> зазвичай приховане. Подвійне клацання на будь-якому пункті у вікні "
-"<interface>Вікно проекту</interface> відкриває вказаний файл."
-
-#: C/anjuta-manual.xml:116(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 this in the preferences. If a project is open, the window shows all "
-"files in the project. Double-clicking opens a file in the appropriate "
-"application as configured in the GNOME MIME preferences. Right-clicking "
-"opens a context menu which gives you choices about how to open the file."
-msgstr ""
-"У вікні <interface>Вікно файлів</interface> показано дерево файлів. Якщо проект не відкрито, "
-"дерево файлів зазвичай показує кореневу на файлову систему, але ви можете змінити це у параметрах. "
-"Якщо відкрито інший проект, у вікні показуються усі файли проекту. "
-"При подвійному клацанні відкривається файл у відповідній програмі "
-"згідно налаштуванням GNOME MIME. При клацанню правою кнопкою "
-"відкривається контекстне меню, у якому є різні варіанти відкриття файлу."
-
-#: C/anjuta-manual.xml:125(para)
+"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 ""
-"The <interface>Symbols window</interface> shows a tree of available symbols "
-"in the project generated from the <application>ctags</application> parser. "
-"Double-clicking opens an editor window with the corresponding file and line."
-msgstr ""
-"У вікні <interface>Вікно символів</interface> показується дерево доступних символів "
-"проекту створеному аналізатором <application>ctags</application>. "
-"При подвійному клацанні на символі відкривається відповідний файл та рядок."
-
-#: C/anjuta-manual.xml:130(para)
-msgid ""
-"There is also a <interface>Search tab</interface> in the Symbols window "
-"where you can search for symbols."
-msgstr ""
-"Також у вікні символів є <interface>Вкладка пошуку</interface> у якій можна шукати такі символи."
-
-#: C/anjuta-manual.xml:136(para)
-msgid ""
-"The <interface>Message window</interface> will list all the messages (both "
-"<filename>stdout</filename> and <filename>stderr</filename> outputs) when an "
-"external command is executed. The <interface>Message window</interface> is "
-"usually hidden, but appears as soon as an external command is executed, such "
-"as during file or project compilation, debugging sessions, searches, and "
-"many other operations. <application>Anjuta</application> also adds its own "
-"messages here when necessary."
-msgstr ""
-"У вікні <interface>Вікно повідомлень</interface> показуються усі повідомлення (з потоків "
-"<filename>stdout</filename> та <filename>stderr</filename>) при виконанні "
-"зовнішньої команди. Зазвичай <interface>Вікно повідомлень</interface> приховане, "
-"але з'являється одразу при виконанні зовнішньої команди, наприклад "
-"при компіляції проекту, сенсі налагодження, пошуку, та "
-"інших операціях. При потребі <application>Anjuta</application> також виводить у ньому "
-"свої повідомлення."
-
-#: C/anjuta-manual.xml:144(para)
-msgid ""
-"The colors used to display the messages are important. Messages displayed in "
-"the standard foreground color (usually black) are normal messages. Messages "
-"displayed in orange are warnings, and those displayed in red are errors. "
-"Warning and error messages are <emphasis>linked</emphasis>: double-clicking "
-"on such a message will take you to the particular file and line number "
-"specified in the message."
-msgstr ""
-"Колір, яким виводиться повідомлення, є важливим. Повідомлення, що показуються "
-"зі стандартним кольором (зазвичай чорний) є звичайними повідомленнями. Повідомлення, "
-"що показані помаранчевим - це попередження, червоним - це помилки. "
-"Попередження та помилки є <emphasis>пов'язаними</emphasis>: при подвійному клацання "
-"на таких повідомленнях ви потрапите до файлу та рядка, який відноситься до цієї помилки."
-
-#: C/anjuta-manual.xml:152(para)
-msgid ""
-"For example, when you compile a file which contains errors, some red "
-"messages will appear showing what the problems are, and where they occur. "
-"Double-clicking on such messages will open the file and highlight the line "
-"containing the error."
-msgstr ""
-"Наприклад, коли ви компілюєте файл з помилками, з'являться червоні повідомлення "
-"з описом проблеми та місцем виникнення проблеми. "
-"При подвійному клацанні на таких повідомленнях відкриється файл та буде виділено рядок, "
-"який містить помилку."
-
-#: C/anjuta-manual.xml:160(para)
-msgid ""
-"The <interface>Terminal window</interface> is a terminal emulator where you "
-"can type commands just like in the GNOME Terminal application."
-msgstr ""
-"<interface>Вікно терміналу</interface> є емулятором терміналу, у якому можна вводити "
-"команди, так само як і у програмі GNOME Terminal."
-
-#: C/anjuta-manual.xml:168(title)
-msgid "Session management"
-msgstr "Керування сеансами"
-
-#: C/anjuta-manual.xml:169(para)
-msgid ""
-"All settings, including window sizes and positions, are saved when you exit "
-"<application>Anjuta</application>. Session management is still under "
-"development, so you should not exit <application>Anjuta</application> with "
-"any unsaved documents. <application>Anjuta</application> will display a "
-"warning if you try to exit with unsaved documents still open."
-msgstr ""
-"Усі параметри, включаючи розміри вікон та їх позиції, зберігаються при завершенні "
-"<application>Anjuta</application>. Керування сеансами досі розробляється, тож "
-"не слід завершувати <application>Anjuta</application>, якщо залишились незбереженими зміни у документах.  "
-"<application>Anjuta</application> буде виводити попередження, якщо ви намагатиметесь завершити програму з 
незбереженими відкритими документами."
-
-#: C/anjuta-manual.xml:2(title)
-msgid "File Operations"
-msgstr "Операції з файлами"
+"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 ""
 
-#: C/anjuta-manual.xml:6(title)
-msgid "Creating a new file and inserting text"
-msgstr "Створення нового файлу та вставка тексту"
+#. (itstool) path: page/title
+#: C/anjuta-code-help.page:19
+msgid "Using the API reference"
+msgstr "Користування довідником з програмного інтерфейсу"
 
-#: C/anjuta-manual.xml:8(title)
-msgid "Creating a New File"
-msgstr "Створення нового файлу"
+#. (itstool) path: section/title
+#: C/anjuta-code-help.page:22
+msgid "Browsing the API reference"
+msgstr "Навігація довідником з програмного інтерфейсу"
 
-#: C/anjuta-manual.xml:9(para)
+#. (itstool) path: section/p
+#: C/anjuta-code-help.page:24
 msgid ""
-"To create a new file, choose <menuchoice><guisubmenu>File</"
-"guisubmenu><guimenuitem>New</guimenuitem></menuchoice> from the menu bar, or "
-"click on the <guibutton>New File</guibutton> button on the main toolbar. A "
-"new page will appear in the editor (or a new window if the parent document "
-"is windowed). New documents will be named <filename>newfile#1</filename>, "
-"<filename>newfile#2</filename>, <filename>newfile#3</filename> and so on."
+"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 ""
-"Для створення нового файлу, виберіть меню <menuchoice><guisubmenu>Файл</"
-"guisubmenu><guimenuitem>Створити</guimenuitem></menuchoice> або "
-"натисніть кнопку <guibutton>Створити файл</guibutton> на головній панелі інструментів. "
-"У редакторі відкриється нова сторінка (або нове вікно, якщо батьківську вікно документу показується у 
окремому вікні). "
-"Нові документи матимуть назву <filename>Новий файл 1</filename>, "
-"<filename>Новий файл 2</filename>, <filename>Новий файл 3</filename> та т.і."
-
-#: C/anjuta-manual.xml:19(title)
-msgid "Save file"
-msgstr "Збереження файлу"
-
-#: C/anjuta-manual.xml:20(para)
-msgid ""
-"You should save new documents as soon as possible to avoid any data loss in "
-"case of a crash."
-msgstr ""
-"Щоб запобігти втраті даних при аварії програми нові документи слід зберігати якнайшвидше."
-
-#: C/anjuta-manual.xml:27(title)
-msgid "File Wizard"
-msgstr "Помічник створення файлу"
-
-#: C/anjuta-manual.xml:38(title)
-msgid "New File Wizard"
-msgstr "Помічник створення нового файлу"
 
-#: C/anjuta-manual.xml:40(screeninfo) C/anjuta-manual.xml:153(screeninfo)
-msgid "The Open File dialog"
-msgstr "Діалог відкривання файлу"
-
-#: C/anjuta-manual.xml:28(para)
+#. (itstool) path: section/p
+#: C/anjuta-code-help.page:30
 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 menu bar. "
-"This will open the New File dialog. Select the file type. Enter the "
-"filename. The suffix will be automatically added. You can add license "
-"information (according to your license choice) and a header. In case of a C/C"
-"++ header file, you can also add an header template. Click <guibutton>OK</"
-"guibutton> to validate the creation. <placeholder-1/>"
+"The API reference has two windows, one for searching for a specific symbol "
+"and the browser for viewing the help documents."
 msgstr ""
-"Для створення нового файлу можна використовувати помічник. Для створення нового файлу, виберіть у меню "
-"<menuchoice><guisubmenu>Файл</guisubmenu><guisubmenu>Створити</"
-"guisubmenu><guimenuitem>Файл</guimenuitem></menuchoice>. "
-"Відкриється діалог Новий файл. Виберіть тип файлу. Введіть "
-"назву файлу. Суфікс додається автоматично. Ви можете додати інформацію про ліцензію "
-"(відповідно до вибору ліцензії) та заголовок. Якщо створюється файл заголовку C/C"
-"++, ви також можете додати шаблон заголовку. Для перевірки файл натисніть <guibutton>Гаразд</"
-"guibutton>.<placeholder-1/>"
-
-#: C/anjuta-manual.xml:45(para)
-msgid ""
-"<application>Anjuta</application> occasionally also creates new file windows "
-"during some operations. For example, some Subversion operations such as "
-"<command>Diff</command> and <command>View Log</command> create new file "
-"windows and add the output there. You can save the contents of these windows "
-"to real files if you like."
-msgstr ""
-"Іноді <application>Anjuta</application> також створює нові вікна за файлами при виконанні деяких операцій. "
-"Наприклад, деякі операції Subversion, такі як <command>Diff</command> та <command>View Log</command> 
призводять до створення нових вікон з файлами "
-"та виводу інформації у них. Якщо хочете, можете зберегти зміст цих вікон у справжні файли."
-
-#: C/anjuta-manual.xml:54(title)
-msgid "Inserting Macros"
-msgstr "Макроси вставки"
-
-#: C/anjuta-manual.xml:55(para)
-msgid ""
-"You can use <emphasis>macros</emphasis> to quickly edit repetitive sequences "
-"of text."
-msgstr ""
-"Можна використовувати <emphasis>макроси</emphasis> для швидкого редагування фрагментів тексту, що 
повторюються."
-
-#: C/anjuta-manual.xml:59(para)
-msgid "The Macro plugin must be activated."
-msgstr "Треба активувати модуль Макрос."
-
-#: C/anjuta-manual.xml:64(title)
-msgid "Inserting"
-msgstr "Вставка"
 
-#: C/anjuta-manual.xml:65(para)
+#. (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 ""
-"Two types of macros are available: Anjuta macros and user macros (displayed "
-"as \"My macros\"). Anjuta macros are not modifiable, but you can define and "
-"modify your own user macros."
+"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 ""
-"Доступні два типи макросів: макроси Anjuta та макроси створені користувачем (показується як "
-"\"Мої макроси\"). Макроси Anjuta незмінні, але ви можете визначити та змінювати власні макроси."
 
-#: C/anjuta-manual.xml:69(para)
+#. (itstool) path: page/title
+#: C/anjuta-code-indentation.page:19
+#| msgid "Anjuta in action"
+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 ""
-"To insert a macro, move the cursor to the desired place. Select "
-"<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
-"guisubmenu><guimenuitem>Macros...</guimenuitem></menuchoice>. A dialog "
-"window appears. Select the desired 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."
+"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 ""
-"Щоб вставити макрос, помістіть курсор на бажане місце. Виберіть "
-"<menuchoice><guisubmenu>Правка</guisubmenu><guisubmenu>Макроси</"
-"guisubmenu><guimenuitem>Макрос...</guimenuitem></menuchoice>. Відкриється діалогове вікно. Виберіть бажаний 
макрос зі списку, у вікні з'явиться "
-"текст макросу, а у діалоговому вікні буде показано зведення. Виберіть <guibutton>Вставити</guibutton>. У 
позиції курсору буде вставлено "
-"виконаний макрос."
 
-#: C/anjuta-manual.xml:82(title)
-msgid "Macro"
-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 ""
 
-#: C/anjuta-manual.xml:84(screeninfo)
-msgid "The Macro dialog"
-msgstr "Діалогове вікно макросу"
+#. (itstool) path: note/p
+#: C/anjuta-code-indentation.page:38
+msgid ""
+"Unless explicitly changed in the preferences the indentation settings found "
+"in the Modeline of a file will be used instead of the configured settings to "
+"keep the file consistent."
+msgstr ""
 
-#: C/anjuta-manual.xml:77(para)
+#. (itstool) path: section/title
+#: C/anjuta-code-indentation.page:45
+msgid "Modelines"
+msgstr "Режим рядків"
+
+#. (itstool) path: section/p
+#: C/anjuta-code-indentation.page:47
 msgid ""
-"Another way to insert a macro is to select <menuchoice><guisubmenu>Edit</"
-"guisubmenu><guisubmenu>Macros</guisubmenu><guimenuitem>Insert Macro...</"
-"guimenuitem></menuchoice>, then to press the desired macro shortcut. "
-"<placeholder-1/>"
+"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 ""
-"Інший спосіб вставити макрос - виберіть <menuchoice><guisubmenu>Правка</"
-"guisubmenu><guisubmenu>Макрос</guisubmenu><guimenuitem>Вставити макрос...</"
-"guimenuitem></menuchoice>, і потім натисніть комбінацію клавіш, що відповідає макросу. "
-"<placeholder-1/>"
 
-#: C/anjuta-manual.xml:91(title)
-msgid "Defining Macros"
-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 ""
 
-#: C/anjuta-manual.xml:92(para)
+#. (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 ""
-"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."
+"Normally new lines are appropriately 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 ""
-"У вікні Вставити макрос виберіть <guibutton>Додати</guibutton> або виберіть"
-"<menuchoice><guisubmenu>Правка</guisubmenu><guisubmenu>Макроси</"
-"guisubmenu><guimenuitem>Додати макрос... </guimenuitem></menuchoice>. Відкриється діалогове вікно 
Додати/змінити макрос. "
-"Введіть назву макросу, виберіть або визначте категорію та введіть "
-"комбінацію клавіш. Потім введіть текст макросу. Символ ' | ' "
-"означатиме, позицію курсору після вставки макросу. Натисніть "
-"<guibutton>Гаразд</guibutton>. Макрос буде додано до списку."
 
-#: C/anjuta-manual.xml:100(para)
+#. (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 ""
-"You can also erase a macro by selecting it in the list and choosing "
-"<guibutton>Remove</guibutton>. This only works for user macros (My Macros), "
-"of course."
+"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 ""
-"Також можна видалити макрос обравши його у списку та натиснувши "
-"<guibutton>Видалити</guibutton>. Працює лише для визначених користувачем макросів (Мої макроси), "
-"of course."
 
-#: C/anjuta-manual.xml:108(title)
-msgid "Add/Edit Macro"
-msgstr "Додати/змінити макрос"
+#. (itstool) path: section/p
+#: C/anjuta-code-symbols.page:26
+msgid "The symbol browser has three tabs:"
+msgstr "На панелі навігації символами передбачено три вкладки:"
 
-#: C/anjuta-manual.xml:110(screeninfo)
-msgid "Add Edit dialog"
-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 ""
 
-#: C/anjuta-manual.xml:104(para)
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:30
 msgid ""
-"Similarly, you can edit and modify a macro by selecting it in the list and "
-"choosing <guibutton>Edit</guibutton>. <placeholder-1/>"
+"<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 ""
-"Подібним чином, ви можете змінити макрос, обравши його у списку та "
-"обрати <guibutton>Змінити</guibutton>. <placeholder-1/>"
 
-#: C/anjuta-manual.xml:117(title)
-msgid "Macro Keywords"
-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 ""
 
-#: C/anjuta-manual.xml:118(para)
+#. (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 ""
-"Macro keywords are available. They can be included in macro definitions. "
-"These macro keywords start and finish with the character ' @ '."
+"In the <gui>Goto</gui> popup-menu of the editor there two items that help "
+"you to quickly navigate through the source code:"
 msgstr ""
-"У макросах підтримуються ключові слова. Їх можна включати у визначення макросів. "
-"Такі слова починаються та закінчуються символом ' @ '."
 
-#: C/anjuta-manual.xml:126(title)
-msgid "Keyword Macro"
-msgstr "Макрос з ключовим словом"
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:43
+msgid "<gui>Symbol definition</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:128(screeninfo)
-msgid "The Keyword macro"
-msgstr "Макрос з ключовим словом"
+#. (itstool) path: item/p
+#: C/anjuta-code-symbols.page:44
+msgid "<gui>Symbol declaration</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:122(para)
+#. (itstool) path: section/p
+#: C/anjuta-code-symbols.page:47
 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@, and @USETABS@. <placeholder-1/>"
+"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 ""
-"Доступні ключові слова @DATE_TIME@, @DATE_YMD@, @DATE_Y@, @USER_NAME@, "
-"@FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, @TABSIZE@, "
-"@INDENTSIZE@, and @USETABS@. <placeholder-1/>"
 
-#: C/anjuta-manual.xml:139(title)
-msgid "Opening and Saving Files"
-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 ""
 
-#: C/anjuta-manual.xml:151(title)
-msgid "Open File dialog"
-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 ""
 
-#: C/anjuta-manual.xml:143(para)
+#. (itstool) path: note/p
+#: C/autotools-project-backend.page:41
 msgid ""
-"<emphasis>Opening a file:</emphasis> To open an existing file, choose "
-"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Open</guimenuitem></"
-"menuchoice> from the menu bar, 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 name of file you want to open, "
-"then click <guibutton>Open</guibutton>. To open more than one file at once, "
-"select multiple files to open by holding down the <keycap>Ctrl</keycap> key "
-"and clicking each file in turn; then press <guibutton>Open</guibutton>. If "
-"you change your mind, click <guibutton>Cancel</guibutton> to dismiss the "
-"dialog without opening the file."
+"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 ""
 
-#: C/anjuta-manual.xml:166(title)
-msgid "Open Multiple File dialog"
-msgstr "Діалог відкривання файлу"
+#. (itstool) path: info/desc
+#: C/autotools-project-folder-edit.page:9
+msgid "Edit autotools folder properties."
+msgstr ""
 
-#: C/anjuta-manual.xml:168(screeninfo)
-msgid "The Open File dialog in multiple-select mode"
-msgstr "Діалог відкривання файлу у режимі з множинним виділенням"
+#. (itstool) path: page/title
+#: C/autotools-project-folder-edit.page:18
+msgid "Edit an Autotools Folder"
+msgstr ""
 
-#: C/anjuta-manual.xml:173(para)
+#. (itstool) path: page/p
+#: C/autotools-project-folder-edit.page:20
 msgid ""
-"You can enable the <emphasis>Show Hidden Files</emphasis> option through the "
-"pop-up menu that appears when you right-click in the Open File dialog. This "
-"option will make hidden files (files starting with \".\") visible in the "
-"file list. Clear the option to hide hidden files. The Open File dialog also "
-"has a built-in file type filter. Select the appropriate file type filter in "
-"the dialog and the file list will be limited to the files of the selected "
-"type only."
+"These properties allows you to define common properties for all targets "
+"belonging to this folder."
 msgstr ""
 
-#: C/anjuta-manual.xml:194(screeninfo)
-msgid "The Save As File"
-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 "<gui>Прапорці компілятора C</gui>"
 
-#: C/anjuta-manual.xml:184(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:26
 msgid ""
-"<emphasis>Saving a file:</emphasis> To save a file, choose "
-"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save</guimenuitem></"
-"menuchoice> from the menu bar, 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/>"
+"The flags to pass to the C compiler if a per target value is not defined."
 msgstr ""
 
-#: C/anjuta-manual.xml:199(title)
-msgid "File autosave"
-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 ""
 
-#: C/anjuta-manual.xml:200(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:31
 msgid ""
-"If you have enabled autosave, Anjuta will not autosave any new files. You "
-"must first save them manually. The same applies to the <guimenuitem>Save "
-"All</guimenuitem> option: Anjuta will not save new files, if you haven't "
-"saved them first manually. <emphasis>You must save a file manually before "
-"autosave or <guimenuitem>Save All</guimenuitem> will work with it.</emphasis>"
+"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 ""
 
-#: C/anjuta-manual.xml:211(para)
+#. (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 "<gui>Прапорці компілятора C++</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:37
 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 menu bar. A <interface>Save As</interface> dialog will "
-"appear prompting you to enter the new filename. Enter the name and click "
-"<guibutton>Save</guibutton>."
+"The flags to pass to the C++ compiler flags if a per target value is not "
+"defined."
 msgstr ""
 
-#: C/anjuta-manual.xml:219(title)
-#, fuzzy
-msgid "File save as overwrite"
-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 ""
 
-#: C/anjuta-manual.xml:220(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:42
 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."
+"The flags to pass to the Fortran 9x compiler if a per target value is not "
+"defined."
 msgstr ""
 
-#: C/anjuta-manual.xml:232(para)
+#. (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 ""
-"<emphasis>Closing a file:</emphasis> To close a file, choose "
-"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Close</guimenuitem></"
-"menuchoice> from the menu bar, or click on the <guibutton>Close</guibutton> "
-"button on the toolbar. (You can also close a file by clicking the X in its "
-"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."
+"This defines installation directories. It is needed if you want to install "
+"files in custom directories."
 msgstr ""
 
-#: C/anjuta-manual.xml:249(title)
-msgid "Editing Files"
-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 ""
 
-#: C/anjuta-manual.xml:250(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:52
 msgid ""
-"<application>Anjuta</application> has a number of features which help you "
-"edit and work with source files. The following sections describe how to use "
-"some of the interesting features available."
+"The flags to pass to the Java compiler if a per target value is not defined."
 msgstr ""
 
-#: C/anjuta-manual.xml:256(title) C/anjuta-manual.xml:265(title)
-msgid "Editor Margins"
-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 ""
 
-#: C/anjuta-manual.xml:267(screeninfo) C/anjuta-manual.xml:315(screeninfo)
-msgid "The Tags toolbar"
+#. (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 ""
 
-#: C/anjuta-manual.xml:257(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:66
 msgid ""
-"<emphasis>Editor Margins:</emphasis> Editor margins appear to the left of "
-"the editor and are used for some special purposes. There are three editor "
-"margins available: the <emphasis>line number margin</emphasis>, the "
-"<emphasis>marker margin</emphasis> and the <emphasis>code fold margin</"
-"emphasis>. By default (that is, when you run <application>Anjuta</"
-"application> for the first time) only the code fold margin will be visible. "
-"The rest can be made visible via <menuchoice><guimenu>View</"
-"guimenu><guisubmenu>Editor</guisubmenu></menuchoice>. <placeholder-1/>"
+"The flags to pass to the Objective C compiler if a per target value is not "
+"defined."
 msgstr ""
 
-#: C/anjuta-manual.xml:272(para)
+#. (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 <emphasis>line number margin</emphasis> is largest of all the three "
-"margins (and is slightly darker then rest) and displays a document's line "
-"numbers. The <emphasis>line number margin</emphasis> can be shown or hidden "
-"by toggling <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
-"guisubmenu><guimenuitem>Line Numbers Margin</guimenuitem></menuchoice>. Left-"
-"clicking on this margin will select an entire line (including the trailing "
-"newline, if present). You can set font properties for the line number margin "
-"in the preferences."
+"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 ""
 
-#: C/anjuta-manual.xml:281(para)
+#. (itstool) path: item/p
+#: C/autotools-project-folder-edit.page:76
 msgid ""
-"The <emphasis>marker margin</emphasis> can be shown or hidden via "
-"<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</"
-"guisubmenu><guimenuitem>Markers Margin</guimenuitem></menuchoice>. This "
-"margin displays graphical icons to mark the given line. The margin may "
-"display bookmark markers (blue and rectangular), breakpoint markers (red and "
-"circular) and line indicator markers (which look like a yellow pointed "
-"arrow). A bookmark marker indicates a bookmarked line, and can be toggled "
-"via <menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</"
-"guisubmenu><guimenuitem> Toggle Bookmark</guimenuitem></menuchoice> with the "
-"cursor placed on that line. A breakpoint marker is used in the debugger to "
-"indicate a debugging breakpoint (see the Debugging section for more "
-"details). A line indicator marker is used to indicate the current program "
-"position in the debugger."
+"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 "Редагування властивостей проєкту Autotools."
+
+#. (itstool) path: page/title
+#: C/autotools-project-root-edit.page:19
+msgid "Edit Autotools Project Properties"
+msgstr "Редагування властивостей проєкту Autotools"
+
+#. (itstool) path: page/p
+#: C/autotools-project-root-edit.page:21
+msgid "These are the properties of the root item."
 msgstr ""
 
-#: C/anjuta-manual.xml:294(para)
+#. (itstool) path: item/title
+#: C/autotools-project-root-edit.page:25
+msgid "<gui>Backend</gui>"
+msgstr "<gui>Модуль</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-project-root-edit.page:26
 msgid ""
-"The <emphasis>code fold margin</emphasis> is where the folding tree is "
-"visible. Clicking on folding tree nodes will fold or unfold code blocks. An "
-"underline will also be drawn below a 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."
+"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 "<gui>Назва</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-project-root-edit.page:33
+msgid "The name of your project. It can contains space."
 msgstr ""
 
-#: C/anjuta-manual.xml:302(title)
-#, fuzzy
-msgid "Invisible margin marker"
-msgstr "Меню видалення маркера"
+#. (itstool) path: item/title
+#: C/autotools-project-root-edit.page:36
+msgid "<gui>Version</gui>"
+msgstr "<gui>Версія</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-project-root-edit.page:37
+msgid "This is the project version."
+msgstr ""
 
-#: C/anjuta-manual.xml:313(title)
-msgid "Editor markers when the marker margin is invisible"
+#. (itstool) path: item/title
+#: C/autotools-project-root-edit.page:40
+msgid "<gui>Bug report URL</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:303(para)
+#. (itstool) path: item/p
+#: C/autotools-project-root-edit.page:41
 msgid ""
-"If the marker margin is not visible, Anjuta displays markers by changing the "
-"background color of a line. For example, if a breakpoint marker is set in a "
-"line and the marker margin is not visible, that line will be displayed with "
-"a red background. Similarly, for a bookmark marker and a line indicator "
-"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 marker margin via <menuchoice><guimenu>View</"
-"guimenu><guisubmenu>Editor</guisubmenu><guimenuitem>Marker Margin</"
-"guimenuitem></menuchoice>. <placeholder-1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:323(title)
-#, fuzzy
-msgid "Editor Guides"
-msgstr "Показувати напрямні"
+#. (itstool) path: item/title
+#: C/autotools-project-root-edit.page:45
+msgid "<gui>Package name</gui>"
+msgstr "<gui>Назва пакунка</gui>"
 
-#: C/anjuta-manual.xml:324(para)
+#. (itstool) path: item/p
+#: C/autotools-project-root-edit.page:46
 msgid ""
-"The editor can be set to display certain document information which is "
-"normally invisible, including <emphasis>indentation guides</emphasis>, "
-"<emphasis>white space</emphasis> and <emphasis>line end characters</"
-"emphasis>. They can be make visible or invisible by toggling the menu items "
-"in <menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></"
-"menuchoice>. Indentation guides are small dotted lines drawn to connect "
-"matching braces in source code. When the cursor is over a matching brace, "
-"its dotted indentation guide is highlighted to emphasize the indentation "
-"level visually."
+"This is the name of distribution package, it shouldn't contain spaces. It is "
+"optional."
 msgstr ""
 
-#: C/anjuta-manual.xml:333(title) C/anjuta-manual.xml:335(screeninfo)
-#, fuzzy
-msgid "Editor with guides"
-msgstr "Зі вмонтованим редактором\n"
+#. (itstool) path: item/title
+#: C/autotools-project-root-edit.page:50
+msgid "<gui>URL</gui>"
+msgstr "<gui>URL</gui>"
 
-#: C/anjuta-manual.xml:341(title)
-#, fuzzy
-msgid "Syntax highlighting"
-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 ""
 
-#: C/anjuta-manual.xml:342(para)
+#. (itstool) path: page/p
+#: C/autotools-project-root-edit.page:55
 msgid ""
-"<application>Anjuta</application> can highlight the syntax of many different "
-"languages. This is usually done automatically by determining the type of a "
-"file from its extension. If <application>Anjuta</application> cannot "
-"determine the type of a 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>."
+"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 ""
 
-#: C/anjuta-manual.xml:352(para)
+#. (itstool) path: info/desc
+#: C/autotools-project-target-edit.page:9
+msgid "Edit autotools target properties."
+msgstr "Редагування властивостей цілі autotools."
+
+#. (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 ""
-"Anjuta uses a properties file named <filename>$prefix/share/anjuta/"
-"properties/anjuta.properties</filename>, which has the same format as a "
-"SciTE properties file but does not use all properties. The style of each "
-"element for all languages is defined in a file named <filename>$prefix/share/"
-"anjuta/properties/styles.properties</filename>. It uses some common "
-"properties defined by Anjuta in the file <filename>$home/.config/anjuta/"
-"scintilla/editor-style.properties</filename>."
+"Here is a list of all target properties used in autotools project. Some of "
+"them are not available on all targets."
 msgstr ""
 
-#: C/anjuta-manual.xml:365(title)
-#, fuzzy
-msgid "Code folding"
-msgstr "Без згортання"
+#. (itstool) path: item/title
+#: C/autotools-project-target-edit.page:25
+msgid "<gui>Build for check only</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:366(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:26
 msgid ""
-"Anjuta can display <emphasis>code folds</emphasis> for source files in block-"
-"structured languages (such as C, C++, Pascal, and Java). All code blocks in "
-"a source file can be folded or unfolded by clicking on the fold points in "
-"the code fold margin of the <interface>Editor</interface> window (usually a "
-"+/- symbol or up/down arrow). These fold points automatically appear for "
-"source files which use code blocks."
+"If checked, this target is not installed and has to be built only when "
+"running checks."
 msgstr ""
 
-#: C/anjuta-manual.xml:374(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:31
 msgid ""
-"Code folding is especially useful when editing large source files with "
-"thousands of lines. Once the folds are closed, a document appears to become "
-"smaller, facilitating easy browsing and editing of the file."
+"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 ""
 
-#: C/anjuta-manual.xml:380(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:36
 msgid ""
-"Please note that code folding and editor guides are only available in the "
-"Scintilla-based editor."
+"These flags are passed to every compilation that invokes the C preprocessor. "
+"This value overrides the one eventually defined in the parent folder."
 msgstr ""
 
-#: C/anjuta-manual.xml:387(title)
-#, fuzzy
-msgid "Auto-formatting source code"
-msgstr "Вихідний код на мові Emacs Lisp"
+#. (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 ""
 
-#: C/anjuta-manual.xml:388(para)
+#. (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 ""
-"Anjuta can automatically indent (auto-format) C or C++ source or header "
-"files. This gives a clean look to the source code, increases legibility, "
-"reduces the likelihood of syntax errors, and above all saves time. To auto-"
-"indent the current source file, choose <menuchoice><guimenu>Edit</"
-"guimenu><guimenuitem>Auto Indent </guimenuitem></menuchoice> on the menu "
-"bar. You can change the style of formatting by customizing the choices in "
-"the preferences."
+"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 ""
 
-#: C/anjuta-manual.xml:401(title)
-#, fuzzy
-msgid "The Symbol Browser"
-msgstr "<b>Зовнішній переглядач 1</b>"
+#. (itstool) path: item/title
+#: C/autotools-project-target-edit.page:53
+msgid "<gui>Do not use prefix</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:402(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:54
 msgid ""
-"You can browse C and C++ source and header files using <emphasis>tags</"
-"emphasis> in the files. A tag (or <emphasis>symbol</emphasis>) refers to a "
-"named entity such as a function definition, structure, or macro. Anjuta "
-"scans open C and C++ source and header files for available tags."
+"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 ""
 
-#: C/anjuta-manual.xml:415(title) C/anjuta-manual.xml:417(screeninfo)
-#, fuzzy
-msgid "Symbol browser"
-msgstr "<b>Зовнішній переглядач 1</b>"
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:65
+msgid "If checked, include the target in the distribution package."
+msgstr "Якщо позначено, включити ціль до пакунка дистрибутива."
 
-#: C/anjuta-manual.xml:407(para)
+#. (itstool) path: item/title
+#: C/autotools-project-target-edit.page:68
+msgid "<gui>Installation directory</gui>"
+msgstr "<gui>Каталог встановлення</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:69
 msgid ""
-"<application>Anjuta</application> will automatically scan for tags in all of "
-"the source and header files of any open project. You can jump to any "
-"function definition, structure definition, class definition or other tag "
-"without manually opening the containing file. You don't even have to know "
-"which file the tag is found in. The symbol browser lists all available "
-"symbols in the project. <placeholder-1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:423(title)
-#, fuzzy
-msgid "Tag synchronization"
-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 ""
 
-#: C/anjuta-manual.xml:424(para)
+#. (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 ""
-"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!"
+"If checked, keep the hierarchy of the project directory when installing "
+"files."
 msgstr ""
 
-#: C/anjuta-manual.xml:435(title)
-msgid "Searching for and Replacing text in files"
+#. (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 ""
 
-#: C/anjuta-manual.xml:437(title)
-#, fuzzy
-msgid "Searching"
-msgstr "Пошук"
+#. (itstool) path: item/title
+#: C/autotools-project-target-edit.page:93
+msgid "<gui>Libraries</gui>"
+msgstr "<gui>Бібліотеки</gui>"
 
-#: C/anjuta-manual.xml:438(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:94
 msgid ""
-"To search for a <emphasis>string</emphasis> or <emphasis>regular expression</"
-"emphasis> in the current file, choose <menuchoice><guimenu>Edit</"
-"guimenu><guisubmenu>Search</guisubmenu><guimenuitem>Find</guimenuitem></"
-"menuchoice> or press <keycombo><keycap>Ctrl</keycap><keycap>Alt</"
-"keycap><keycap>F</keycap></keycombo>. This will open the <interface>Find</"
-"interface> dialog."
+"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 ""
 
-#: C/anjuta-manual.xml:445(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:101
 msgid ""
-"Use the text box to specify the string to search for, and select whether it "
-"is a normal string or a regular expression. You can also 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."
+"The flags to pass to the linker when linking the target. This value "
+"overrides the one eventually defined in the parent folder."
 msgstr ""
 
-#: C/anjuta-manual.xml:451(para)
+#. (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 ""
-"If the search is successful, Anjuta will jump to the matched text or perform "
-"another action (according to the <guilabel>Search Action</guilabel> you "
-"choose in the <guilabel>Search Target</guilabel> tab). If the search is not "
-"successful, Anjuta will display a message indicating that the search text "
-"was not found."
+"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 ""
 
-#: C/anjuta-manual.xml:456(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-edit.page:112
 msgid ""
-"If you want to search again, click the <guibutton>Search</guibutton> button "
-"again or press <keycombo><keycap>Ctrl</keycap><keycap>G</keycap></keycombo>. "
-"This will find the next match (use <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 search "
-"dialog."
+"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 ""
 
-#: C/anjuta-manual.xml:465(title)
-#, fuzzy
-msgid "Search Text dialog"
-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 ""
 
-#: C/anjuta-manual.xml:470(para)
-msgid "To stop a long search, press the <guibutton>Stop</guibutton> button."
+#. (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 ""
 
-#: C/anjuta-manual.xml:475(title)
-#, fuzzy
-msgid "Specifying Search Range"
-msgstr "Діапазон пошуку неправильний."
+#. (itstool) path: info/desc
+#: C/autotools-project-target-type.page:8
+msgid "Autotools target type."
+msgstr "Тип цілі Autotools."
+
+#. (itstool) path: page/title
+#: C/autotools-project-target-type.page:17
+msgid "Autotools project type"
+msgstr ""
 
-#: C/anjuta-manual.xml:476(para)
+#. (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 "Спільна бібліотека (Libtool)"
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:24
 msgid ""
-"In the <interface>Search Target</interface> tab, define the search location "
-"and the action to be performed if the search succeeds."
+"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 ""
 
-#: C/anjuta-manual.xml:480(para)
-msgid "You can define the maximum number of actions to be performed."
+#. (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 ""
 
-#: C/anjuta-manual.xml:484(title)
-#, fuzzy
-msgid "Search Target dialog"
-msgstr "Відкрити діалог пошуку"
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:31
+msgid "Module (Libtool)"
+msgstr ""
 
-#: C/anjuta-manual.xml:489(para)
-msgid "You can select which text will be searched."
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:32
+msgid ""
+"It represents a library, often named a plugin, linked at run time explicitly "
+"by the program itself. It is used to only load the code corresponding to the "
+"used features."
 msgstr ""
 
-#: C/anjuta-manual.xml:493(title)
-#, fuzzy
-msgid "Search Target In choice"
-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 ""
 
-#: C/anjuta-manual.xml:499(title)
-#, fuzzy
-msgid "Searching in Files"
-msgstr "Створення переліку файлів у '%s'..."
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:39
+msgid "Static Library (Libtool)"
+msgstr ""
 
-#: C/anjuta-manual.xml:500(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:40
 msgid ""
-"To find text in your project, set <guilabel>Search In</guilabel> to All "
-"Project Files."
+"It represents a library linked with the program at compile time. Only the "
+"function used are kept inside the generated executable."
 msgstr ""
 
-#: C/anjuta-manual.xml:504(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:42
 msgid ""
-"In the <guilabel>Search Expression</guilabel> tab, enter the text you want "
-"to search for and specify search options, such as the <guilabel>Match case</"
-"guilabel> or <guilabel>Match complete words</guilabel> options. Click "
-"<guibutton>Search</guibutton> to start searching."
+"It uses the Libtool package. Its name must start with 'lib' and has the '.a' "
+"extension."
 msgstr ""
 
-#: C/anjuta-manual.xml:509(para)
+#. (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 ""
-"To find text in a set of files, set <guilabel>Search In</guilabel> to "
-"Specify File Patterns. Define the search variables. Click <guibutton>Search</"
-"guibutton> to start searching."
+"It represents compiled program by example from C source files. All children "
+"represent the source files compiled to generate the program."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:52
+msgid "Python module"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:53
+msgid "It represents a program written in Python."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:56
+msgid "Java module"
 msgstr ""
 
-#: C/anjuta-manual.xml:515(title)
-#, fuzzy
-msgid "Search File Pattern"
-msgstr "  [-E | -F] [-e @var{шаблон} | -f @var{файл}]...\n"
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:57
+msgid "It represents a program written in Java."
+msgstr ""
 
-#: C/anjuta-manual.xml:525(title)
-#, fuzzy
-msgid "Specifying a Search Action"
-msgstr "Скасувати останню операцію"
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:60
+msgid "LISP module"
+msgstr ""
 
-#: C/anjuta-manual.xml:526(para)
-msgid "You can select which action will be performed when a search succeeds."
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:61
+msgid "It represents a program written in LISP."
 msgstr ""
 
-#: C/anjuta-manual.xml:529(para)
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:64
+#| msgid "Save file"
+msgid "Header files"
+msgstr "Файли заголовків"
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:65
 msgid ""
-"Depending on the previous selections (<guilabel>Search In</guilabel>, "
-"<guilabel>Search Direction</guilabel> , and so on), some actions may be "
-"unavailable."
+"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 ""
 
-#: C/anjuta-manual.xml:535(title)
-msgid "Search Target Action choice"
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:73
+#| msgid "Introduction"
+msgid "Info documentation"
+msgstr "Документація Info"
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:74
+msgid "It groups info page needed by the project."
 msgstr ""
 
-#: C/anjuta-manual.xml:543(title) C/anjuta-manual.xml:551(title)
-#, fuzzy
-msgid "Replacing"
-msgstr "Потрібна заміна"
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:77
+msgid "Miscellaneous Data"
+msgstr ""
 
-#: C/anjuta-manual.xml:544(para)
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:78
 msgid ""
-"Searching and replacing is similar to just finding text, except that you "
-"also specify the replacement text in the <guilabel>Replace With</guilabel> "
-"text box, and also specify whether or not you want to be prompted before "
-"each replacement takes place (Replace First Match or Replace All Matches)."
+"It groups data files which needed by the project like pictures, ui "
+"description, settings files..."
 msgstr ""
 
-#: C/anjuta-manual.xml:556(para)
+#. (itstool) path: item/title
+#: C/autotools-project-target-type.page:82
+msgid "Script"
+msgstr "Скрипт"
+
+#. (itstool) path: item/p
+#: C/autotools-project-target-type.page:83
 msgid ""
-"Choose <guibutton>Replace</guibutton> to replace the matched text or "
-"<guibutton>Forward</guibutton> to jump to the next matched text."
+"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/anjuta-manual.xml:563(title)
-#, fuzzy
-msgid "Search Setting"
-msgstr "Налаштовування віртуальної теки: %s"
+#. (itstool) path: info/desc
+#: C/autotools-build-build.page:11
+msgid "Build targets or project."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/autotools-build-build.page:24
+msgid "Build targets"
+msgstr "Цілі збирання"
 
-#: C/anjuta-manual.xml:564(para)
-msgid "You may also save search options."
+#. (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/anjuta-manual.xml:567(para)
+#. (itstool) path: page/p
+#: C/autotools-build-build.page:30
 msgid ""
-"The item highlighted in red is the active item. The default item specifies "
-"search settings which are loaded when Anjuta launches."
+"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/anjuta-manual.xml:572(title)
-#, fuzzy
-msgid "Search Setting dialog"
-msgstr "Відкрити діалог пошуку"
+#. (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/anjuta-manual.xml:583(title)
-#, fuzzy
-msgid "Printing a file"
-msgstr "Друк списку файлів, які видаляються."
+#. (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/anjuta-manual.xml:592(title)
-#, fuzzy
-msgid "Print preview of a C file"
-msgstr "Попередній вигляд: Перейменування файла..."
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:57 C/autotools-build-clean.page:45
+#: C/autotools-build-install.page:50
+msgid "From the <gui>file manager pane</gui>, select a file or a directory."
+msgstr ""
 
-#: C/anjuta-manual.xml:594(screeninfo)
-#, fuzzy
-msgid "Print preview"
-msgstr "Попередній перегляд друку"
+#. (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/anjuta-manual.xml:584(para)
+#. (itstool) path: item/p
+#: C/autotools-build-build.page:72 C/autotools-build-clean.page:60
+#: C/autotools-build-install.page:65
 msgid ""
-"You can perform a print preview by selecting <menuchoice><guisubmenu>File</"
-"guisubmenu><guimenuitem>Print Preview</guimenuitem></menuchoice>. This will "
-"render the current file and present a preview of the print. Source code "
-"which is highlighted in the editor is also highlighted similarly in the "
-"preview (and subsequent print). The <guilabel>Printing</guilabel> tab of "
-"your editor plugin preferences contains additional options which let you "
-"print with line numbers, wrapped lines and/or headers. <placeholder-1/>"
+"From the <gui>project manager pane</gui>, select a source file or a target."
 msgstr ""
 
-#: C/anjuta-manual.xml:601(title)
-#, fuzzy
-msgid "Print Preferences"
-msgstr "X-Chat: Настройки"
+#. (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 ""
+
+#. (itstool) path: info/desc
+#: C/autotools-build-clean.page:11
+msgid "Remove built files."
+msgstr "Вилучення зібраних файлів."
 
-#: C/anjuta-manual.xml:603(screeninfo)
-#, fuzzy
-msgid "Print preferences"
-msgstr "X-Chat: Настройки"
+#. (itstool) path: page/title
+#: C/autotools-build-clean.page:20
+msgid "Clean targets"
+msgstr "Очищення цілей"
 
-#: C/anjuta-manual.xml:608(para)
+#. (itstool) path: page/p
+#: C/autotools-build-clean.page:22
 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 press <guibutton>Print</guibutton> to print "
-"the file."
+"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/anjuta-manual.xml:615(para)
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:28
 msgid ""
-"You can also set landscaped or portrait page layout and the paper size, page "
-"orientation and paper type. Remember to set them up properly according to "
-"your printer, otherwise printing may not look correct."
+"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/anjuta-manual.xml:622(title) C/anjuta-manual.xml:624(screeninfo)
-#, fuzzy
-msgid "Print Dialog"
-msgstr "Діалог друку середовища GNOME"
+#. (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/anjuta-manual.xml:3(title)
-#, fuzzy
-msgid "Project Management"
-msgstr "Керування проектами"
+#. (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/anjuta-manual.xml:5(para)
+#. (itstool) path: item/p
+#: C/autotools-build-clean.page:65
 msgid ""
-"Anjuta has a powerful Project Manager plugin which can open most <ulink type="
-"\"info\" url=\"info:automake\">automake/autoconf</ulink>-based projects. It "
-"might fail on some oddly-configured projects, but as long as the project "
-"uses automake/autoconf in a typical way, it should work."
+"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/anjuta-manual.xml:13(para)
+#. (itstool) path: info/desc
+#: C/autotools-build-compile.page:11
+msgid "Compile files."
+msgstr "Компіляція файлів."
+
+#. (itstool) path: page/title
+#: C/autotools-build-compile.page:20
+msgid "Compile files"
+msgstr "Компіляція файлів"
+
+#. (itstool) path: page/p
+#: C/autotools-build-compile.page:22
 msgid ""
-"The neat thing is that Anjuta does not store any project information beyond "
-"what is already available in the project structure. That is, there is no "
-"separate project data maintained by Anjuta and all project processing is "
-"done directly within the project structure. This allows a project to be "
-"maintained or developed outside Anjuta without any need to convert to or "
-"from an Anjuta-specific format. Since technically Anjuta projects are just "
-"automake projects, mixed development (with both Anjuta and non-Anjuta users) "
-"or switching back and forth between Anjuta and other tools is quite possible "
-"without any hindrance."
+"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/anjuta-manual.xml:26(title)
-#, fuzzy
-msgid "Creating a New Project"
-msgstr "Створення нового проекту відео-DVD."
+#. (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/anjuta-manual.xml:28(title)
-#, fuzzy
-msgid "Creating a project from a template"
-msgstr "Створити правило на основі шаблона"
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:39
+msgid "From the <gui>file manager pane</gui>, select a file."
+msgstr ""
 
-#: C/anjuta-manual.xml:29(para)
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:44
 msgid ""
-"The project wizard plugin uses a powerful template processing engine called "
-"<application>autogen</application>. All new projects are created from "
-"templates that are written in <application>autogen</application> syntax. The "
-"project wizard lets you create new projects from a selection of project "
-"templates. The selection includes simple generic, flat (no subdirectory), GTK"
-"+, GNOME, Java, Python projects and more. New templates can be easily "
-"downloaded and installed since each template is just a collection of text "
-"files."
+"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 ""
+
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:53
+msgid "From the <gui>project manager pane</gui>, select a source file."
 msgstr ""
 
-#: C/anjuta-manual.xml:41(para)
+#. (itstool) path: item/p
+#: C/autotools-build-compile.page:58
 msgid ""
-"To create a project, choose the menu item <menuchoice><guisubmenu>File</"
-"guisubmenu><guisubmenu>New</guisubmenu><guimenuitem>Project …</guimenuitem></"
-"menuchoice> to start the application wizard. Read the first page carefully. "
-"Click on <guibutton>Next</guibutton> to proceed."
+"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/anjuta-manual.xml:48(para)
+#. (itstool) path: note/p
+#: C/autotools-build-compile.page:66
 msgid ""
-"Select the type of application you want to create in the second page. Click "
-"on <guibutton>Next</guibutton> to proceed."
+"You do not need to save your file before compiling it, it will be done "
+"automatically by <app>Anjuta</app> if needed."
+msgstr ""
+
+#. (itstool) path: info/desc
+#: C/autotools-build-configure-dialog.page:11
+msgid "Autotools configure dialog"
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/autotools-build-configure-dialog.page:20
+msgid "Autotools Configure Dialog"
 msgstr ""
 
-#: C/anjuta-manual.xml:54(para)
+#. (itstool) path: page/p
+#: C/autotools-build-configure-dialog.page:22
 msgid ""
-"On the following pages, enter all necessary details for your project. You "
-"can change these settings later, but it is advisable to set them right "
-"initially in order to maintain the project's integrity. White spaces or any "
-"non-alphanumeric characters, except underscore (_) and dash (-), are not "
-"allowed in many of the entry boxes that follow (except perhaps the "
-"<guilabel>Author</guilabel> text box)."
+"The <gui>Configure</gui> dialog allows you to set the following options and "
+"configure the project."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:29
+msgid "<gui>Regenerate Project</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:65(para)
+#. (itstool) path: item/p
+#: C/autotools-build-configure-dialog.page:30
 msgid ""
-"You can also specify whether your project will have "
-"<emphasis>internationalization support</emphasis> using "
-"<application>gettext</application> (read the <ulink type=\"info\" url=\"info:"
-"gettext\">gettext info page</ulink> for more details). This gives your "
-"project multilingual support for different languages such as English, French "
-"and Dutch. 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 for "
-"enabling GNOME desktop menu information if necessary. Shared library support "
-"allows you to add shared library modules later on. If you plan to have "
-"libraries in your project, it would be good to enable this. Depending on the "
-"project type that is being created, Anjuta may request additional "
-"information."
+"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/anjuta-manual.xml:81(para)
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:37
+msgid "<gui>Configuration</gui>"
+msgstr "<gui>Налаштування</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-build-configure-dialog.page:38
 msgid ""
-"The final step is to verify the information you have just supplied. Click on "
-"<guibutton>Finish</guibutton> to start generating the project."
+"You can have several configurations having their own options and build "
+"directory, this text box allows to name them. Typically you have already "
+"defined a Default configuration, a Debug configuration making programs "
+"easier to debug (keeping intermediate variables and code ordering) and an "
+"Optimized configuration generating faster programs but increasing build "
+"time. You can define additional custom configurations."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:49
+msgid "<gui>Build Directory</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:86(para)
+#. (itstool) path: item/p
+#: C/autotools-build-configure-dialog.page:50
 msgid ""
-"Once the project has been generated, you can try it out by building it and "
-"executing it."
+"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/anjuta-manual.xml:92(title)
-#, fuzzy
-msgid "Importing Projects"
-msgstr "*.k3b|Проекти K3b"
+#. (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/anjuta-manual.xml:93(para)
+#. (itstool) path: note/p
+#: C/autotools-build-configure-dialog.page:63
 msgid ""
-"The import project feature is used to import an already existing project and "
-"convert it into an <application>Anjuta</application> project. Activate the "
-"import project wizard via <menuchoice><guimenu>File</guimenu><guimenu>New</"
-"guimenu><guimenuitem>Project from existing sources</guimenuitem></"
-"menuchoice> and follow the instructions dictated by the wizard. Once a "
-"project has been imported, it can be opened in <application>Anjuta</"
-"application> subsequently just like any other <application> Anjuta</"
-"application> project."
+"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/anjuta-manual.xml:103(para)
+#. (itstool) path: item/title
+#: C/autotools-build-configure-dialog.page:72
+msgid "<gui>Configure Options</gui>"
+msgstr "<gui>Параметри конфігурації</gui>"
+
+#. (itstool) path: item/p
+#: C/autotools-build-configure-dialog.page:73
 msgid ""
-"The import project feature only works if your existing project uses <ulink "
-"type=\"info\" url=\"info:automake\">autoconf/automake</ulink> or, to a very "
-"limited extent, a plain Makefile."
+"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/anjuta-manual.xml:113(title)
-#, fuzzy
-msgid "Loading and Saving Projects"
-msgstr "Перетворення та завантаження графіки"
+#. (itstool) path: note/p
+#: C/autotools-build-configure-dialog.page:80
+msgid ""
+"Each autotools project supports a common list of arguments but can have "
+"specify arguments. You can have a list of all accepted arguments by running "
+"<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 ""
+
+#. (itstool) path: info/desc
+#: C/autotools-build-configure.page:11
+msgid "Configure an autotools project and manage configurations."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/autotools-build-configure.page:20
+msgid "Configure a project"
+msgstr "Налаштовування проєкту"
+
+#. (itstool) path: page/p
+#: C/autotools-build-configure.page:22
+msgid ""
+"Before compiling and building files, an autotools project has to be "
+"configured. This step is needed to set global options, to check that all "
+"required libraries and programs are installed on your system and to generate "
+"appropriate build scripts."
+msgstr ""
 
-#: C/anjuta-manual.xml:115(title)
-#, fuzzy
-msgid "Loading Projects"
-msgstr "*.k3b|Проекти K3b"
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:30
+msgid "Configure the project"
+msgstr "Налаштовування проєкту"
 
-#: C/anjuta-manual.xml:116(para)
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:34
 msgid ""
-"To open a project, choose the menu item <menuchoice><guisubmenu>File</"
-"guisubmenu><guimenuitem>Open …</guimenuitem></menuchoice>. Select the "
-"project file (<filename>*.anjuta</filename>) in the dialog and click "
-"<guibutton>OK</guibutton>."
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> "
+"<gui>Configure Project...</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:123(para)
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:40
 msgid ""
-"If the project has recently been opened, then you will find it listed in the "
-"menu <menuchoice><guisubmenu>File</guisubmenu><guisubmenu>Recent</"
-"guisubmenu></menuchoice>. Choose the project filename from the list, and the "
-"project will be opened."
+"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/anjuta-manual.xml:128(para)
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:47
+msgid "Click on <gui>Execute</gui> to configure the project."
+msgstr "Натисніть <gui>Виконати</gui>, щоб налаштувати проєкт."
+
+#. (itstool) path: section/p
+#: C/autotools-build-configure.page:53
 msgid ""
-"As soon as a project is opened, <application>Anjuta</application> will enter "
-"<emphasis>Project mode</emphasis>. There are three panes in the project "
-"window. The first is the project pane and lists project files organized by "
-"file type. The second is the symbol browser, which has already been "
-"discussed in the section <emphasis>The Symbol Browser</emphasis>. The third "
-"pane is the file view of the project and is more or less similar to a mini "
-"file-manager. In the file view, all the files present in the project tree "
-"are visible. Right-clicking on these files will pop up a context menu with "
-"file operations."
+"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/anjuta-manual.xml:137(para)
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:60
+msgid "Change the configuration"
+msgstr "Зміна налаштувань"
+
+#. (itstool) path: item/p
+#: C/autotools-build-configure.page:64
 msgid ""
-"If the project is also a CVS tree, then corresponding file revision numbers "
-"are also listed to the right of file names in the file view pane."
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Select "
+"Configuration</gui><gui>Another configuration</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:143(title)
-#, fuzzy
-msgid "Saving Projects"
-msgstr "*.k3b|Проекти K3b"
+#. (itstool) path: section/p
+#: C/autotools-build-configure.page:71
+msgid ""
+"If the project has not been already configured, it will be automatically "
+"configured before building any file."
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/autotools-build-configure.page:79
+msgid "Remove configuration"
+msgstr "Вилучення налаштувань"
 
-#: C/anjuta-manual.xml:144(para)
+#. (itstool) path: section/p
+#: C/autotools-build-configure.page:81
 msgid ""
-"The project is automatically saved when you close because all changes are "
-"made directly in the project structure."
+"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/anjuta-manual.xml:152(title)
-#, fuzzy
-msgid "Project structure"
-msgstr "Структура вмісту"
+#. (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/anjuta-manual.xml:158(title)
-#, fuzzy
-msgid "Project window"
-msgstr "Розмістити проект у вікні"
+#. (itstool) path: info/desc
+#: C/autotools-build-distribute.page:11
+msgid "Create a distribution package."
+msgstr "Створення пакунка дистрибутива."
 
-#: C/anjuta-manual.xml:160(screeninfo)
-#, fuzzy
-msgid "The Project window"
-msgstr "Розмістити проект у вікні"
+#. (itstool) path: page/title
+#: C/autotools-build-distribute.page:20
+msgid "Create a distribution package"
+msgstr "Створення пакунка дистрибутива"
 
-#: C/anjuta-manual.xml:153(para)
+#. (itstool) path: page/p
+#: C/autotools-build-distribute.page:22
 msgid ""
-"Here is the <interface>Project window</interface> with its context menu "
-"(accessible by clicking on the right mouse button). <placeholder-1/>"
+"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/anjuta-manual.xml:165(para)
+#. (itstool) path: item/p
+#: C/autotools-build-distribute.page:30
 msgid ""
-"The <interface>Project window</interface> displays the project's <ulink type="
-"\"info\" url=\"info:automake\"><application>automake</application></ulink> "
-"hierarchy organized into <emphasis>groups</emphasis> of <emphasis>targets</"
-"emphasis>. Groups correspond to directories in your project and targets "
-"correspond to normal <application>automake</application> targets (not to be "
-"confused with make targets). The <interface>Project window</interface> "
-"actually has two parts: the lower part shows the complete project hierarchy "
-"and the upper part lists important targets directly. Important targets "
-"include executable and library targets; the view makes these easily "
-"accessible. This is particularly useful in large projects where the "
-"hierarchy can be deep and hard to navigate from the tree alone. Targets are, "
-"in turn, composed of source files."
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Build "
+"Tarball</gui></guiseq> to create a source distribution package."
 msgstr ""
 
-#: C/anjuta-manual.xml:185(para)
+#. (itstool) path: info/desc
+#: C/autotools-build-install.page:11
+msgid "Install targets or project."
+msgstr "Встановлення цілей або проєкту."
+
+#. (itstool) path: page/title
+#: C/autotools-build-install.page:20
+msgid "Install targets"
+msgstr "Встановлення цілей"
+
+#. (itstool) path: page/p
+#: C/autotools-build-install.page:22
 msgid ""
-"<emphasis>Groups</emphasis> are used to logically organize targets. A "
-"project can contain any number of groups. Each group can have subgroups as "
-"well as targets. In automake projects, groups are just subdirectories in the "
-"project. The top-level group is always labeled \"/\"."
+"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 ""
+
+#. (itstool) path: page/p
+#: C/autotools-build-install.page:29
+msgid "There are several possibilities to install targets or a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:193(para)
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:33
 msgid ""
-"<emphasis>Targets</emphasis> are the build targets in the project, such as "
-"programs (executable binaries), scripts, libraries and miscellaneous data. "
-"Not all target types are built from sources; some exist just to organize "
-"sources and therefore may not exist physically (e.g. a Miscellaneous Data "
-"target). Targets exist under groups. See <link linkend=\"adding-target\">"
-"\"Adding targets\"</link> for a full list of available target types."
+"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/anjuta-manual.xml:204(para)
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:42
 msgid ""
-"<emphasis>Source files</emphasis> may be used to build targets, though some "
-"source files simply belong to targets. They exist only under targets. Many "
-"target types expect certain type of source files (e.g. the Programs and "
-"Libraries target types), but some can accept any file (e.g. a Miscellaneous "
-"Data target)."
+"From the <gui>main menu</gui>, select <guiseq><gui>Build</gui> <gui>Install "
+"Project</gui></guiseq> to install all project files,"
 msgstr ""
 
-#: C/anjuta-manual.xml:214(para)
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:55
 msgid ""
-"Each project group and target is configurable in the standard "
-"<application>automake</application> way. You can set compiler and linker "
-"flags directly for each target, or set <application>configure</application> "
-"variables. Groups allow you to set an installation destination for their "
-"targets."
+"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/anjuta-manual.xml:221(para)
+#. (itstool) path: item/p
+#: C/autotools-build-install.page:70
 msgid ""
-"Just like the file manager, the project manager view also has convenience "
-"actions (accessible from the context menu) for source files and targets."
+"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/anjuta-manual.xml:227(para)
+#. (itstool) path: note/p
+#: C/autotools-build-install.page:79
 msgid ""
-"Many command-line tools are available to maintain and manage a project, and "
-"each tool has its own specific rules and capabilities. <application>Anjuta</"
-"application> tries to automate most common operations using plugins. "
-"However, you might occasionally still need to perform certain operations "
-"manually."
+"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 ""
+
+#. (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/anjuta-manual.xml:235(para)
+#. (itstool) path: page/p
+#: C/autotools-build-plugin.page:19
 msgid ""
-"You may modify a project's structure using external tools or by hand-editing "
-"the project files. It doesn't matter whether the project is loaded in "
-"<application>Anjuta</application> or not. <application>Anjuta</application> "
-"will update itself with any external changes made to a project."
+"This plugin is targeted at autotools projects but as they use make it is "
+"useful for other kind of projects using make."
 msgstr ""
 
-#: C/anjuta-manual.xml:244(title)
-#, fuzzy
-msgid "Groups and targets"
-msgstr "Користувачі та групи"
+#. (itstool) path: section/title
+#: C/autotools-build-plugin.page:25
+msgid "Make command used"
+msgstr "Використана команда Make"
 
-#: C/anjuta-manual.xml:247(title)
-#, fuzzy
-msgid "Adding Groups"
-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 ""
 
-#: C/anjuta-manual.xml:252(para)
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:32
 msgid ""
-"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Group</"
-"guimenuitem></menuchoice> and a dialog to add a new group will pop up."
+"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/anjuta-manual.xml:259(para)
-msgid "Select the group under which to add the new group."
+#. (itstool) path: item/title
+#: C/autotools-build-plugin.page:40
+msgid "<cmd>make install</cmd>"
 msgstr ""
 
-#: C/anjuta-manual.xml:262(para)
-msgid "Enter the name of the new group and click <guibutton>Add</guibutton>."
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:41
+msgid "Use to install all targets in a directory."
 msgstr ""
 
-#: C/anjuta-manual.xml:248(para)
+#. (itstool) path: item/title
+#: C/autotools-build-plugin.page:44
+msgid "<cmd>make clean</cmd>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:45
+msgid "Use to delete all file built in a directory."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-build-plugin.page:48
+msgid "<cmd>make dist</cmd>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/autotools-build-plugin.page:49
 msgid ""
-"To add a new group (which is a directory in automake-based projects): "
-"<placeholder-1/>"
+"Use to build a distribution package, called only in the project directory."
 msgstr ""
 
-#: C/anjuta-manual.xml:266(para)
+#. (itstool) path: note/p
+#: C/autotools-build-plugin.page:54
 msgid ""
-"With automake projects, a new directory with the given name will be created "
-"under the parent group's directory."
+"As make comes with default rules allowing it to compile and link a C program "
+"without needing a makefile. You can compile a C program from a single source "
+"file without a makefile nor a project."
+msgstr ""
+
+#. (itstool) path: info/desc
+#: C/autotools-build-preferences-dialog.page:10
+msgid "Autotools build preferences dialog."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/autotools-build-preferences-dialog.page:19
+msgid "Autotools Build Preferences Dialog"
+msgstr ""
+
+#. (itstool) path: page/p
+#: C/autotools-build-preferences-dialog.page:21
+msgid "The dialog allows you to set global options for building files."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:27
+msgid "<gui>Run several commands at a time</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:271(para)
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:28
 msgid ""
-"You can also add a new group from the <interface>Project</interface> window "
-"directly. Right-click the group under which to add the new group, then "
-"choose <guimenuitem>Add Group</guimenuitem> from the context menu."
+"<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/anjuta-manual.xml:279(title)
-#, fuzzy
-msgid "Removing Groups"
-msgstr "Підготовка до видалення груп"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:33
+msgid "<gui>Continue on errors</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:284(para)
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:34
 msgid ""
-"Right-click the group in the <interface>Project Manager</interface> view."
+"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 ""
+
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:39
+msgid "<gui>Translate messages</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:287(para) C/anjuta-manual.xml:426(para)
-msgid "Select <guimenuitem>Remove</guimenuitem> from the context menu."
+#. (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/anjuta-manual.xml:280(para)
-#, fuzzy
-msgid "To remove a group: <placeholder-1/>"
-msgstr "Не можна видалити нульову групу"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:48
+msgid "<gui>Highlight build warnings and errors in editor</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:292(para)
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:49
 msgid ""
-"The target and sources associated with the group will also be removed from "
-"the project. (They are not deleted from the file system, though. You can add "
-"them to the project again later if you like.)"
+"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/anjuta-manual.xml:300(title)
-#, fuzzy
-msgid "Adding Targets"
-msgstr "Спеціальні цілі"
+#. (itstool) path: item/title
+#: C/autotools-build-preferences-dialog.page:54
+msgid "<gui>Install as root</gui>"
+msgstr ""
 
-#: C/anjuta-manual.xml:305(para)
+#. (itstool) path: item/p
+#: C/autotools-build-preferences-dialog.page:55
 msgid ""
-"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Target</"
-"guimenuitem></menuchoice> and a dialog to add a new target will popup."
+"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/anjuta-manual.xml:310(para)
-msgid "Select the group under which to add the target."
+#. (itstool) path: info/desc
+#: C/debug-breakpoint-dialog.page:10
+msgid "Used to create or edit a breakpoint"
 msgstr ""
 
-#: C/anjuta-manual.xml:313(para)
-#, fuzzy
-msgid "Select the target type."
-msgstr "/Виділення/Того ж типу"
+#. (itstool) path: page/title
+#: C/debug-breakpoint-dialog.page:23
+msgid "Breakpoint Dialog"
+msgstr "Діалогове вікно точки зупинки"
 
-#: C/anjuta-manual.xml:316(para)
-msgid "Enter a name for the new target and click <guibutton>Add</guibutton>."
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:27
+msgid "<gui>Location</gui>"
+msgstr "<gui>Розташування</gui>"
+
+#. (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/anjuta-manual.xml:301(para)
-#, fuzzy
-msgid "To add a new target: <placeholder-1/>"
-msgstr "Натисніть кнопку для додавання нової палітри"
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:33
+msgid "<var>file_name</var>:<var>line_number</var>"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:34
+msgid "<var>function_name</var>"
+msgstr "<var>назва_функції</var>"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:35
+msgid "<var>file_name</var>:<var>function_name</var>"
+msgstr "<var>назва_файла</var>:<var>назва_функції</var>"
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:39
+msgid "<gui>Condition</gui>"
+msgstr "<gui>Умова</gui>"
 
-#: C/anjuta-manual.xml:320(para)
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:40
 msgid ""
-"You can also add a new target from the <interface>Project</interface> window "
-"directly. Right-click the group under which to add the target, then select "
-"<guimenuitem>Add target</guimenuitem> from the context menu."
+"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/anjuta-manual.xml:326(para)
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:45
 msgid ""
-"Target names usually require some standard prefix and suffix, depending on "
-"the type of target. Anjuta will warn you if a name is not valid and may "
-"provide an example of a valid name."
+"If you leave this field blank the condition is always considered <code>TRUE</"
+"code>."
 msgstr ""
 
-#: C/anjuta-manual.xml:335(para)
+#. (itstool) path: item/title
+#: C/debug-breakpoint-dialog.page:49
+msgid "<gui>Pass Count</gui>"
+msgstr "<gui>Кількість проходів</gui>"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:50
 msgid ""
-"The <emphasis>Program</emphasis> target type is for executable binaries. "
-"Select this type if you want to add an executable to the project. By "
-"default, all program targets will be installed in the standard executable "
-"directory, e.g. /usr/bin or /usr/local/bin. You can override this by "
-"specifying a different installation directory in the properties of the group "
-"containing the target."
+"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/anjuta-manual.xml:344(para)
+#. (itstool) path: item/p
+#: C/debug-breakpoint-dialog.page:53
 msgid ""
-"The <emphasis>Shared Library</emphasis> target type is for shared or dynamic "
-"libraries. Select this type if you are adding a shared library to the "
-"project. By default, all shared libraries are installed in the standard "
-"libraries directory, e.g. /usr/lib or /usr/local/lib. You can override this "
-"by specifying a different installation directory in the properties of the "
-"group containing the target."
+"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/anjuta-manual.xml:353(para)
+#. (itstool) path: info/desc
+#: C/debug-breakpoint.page:9
+msgid "Managing breakpoints."
+msgstr "Керування точками зупинки."
+
+#. (itstool) path: page/title
+#: C/debug-breakpoint.page:22
+msgid "Breakpoints"
+msgstr "Точки зупинки"
+
+#. (itstool) path: page/p
+#: C/debug-breakpoint.page:24
 msgid ""
-"The <emphasis>Static Library</emphasis> target type is for static libraries. "
-"Select this type if you are adding a static library to the project. By "
-"default, all static libraries are installed in the standard libraries "
-"directory, e.g. /usr/lib or /usr/local/lib. You can override this by "
-"specifying a different installation directory in the properties of the group "
-"containing the target."
+"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/anjuta-manual.xml:362(para)
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:28
+msgid "Listing breakpoints"
+msgstr "Список точок зупинки"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:32
 msgid ""
-"The <emphasis>Java Module</emphasis> target type is for Java modules. Select "
-"this type if you are grouping Java sources into a module. You need to "
-"provide an installation directory for this target where the .class files "
-"will be installed. It can be set in the properties of the group containing "
-"the target."
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Breakpoints</gui></guiseq> to open the <gui>Breakpoint</gui> window."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:38
+msgid "This view has the following columns:"
 msgstr ""
 
-#: C/anjuta-manual.xml:369(para)
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:42
+msgid "Location"
+msgstr "Розташування"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:43
 msgid ""
-"There can really be only one Java module in a group. This is a restriction "
-"made by automake. Please read the automake info page for more details."
+"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/anjuta-manual.xml:377(para)
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:48 C/debug-stack.page:79
+msgid "Address"
+msgstr "Адреса"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:49
 msgid ""
-"The <emphasis>Python Module</emphasis> target type is for Python modules. "
-"Select this type if you are grouping Python sources into a module. You need "
-"to provide an installation directory for this target where the sources will "
-"be installed. It can be set in the properties of the group containing the "
-"target."
+"This field is filled with the address of the breakpoint when it is set by "
+"the debugger."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:53 C/debug-local.page:55 C/debug-watch.page:53
+msgid "Type"
+msgstr "Тип"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:54
+msgid ""
+"This always displays <gui>breakpoint</gui>. It will be used in a future "
+"release supporting different kinds of breakpoints."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:58
+msgid "Condition"
+msgstr "Умова"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:59
+msgid ""
+"This is the breakpoint condition. It is empty if no condition is defined."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:63
+msgid "Pass count"
+msgstr "Кількість проходів"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:64
+msgid ""
+"When the debugger is not running, this column displays the pass count of the "
+"breakpoint, or zero if it is not defined."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:66
+msgid ""
+"When the debugger is running, if the pass count is zero, this column "
+"displays the number of times this breakpoint has been triggered. If the pass "
+"count is not zero, both numbers are displayed. The pass count is the second "
+"number."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:72
+msgid "State"
+msgstr "Стан"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:73
+msgid "This is the state of the breakpoint. It may be"
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:75
+msgid "Pending:"
+msgstr "Очікування:"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:75
+msgid "the breakpoint is not set in your program."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:76
+msgid "Permanent:"
+msgstr "Постійна:"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:76
+msgid "the breakpoint is set (its id number is displayed in parentheses)."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-breakpoint.page:77
+msgid "Temporary:"
+msgstr "Тимчасова:"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:77
+msgid "the breakpoint is set but will be deleted if reached."
+msgstr ""
+
+#. (itstool) path: note/p
+#: C/debug-breakpoint.page:83
+msgid ""
+"All breakpoints are kept across Anjuta sessions even if they correspond to a "
+"non-existing locations, for example in a source file of a shared library not "
+"loaded yet. In this case their states are set as pending."
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:90
+msgid "Setting breakpoints"
+msgstr "Встановлення точок зупинки"
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:94
+msgid ""
+"From the <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 ""
+
+#. (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 ""
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:108
+msgid ""
+"Another solution is to use the toggle breakpoint function. If there is no "
+"breakpoint on the current line, it will add one. Otherwise, it will remove "
+"it."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:114
+msgid ""
+"From the <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 ""
+
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:125
+msgid "Editing breakpoints"
+msgstr "Редагування точок зупинки"
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:127
+msgid ""
+"You can't change the location of a breakpoint; create a new breakpoint "
+"instead. However, you can change the break condition or the pass count. To "
+"edit a breakpoint:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:133 C/debug-breakpoint.page:160
+msgid "Select a breakpoint in the <gui>Breakpoint</gui> window."
+msgstr ""
+
+#. (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 ""
+
+#. (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 ""
+
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:151
+msgid "Removing breakpoints"
+msgstr "Вилучення точок зупинки"
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:153
+msgid ""
+"You can remove a breakpoint using the toggle breakpoint function described "
+"above. However, if you want to remove more than one breakpoint or the "
+"breakpoint is in a different file than the one you are editing, you can use "
+"the breakpoint window:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:163
+msgid ""
+"Right click in the <gui>Breakpoint</gui> window and select <gui>Remove "
+"Breakpoint</gui>."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:169
+msgid "To remove all breakpoints:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:173
+msgid ""
+"From the <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 ""
+
+#. (itstool) path: section/title
+#: C/debug-breakpoint.page:184
+msgid "Enabling and disabling breakpoints"
+msgstr "Вмикання і вимикання точок зупинки"
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:186
+msgid ""
+"Sometimes you might want to disable a breakpoint temporarily instead of "
+"deleting it altogether. To disable or re-enable a breakpoint:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:191
+msgid ""
+"Click on the <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 ""
+
+#. (itstool) path: section/p
+#: C/debug-breakpoint.page:197
+msgid "You can disable all breakpoints using:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-breakpoint.page:201
+msgid ""
+"From the <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 ""
+
+#. (itstool) path: info/desc
+#: C/debug-cpu.page:9
+msgid "Examine CPU information."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/debug-cpu.page:22
+msgid "CPU"
+msgstr "Процесор"
+
+#. (itstool) path: section/title
+#: C/debug-cpu.page:25
+msgid "View CPU registers"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-cpu.page:29
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Registers</gui></guiseq> to open the <gui>Register</gui> window."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-cpu.page:35
+msgid ""
+"Registers whose values have changed since the last stop are in red. It is "
+"possible to change the value of any register by clicking in the value column "
+"and entering a new value."
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/debug-cpu.page:42
+msgid "View memory"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-cpu.page:46
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Memory</"
+"gui></guiseq> to open the <gui>Memory</gui> window."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-cpu.page:52
+msgid ""
+"The first column displays memory addresses in hexadecimal, the second "
+"displays memory contents in hexadecimal and the last column shows memory "
+"contents in ASCII."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-cpu.page:55 C/debug-cpu.page:82
+msgid ""
+"The addressing space of even a 32-bit microprocessor is very large (4 "
+"gigabytes), so it is very difficult to go to a particular address with the "
+"scrollbar. But you can click the right mouse button and select <gui>Go to "
+"address</gui> to get a small edit box where you can enter an address in "
+"hexadecimal."
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/debug-cpu.page:64
+msgid "View Disassembly"
+msgstr "Перегляд дизасемблера"
+
+#. (itstool) path: item/p
+#: C/debug-cpu.page:69
+msgid ""
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> "
+"<gui>Disassembly</gui></guiseq> to open the <gui>Disassembly</gui> window."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-cpu.page:75
+msgid ""
+"The first column displays addresses in hexadecimal. In the second column, "
+"you can have a label starting at the beginning of the line and ending with a "
+"colon or a assembly-language instruction indented by 4 space characters."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-cpu.page:79
+msgid ""
+"The position in the disassembly window will be changed to the program "
+"counter value when the program is stopped."
+msgstr ""
+
+#. (itstool) path: info/desc
+#: C/debug-custom.page:9
+msgid "Use custom debugger command."
+msgstr "Використання нетипової команди діагностики."
+
+#. (itstool) path: page/title
+#: C/debug-custom.page:22
+msgid "Custom command"
+msgstr "Нетипова команда"
+
+#. (itstool) path: page/p
+#: C/debug-custom.page:24
+msgid "You can send a custom command to the debugger like this:"
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-custom.page:28
+msgid ""
+"From the <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 ""
+
+#. (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 ""
+
+#. (itstool) path: info/desc
+#: C/debug-data.page:9
+msgid "Examine program Data."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/debug-data.page:18
+msgid "Examine data"
+msgstr ""
+
+#. (itstool) path: info/desc
+#: C/debug-execute.page:9
+msgid "Control program execution."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/debug-execute.page:18
+#| msgid "Introduction"
+msgid "Control execution"
+msgstr "Керування виконанням"
+
+#. (itstool) path: info/desc
+#: C/debug-expression.page:9
+msgid "Evaluate expressions and modify variables."
+msgstr ""
+
+#. (itstool) path: page/title
+#: C/debug-expression.page:22
+msgid "Examine expressions"
+msgstr "Інспектування виразів"
+
+#. (itstool) path: section/title
+#: C/debug-expression.page:25
+msgid "Inspect an expression and modify a variable"
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/debug-expression.page:27
+msgid ""
+"While you are debugging a program, you can find out the value of an "
+"expression or variable while the program is paused. It is also sometimes "
+"useful to change the value of a variable."
+msgstr ""
+
+#. (itstool) path: item/p
+#: C/debug-expression.page:33
+msgid ""
+"From the <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 ""
+
+#. (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 ""
+
+#. (itstool) path: info/desc
+#: C/debug-information.page:9
+msgid "Examine additional program information."
 msgstr ""
 
-#: C/anjuta-manual.xml:385(para)
+#. (itstool) path: page/title
+#: C/debug-information.page:22
+msgid "Miscellaneous information"
+msgstr "Різноманітні відомості"
+
+#. (itstool) path: page/p
+#: C/debug-information.page:24
+msgid ""
+"The debugger can tell you various information about the program while it is "
+"running."
+msgstr ""
+
+#. (itstool) path: section/title
+#: C/debug-information.page:28
+msgid "View shared libraries"
+msgstr "Перегляд спільних бібліотек"
+
+#. (itstool) path: item/p
+#: C/debug-information.page:32
 msgid ""
-"The <emphasis>Scripts</emphasis> target type is for grouping scripts. They "
-"will be installed in the standard executable directory."
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Info</"
+"gui><gui>Shared Libraries</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:391(para)
+#. (itstool) path: section/p
+#: C/debug-information.page:37
 msgid ""
-"The <emphasis>Miscellaneous Data</emphasis> target type is for grouping "
-"simple files in a project. You must specify an installation directory in the "
-"group properties."
+"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/anjuta-manual.xml:398(para)
+#. (itstool) path: section/title
+#: C/debug-information.page:44
+msgid "View signals"
+msgstr "Перегляд сигналів"
+
+#. (itstool) path: item/p
+#: C/debug-information.page:48
 msgid ""
-"The <emphasis>Header Files</emphasis> target type is for grouping C/C++ "
-"header files that need to be installed on a system (for example as part of a "
-"library API). (For header files that do not need to be installed, make them "
-"part of the Program target along with the sources.) Header files will be "
-"installed in the standard include directory unless an installation path is "
-"specified in the group properties."
+"From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui> <gui>Info</"
+"gui><gui>Kernel signals</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:408(para)
+#. (itstool) path: section/p
+#: C/debug-information.page:53
 msgid ""
-"The <emphasis>Man Documentation</emphasis> and <emphasis>Info Documentation</"
-"emphasis> target types are for grouping man and info documentation "
-"respectively. By default, documentation files will be installed in the "
-"standard installation directories."
+"This lists all available signals with a small description and three columns "
+"to specify what to do when a signal is received:"
 msgstr ""
 
-#: C/anjuta-manual.xml:331(para)
+#. (itstool) path: item/title
+#: C/debug-information.page:58
+msgid "Stop"
+msgstr "Зупинити"
+
+#. (itstool) path: item/p
+#: C/debug-information.page:59
+msgid ""
+"The debugger stops the program execution when the program receives this "
+"signal."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-information.page:63
+msgid "Print"
+msgstr "Надрукувати"
+
+#. (itstool) path: item/p
+#: C/debug-information.page:64
+msgid "The debugger displays the received signal."
+msgstr ""
+
+#. (itstool) path: item/title
+#: C/debug-information.page:67
+msgid "Pass"
+msgstr "Передати"
+
+#. (itstool) path: item/p
+#: C/debug-information.page:68
+msgid "The debugger passes the signal to the program."
+msgstr ""
+
+#. (itstool) path: note/p
+#: C/debug-information.page:73
+msgid ""
+"The context menu that is displayed when you click the right mouse button has "
+"all its items disabled because the corresponding functions are not "
+"implemented yet."
+msgstr ""
+
+#. (itstool) path: info/desc
+#: C/debug-local.page:9
+msgid "Examine local variables."
+msgstr "Інспектування локальних змінних."
+
+#. (itstool) path: page/title
+#: C/debug-local.page:22
+msgid "Local variables"
+msgstr "Локальні змінні"
+
+#. (itstool) path: page/p
+#: C/debug-local.page:24
+msgid ""
+"Local variables of the current frame (the current function in which the "
+"program control is present) are displayed in the <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 ""
+
+#. (itstool) path: section/title
+#: C/debug-local.page:32
+msgid "Listing local variables"
+msgstr "Список локальних змінних"
+
+#. (itstool) path: item/p
+#: C/debug-local.page:36
 msgid ""
-"There are several target types for automake projects. They are: <placeholder-"
-"1/>"
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Locals</"
+"gui></guiseq> to open the <gui>Locals</gui> window."
 msgstr ""
 
-#: C/anjuta-manual.xml:418(title)
-#, fuzzy
-msgid "Removing Targets"
-msgstr "Спеціальні цілі"
-
-#: C/anjuta-manual.xml:423(para)
+#. (itstool) path: section/p
+#: C/debug-local.page:42
 msgid ""
-"Right-click the target in the <interface>Project Manager</interface> view."
+"All local variables are displayed in a tree view with children used to "
+"represent structure or array members."
 msgstr ""
 
-#: C/anjuta-manual.xml:419(para)
-#, fuzzy
-msgid "To remove a target: <placeholder-1/>"
-msgstr "Змінювати розмір тексту за шириною рамки"
+#. (itstool) path: item/title
+#: C/debug-local.page:47 C/debug-watch.page:45
+msgid "Variable"
+msgstr "Змінна"
 
-#: C/anjuta-manual.xml:431(para)
-msgid ""
-"The sources associated with the targets will also be removed from the "
-"project (they are not deleted from the file system, though)."
+#. (itstool) path: item/p
+#: C/debug-local.page:48
+msgid "The name of the variable."
 msgstr ""
 
-#: C/anjuta-manual.xml:440(title)
-#, fuzzy
-msgid "Adding and Removing Files"
-msgstr "Видалення файлів із диска."
+#. (itstool) path: item/title
+#: C/debug-local.page:51 C/debug-watch.page:49
+msgid "Value"
+msgstr "Значення"
 
-#: C/anjuta-manual.xml:442(title)
-#, fuzzy
-msgid "Adding Source Files"
-msgstr "Робити резервні копії"
+#. (itstool) path: item/p
+#: C/debug-local.page:52
+msgid "The variable value."
+msgstr ""
 
-#: C/anjuta-manual.xml:443(para)
-msgid ""
-"Select the menu item <menuchoice><guisubmenu>Project</"
-"guisubmenu><guimenuitem>Add Source File</guimenuitem></menuchoice>. From the "
-"dialog, select the target to which the file should be added and the file "
-"itself. You can add multiple files at once. To do that, select multiple "
-"files from the file selection dialog using either the <keycap>Shift</keycap> "
-"or <keycap>Ctrl</keycap> key. Then click <guibutton>Add</guibutton> to add "
-"the files to the project."
+#. (itstool) path: item/p
+#: C/debug-local.page:56
+msgid "The type of the variable."
 msgstr ""
 
-#: C/anjuta-manual.xml:452(para)
-msgid ""
-"By default, the current editor file will be preselected for addition in the "
-"dialog. Another convenient way to add a file is to right-click it in the "
-"<interface>File Manager</interface> and choose <guimenuitem>Add to project</"
-"guimenuitem> from the context menu."
+#. (itstool) path: section/title
+#: C/debug-local.page:62 C/debug-watch.page:153
+msgid "Changing the value of a variable"
 msgstr ""
 
-#: C/anjuta-manual.xml:459(para)
+#. (itstool) path: item/p
+#: C/debug-local.page:66
 msgid ""
-"If the file you choose has already been added to the project, then "
-"<application>Anjuta</application> will not add it again. It will also give "
-"you a warning that the file has already been added."
+"In the <gui>Locals</gui> window, select the variable you want to edit and "
+"double click in the <gui>Value</gui> column."
 msgstr ""
 
-#: C/anjuta-manual.xml:464(para)
-msgid ""
-"If the file you choose is not in the project directory, you will be asked to "
-"confirm that you wish to copy the file into the target's directory. "
-"<application>Anjuta</application> cannot add files which are outside of a "
-"target's directory without copying them in."
+#. (itstool) path: item/p
+#: C/debug-local.page:70
+msgid "Type the new value."
 msgstr ""
 
-#: C/anjuta-manual.xml:472(title)
-#, fuzzy
-msgid "Removing Source Files"
-msgstr "Робити резервні копії"
+#. (itstool) path: info/desc
+#: C/debug-process-dialog.page:9
+msgid "Attach to process dialog"
+msgstr "Вікно долучення до процесу"
 
-#: C/anjuta-manual.xml:473(para)
+#. (itstool) path: page/title
+#: C/debug-process-dialog.page:22
+msgid "Attach to Process Dialog"
+msgstr "Вікно долучення до процесу"
+
+#. (itstool) path: page/p
+#: C/debug-process-dialog.page:24
 msgid ""
-"To remove a file from the project, right-click the file you want to remove "
-"in the <interface>Project window</interface> and choose <guimenuitem>Remove</"
-"guimenuitem> from the context menu."
+"The <gui>Attach to process</gui> dialog allows you to select a currently "
+"running process."
 msgstr ""
 
-#: C/anjuta-manual.xml:478(para)
-msgid ""
-"A confirmation dialog will appear, and the file will be removed from the "
-"project."
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:28
+msgid "<gui>Hide paths</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:483(title)
-#, fuzzy
-msgid "The file is not deleted!"
+#. (itstool) path: item/p
+#: C/debug-process-dialog.page:29
+msgid "This hides command paths in the process list if checked."
 msgstr ""
-"%s не є звичайним файлом.\n"
-"%s"
 
-#: C/anjuta-manual.xml:484(para)
-msgid ""
-"The file is not deleted from the filesystem. It still exists, and you can "
-"add it back again later if you so wish. The file is only removed from the "
-"project listing, and will not take part in any project operations such as "
-"compiling, building, or distribution."
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:32
+msgid "<gui>Hide process parameters</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:495(title)
-#, fuzzy
-msgid "Project Configuration"
-msgstr "Конфігурація GTK"
+#. (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/anjuta-manual.xml:496(para)
-msgid ""
-"Project configuration involves setting the correct build flags for targets, "
-"groups and the project itself. You can set these flags in their respective "
-"properties dialogs."
+#. (itstool) path: item/title
+#: C/debug-process-dialog.page:36
+msgid "<gui>Display process tree</gui>"
 msgstr ""
 
-#: C/anjuta-manual.xml:502(para)
+#. (itstool) path: item/p
+#: C/debug-process-dialog.page:37
 msgid ""
-"You can freely use autoconf and automake variables that are automatically "
-"set for the project during configuration. Apart from these automatically set "
-"variables, you can also define your own variables in <link linkend=\"project-"
-"properties\">Project Properties</link> and use them in properties. This will "
-"make it easy to update flags later, especially when a variable is used in "
-"several targets."
+"If unchecked, the processes are displayed in a list. If checked, the "
+"processes are displayed in a tree."
 msgstr ""
 
-#: C/anjuta-manual.xml:517(para)
-msgid ""
-"<emphasis>$(prefix)</emphasis>: The installation prefix. The project is "
-"installed under various subdirectories under this prefix. By default it is /"
-"usr/local."
+#. (itstool) path: info/desc
+#: C/debug-run.page:11
+msgid "Start a program with the debugger."
 msgstr ""
 
-#: C/anjuta-manual.xml:524(para)
-msgid ""
-"<emphasis>$(bindir)</emphasis>: The installation directory for executable "
-"binaries. All your executable and script targets will be installed in this "
-"directory. By default, it is $(prefix)/bin."
+#. (itstool) path: page/title
+#: C/debug-run.page:24
+msgid "Debug a program"
 msgstr ""
 
-#: C/anjuta-manual.xml:531(para)
+#. (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 ""
-"<emphasis>$(libdir)</emphasis>: The installation directory for libraries. "
-"All your library targets (both shared and static) will be installed in this "
-"directory or a subdirectory below it. By default, it is $(prefix)/lib."
+"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 ""
 
-#: C/anjuta-manual.xml:539(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:35
 msgid ""
-"<emphasis>$(module_CFLAGS)</emphasis> and $(module_LIBS): These flags are "
-"set by <application>configure</application> for the packages that your "
-"project depends on. The packages used by the project are set in <link "
-"linkend=\"project-properties\">Project Properties</link>. 'module' is a "
-"package group that you specify in the project properties as described below."
+"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 ""
 
-#: C/anjuta-manual.xml:511(para)
+#. (itstool) path: note/p
+#: C/debug-run.page:41
 msgid ""
-"Some of the many common variables are listed here. For full list of them see "
-"the <ulink url=\"info:automake\">automake info documentation</ulink>. "
-"<placeholder-1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:553(title)
-#, fuzzy
-msgid "Project properties"
-msgstr "Властивості проекту..."
-
-#: C/anjuta-manual.xml:560(para)
-msgid ""
-"Set the project name, version and URL in the <guibutton>General</guibutton> "
-"page. <application>configure</application> variables can also be use in "
-"these fields. The URL is the bug report URL for the project."
+#. (itstool) path: section/title
+#: C/debug-run.page:52
+msgid "Debug an already running application"
 msgstr ""
 
-#: C/anjuta-manual.xml:567(para)
-msgid ""
-"Add and remove dependencies for your project in the <guibutton>Packages</"
-"guibutton> page. See below for details."
+#. (itstool) path: section/p
+#: C/debug-run.page:54
+msgid "The debugger can be used on an already running application."
 msgstr ""
 
-#: C/anjuta-manual.xml:573(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:58
 msgid ""
-"Create more configure variables in the <guibutton>Variables</guibutton> page "
-"to use in group and target properties."
+"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 ""
 
-#: C/anjuta-manual.xml:554(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:63
 msgid ""
-"The project properties dialog can be opened only by choosing "
-"<menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
-"guimenuitem></menuchoice> from the toplevel menu bar. You can: <placeholder-"
-"1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:588(title) C/anjuta-manual.xml:590(screeninfo)
-#, fuzzy
-msgid "Project properties dialog"
-msgstr "Вікно властивостей об'єкта"
-
-#: C/anjuta-manual.xml:580(para)
-msgid ""
-"Dependencies are external packages that the project uses and are hence "
-"required to build it. Only packages installed using <ulink url=\"info:pkg-"
-"config\">pkg-config</ulink> can be added from this interface. For others, "
-"the configure.ac file can be edited manually. <placeholder-1/>"
+#. (itstool) path: section/title
+#: C/debug-run.page:71
+msgid "Debug a remote application"
 msgstr ""
 
-#: C/anjuta-manual.xml:595(para)
+#. (itstool) path: section/p
+#: C/debug-run.page:73
 msgid ""
-"External package dependencies are grouped into <emphasis>modules</emphasis>, "
-"so that their combined build flags can be conveniently added to different "
-"targets. <emphasis>Modules</emphasis> are just arbitrary groups of packages "
-"and can be named anything (only alphanumeric characters and _ are allowed in "
-"module names). Usually, they follow the name of targets they would be used "
-"in. Consequently, for small projects with single targets, just one module to "
-"hold all dependencies is enough."
+"The debugger can be used to debug an application running on another computer "
+"connected through a TCP or serial connection."
 msgstr ""
 
-#: C/anjuta-manual.xml:604(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:78
 msgid ""
-"Each package exports a set of <emphasis>compiler flags</emphasis> and "
-"<emphasis>libraries</emphasis>. They are aggregated together for all "
-"packages under a module, and <application>configure</application> variables "
-"<emphasis>$(module_CFLAGS)</emphasis> and <emphasis>$(module_LIBS)</"
-"emphasis> are defined. These variables can then be used in <link linkend="
-"\"group-properties\">Group properties</link> and <link linkend=\"target-"
-"properties\">Target properties</link>."
+"From the <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Debug "
+"Remote...</gui></guiseq>"
 msgstr ""
 
-#: C/anjuta-manual.xml:617(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:82
 msgid ""
-"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
-"guimenuitem></menuchoice> to bring up the project properties dialog."
+"Select the type of the connection to the remote application, <gui>Serial "
+"Line Connection</gui> or <gui>TCP/IP Connection</gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:624(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:86
 msgid ""
-"Select the tab <guibutton>Packages</guibutton> to bring up the Packages page."
+"For a TCP connection, fill in the <gui>Address</gui> and <gui>Port</gui> "
+"fields."
 msgstr ""
 
-#: C/anjuta-manual.xml:628(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:88
 msgid ""
-"Select the <emphasis>module</emphasis> to add the package to. If there is no "
-"module created yet or there is no appropriate module, create one by clicking "
-"<guibutton>Add module</guibutton>. Give a sensible name to the module, "
-"preferably in UPPERCASE to match other <application>configure</application> "
-"variables (only use alphanumeric and '_' characters) and press "
-"<keycap>Enter</keycap> to create it."
+"For a serial connection, fill in the text box below with the serial device "
+"name, for example <cmd>/dev/ttyb</cmd>."
 msgstr ""
 
-#: C/anjuta-manual.xml:638(para)
+#. (itstool) path: item/p
+#: C/debug-run.page:92
 msgid ""
-"Click <guibutton>Add Package</guibutton> to bring up the package selection "
-"dialog."
+"Click on <gui>Connect</gui> to start the debugger and connect to the remote "
+"target."
 msgstr ""
 
-#: C/anjuta-manual.xml:641(para)
-msgid "Select the package to add and click <guibutton>Add</guibutton>."
-msgstr ""
+#. (itstool) path: section/title
+#: C/debug-run.page:100
+msgid "Stop the debugger"
+msgstr "Припинення діагностики"
 
-#: C/anjuta-manual.xml:644(para)
-#, fuzzy
-msgid "Click <guibutton>Close</guibutton> to close the properties dialog."
+#. (itstool) path: section/p
+#: C/debug-run.page:102
+msgid "The debugger and the program can be stopped at any time like this:"
 msgstr ""
-"Щоб закрити діалогове вікно <guilabel>Параметри аплету \"Зведення погоди\"</"
-"guilabel>, натисніть <guibutton>Закрити</guibutton>."
 
-#: C/anjuta-manual.xml:613(para)
-msgid "To add a package dependency: <placeholder-1/>"
+#. (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 ""
 
-#: C/anjuta-manual.xml:651(title)
-#, fuzzy
-msgid "Group properties"
-msgstr "Властивості групи"
+#. (itstool) path: info/desc
+#: C/debug-stack.page:9
+msgid "Examine the stack."
+msgstr ""
 
-#: C/anjuta-manual.xml:658(title) C/anjuta-manual.xml:660(screeninfo)
-#, fuzzy
-msgid "Group properties dialog"
-msgstr "Вікно властивостей об'єкта"
+#. (itstool) path: page/title
+#: C/debug-stack.page:22
+msgid "Stack"
+msgstr "Стек"
 
-#: C/anjuta-manual.xml:652(para)
-msgid ""
-"To edit a group's properties, double-click the group in the "
-"<interface>Project</interface> window to open the <interface>Group "
-"Properties</interface> dialog. (You can alternatively right-click the group "
-"and select <guimenuitem>Properties</guimenuitem> from the context menu.) "
-"<placeholder-1/>"
+#. (itstool) path: section/title
+#: C/debug-stack.page:25
+msgid "List stack frames"
 msgstr ""
 
-#: C/anjuta-manual.xml:675(para)
+#. (itstool) path: section/p
+#: C/debug-stack.page:27
 msgid ""
-"<emphasis>Includes</emphasis>: Set your include directories for your C and C+"
-"+ targets here. You need to provide the full include options of the compiler "
-"here, e.g. -I/usr/include/blah. The include paths will be used to find "
-"header files included by your source files. (You can also add other compiler "
-"flags here, but it's preferable to set them in their respective "
-"<emphasis>compiler flags</emphasis> fields as described below.)"
+"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 ""
 
-#: C/anjuta-manual.xml:685(para)
+#. (itstool) path: section/p
+#: C/debug-stack.page:32
 msgid ""
-"<emphasis>Compiler flags</emphasis>: Set your compiler-specific flags here. "
-"There are different fields for different compiler categories. Flags that can "
-"be set here depend on the actual compiler used. The default compiler used "
-"for C/C++ is gcc/g++ (the GNU C compiler). Check out the <ulink url=\"info:"
-"gcc\">gcc info documentation</ulink> for more details."
+"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 ""
 
-#: C/anjuta-manual.xml:695(para)
+#. (itstool) path: item/p
+#: C/debug-stack.page:38
 msgid ""
-"<emphasis>Install directories</emphasis>: The dialog will display a field "
-"for each target in the group that requires an installation directory. Set "
-"each installation directory as relative to one of the many "
-"<application>automake</application> directory variables, such as $(prefix), "
-"$(bindir), $(libdir), or $(datadir)."
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Stack</"
+"gui></guiseq> to open the <gui>Stack</gui> window."
 msgstr ""
 
-#: C/anjuta-manual.xml:666(para)
+#. (itstool) path: section/p
+#: C/debug-stack.page:44
 msgid ""
-"Properties set for a group apply to all the targets under it. So any "
-"compiler or linker flags set for a group will be automatically be part of "
-"all the targets in it (in addition to each target's individual properties). "
-"The following fields are available in the Group Properties dialog. "
-"<placeholder-1/>"
+"The stacks are displayed in a tree view having their corresponding thread as "
+"parent and displaying the following information:"
 msgstr ""
 
-#: C/anjuta-manual.xml:710(title)
-#, fuzzy
-msgid "Target properties"
-msgstr "Властивості друку"
+#. (itstool) path: item/title
+#: C/debug-stack.page:49
+msgid "Active"
+msgstr "Активний"
 
-#: C/anjuta-manual.xml:711(para)
+#. (itstool) path: item/p
+#: C/debug-stack.page:50
 msgid ""
-"Any properties set for a target apply to that target only. A target also "
-"inherits properties from its containing group."
+"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 ""
 
-#: C/anjuta-manual.xml:721(title) C/anjuta-manual.xml:723(screeninfo)
-#: C/anjuta-manual.xml:743(title) C/anjuta-manual.xml:745(screeninfo)
-#, fuzzy
-msgid "Target properties dialog"
-msgstr "Вікно властивостей об'єкта"
-
-#: C/anjuta-manual.xml:715(para)
-msgid ""
-"To set a target's properties, double-click the target in the "
-"<interface>Project window</interface> to open the Target Properties dialog. "
-"(You can alternatively right-click the target and select "
-"<guimenuitem>Properties</guimenuitem> from the context menu.) <placeholder-1/"
-">"
-msgstr ""
+#. (itstool) path: item/title
+#: C/debug-stack.page:56
+msgid "Thread"
+msgstr "Потік"
 
-#: C/anjuta-manual.xml:728(para)
-msgid ""
-"You can add the modules you have added in <link linkend=\"project-properties"
-"\">Project properties</link> to a specific target here. To activate the "
-"module simply toggle the checkbox next to the module name. This will "
-"automatically add include and linker flags to that target and enable you to "
-"use the module within this target."
+#. (itstool) path: item/p
+#: C/debug-stack.page:57
+msgid "This is a number corresponding to each thread."
 msgstr ""
 
-#: C/anjuta-manual.xml:735(title)
-#, fuzzy
-msgid "Advanced target options"
-msgstr "Використання: %s [КЛЮЧІ]... [ЦІЛЬ]...\n"
+#. (itstool) path: item/title
+#: C/debug-stack.page:60
+msgid "Frame"
+msgstr "Кадр"
 
-#: C/anjuta-manual.xml:736(para)
+#. (itstool) path: item/p
+#: C/debug-stack.page:61
 msgid ""
-"The following fields are available in the advanced target configuration that "
-"you reach when you clicked the <guibutton>Advanded...</guibutton> button in "
-"the target properties dialog."
+"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 ""
 
-#: C/anjuta-manual.xml:751(para)
-msgid ""
-"<emphasis>Compiler settings</emphasis>: Set your compiler-specific flags "
-"here. There are different fields for different compiler categories. Flags "
-"that can be set here depend on the actual compiler used. The default "
-"compiler used for C/C++ is gcc/g++ (the GNU C compiler). Check out the "
-"<ulink url=\"info:gcc\">gcc info documentation</ulink> for more details."
-msgstr ""
+#. (itstool) path: item/title
+#: C/debug-stack.page:66
+#| msgid "File menu"
+msgid "File"
+msgstr "Файл"
 
-#: C/anjuta-manual.xml:761(para)
+#. (itstool) path: item/p
+#: C/debug-stack.page:67
 msgid ""
-"<emphasis>Linker flags</emphasis>: Set linker flags that should be used when "
-"linking the target. These flags apply only to Program and Library targets. "
-"See the <ulink url=\"info:ld\">ld info documentation</ulink> for available "
-"linker options."
+"The name of the file containing the function corresponding to this frame."
 msgstr ""
 
-#: C/anjuta-manual.xml:769(para)
-msgid ""
-"<emphasis>Libraries</emphasis>: Set the libraries that the target depends on."
+#. (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 ""
 
-#: C/anjuta-manual.xml:3(title)
-#, fuzzy
-msgid "Building"
-msgstr "Створення документу."
+#. (itstool) path: item/title
+#: C/debug-stack.page:75
+msgid "Function"
+msgstr "Функція"
 
-#: C/anjuta-manual.xml:4(para)
-msgid ""
-"Anjuta handles <application>autotools</application> projects. It is able to "
-"cope with other kinds of projects, such as projects using a user-written "
-"Makefile, but the current build interface is targeted at autotools projects. "
-"Some knowledge of them is useful to better understand the way a project is "
-"built."
+#. (itstool) path: item/p
+#: C/debug-stack.page:76
+msgid "The name of the function corresponding to this frame."
 msgstr ""
 
-#: C/anjuta-manual.xml:10(para)
-msgid "An autotools project is built in three steps:"
+#. (itstool) path: item/p
+#: C/debug-stack.page:80
+msgid "The address of the function corresponding to this frame."
 msgstr ""
 
-#: C/anjuta-manual.xml:15(para)
-#, fuzzy
-msgid "Generate"
-msgstr "&Створення"
+#. (itstool) path: item/title
+#: C/debug-stack.page:83
+msgid "Arguments"
+msgstr "Аргументи"
 
-#: C/anjuta-manual.xml:16(para)
-#, fuzzy
-msgid "Configure"
-msgstr "Налаштувати"
+#. (itstool) path: item/p
+#: C/debug-stack.page:84
+msgid "The function arguments."
+msgstr "Аргументи функції."
 
-#: C/anjuta-manual.xml:17(para)
-#, fuzzy
-msgid "Build"
-msgstr "Зібрати"
+#. (itstool) path: section/title
+#: C/debug-stack.page:92
+msgid "Change the current stack frame or thread"
+msgstr "Зміна кадру або потоку поточного стека"
 
-#: C/anjuta-manual.xml:20(para)
-msgid ""
-"<emphasis>Build</emphasis> is the main step in which all target files are "
-"generated from the source files. It can be divided into two subphases: "
-"<emphasis>Compile</emphasis> and <emphasis>Link</emphasis>. In the "
-"<emphasis>Compile</emphasis> phase each object file is generated from its "
-"corresponding source file. For instance, a source file <filename>hello.c</"
-"filename> will generate <filename>hello.o</filename> after compilation. "
-"Usually you do not need to worry about these object files — just think of "
-"them as intermediate files. In the <emphasis>Link</emphasis> phase, all "
-"object files and libraries are linked together to create the final "
-"executable. Some programming languages do not need a <emphasis>Compile</"
-"emphasis> and a <emphasis>Link</emphasis> phase. Moreover the "
-"<emphasis>Build</emphasis> step may be used to generate other files, like "
-"documentation which doesn't need such phases."
+#. (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 ""
 
-#: C/anjuta-manual.xml:34(para)
-msgid ""
-"<emphasis>Configure</emphasis> is the step in which the source tree is "
-"adjusted to your system. <application>autotools</application> projects can "
-"be built on a wide range of systems using different compilers and having "
-"different library functions. This step runs a script named "
-"<filename>configure</filename> that will check for various characteristics "
-"of your system and create some of the files required to perform a build "
-"(such as <filename>Makefile</filename> and <filename>config.h</filename>). "
-"This step is used to select build options, too; for instance, a build option "
-"may disable optimization to make debugging easier or disable some "
-"experimental part of a program."
+#. (itstool) path: item/p
+#: C/debug-stack.page:99
+msgid "Right-click and select <gui>Set current frame</gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:46(para)
+#. (itstool) path: section/p
+#: C/debug-stack.page:103
 msgid ""
-"<emphasis>Generate</emphasis> is the step in which the <filename>configure</"
-"filename> script and other related files are created. The "
-"<filename>configure</filename> script used above needs to run on various "
-"systems and checks a lot of things. It would be quite difficult to write it "
-"by hand. Moreover <application>autotools</application> enforces some project "
-"organization rules such as the presence of some mandatory files: "
-"<filename>NEWS</filename> and <filename>COPYING</filename>, for example. It "
-"includes several tools to create necessary files from simpler files written "
-"by the developer such as <filename>configure.in</filename> (or "
-"<filename>configure.ac</filename>) and <filename>Makefile.am</filename>. All "
-"these tools are commonly run from a script named <filename>autogen.sh</"
-"filename> in the project directory. This step is useful only for a developer "
-"(someone modifying the source files), as the <filename>configure</filename> "
-"script depends only on the source files, and is distributed within the "
-"project package. Note that the makefiles created by <application>configure</"
-"application> include some rules to automatically regenerate the project when "
-"needed, so it often not needed to rerun it directly."
+"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 ""
 
-#: C/anjuta-manual.xml:65(para)
-msgid ""
-"Read the info pages of <ulink type=\"info\" url=\"info:automake"
-"\"><application>automake</application></ulink> and <ulink type=\"info\" url="
-"\"info:autoconf\"><application>autoconf</application></ulink> for more "
-"details on how these tools work."
+#. (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 ""
 
-#: C/anjuta-manual.xml:75(title)
-#, fuzzy
-msgid "Generate and Configure"
-msgstr "Н_алаштувати колір та прозорість..."
-
-#: C/anjuta-manual.xml:77(title)
-#, fuzzy
-msgid "Configure a project"
-msgstr "Проект Glade"
+#. (itstool) path: section/title
+#: C/debug-stack.page:126
+msgid "Get a stack trace"
+msgstr "Отримання трасування стека"
 
-#: C/anjuta-manual.xml:78(para)
+#. (itstool) path: item/p
+#: C/debug-stack.page:130
 msgid ""
-"You need to run this step before being able to build your project. This is "
-"usually run only once at the beginning of the first build process — for "
-"example, just after you have extracted a source tarball of a project "
-"distribution. After that, configuration is automatically handled by the "
-"subsequent build processes. If you have used the <emphasis>Application "
-"Wizard</emphasis> to create the application, then you will not need to run "
-"this separately: the wizard will run it as a part of the project generation "
-"process."
+"In the <gui>Stack</gui> window, right-click and select <gui>Get stack trace</"
+"gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:88(para)
-msgid ""
-"There is no requirement to run this only once. It can be run at any time, "
-"usually when the configuration options need to be changed. One thing to note "
-"is that if the <filename>config.h</filename> file in the top level directory "
-"is changed, running <filename>configure</filename> again will not overwrite "
-"it."
+#. (itstool) path: info/desc
+#: C/debug-step.page:9
+msgid "Stopping and continuing."
 msgstr ""
 
-#: C/anjuta-manual.xml:100(para)
-msgid "Whether you want to run the generate step or not"
-msgstr ""
+#. (itstool) path: page/title
+#: C/debug-step.page:22
+msgid "Stop and step"
+msgstr "Зупинка і покрокове виконання"
 
-#: C/anjuta-manual.xml:101(para)
+#. (itstool) path: page/p
+#: C/debug-step.page:24
 msgid ""
-"The generate step needs to be run once at the beginning of the project; then "
-"it is automatically handled by the build process. You can force it to run by "
-"checking the checkbox <interface>Regenerate project</interface>; you might "
-"do this if you encounter difficulties while building a project (e.g. if you "
-"receive build errors after you've modified lots of build files)."
+"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 ""
 
-#: C/anjuta-manual.xml:109(para)
-#, fuzzy
-msgid "The configuration name"
-msgstr "Повне ім'я "
+#. (itstool) path: section/title
+#: C/debug-step.page:30
+msgid "Step in"
+msgstr ""
 
-#: C/anjuta-manual.xml:110(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:34
 msgid ""
-"This name is used to refer to each configuration. Some configurations "
-"(Default, Debug, Optimized) are already defined by default. One "
-"configuration includes a build directory and some configuration options."
+"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 ""
 
-#: C/anjuta-manual.xml:116(para)
-#, fuzzy
-msgid "The build directory"
-msgstr "Перелік вмісту каталогу"
-
-#: C/anjuta-manual.xml:117(para)
+#. (itstool) path: section/p
+#: C/debug-step.page:40
 msgid ""
-"This is the build directory name. In the Default configuration, it is the "
-"same directory as the source directory but autotools supports building in a "
-"different directory."
+"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 ""
 
-#: C/anjuta-manual.xml:122(para)
+#. (itstool) path: note/p
+#: C/debug-step.page:48
 msgid ""
-"Each configuration must have a different build directory and if one "
-"configuration uses the source directory, you cannot have other "
-"configurations at the same time. You need to run "
-"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Remove Configuration</"
-"guimenuitem></menuchoice> on the configuration using the source directory "
-"before adding a new configuration."
+"If the <gui>Disassembly window</gui> has the focus when this command is "
+"selected, it executes only one assembler instruction."
 msgstr ""
 
-#: C/anjuta-manual.xml:130(para)
-#, fuzzy
-msgid "Configure options"
-msgstr "Параметри конфігурації"
+#. (itstool) path: section/title
+#: C/debug-step.page:55
+msgid "Step over"
+msgstr "Переступання"
 
-#: C/anjuta-manual.xml:131(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:59
 msgid ""
-"These options are passed to the <filename>configure</filename> script. Some "
-"are standard, such as --prefix and CFLAGS; others depend on the project. You "
-"can get a list of allowed configuration options by running the "
-"<filename>configure</filename> script with the <option>--help</option> "
-"argument."
+"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 ""
 
-#: C/anjuta-manual.xml:94(para)
+#. (itstool) path: section/p
+#: C/debug-step.page:65
 msgid ""
-"Both generate and configure steps are launched with a single menu item: "
-"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Configure Project…</"
-"guimenuitem></menuchoice>. This menu item brings a dialog where you can "
-"choose: <placeholder-1/>"
+"Stepping over is similar to stepping except that it does not stop inside any "
+"function in the statement being executed."
 msgstr ""
 
-#: C/anjuta-manual.xml:140(title)
-#, fuzzy
-msgid "Select a configuration"
-msgstr "Вибір настройки MS-DOS"
-
-#: C/anjuta-manual.xml:141(para)
+#. (itstool) path: note/p
+#: C/debug-step.page:69
 msgid ""
-"If you have created different configurations, you can select which one is "
-"active by selecting it in <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Select Configuration</guimenuitem></menuchoice>."
+"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 ""
 
-#: C/anjuta-manual.xml:148(title)
-#, fuzzy
-msgid "Clean a configuration"
-msgstr "Конфігурація GTK"
+#. (itstool) path: section/title
+#: C/debug-step.page:78
+msgid "Step out"
+msgstr "Вийти"
 
-#: C/anjuta-manual.xml:149(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:82
 msgid ""
-"To clean the project and leave it in a state that requires rerunning the "
-"configure step, choose <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Remove Configuration</guimenuitem></menuchoice>. It "
-"run <command>make distclean</command> and deletes more files than "
-"<guimenuitem>Clean Project</guimenuitem>. In other words, it leaves the "
-"project as though it has just been extracted from a distribution tarball. "
-"Note that it does not remove the configuration directory itself; you can do "
-"that yourself if you like."
+"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 ""
 
-#: C/anjuta-manual.xml:166(title)
-#, fuzzy
-msgid "Compile and Build"
-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 ""
 
-#: C/anjuta-manual.xml:168(title)
-#, fuzzy
-msgid "Compiling a file"
-msgstr "Надіслати файл"
+#. (itstool) path: section/title
+#: C/debug-step.page:94
+msgid "Run and continue"
+msgstr "Запуск і продовження"
 
-#: C/anjuta-manual.xml:169(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:98
 msgid ""
-"In a project, individual source files can be compiled separately into "
-"objects (<filename>*.o</filename> files). Although you do not have to worry "
-"about these object files, sometimes it is handy to compile a file first (for "
-"example, to make sure there are no syntax errors). Building a whole project "
-"can take a lot of time, especially in the case of larger and more complex "
-"applications. Therefore, you will probably go through a series of edit-"
-"compile iterations while developing a project."
+"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 ""
 
-#: C/anjuta-manual.xml:177(para)
+#. (itstool) path: section/p
+#: C/debug-step.page:104
 msgid ""
-"To compile a file, choose the menu item <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Compile</guimenuitem></menuchoice> or press "
-"<keycap>F11</keycap>. This will compile the active file."
+"This command restarts the program and lets it run until a breakpoint is "
+"encountered or the program exits."
 msgstr ""
 
-#: C/anjuta-manual.xml:185(title)
-#, fuzzy
-msgid "Building an executable"
-msgstr "Виконуваний файл PEF"
+#. (itstool) path: section/title
+#: C/debug-step.page:109
+msgid "Run To"
+msgstr "Запуск до"
 
-#: C/anjuta-manual.xml:186(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:113
 msgid ""
-"<application>Anjuta</application> has no separate link command, simply "
-"because it is not necessary. The build process will compile all source files "
-"and link them together along with the necessary libraries. The build command "
-"will not recompile those files which are already up-to-date (this is called "
-"the <emphasis>dependency check</emphasis>). If you have already compiled all "
-"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."
+"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 ""
 
-#: C/anjuta-manual.xml:195(para)
+#. (itstool) path: section/p
+#: C/debug-step.page:119
 msgid ""
-"So how exactly does the dependency check influence 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 just 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 regenerated."
+"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 ""
 
-#: C/anjuta-manual.xml:203(para)
-msgid ""
-"Can you imagine how your life (as a programmer) would be if the dependency "
-"check were not there? If you cannot answer just yet, then you will find out "
-"when you start developing big projects!"
-msgstr ""
+#. (itstool) path: section/title
+#: C/debug-step.page:125
+msgid "Stopping the Program"
+msgstr "Зупинка програми"
 
-#: C/anjuta-manual.xml:207(para)
+#. (itstool) path: item/p
+#: C/debug-step.page:129
 msgid ""
-"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></"
-"menuchoice> will build all files in the directory of the currently active "
-"file."
+"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 ""
 
-#: C/anjuta-manual.xml:211(para)
+#. (itstool) path: section/p
+#: C/debug-step.page:135
 msgid ""
-"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Project</"
-"guimenuitem></menuchoice> will build the whole project — all subdirectories "
-"are built recursively."
+"This interrupts the program and returns control to the debugger, allowing "
+"you to perform debugging tasks, like inspecting data or adding breakpoints."
 msgstr ""
 
-#: C/anjuta-manual.xml:223(title)
-#, fuzzy
-msgid "Other operations"
-msgstr "Операції з сайтом"
+#. (itstool) path: info/desc
+#: C/debug-tips.page:9
+msgid "Debugging tips and tricks."
+msgstr ""
 
-#: C/anjuta-manual.xml:225(title)
-#, fuzzy
-msgid "Creating a distribution package"
-msgstr "Створення списків розсилки"
+#. (itstool) path: page/title
+#: C/debug-tips.page:22
+msgid "Debugging tips"
+msgstr "Підказки щодо діагностики"
 
-#: C/anjuta-manual.xml:226(para)
-msgid ""
-"To build a tarball distribution of the project choose "
-"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Tarball</"
-"guimenuitem></menuchoice>. This will create a tarball (<filename>*.tar.gz</"
-"filename>) and put it in the top-level project directory. Copy the file to a "
-"safe place for distribution."
+#. (itstool) path: section/title
+#: C/debug-tips.page:25
+msgid "Fixing GLib/GTK+ critical errors"
 msgstr ""
 
-#: C/anjuta-manual.xml:234(title)
-#, fuzzy
-msgid "Installing a project"
-msgstr "Проект Glade"
-
-#: C/anjuta-manual.xml:235(para)
+#. (itstool) path: section/p
+#: C/debug-tips.page:27
 msgid ""
-"Choosing the menu item <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Install</guimenuitem></menuchoice> will install the "
-"generated application on your system."
+"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/anjuta-manual.xml:241(title)
-#, fuzzy
-msgid "System-wide installation"
-msgstr "Перезавантажувати систему після встановлення"
-
-#: C/anjuta-manual.xml:242(para)
+#. (itstool) path: item/p
+#: C/debug-tips.page:35
 msgid ""
-"You must be logged in as root to perform a system-wide install. Also note "
-"that for a GNOME application to use the pixmaps in the project, it must be "
-"installed as a system-wide application. Otherwise, when the application is "
-"executed in your project, there will be lots of \"pixmap not found\" errors. "
-"You can configure Anjuta to use <command>sudo</command> or <command>su</"
-"command> before installing the project in the build preferences."
+"Open the <link xref=\"run-parameters-dialog\"/> by selecting "
+"<guiseq><gui>Run</gui><gui>Program Parameters...</gui></guiseq> from the "
+"main menu."
 msgstr ""
 
-#: C/anjuta-manual.xml:252(title)
-#, fuzzy
-msgid "Cleaning"
-msgstr "Очищення:"
-
-#: C/anjuta-manual.xml:253(para)
+#. (itstool) path: item/p
+#: C/debug-tips.page:40
 msgid ""
-"This deletes all of the files generated by the build process, including all "
-"object files (<filename>*.o</filename> files) and the executable(s). It can "
-"be applied on one directory or the whole project."
+"Click the plus sign next to <gui>Environment Variables</gui> to expand the "
+"list of environment variables."
 msgstr ""
 
-#: C/anjuta-manual.xml:258(para)
-msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Clean Project</guimenuitem></menuchoice> to clean "
-"all project files."
+#. (itstool) path: item/p
+#: C/debug-tips.page:44
+msgid "Click <gui>New</gui> to add a new entry to the list."
 msgstr ""
 
-#: C/anjuta-manual.xml:263(para)
+#. (itstool) path: item/p
+#: C/debug-tips.page:47
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Build</"
-"guisubmenu><guimenuitem>Clean</guimenuitem></menuchoice> to clean only the "
-"directory of the current active file."
+"Fill in <gui>Name</gui> with <input>G_DEBUG</input> and <gui>Value</gui> "
+"with <input>fatal_criticals</input>."
 msgstr ""
 
-#: C/anjuta-manual.xml:3(title)
-#, fuzzy
-msgid "Debugging"
-msgstr "Налагодження `"
-
-#: C/anjuta-manual.xml:5(emphasis)
-msgid "To debug is human. To fix it is divine..."
+#. (itstool) path: item/p
+#: C/debug-tips.page:51
+msgid "Click <gui>Apply</gui> to confirm the changes."
 msgstr ""
 
-#: C/anjuta-manual.xml:7(para)
+#. (itstool) path: item/p
+#: C/debug-tips.page:54
 msgid ""
-"Well, the <emphasis>human</emphasis> part is what this section is about. The "
-"<emphasis>divine</emphasis> part is up to you!"
+"Run the program with the debugger by selecting <guiseq><gui>Run</"
+"gui><gui>Debug Program</gui></guiseq> from the main menu."
 msgstr ""
 
-#: C/anjuta-manual.xml:11(para)
-msgid ""
-"When a program does not behave in the way it is supposed to, we say the "
-"program contains a <emphasis>bug</emphasis>. A bug is not a compilation "
-"error — compilation errors are relatively easy to clear, because the "
-"compiler tells you where the problems are. By contrast, bugs are errors that "
-"happen during program execution and they can be hard (sometimes very hard!) "
-"to detect."
+#. (itstool) path: item/p
+#: C/debug-tips.page:58
+msgid "Use the program until the critical error occurs."
 msgstr ""
 
-#: C/anjuta-manual.xml:19(para)
+#. (itstool) path: item/p
+#: C/debug-tips.page:61
 msgid ""
-"Any program that you think is bug-free is never completely bug-free. All we "
-"can try to do is to reduce the number of bugs contained in the program. The "
-"process of removing bugs is known as <emphasis>debugging</emphasis>, and the "
-"tool that is used for debugging is called the <emphasis>debugger</emphasis>. "
-"<application>Anjuta</application> provides a very user-friendly and powerful "
-"debugging environment (actually, a GUI wrapper over <application>gdb</"
-"application>, a powerful command line debugging tool and standard on Linux)."
+"When the debugger stops your program, look at the <link xref=\"debug-stack\"/"
+"> to check where this error comes from."
 msgstr ""
 
-#: C/anjuta-manual.xml:27(para)
+#. (itstool) path: section/p
+#: C/debug-tips.page:66
 msgid ""
-"A debugger tracks and traces the execution of the program and provides "
-"various views of information needed to study the execution of the program."
+"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/anjuta-manual.xml:35(title)
-#, fuzzy
-msgid "Start and stop"
-msgstr "Призупинити"
-
-#: C/anjuta-manual.xml:40(emphasis) C/anjuta-manual.xml:56(title)
-#, fuzzy
-msgid "Running an executable"
-msgstr "Виконуваний файл PEF"
+#. (itstool) path: info/desc
+#: C/debug-watch.page:9
+msgid "Monitor expressions and variables."
+msgstr ""
 
-#: C/anjuta-manual.xml:41(emphasis)
-#, fuzzy
-msgid "Attaching to a process"
-msgstr "Перетворити на процес"
+#. (itstool) path: page/title
+#: C/debug-watch.page:22
+msgid "Watch expressions"
+msgstr "Вирази спостереження"
 
-#: C/anjuta-manual.xml:44(para)
+#. (itstool) path: page/p
+#: C/debug-watch.page:24
 msgid ""
-"Almost every feature of Anjuta is provided by a plugin. If you do not see "
-"the menus described here. It is probably because the debugger plugin is not "
-"loaded. Go in <menuchoice><guisubmenu>Edit</"
-"guisubmenu><guimenuitem>Preferences</guimenuitem><guimenuitem>General</"
-"guimenuitem><guimenuitem>Installed plugins</guimenuitem></menuchoice> and "
-"check that the debugger plugin is loaded. It is an user activatable plugin, "
-"so loaded or unloaded on request."
+"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/anjuta-manual.xml:37(para)
-msgid ""
-"The debugger is always started with a program loaded. There are two ways to "
-"do this: <placeholder-1/><placeholder-2/>"
-msgstr ""
+#. (itstool) path: section/title
+#: C/debug-watch.page:30
+msgid "List watched expressions"
+msgstr "Список виразів спостереження"
 
-#: C/anjuta-manual.xml:57(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:34
 msgid ""
-"Running a program with or without the debugger uses the same menu: select "
-"<menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Run Program</"
-"guimenuitem></menuchoice> to run a program without the debugger and "
-"<menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Debug Program</"
-"guimenuitem></menuchoice> to run it with the debugger."
+"From the <gui>main menu</gui>, select <guiseq><gui>View</gui> <gui>Watches</"
+"gui></guiseq> to open the <gui>Watches</gui> window."
 msgstr ""
 
-#: C/anjuta-manual.xml:65(para)
+#. (itstool) path: section/p
+#: C/debug-watch.page:40
 msgid ""
-"In order to better use the debugger, it is strongly recommended that you "
-"build your program with debugging information (-g for gcc) and no "
-"optimization (-O0 for gcc). This can be done by selecting the Debug "
-"configuration before building the program for the first time."
+"Like local variables, all watch expressions are displayed in a tree with "
+"children used to represent structure or array members."
 msgstr ""
 
-#: C/anjuta-manual.xml:76(para)
-#, fuzzy
-msgid "The program that you want to debug"
-msgstr "Виберіть програму, яку потрібно використовувати:"
-
-#: C/anjuta-manual.xml:77(para)
-msgid ""
-"The drop-down menu of the target drop-down combination box is pre-filled "
-"with all executables of the current project. But you can alternatively "
-"select another executable which is not part of the project. The debugger "
-"also accepts libtool executables; these are scripts generated by libtool "
-"which wrap real executables."
+#. (itstool) path: item/p
+#: C/debug-watch.page:46
+msgid "The name of the variable or the expression."
 msgstr ""
 
-#: C/anjuta-manual.xml:84(para)
-#, fuzzy
-msgid "The command-line parameters"
-msgstr "Очікується більша кількість параметрів."
-
-#: C/anjuta-manual.xml:85(para)
-#, fuzzy
-msgid "The working directory"
-msgstr "Неправильний робочий каталог: %s"
+#. (itstool) path: item/p
+#: C/debug-watch.page:50
+msgid "The variable or expression value."
+msgstr ""
 
-#: C/anjuta-manual.xml:86(para)
-#, fuzzy
-msgid "Environment variables"
-msgstr "Змінні оточення"
+#. (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:87(para)
-msgid ""
-"Environment variables displayed in light gray are the current environment "
-"variables. You can add, modify or remove environment variables here."
+#. (itstool) path: section/title
+#: C/debug-watch.page:60
+msgid "Update watches"
 msgstr ""
 
-#: C/anjuta-manual.xml:91(para)
+#. (itstool) path: section/p
+#: C/debug-watch.page:62
 msgid ""
-"To debug Anjuta using Anjuta, you can use a different theme to change the "
-"look of the instance being debugged; for example, you could add "
-"\"GTK2_RC_FILES=/usr/share/themes/Crux/gtk-2.0/gtkrc\"."
+"Watch expressions can be updated automatically as soon as the program is "
+"stopped or on user request."
 msgstr ""
 
-#: C/anjuta-manual.xml:96(para)
-msgid ""
-"Whether the program should run in a terminal or not. If so, the Anjuta "
-"terminal plugin is used."
+#. (itstool) path: section/p
+#: C/debug-watch.page:65
+msgid "To set a watch expression to update automatically:"
 msgstr ""
 
-#: C/anjuta-manual.xml:71(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:69
 msgid ""
-"You can select which program to run and its environment using "
-"<menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Program Parameters…</"
-"guimenuitem></menuchoice>. You can choose: <placeholder-1/>"
+"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:102(title)
-#, fuzzy
-msgid "Attaching to a Process"
-msgstr "Перетворити на процес"
+#. (itstool) path: section/p
+#: C/debug-watch.page:75
+msgid "To update a watch expression manually:"
+msgstr ""
 
-#: C/anjuta-manual.xml:103(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:79
 msgid ""
-"It is also possible to attach to a running process and debug it by choosing "
-"the menu item <menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Debug "
-"Process …</guimenuitem></menuchoice>. A list of all processes running on the "
-"system will appear."
+"In the <gui>Watches</gui> window, right click and select <gui>Update Watch</"
+"gui> to update the selected watch."
 msgstr ""
 
-#: C/anjuta-manual.xml:110(title) C/anjuta-manual.xml:112(screeninfo)
-#, fuzzy
-msgid "Attach to Process dialog"
-msgstr "Перехід до вікна \"Прив'язка до сітки\""
+#. (itstool) path: section/p
+#: C/debug-watch.page:84
+msgid "To update all watch expressions manually at once:"
+msgstr ""
 
-#: C/anjuta-manual.xml:116(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:88
 msgid ""
-"Select the process to attach to and click <guibutton>OK</guibutton> to start "
-"the debugger, attach to the selected process and stop it."
+"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:121(para)
+#. (itstool) path: section/title
+#: C/debug-watch.page:97
+msgid "Add a watch on an expression"
+msgstr "Додавання спостереження до виразу"
+
+#. (itstool) path: section/p
+#: C/debug-watch.page:99
+msgid "To add an expression to the watch list:"
+msgstr "Щоб додати вираз до списку спостереження, виконайте такі дії:"
+
+#. (itstool) path: item/p
+#: C/debug-watch.page:103
 msgid ""
-"It is currently not possible to load symbol information for an attached "
-"process. Symbols should be included in the process."
+"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:129(title)
-#, fuzzy
-msgid "Stopping the Debugger"
-msgstr "Налагоджувач сценаріїв"
-
-#: C/anjuta-manual.xml:130(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:108
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Run</"
-"guisubmenu><guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the "
-"debugger. This will kill the program which is being debugged. If the "
-"debugger has been attached to a running process, the debugger will just "
-"detach from it without killing it. You will get a confirmation box if a "
-"program is currently attached or running."
+"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:140(title)
-#, fuzzy
-msgid "Adding source directories"
-msgstr "Каталоги джерела/призначення"
+#. (itstool) path: section/p
+#: C/debug-watch.page:114
+msgid "An expression can be evaluated and then added as a watch like this:"
+msgstr ""
 
-#: C/anjuta-manual.xml:141(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:118
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Add source paths…</guimenuitem></menuchoice> to "
-"display a dialog box allowing you to add and remove source directories."
+"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:146(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:123
 msgid ""
-"Most executables include full file paths, so defining the directories where "
-"are the source files is normally not useful. But some executables include "
-"only file names without paths; in this case, the debugger will search for "
-"source files in all these directories. The order of directories can be "
-"important if several files have the same name, so you can change it using "
-"the <guibutton>Up</guibutton> and <guibutton>Down</guibutton> buttons. The "
-"directory list is sent to the debugger when it is started. After changing "
-"it, you need to restart the debugger to cause it to use the new list."
+"Click on <gui>Add</gui> button to add this expression to the watches list."
 msgstr ""
 
-#: C/anjuta-manual.xml:162(title)
-#, fuzzy
-msgid "Execution"
-msgstr "Виконання %s не вдалось"
+#. (itstool) path: section/title
+#: C/debug-watch.page:131
+msgid "Remove a watch"
+msgstr "Вилучення спостереження"
 
-#: C/anjuta-manual.xml:163(para)
-msgid ""
-"Execution of a program in the debugger can be finely controlled. The program "
-"can be executed in single steps, or allowed to continue until it encounters "
-"a breakpoint. Executing like this is essential for tracking program "
-"behavior. Like a video editing session, the program can be executed in "
-"<emphasis>slow motion</emphasis> with the ability to go forward, pause, "
-"stop, and so on. You cannot go backward yet though."
+#. (itstool) path: section/p
+#: C/debug-watch.page:133
+msgid "You can remove an expression from the watches list."
 msgstr ""
 
-#: C/anjuta-manual.xml:170(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:137
 msgid ""
-"The methods those can be used to execute a program in the debugger are "
-"described in the following sections. These commands are available only when "
-"the program has already been started."
+"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:177(title)
-#, fuzzy
-msgid "Single stepping (step in)"
-msgstr "Визначення діапазонів однією дією"
+#. (itstool) path: section/p
+#: C/debug-watch.page:142
+msgid "All watches can be removed at the same time."
+msgstr ""
 
-#: C/anjuta-manual.xml:178(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:146
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Step In</guimenuitem></menuchoice> or click on the "
-"<guibutton>Step In</guibutton> icon in the <interface>Debug toolbar</"
-"interface> to step into a program."
+"In the <gui>Watches</gui> window, right-click and select <gui>Remove all</"
+"gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:184(para)
+#. (itstool) path: section/p
+#: C/debug-watch.page:155
 msgid ""
-"Single stepping executes only one statement of the program (from the place "
-"where it has stopped) and then returns control. If the statement that is "
-"executed contains one or more functions, the debugger tries to step inside "
-"the functions (in the sequence in which the functions are executed). Once "
-"the statement is executed and control is passed back, you can study your "
-"program's state."
+"If a watch expression corresponds to a variable, you can change its value."
 msgstr ""
 
-#: C/anjuta-manual.xml:191(para)
+#. (itstool) path: item/p
+#: C/debug-watch.page:160
 msgid ""
-"If the <interface>Disassembly window</interface> has the focus when this "
-"command is selected, it executes only one assembler instruction."
+"In the <gui>Watches</gui> window, select the variable you want to edit and "
+"double click in the <gui>Value</gui> column."
 msgstr ""
 
-#: C/anjuta-manual.xml:198(title)
-msgid "Single stepping (step over)"
-msgstr ""
+#. (itstool) path: item/p
+#: C/debug-watch.page:164
+msgid "Enter the new value."
+msgstr "Введіть нове значення."
 
-#: C/anjuta-manual.xml:199(para)
-msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Step Over</guimenuitem></menuchoice> or click on the "
-"<guibutton>Step Over</guibutton> icon in the <interface>Debug toolbar</"
-"interface> to step over statements in a program."
+#. (itstool) path: info/desc
+#: C/directory-project-backend.page:8
+msgid "Directory project backend."
 msgstr ""
 
-#: C/anjuta-manual.xml:205(para)
-msgid ""
-"<emphasis>Step over</emphasis> is similar to <emphasis>step in</emphasis>, "
-"except that it does not step inside any function in the statement being "
-"executed. The statement will be executed in one go."
+#. (itstool) path: page/title
+#: C/directory-project-backend.page:21
+msgid "Directory project backend plugin"
 msgstr ""
 
-#: C/anjuta-manual.xml:210(para)
+#. (itstool) path: page/p
+#: C/directory-project-backend.page:23
 msgid ""
-"If the <interface>Disassembly window</interface> has the focus when this "
-"command is selected, it executes one assembler instruction but does not stop "
-"inside if this instruction is a call to a subroutine."
+"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 ""
 
-#: C/anjuta-manual.xml:216(para)
+#. (itstool) path: page/p
+#: C/directory-project-backend.page:32
 msgid ""
-"If a dynamic library is loaded during the step, the program will not stop at "
-"the end of the step. But it will run until it finds a breakpoint or you stop "
-"it."
+"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 ""
 
-#: C/anjuta-manual.xml:225(title)
-#, fuzzy
-msgid "Single stepping (step out)"
-msgstr "Зменшити на крок"
-
-#: C/anjuta-manual.xml:226(para)
+#. (itstool) path: page/p
+#: C/directory-project-backend.page:38
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Step Out</guimenuitem></menuchoice> or click on the "
-"<guibutton>Step Out</guibutton> icon in the <interface>Debug toolbar</"
-"interface> to step out in a program."
+"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 ""
 
-#: C/anjuta-manual.xml:232(para)
-msgid ""
-"<emphasis>Step out</emphasis> will execute the current function until it "
-"returns. The program will be stopped once it exits from the function. Step "
-"out is not really single stepping, because it does not only execute a single "
-"statement — it executes the whole function until that function returns to "
-"the calling function."
+#. (itstool) path: info/desc
+#: C/full-index.page:8
+msgid "All help topics."
 msgstr ""
 
-#: C/anjuta-manual.xml:242(title)
-#, fuzzy
-msgid "Run/Continue"
-msgstr "</B/24>Продовжити"
+#. (itstool) path: page/title
+#: C/full-index.page:16
+msgid "Index"
+msgstr "Покажчик"
 
-#: C/anjuta-manual.xml:243(para)
-msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Run/Continue</guimenuitem></menuchoice> or click on "
-"the <guibutton>Run/Continue</guibutton> icon in the <interface>Debug "
-"toolbar</interface> to continue the execution of a program."
-msgstr ""
+#. (itstool) path: info/title
+#. (itstool) path: page/title
+#: C/introduction.page:7 C/introduction.page:12
+msgid "Introduction"
+msgstr "Вступ"
 
-#: C/anjuta-manual.xml:249(para)
+#. (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 ""
+#| "<application>Anjuta</application> is a versatile Integrated Development "
+#| "Environment (IDE) for the GNOME desktop. It features a number of advanced "
+#| "programming facilities includes project management, application wizards, "
+#| "an interactive debugger, an integrated Glade UI designer, integrated "
+#| "Devhelp API help, an integrated Valgrind memory profiler, an integrated "
+#| "gprof performance profiler, a class generator, a powerful source editor, "
+#| "source browsing, and more."
+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 ""
+"<app>Anjuta</app> — універсальне інтегроване середовище "
+"розробки (IDE) для робочого столу GNOME. Воно містить багато розвинених "
+"можливостей програмування, включаючи керування проєктами, помічники "
+"створення програм, інтерактивне налагодження, інтегрований засіб дизайну "
+"інтерфейсу Glade, інтегровану довідку Devhelp API, генератор класів, потужний"
+" редактор коду, навігатор символами, підтримку Git, C/C++, Python, Vala тощо."
+
+#. (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 ""
+#| "Anjuta DevStudio has been designed to be simple to operate yet powerful "
+#| "enough to fulfill all your programming needs. We've added many new "
+#| "features to Anjuta over the course of its development. Our focus is on "
+#| "delivering power and usability at the same time and making your software "
+#| "development enjoyable without overloading your senses. We intend to "
+#| "continue improving and stabilizing Anjuta to give you the best IDE "
+#| "experience possible. We hope you will have a good time using Anjuta. If "
+#| "not, please help us make it better by reporting bugs and suggestions."
+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 ""
+"<app>Anjuta</app> розроблено простим у використанні та водночас досить "
+"потужним для потреб програмістів. Протягом історії розробки ми додали до "
+"<app>Anjuta</app> багато нових функцій. Ми намагались досягнути потужності та"
+" зручності "
+"у використанні, та водночас зробити розробку програм для вас задоволенням "
+"без надмірного укладення. Ми намагаємося постійно вдосконалювати та "
+"стабілізувати <app>Anjuta</app>, щоб надати вам найкращу IDE."
+
+#. (itstool) path: page/p
+#: C/introduction.page:39
+#| msgid ""
+#| "Please report any problems with <application>Anjuta</application> - this "
+#| "will help to improve the software, as well as helping the open source "
+#| "community."
+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 ""
+"Ми сподіваємося, ви отримаєте задоволення від використання <app>Anjuta</app>."
+" Якщо ні, будь ласка, "
+"допоможіть нам покращити програму, сповіщайте про усі помилки та "
+"висловлюйте пропозиції — це допоможе вдосконалити програму, а також допоможе"
+" спільноті open source."
+
+#. (itstool) path: page/p
+#: C/introduction.page:45
+#| msgid ""
+#| "The following screenshot illustrates some of the things you will find in "
+#| "Anjuta."
 msgid ""
-"This option continues the execution of the program until a breakpoint is "
-"encountered, or the program exits."
+"The following screenshot illustrates some of the things you will find in "
+"<app>Anjuta</app>."
 msgstr ""
+"Наступний знімок ілюструє деякі елементи, які ви знайдете у <app>Anjuta</app>."
 
-#: C/anjuta-manual.xml:256(title)
-#, fuzzy
-msgid "Run To"
+#. (itstool) path: figure/title
+#: C/introduction.page:51
+#| msgid "Anjuta in action"
+msgid "<app>Anjuta</app> in action"
+msgstr "<app>Anjuta</app> у дії"
+
+#. (itstool) path: figure/desc
+#. (itstool) path: media/p
+#: C/introduction.page:52 C/introduction.page:54
+msgid "<app>Anjuta</app> main window"
 msgstr ""
-"Неможливо запустити:\n"
-"%s"
 
-#: C/anjuta-manual.xml:257(para)
+#. (itstool) path: figure/media
+#. This is a reference to an external file such as an image or video. When
+#. the file changes, the md5 hash will change to let you know you need to
+#. update your localized copy. The msgstr is not used at all. Set it to
+#. whatever you like once you have updated your copy of the file.
+#: C/introduction.page:53
+msgctxt "_"
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Run to Cursor</guimenuitem></menuchoice> or click on "
-"the <guibutton>Run to Cursor</guibutton> icon in the <interface>Debug "
-"toolbar</interface> to run until the line at the cursor is reached."
+"external ref='figures/anjuta-in-action.png' "
+"md5='a31f1c85a4a14032fcd30ab6f6d6b3c0'"
 msgstr ""
 
-#: C/anjuta-manual.xml:263(para)
-msgid ""
-"This option continues the execution of the program until the line or the "
-"address (if the <interface>Disassembly window</interface> has the focus) at "
-"the cursor is reached."
+#. (itstool) path: info/desc
+#: C/language-support-cpp-modelines-emacs.page:9
+msgid "Supported Emacs modelines features."
 msgstr ""
 
-#: C/anjuta-manual.xml:271(title)
-#, fuzzy
-msgid "Stop Program"
-msgstr "Запускається програма \"%s\" ...\n"
+#. (itstool) path: page/title
+#: C/language-support-cpp-modelines-emacs.page:18
+msgid "Emacs modelines"
+msgstr "Режим рядків «Emacs»"
 
-#: C/anjuta-manual.xml:272(para)
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-emacs.page:20
 msgid ""
-"While the program is running and has control, no debugging tasks can be "
-"performed. To obtain control while the program is running, choose the menu "
-"item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Pause Program</"
-"guimenuitem></menuchoice> or click on the <guibutton>Pause Program</"
-"guibutton> icon in the <interface>Debug toolbar</interface>. This will "
-"interrupt the program and return control to the debugger."
+"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 ""
 
-#: C/anjuta-manual.xml:287(title)
-#, fuzzy
-msgid "Breakpoints"
-msgstr "Видалити всі точки зупинки"
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-emacs.page:25
+msgid "A typical <app>Emacs</app> modeline looks like this:"
+msgstr ""
 
-#: C/anjuta-manual.xml:288(para)
+#. (itstool) path: page/code
+#: C/language-support-cpp-modelines-emacs.page:27
+#, no-wrap
 msgid ""
-"When debugging a program, it is useful to be able to stop the execution of "
-"the program at a particular point, so that the state of the program can be "
-"examined at that location. Breakpoints enable this to happen. Breakpoints "
-"can be set at different locations in a source file and then the program is "
-"allowed to run. When a breakpoint is encountered, the execution of the "
-"program is suspended, enabling expressions to be evaluated, variables to be "
-"inspected, the stack trace to be studied, and so on."
+"\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 ""
 
-#: C/anjuta-manual.xml:298(title)
-#, fuzzy
-msgid "Listing Breakpoints"
-msgstr "Перелік вмісту каталогу"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-emacs.page:35
+msgid "<code>indent-tabs-mode</code>"
+msgstr "<code>indent-tabs-mode</code>"
 
-#: C/anjuta-manual.xml:299(para)
+#. (itstool) path: item/p
+#: C/language-support-cpp-modelines-emacs.page:36
 msgid ""
-"The <interface>Breakpoint list window</interface> can be opened by choosing "
-"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Breakpoints</"
-"guimenuitem></menuchoice>"
+"Set to <code>t</code> to use tabulation for indentation or <code>nil</code> "
+"to use spaces."
 msgstr ""
 
-#: C/anjuta-manual.xml:306(title) C/anjuta-manual.xml:308(screeninfo)
-#, fuzzy
-msgid "Breakpoint view"
-msgstr "Переглянути _журнал"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-emacs.page:40
+msgid "<code>tab-width</code>"
+msgstr "<code>tab-width</code>"
 
-#: C/anjuta-manual.xml:317(term) C/anjuta-manual.xml:413(term)
-#, fuzzy
-msgid "Location"
-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 ""
 
-#: C/anjuta-manual.xml:319(para)
-msgid ""
-"This is the position of the breakpoint in the source file. When the "
-"breakpoint is set by the debugger, you can get additional information such "
-"as the function containing the breakpoint."
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-emacs.page:44
+msgid "<code>c-basic-offset</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:327(term)
-#, fuzzy
-msgid "Address"
-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 ""
 
-#: C/anjuta-manual.xml:329(para)
-msgid ""
-"This field is filled with the address of the breakpoint when it is set by "
-"the debugger."
+#. (itstool) path: info/desc
+#: C/language-support-cpp-modelines-vim.page:9
+msgid "Supported Vim modelines features."
 msgstr ""
 
-#: C/anjuta-manual.xml:336(term)
-#, fuzzy
-msgid "Type"
-msgstr "Тип"
+#. (itstool) path: page/title
+#: C/language-support-cpp-modelines-vim.page:18
+msgid "Vim modelines"
+msgstr "Режим рядків «Vim»"
 
-#: C/anjuta-manual.xml:338(para)
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-vim.page:20
 msgid ""
-"This always displays \"breakpoint\". It will be used in a future release "
-"supporting different kinds of breakpoints."
+"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 ""
 
-#: C/anjuta-manual.xml:345(term) C/anjuta-manual.xml:440(term)
-#, fuzzy
-msgid "Condition"
-msgstr "Умова"
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-vim.page:25
+msgid "A typical <app>Vim</app> modeline looks like this:"
+msgstr ""
 
-#: C/anjuta-manual.xml:347(para)
+#. (itstool) path: page/code
+#: C/language-support-cpp-modelines-vim.page:27
+#, no-wrap
 msgid ""
-"This is the breakpoint condition. It is empty if no condition is defined."
+"\n"
+"/* vim: set noet ts=4 sw=4: */"
 msgstr ""
 
-#: C/anjuta-manual.xml:353(term)
-#, fuzzy
-msgid "Pass count"
-msgstr " (%(count)d з %(total)d)"
-
-#: C/anjuta-manual.xml:355(para)
-msgid ""
-"When the debugger is not running, this column displays the pass count of the "
-"breakpoint, or zero if it is not defined."
+#. (itstool) path: page/p
+#: C/language-support-cpp-modelines-vim.page:30
+msgid "Anjuta support only the following variables."
 msgstr ""
 
-#: C/anjuta-manual.xml:359(para)
-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."
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:34
+msgid "<code>expandtab</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:367(term)
-#, fuzzy
-msgid "State"
-msgstr "Область"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:35
+msgid "<code>et</code>"
+msgstr "<code>et</code>"
 
-#: C/anjuta-manual.xml:372(para)
-msgid "Pending: the breakpoint is not set in your program."
+#. (itstool) path: item/p
+#: C/language-support-cpp-modelines-vim.page:36
+msgid "Use spaces for indentation."
 msgstr ""
 
-#: C/anjuta-manual.xml:373(para)
-msgid ""
-"Permanent: the breakpoint is set (its id number in given inside parentheses)."
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:39
+msgid "<code>noexpandtab</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:374(para)
-msgid "Temporary: the breakpoint is set but will be deleted if reached."
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:40
+msgid "<code>noet</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:369(para)
-msgid "This is the state of the breakpoint. It may be <placeholder-1/>"
+#. (itstool) path: item/p
+#: C/language-support-cpp-modelines-vim.page:41
+msgid "Use tabulation for indentation."
 msgstr ""
 
-#: C/anjuta-manual.xml:313(para)
-msgid "The view has the following columns: <placeholder-1/>"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:44
+msgid "<code>softtabstop</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:382(para)
-msgid ""
-"All breakpoints are kept across Anjuta sessions even if they correspond to a "
-"non-existing location. In this case their states are set as pending. The "
-"interface tries to set them each time the program is started or a new "
-"dynamic library is loaded."
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:45
+msgid "<code>sts</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:391(title)
-#, fuzzy
-msgid "Adding or Setting Breakpoints"
-msgstr "Настройка або визначення параметрів"
-
-#: C/anjuta-manual.xml:392(para)
-msgid ""
-"Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> or "
-"<menuchoice><guimenuitem>Add Breakpoint…</guimenuitem></menuchoice> in the "
-"breakpoint list popup menu to open the <interface>add breakpoint</interface> "
-"dialog."
-msgstr ""
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:46
+msgid "<code>tabstop</code>"
+msgstr "<code>tabstop</code>"
 
-#: C/anjuta-manual.xml:400(title) C/anjuta-manual.xml:402(screeninfo)
-#, fuzzy
-msgid "Breakpoint add dialog"
-msgstr "Вікно додавання файлів"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:47
+msgid "<code>ts</code>"
+msgstr "<code>ts</code>"
 
-#: C/anjuta-manual.xml:415(para)
-msgid ""
-"Enter the location at which to set the breakpoint. It can be specified in "
-"any of the following formats:"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:51
+msgid "<code>shiftwidth</code>"
 msgstr ""
 
-#: C/anjuta-manual.xml:421(para)
-#, fuzzy
-msgid "File_name:Line_number"
-msgstr "!ім'я_файлу,номер_фільтра"
+#. (itstool) path: item/title
+#: C/language-support-cpp-modelines-vim.page:52
+msgid "<code>sw</code>"
+msgstr "<code>sw</code>"
 
-#: C/anjuta-manual.xml:422(para)
-#, fuzzy
-msgid "Function_name"
-msgstr "Неприпустиме ім'я функції"
+#. (itstool) path: info/desc
+#: C/makefile-project-backend.page:8
+msgid "Makefile project backend."
+msgstr ""
 
-#: C/anjuta-manual.xml:423(para)
-#, fuzzy
-msgid "File:Function_name"
-msgstr "Неприпустиме ім'я функції"
+#. (itstool) path: page/title
+#: C/makefile-project-backend.page:21
+msgid "Makefile project backend plugin"
+msgstr ""
 
-#: C/anjuta-manual.xml:426(para)
+#. (itstool) path: page/p
+#: C/makefile-project-backend.page:23
 msgid ""
-"The first format is obvious — the location refers to the line number "
-"<emphasis>Line_number</emphasis> in the source file <emphasis>File</"
-"emphasis>. The second format refers to the first line of the function "
-"<emphasis>Function_name</emphasis>. The third is similar to the second, "
-"except that this notation is used where there is more than one function with "
-"the name <emphasis>Function_name</emphasis> in the program. It is possible "
-"to differentiate between them by providing the <emphasis>File</emphasis>, so "
-"the notation refers to the function <emphasis>Function_name</emphasis> in "
-"the file <emphasis>File</emphasis>."
+"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 ""
 
-#: C/anjuta-manual.xml:442(para)
+#. (itstool) path: page/p
+#: C/makefile-project-backend.page:33
 msgid ""
-"The <emphasis>Condition</emphasis> parameter displays a associated "
-"expression which should evaluate to a Boolean value — that is, the "
-"evaluation of the expression should result in either TRUE(1) or FALSE(0). If "
-"the final evaluation value is not a Boolean value, then it will be "
-"appropriately type cast to a Boolean."
+"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 ""
 
-#: C/anjuta-manual.xml:449(para)
+#. (itstool) path: note/p
+#: C/makefile-project-backend.page:42
 msgid ""
-"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 evaluation results in a TRUE value, otherwise it will continue "
-"the execution as though there had been no breakpoint."
+"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 ""
 
-#: C/anjuta-manual.xml:455(para)
+#. (itstool) path: page/p
+#: C/makefile-project-backend.page:49
 msgid ""
-"The default value, if you leave this field blank, of <emphasis>Condition</"
-"emphasis> is TRUE. The debugger will always break the execution at the "
-"breakpoint location."
+"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 ""
 
-#: C/anjuta-manual.xml:462(term)
-#, fuzzy
-msgid "Pass Count"
-msgstr " (%(count)d з %(total)d)"
+#. (itstool) path: info/desc
+#: C/project-import.page:11
+msgid "Import an existing project."
+msgstr "Імпортування наявного проєкту."
+
+#. (itstool) path: page/title
+#: C/project-import.page:24
+msgid "Import a Project"
+msgstr "Імпортування проєкту"
 
-#: C/anjuta-manual.xml:464(para)
+#. (itstool) path: page/p
+#: C/project-import.page:26
 msgid ""
-"The <emphasis>Pass count</emphasis> is an integer (unsigned) value which "
-"tells the debugger to skip the breakpoint that number of times before it is "
-"considered. <emphasis>Pass count</emphasis> has a higher priority than the "
-"<emphasis>Break condition</emphasis>. Only when the <emphasis>Pass count</"
-"emphasis> reaches zero will the debugger evaluate the <emphasis>Break "
-"condition</emphasis> (if any condition is present). If there is no "
-"condition, the debugger will break the execution once the <emphasis>Pass "
-"count</emphasis> counts down to zero."
+"<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 ""
 
-#: C/anjuta-manual.xml:474(para)
+#. (itstool) path: item/p
+#: C/project-import.page:38
 msgid ""
-"The default value, if you leave this field blank, of the <emphasis>Pass "
-"count</emphasis> is zero. The breakpoint will be considered when it is first "
-"encountered."
+"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 ""
 
-#: C/anjuta-manual.xml:407(para)
+#. (itstool) path: item/p
+#: C/project-import.page:47
 msgid ""
-"Enter the location and, optionally, the break condition and the pass count; "
-"then click <guibutton>OK</guibutton> to set the breakpoint. <placeholder-1/>"
+"Select <gui>Import from folder</gui> if the project is already present on "
+"your computer, then select the project directory."
 msgstr ""
 
-#: C/anjuta-manual.xml:482(para)
+#. (itstool) path: item/p
+#: C/project-import.page:51
 msgid ""
-"A breakpoint may also be set by selecting a line in the editor and choosing "
-"the menu item <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Toggle "
-"Breakpoint</guimenuitem></menuchoice> in the editor context menu or the "
-"<guibutton>Toggle Breakpoint</guibutton> icon in the <interface>Debug "
-"toolbar</interface>."
+"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 ""
 
-#: C/anjuta-manual.xml:491(para)
+#. (itstool) path: item/p
+#: C/project-import.page:59
 msgid ""
-"Breakpoints can be added even if the debugger is not started, or in a "
-"dynamic library which is not loaded yet. But they cannot be added while a "
-"program is running under control of the debugger."
+"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 ""
 
-#: C/anjuta-manual.xml:500(title)
-#, fuzzy
-msgid "Editing Breakpoints"
-msgstr "Повторити попередню дію"
-
-#: C/anjuta-manual.xml:501(para)
+#. (itstool) path: item/p
+#: C/project-import.page:68
 msgid ""
-"You can change the condition and the pass count by selecting the breakpoint "
-"in the breakpoint list and clicking <menuchoice><guimenuitem>Edit "
-"Breakpoint</guimenuitem></menuchoice> in the popup menu."
+"<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 ""
 
-#: C/anjuta-manual.xml:506(para)
-msgid ""
-"Edit the entries as required and click on <guibutton>OK</guibutton> to "
-"commit the changes."
+#. (itstool) path: info/desc
+#: C/project-manager-folder-add.page:9
+msgid "Add a folder to a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:513(title)
-#, fuzzy
-msgid "Deleting Breakpoints"
-msgstr "Видаляється каталог"
+#. (itstool) path: page/title
+#: C/project-manager-folder-add.page:18
+msgid "Add a Folder"
+msgstr ""
 
-#: C/anjuta-manual.xml:514(para)
+#. (itstool) path: page/p
+#: C/project-manager-folder-add.page:20
 msgid ""
-"Select the breakpoint in the breakpoint list view and click on "
-"<menuchoice><guimenuitem>Remove Breakpoint</guimenuitem></menuchoice> to "
-"delete it."
+"A folder allows you to group several target allowing to set common "
+"properties for all of them. It often corresponds to a directory."
 msgstr ""
 
-#: C/anjuta-manual.xml:518(para)
+#. (itstool) path: item/p
+#: C/project-manager-folder-add.page:25
 msgid ""
-"A existing breakpoint may also be deleted by selecting its line in the "
-"editor and choosing the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Toggle Breakpoint</guimenuitem></menuchoice>, the "
-"editor context menu item <menuchoice><guimenuitem>Toggle Breakpoint</"
-"guimenuitem></menuchoice> or the <guibutton>Toggle Breakpoint</guibutton> "
-"icon in the <interface>Debug toolbar</interface>."
+"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 ""
 
-#: C/anjuta-manual.xml:527(para)
+#. (itstool) path: item/p
+#: C/project-manager-folder-add.page:29
 msgid ""
-"You can remove all breakpoints by clicking on <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Remove All Breakpoints</guimenuitem></menuchoice> or "
-"on <menuchoice><guimenuitem>Remove All Breakpoints</guimenuitem></"
-"menuchoice> in the breakpoint list context menu."
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>Add "
+"Group</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:536(title)
-msgid "Enabling or Disabling Breakpoints"
+#. (itstool) path: item/p
+#: C/project-manager-folder-add.page:33
+msgid "Enter a new group name."
 msgstr ""
 
-#: C/anjuta-manual.xml:537(para)
+#. (itstool) path: note/p
+#: C/project-manager-folder-add.page:35
 msgid ""
-"Click on the Enable column of the <interface>Breakpoint list window</"
-"interface> or in the context menu item <menuchoice><guimenuitem>Enable "
-"Breakpoint</guimenuitem></menuchoice> to enable or disable the selected "
-"breakpoint. The breakpoint will be enabled or disabled, depending on its "
-"current state."
+"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 ""
 
-#: C/anjuta-manual.xml:543(para)
+#. (itstool) path: item/p
+#: C/project-manager-folder-add.page:43
 msgid ""
-"To disable all breakpoints, click on <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Disable All Breakpoints</guimenuitem></menuchoice> "
-"or on <menuchoice><guimenuitem>Disable All Breakpoints</guimenuitem></"
-"menuchoice> in the breakpoint list context menu."
+"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 ""
 
-#: C/anjuta-manual.xml:554(title)
-#, fuzzy
-msgid "Expressions"
-msgstr "Регулярні вирази"
+#. (itstool) path: info/desc
+#: C/project-manager-folder.page:11
+msgid "Add, edit or remove folders from a project."
+msgstr ""
 
-#: C/anjuta-manual.xml:557(title)
-#, fuzzy
-msgid "Listing local variables"
-msgstr "Покажчик змінних оточення"
+#. (itstool) path: page/title
+#: C/project-manager-folder.page:20
+msgid "Manage Folders"
+msgstr ""
 
-#: C/anjuta-manual.xml:558(para)
-msgid ""
-"When a program is running under the control of the debugger, the "
-"<interface>Locals list window</interface> can be opened by choosing "
-"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Locals</guimenuitem></"
-"menuchoice>."
+#. (itstool) path: info/desc
+#: C/project-manager-folder-remove.page:9
+msgid "Remove folders from a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:572(title) C/anjuta-manual.xml:574(screeninfo)
-#, fuzzy
-msgid "Local variables"
-msgstr "В_ивести змінні"
+#. (itstool) path: page/title
+#: C/project-manager-folder-remove.page:18
+msgid "Remove Folder"
+msgstr "Вилучення теки"
 
-#: C/anjuta-manual.xml:564(para)
+#. (itstool) path: item/p
+#: C/project-manager-folder-remove.page:22
 msgid ""
-"Local variables of the current frame (the current function in which the "
-"program control is present) are displayed in the <interface>Locals window</"
-"interface>. 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. <placeholder-1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:579(para)
+#. (itstool) path: item/p
+#: C/project-manager-folder-remove.page:28
 msgid ""
-"The value of a local variable can be modified by selecting it and clicking "
-"in the <guilabel>Value</guilabel> column."
+"Confirm the removal. This will only remove the folder from the project files "
+"without removing any files or directories from your disk."
 msgstr ""
 
-#: C/anjuta-manual.xml:584(para)
-msgid ""
-"<application>gdb</application> is more and more often used as a back end for "
-"a graphical front end. It has been improved recently in this area. It is "
-"recommended that you use the latest version (6.6) of gdb. With older "
-"versions, gdb can crash when the front end asks for an pointer with an "
-"invalid (but unused) value."
+#. (itstool) path: info/desc
+#: C/project-manager-library-add.page:10
+msgid "Add a custom library to a target."
 msgstr ""
 
-#: C/anjuta-manual.xml:594(title)
-#, fuzzy
-msgid "Listing watched expressions"
-msgstr "Заміна регулярних виразів"
+#. (itstool) path: page/title
+#: C/project-manager-library-add.page:23
+msgid "Add a Custom Library"
+msgstr ""
 
-#: C/anjuta-manual.xml:595(para)
+#. (itstool) path: page/p
+#: C/project-manager-library-add.page:25
 msgid ""
-"Inspecting or evaluating an expression provides the result only once. To "
-"continuously monitor some variables or expressions, use <emphasis>expression "
-"watches</emphasis>."
+"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 ""
 
-#: C/anjuta-manual.xml:599(para)
+#. (itstool) path: page/p
+#: C/project-manager-library-add.page:29
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>View</"
-"guisubmenu><guimenuitem>Watches</guimenuitem></menuchoice> to display the "
-"<interface>Watches window</interface>."
+"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 ""
 
-#: C/anjuta-manual.xml:606(title)
-#, fuzzy
-msgid "Adding an expression to watch"
-msgstr "Вираз запиту для аналізу"
-
-#: C/anjuta-manual.xml:607(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:36
 msgid ""
-"Right-click on the <interface>Watches window</interface> to open the context "
-"menu. Choose the menu item <guimenuitem>Add Watch…</guimenuitem>. "
-"Alternatively, you can use <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Add Watch…</guimenuitem></menuchoice> A dialog "
-"prompting for the expression will appear. Enter the expression and click "
-"<guibutton>OK</guibutton>."
+"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 ""
 
-#: C/anjuta-manual.xml:616(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:41 C/project-manager-library-add.page:65
 msgid ""
-"By default watch expressions are updated automatically each time the program "
-"is stopped. This can be changed in the add watch dialog or later using the "
-"<guimenuitem>Automatic update</guimenuitem> menu item in the "
-"<interface>Watches window</interface> context menu. A watched expression can "
-"be updated manually by choosing <guimenuitem>Update Watch</guimenuitem> or "
-"<guimenuitem>Update All</guimenuitem> in the context menu."
+"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 ""
 
-#: C/anjuta-manual.xml:625(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:47
 msgid ""
-"It is not necessary to have the debugger running to add a new watch "
-"expression. If the debugger is not running or the corresponding expression "
-"cannot be found, the front end will try to create the watch expression each "
-"time the program is stopped."
+"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 ""
 
-#: C/anjuta-manual.xml:634(title)
-#, fuzzy
-msgid "Removing a watched expression"
-msgstr "у виразі очікувався \"?\""
-
-#: C/anjuta-manual.xml:635(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:55
 msgid ""
-"Right-click the watch expression that you want to remove in the "
-"<interface>Watches window</interface>, then choose the context menu item "
-"<guimenuitem>Remove</guimenuitem> to remove it."
+"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 ""
 
-#: C/anjuta-manual.xml:640(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:59
 msgid ""
-"All watches can be removed by choosing <guimenuitem>Remove All</guimenuitem> "
-"in the context menu of the <interface>Watches window</interface>."
+"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 ""
 
-#: C/anjuta-manual.xml:647(title)
-#, fuzzy
-msgid "Evaluating expressions"
-msgstr "Регулярні вирази"
-
-#: C/anjuta-manual.xml:648(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:71
 msgid ""
-"When control is returned from a program — possibly at a breakpoint — it is "
-"possible to evaluate expressions or inspect the values of variables in the "
-"program. Choose the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice>, "
-"<menuchoice><guimenuitem>Inspect/Evaluate …</guimenuitem></menuchoice> in "
-"the context menu of the editor or click the <guibutton>Inspect</guibutton> "
-"button on the <interface>Debug Toolbar</interface>."
+"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 ""
 
-#: C/anjuta-manual.xml:657(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-add.page:77
 msgid ""
-"A window will appear showing the evaluation of the expression highlighted in "
-"the editor. You can evaluate a new expression by clicking on the "
-"<guilabel>name</guilabel> column and entering the new one."
+"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 ""
 
-#: C/anjuta-manual.xml:663(para)
-msgid ""
-"You can add the expression to the list of watched expressions directly by "
-"clicking on the <guibutton>Add</guibutton> button."
+#. (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 ""
 
-#: C/anjuta-manual.xml:670(title)
-msgid "Inspecting expressions in editor window"
+#. (itstool) path: page/title
+#: C/project-manager-library-remove.page:23
+msgid "Remove a Custom Library"
 msgstr ""
 
-#: C/anjuta-manual.xml:671(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-remove.page:27
 msgid ""
-"When the debugger is active with the program stopped, you can get the value "
-"of an expression just by putting the mouse pointer over it and staying there "
-"for a short time. If the expression is already present in the "
-"<interface>Locals</interface> or <interface>Watches</interface> window, its "
-"value is displayed in a tooltip."
+"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 ""
 
-#: C/anjuta-manual.xml:677(para)
+#. (itstool) path: item/p
+#: C/project-manager-library-remove.page:33
 msgid ""
-"This capability is currently working only for simple variables, not for "
-"structures or arrays."
+"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 ""
 
-#: C/anjuta-manual.xml:686(title)
-#, fuzzy
-msgid "Stack Trace"
-msgstr "Провести векторизацію"
+#. (itstool) path: info/desc
+#: C/project-manager-module-add.page:10
+msgid "Add a set of libraries to a target."
+msgstr ""
 
-#: C/anjuta-manual.xml:689(title)
-#, fuzzy
-msgid "Stack Window"
-msgstr "Вікно сервера..."
+#. (itstool) path: page/title
+#: C/project-manager-module-add.page:23
+msgid "Add packaged libraries"
+msgstr ""
 
-#: C/anjuta-manual.xml:690(para)
+#. (itstool) path: page/p
+#: C/project-manager-module-add.page:25
 msgid ""
-"The <interface>stack trace window</interface> shows the contents of the "
-"program stack. It lists all functions and their arguments in the sequence "
-"they were called. There is also a number representing each call. This number "
-"is called the <emphasis>frame</emphasis>. Each call in the trace exists in a "
-"different frame. This starts from frame 0 (the last function called) and "
-"grows higher as function nesting becomes deeper."
+"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 ""
 
-#: C/anjuta-manual.xml:698(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-add.page:33
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>View </"
-"guisubmenu><guimenuitem>Stack</guimenuitem></menuchoice> to open the stack "
-"trace for the program being debugged."
+"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 ""
 
-#: C/anjuta-manual.xml:705(title) C/anjuta-manual.xml:707(screeninfo)
-#, fuzzy
-msgid "Stack trace window"
-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 ""
 
-#: C/anjuta-manual.xml:712(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-add.page:41
 msgid ""
-"A small arrow points to the currently selected frame in the stack trace. By "
-"default, this will be frame 0, the last function called. All evaluation and "
-"inspection of expressions or variables will be with reference to this "
-"selected frame. The scope of variables or expressions being evaluated will "
-"be limited to the selected frame only. The same applies for new expressions "
-"only in the watch."
+"You need to select the target where you want to add the library in the "
+"<gui>target button</gui> above."
 msgstr ""
 
-#: C/anjuta-manual.xml:722(title)
-#, fuzzy
-msgid "Setting the current frame"
-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 ""
 
-#: C/anjuta-manual.xml:723(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-add.page:50
 msgid ""
-"Double-clicking on any frame in the stack trace sets 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 context "
-"menu by right-clicking on the <interface>Stack trace window</interface>, and "
-"choose the menu item <guimenuitem>Set current frame</guimenuitem> to set the "
-"frame."
+"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 ""
 
-#: C/anjuta-manual.xml:731(para)
+#. (itstool) path: note/p
+#: C/project-manager-module-add.page:55
 msgid ""
-"Changing the stack frame changes the <interface>Locals window</interface> "
-"content, but not the <interface>Watches window</interface> as each "
-"expression is evaluated in the frame used when it was defined."
+"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 ""
 
-#: C/anjuta-manual.xml:741(title)
-#, fuzzy
-msgid "Thread"
-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 ""
 
-#: C/anjuta-manual.xml:744(title)
-#, fuzzy
-msgid "Thread Window"
-msgstr "Вікно сервера..."
+#. (itstool) path: info/desc
+#: C/project-manager-module-new.page:12
+msgid "Groups libraries in a module."
+msgstr ""
 
-#: C/anjuta-manual.xml:745(para)
-msgid ""
-"The <interface>Thread window</interface> shows all threads used by the "
-"program and indicates the current thread. Choose the menu item "
-"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Thread</guimenuitem></"
-"menuchoice> to open this window."
+#. (itstool) path: page/title
+#: C/project-manager-module-new.page:25
+msgid "Add a Module"
 msgstr ""
 
-#: C/anjuta-manual.xml:750(para)
+#. (itstool) path: page/p
+#: C/project-manager-module-new.page:27
 msgid ""
-"A small arrow points to the current thread. When the program is stopped, the "
-"current thread is the thread which has been interrupted. Each thread has its "
-"own stack frame, so changing the current thread changes the current stack "
-"frame."
+"Packages cannot be added directly to a program but have to be grouped in a "
+"module."
 msgstr ""
 
-#: C/anjuta-manual.xml:759(title)
-#, fuzzy
-msgid "Setting the current thread"
-msgstr "виділити поточну бесіду"
-
-#: C/anjuta-manual.xml:760(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:32
 msgid ""
-"Double-clicking on any thread in the thread list will set that thread as the "
-"currently selected thread. The arrow will point to the thread, indicating "
-"that it has been selected as the current thread. Alternatively, open the "
-"context menu by right-clicking on the <interface>Thread list window</"
-"interface>, and choose the menu item <guimenuitem>Set current thread</"
-"guimenuitem> to set the thread."
+"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 ""
 
-#: C/anjuta-manual.xml:768(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:39
 msgid ""
-"Changing the thread changes the value of CPU registers and the current stack "
-"frame, so the <interface>Locals window</interface> changes too."
+"On the <gui>Add Library</gui> dialog, click on the <gui>New Library</gui> "
+"button."
 msgstr ""
 
-#: C/anjuta-manual.xml:777(title)
-#, fuzzy
-msgid "CPU"
-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 ""
 
-#: C/anjuta-manual.xml:780(title)
-#, fuzzy
-msgid "Register window"
-msgstr "Вікно сервера..."
+#. (itstool) path: note/p
+#: C/project-manager-module-new.page:46
+msgid "If the library you want does not appear here:"
+msgstr ""
 
-#: C/anjuta-manual.xml:781(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:49
 msgid ""
-"It is possible to examine the contents of the internal registers of the CPU "
-"(microprocessor). Choose the menu item <menuchoice><guisubmenu>View</"
-"guisubmenu><guimenuitem>Registers</guimenuitem></menuchoice>. A window "
-"listing all available registers in the microprocessor and their "
-"corresponding contents will appear."
+"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 ""
 
-#: C/anjuta-manual.xml:788(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:57
 msgid ""
-"If any register value was changed in the last debugging step, its value will "
-"be highlighted in red. It is possible to change one register value by "
-"selecting it and clicking in the <guilabel>value</guilabel> column."
+"It could be that the library is not packaged, it is often the case for "
+"libraries not developed on Linux. See the chapter <link xref=\"project-"
+"manager-library-add\"/> explaining how to use them."
 msgstr ""
 
-#: C/anjuta-manual.xml:796(title)
-#, fuzzy
-msgid "Memory window"
-msgstr "Вікно сервера..."
-
-#: C/anjuta-manual.xml:797(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:66
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>View</"
-"guisubmenu><guimenuitem>Memory </guimenuitem></menuchoice> to open the "
-"<interface>memory window</interface> for the program being debugged. This "
-"window shows the contents of all memory."
+"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 ""
 
-#: C/anjuta-manual.xml:802(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-new.page:72
 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."
+"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 ""
 
-#: C/anjuta-manual.xml:806(para)
-msgid ""
-"The addressing space of even a 32-bit microprocessor is quite large (4 "
-"gigabytes), so it is very difficult to go to a particular address with the "
-"scrollbar. But you can click on the right mouse button to display a context "
-"menu and select <menuchoice><guimenuitem>Goto address</guimenuitem></"
-"menuchoice> to get a small edit box where you can enter an address in "
-"hexadecimal."
+#. (itstool) path: info/desc
+#: C/project-manager-module-remove.page:10
+msgid "Remove a set of libraries from a target."
 msgstr ""
 
-#: C/anjuta-manual.xml:816(title)
-#, fuzzy
-msgid "Disassembly window"
-msgstr "Вікно сервера..."
+#. (itstool) path: page/title
+#: C/project-manager-module-remove.page:23
+msgid "Remove a Module"
+msgstr "Вилучення модуля"
 
-#: C/anjuta-manual.xml:817(para)
+#. (itstool) path: item/p
+#: C/project-manager-module-remove.page:27
 msgid ""
-"Choose the menu item <menuchoice><guisubmenu>View</"
-"guisubmenu><guimenuitem>Disassembly </guimenuitem></menuchoice> to open the "
-"<interface>disassembly window</interface> for the program being debugged."
+"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 ""
 
-#: C/anjuta-manual.xml:822(para)
+#. (itstool) path: item/p
+#: C/project-manager-package-remove.page:26
 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."
+"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 ""
 
-#: C/anjuta-manual.xml:827(para)
+#. (itstool) path: item/p
+#: C/project-manager-package-remove.page:32
 msgid ""
-"Again, as the addressing space is very large, the scrollbar is quite "
-"useless. You can click on the right mouse button to display the context menu "
-"and select <menuchoice><guimenuitem>Goto address</guimenuitem></menuchoice> "
-"to get a small edit box where you can enter an address in hexadecimal. The "
-"position in the disassembly window will be changed to the program counter "
-"value when the program is stopped."
+"Confirm the removal. This package will be removed from the project file."
 msgstr ""
 
-#: C/anjuta-manual.xml:840(title)
-#, fuzzy
-msgid "Others"
-msgstr "Інші"
+#. (itstool) path: info/desc
+#: C/project-manager.page:8
+msgid "Project manager."
+msgstr "Керування проєктами."
 
-#: C/anjuta-manual.xml:842(para)
+#. (itstool) path: page/title
+#: C/project-manager.page:21
+msgid "Project manager plugin"
+msgstr "Додаток керування проєктами"
+
+#. (itstool) path: page/p
+#: C/project-manager.page:23
 msgid ""
-"There are a number of other debugger features used less frequently and not "
-"very well integrated in the new front end but which are still working."
+"<app>Anjuta</app> supports several already existing project formats through "
+"plugin backends. The main one is the autotools format commonly used on Linux."
 msgstr ""
 
-#: C/anjuta-manual.xml:848(title)
-#, fuzzy
-msgid "Dynamically loaded Libraries"
-msgstr "Робоче середовище KDE - Бібліотеки"
+#. (itstool) path: page/p
+#: C/project-manager.page:29
+msgid ""
+"The project backend to use is chosen when creating or importing a new "
+"project in <app>Anjuta</app>. It is displayed in the properties of the "
+"project root node and can be changed at any time."
+msgstr ""
 
-#: C/anjuta-manual.xml:849(para)
+#. (itstool) path: page/p
+#: C/project-manager.page:35
 msgid ""
-"To obtain a list of the dynamic libraries used by a program, choose the menu "
-"item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
-"guisubmenu><guimenuitem>Shared Libraries</guimenuitem></menuchoice>. This "
-"will bring open a window which will list all shared libraries the program "
-"has loaded and their locations in memory. It also shows whether each "
-"library's symbol table is loaded or not (Yes/No)."
+"Whatever the underlying backend, the graphical interface is the same but "
+"some functions might be disabled."
 msgstr ""
 
-#: C/anjuta-manual.xml:859(title) C/anjuta-manual.xml:861(screeninfo)
-#, fuzzy
-msgid "Shared Libraries window"
-msgstr "Лише LAMELib|LAMELib|Спільні бібліотеки (*)|*"
+#. (itstool) path: section/title
+#: C/project-manager.page:41
+msgid "Project Backend Plugin"
+msgstr "Додаток модуля проєктів"
 
-#: C/anjuta-manual.xml:869(title)
-#, fuzzy
-msgid "Kernel Signals"
-msgstr "Перевірка сигналів"
+#. (itstool) path: info/desc
+#: C/project-manager-root.page:12
+msgid "Edit project properties."
+msgstr "Редагування властивостей проєкту."
 
-#: C/anjuta-manual.xml:870(para)
-msgid ""
-"Kernel signals are a way of signaling between processes in Linux. The list "
-"of signals available for a program can be displayed by choosing the menu "
-"item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Info</"
-"guisubmenu><guimenuitem>Kernel Signals</guimenuitem></menuchoice>. A window "
-"will open which lists all signals available in the system along with a brief "
-"description of each signal."
+#. (itstool) path: page/title
+#: C/project-manager-root.page:21
+msgid "Edit a Project"
+msgstr "Редагування проєкту"
+
+#. (itstool) path: info/desc
+#: C/project-manager-source-add.page:9
+msgid "Add existing files to a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:879(title) C/anjuta-manual.xml:881(screeninfo)
-#, fuzzy
-msgid "Kernel Signals window"
-msgstr "Відкрити діалогове вікно"
+#. (itstool) path: page/title
+#: C/project-manager-source-add.page:22
+msgid "Add Files"
+msgstr "Додати файли"
 
-#: C/anjuta-manual.xml:886(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:26
 msgid ""
-"There are three columns which specify what to do when a signal is received:"
+"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 ""
 
-#: C/anjuta-manual.xml:892(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:31
 msgid ""
-"<emphasis>Stop</emphasis> — this tells the debugger whether to stop the "
-"program execution (and return control) when the program receives this signal."
+"Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui> <gui>Add "
+"Source File...</gui></guiseq>"
 msgstr ""
 
-#: C/anjuta-manual.xml:898(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:35
 msgid ""
-"<emphasis>Print</emphasis> — this tells the debugger whether to display the "
-"received signal."
+"You can select another target in the top <gui>target chooser button</gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:903(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-add.page:39
 msgid ""
-"<emphasis>Pass</emphasis> — this tells the debugger whether to pass the "
-"signal to the program."
+"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 ""
 
-#: C/anjuta-manual.xml:909(para)
+#. (itstool) path: note/p
+#: C/project-manager-source-add.page:48
 msgid ""
-"The context menu that is displayed when you click on the right mouse button "
-"has all its items disabled because the corresponding functions are not "
-"implemented yet."
+"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 ""
 
-#: C/anjuta-manual.xml:918(title)
-#, fuzzy
-msgid "Information about used files"
-msgstr "Не вдається отримати інформацію про локальні файли."
-
-#: C/anjuta-manual.xml:919(para)
-msgid ""
-"You can get some information about the files used by the debugged program by "
-"choosing the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Target files</"
-"guimenuitem></menuchoice>. A window will open displaying this information."
+#. (itstool) path: info/desc
+#: C/project-manager-source.page:12
+msgid "Add or remove files from a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:928(title)
-#, fuzzy
-msgid "Information about debugged program"
-msgstr "Інформація про авторське право програми"
+#. (itstool) path: page/title
+#: C/project-manager-source.page:21
+#| msgid "Editing Files"
+msgid "Manage Files"
+msgstr "Керування файлами"
 
-#: C/anjuta-manual.xml:929(para)
-msgid ""
-"You can get some information about the debugged program by choosing the menu "
-"item <menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Information</"
-"guisubmenu><guimenuitem>Program</guimenuitem></menuchoice>. A window will "
-"open displaying this information."
+#. (itstool) path: info/desc
+#: C/project-manager-source-remove.page:9
+msgid "Remove files from a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:938(title)
-#, fuzzy
-msgid "Information about kernel structure"
-msgstr "Інформацію про GThumb"
+#. (itstool) path: page/title
+#: C/project-manager-source-remove.page:22
+msgid "Remove Files"
+msgstr "Вилучення файлів"
 
-#: C/anjuta-manual.xml:939(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-remove.page:26
 msgid ""
-"You can get some information about kernel data for the current process by "
-"choosing the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Kernel user "
-"struct</guimenuitem></menuchoice>. A window will open displaying this "
-"information."
+"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 ""
 
-#: C/anjuta-manual.xml:948(title)
-#, fuzzy
-msgid "Information about global variables"
-msgstr "Інформацію про GThumb"
-
-#: C/anjuta-manual.xml:949(para)
+#. (itstool) path: item/p
+#: C/project-manager-source-remove.page:32
 msgid ""
-"You can list all global variables by choosing the menu item "
-"<menuchoice><guisubmenu>Debug</guisubmenu><guisubmenu>Information</"
-"guisubmenu><guimenuitem>Info Global Variable</guimenuitem></menuchoice>. A "
-"window will open listing all global variables."
+"Confirm the removal. The file will only be removed from the project, not "
+"from your disk."
 msgstr ""
 
-#: C/anjuta-manual.xml:958(title)
-#, fuzzy
-msgid "Information about the current frame"
-msgstr "Показати інформацію про поточний файл"
-
-#: C/anjuta-manual.xml:959(para)
+#. (itstool) path: note/p
+#: C/project-manager-source-remove.page:38
 msgid ""
-"You can obtain information about the currently selected frame by choosing "
-"the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Info Current "
-"Frame</guimenuitem></menuchoice>. A window will open describing the current "
-"frame."
+"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 ""
 
-#: C/anjuta-manual.xml:968(title)
-#, fuzzy
-msgid "Information about the current function arguments"
-msgstr "Показати інформацію про поточний файл"
-
-#: C/anjuta-manual.xml:969(para)
-msgid ""
-"You can obtain information about the arguments of the current function by "
-"choosing the menu item <menuchoice><guisubmenu>Debug</"
-"guisubmenu><guisubmenu>Information</guisubmenu><guimenuitem>Arguments</"
-"guimenuitem></menuchoice>. A window will open describing the arguments."
+#. (itstool) path: info/desc
+#: C/project-manager-target-add.page:9
+msgid "Add a target to a project."
 msgstr ""
 
-#: C/anjuta-manual.xml:978(title)
-#, fuzzy
-msgid "User command"
-msgstr "Вихід за вимогою користувача."
+#. (itstool) path: page/title
+#: C/project-manager-target-add.page:22
+msgid "Add a Target"
+msgstr "Додавання цілі"
 
-#: C/anjuta-manual.xml:979(para)
+#. (itstool) path: page/p
+#: C/project-manager-target-add.page:24
 msgid ""
-"To send directly a command to the back end choose the menu item "
-"<menuchoice><guimenu>Debug</guimenu><guimenuitem>Debugger command</"
-"guimenuitem></menuchoice>. This will bring a small dialog where you can "
-"enter commands that will be send to the debugger when you press "
-"<keycap>Return</keycap>."
+"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 ""
 
-#: C/anjuta-manual.xml:987(para)
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:30
 msgid ""
-"The front end sends this command directly to the back end without performing "
-"any checks. By example if you set a breakpoint like this, it will not appear "
-"in the <interface>breakpoint list window</interface>. It is better to avoid "
-"using this command unless you know exactly what you are doing."
+"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 ""
 
-#: C/anjuta-manual.xml:2(title)
-#, fuzzy
-msgid "Glade Interface Designer"
-msgstr "Файл програми Qt-дизайнер"
-
-#: C/anjuta-manual.xml:5(title)
-#, fuzzy
-msgid "Quick start"
-msgstr "Початкові маркери:"
-
-#: C/anjuta-manual.xml:10(para)
-msgid "You should have a project containing Glade file opened;"
+#. (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 ""
 
-#: C/anjuta-manual.xml:13(para)
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:38
 msgid ""
-"Unlike original Glade designer, Anjuta plugin uses double click for creating "
-"handlers for default signal. You can perform a click on widgets (e.g. switch "
-"current tab in a GtkNotebook) by keeping \"Windows\" or \"Super\" key "
-"pressed;"
+"You can select another directory in the bottom <gui>directory tree view</"
+"gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:19(para)
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:40
 msgid ""
-"Open <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Glade "
-"GUI Designer</guimenuitem></menuchoice> and check the three topmost flags "
-"<guilabel>Insert handler on edit</guilabel>, <guilabel>Separated designer "
-"layout</guilabel> and <guilabel>Automatically add resources</guilabel>;"
+"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 ""
 
-#: C/anjuta-manual.xml:28(para)
+#. (itstool) path: note/p
+#: C/project-manager-target-add.page:45
 msgid ""
-"Check <menuchoice><guimenuitem>View</guimenuitem><guimenuitem>Designer</"
-"guimenuitem></menuchoice> flag and move this window to a better place;"
+"Target names are typically restricted to letters, digits and the underscore, "
+"so it's safer to avoid other characters."
 msgstr ""
 
-#: C/anjuta-manual.xml:36(para)
+#. (itstool) path: item/p
+#: C/project-manager-target-add.page:50
 msgid ""
-"Switch to a Glade file in the design area and to the source code file that "
-"should contain callbacks for the Glade file, then press "
-"<menuchoice><guimenuitem>Glade</guimenuitem><guimenuitem>Associate last "
-"designer and editor</guimenuitem></menuchoice>;"
+"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 ""
 
-#: C/anjuta-manual.xml:42(para)
+#. (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 ""
-"Optionally select a target for image and other resources in the project "
-"manager and press <guilabel>Set as default resource target</guilabel> in the "
-"context menu."
+"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 ""
 
-#: C/anjuta-manual.xml:6(para)
+#. (itstool) path: item/p
+#: C/project-manager-target-remove.page:32
 msgid ""
-"If you don't want to read all this boring manual, here is few steps to get "
-"all things ready for use: <placeholder-1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:52(title)
-msgid "Glade general usage questions"
+#. (itstool) path: info/desc
+#: C/project-manager-treeview.page:8
+msgid "Display project's content."
 msgstr ""
 
-#: C/anjuta-manual.xml:53(para)
+#. (itstool) path: page/title
+#: C/project-manager-treeview.page:17
+msgid "View a Project"
+msgstr "Перегляд проєкту"
+
+#. (itstool) path: page/p
+#: C/project-manager-treeview.page:19
 msgid ""
-"Glade plugin mostly copies functionality of standalone Glade designer, but "
-"there are some special features. The four windows of the Glade desinger are "
-"design area, palette, widgets inspector and property editor. They have the "
-"same purpose as in the standalone designer, so please consult <ulink type="
-"\"help\" url=\"ghelp:glade\">Glade Interface Designer Manual</ulink> for "
-"their description. An extra functionality allows you to use infrastructure "
-"of Anjuta more effectively and is described here."
+"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 ""
 
-#: C/anjuta-manual.xml:66(title)
-#, fuzzy
-msgid "Editor and designer association"
-msgstr "Редактор та система керування веб-сторінками"
+#. (itstool) path: item/title
+#: C/project-manager-treeview.page:28
+msgid "Root"
+msgstr "Корінь"
 
-#: C/anjuta-manual.xml:67(para)
+#. (itstool) path: item/p
+#: C/project-manager-treeview.page:29
 msgid ""
-"You can associate text editor and Glade designer so you will easily switch "
-"between them and automatically insert handler stubs for newly entered "
-"handlers. You can associate more then one editor to a designer. The most "
-"recent editor or associated with the current toplevel widget will be used. "
-"There are two ways of associating editor and designer. The first way is "
-"using associations dialog. The second way is to choose designer and editor "
-"document in any order and then press <menuchoice><guimenuitem>Glade</"
-"guimenuitem><guimenuitem>Associate last designer and editor</guimenuitem></"
-"menuchoice> menu item."
+"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 ""
 
-#: C/anjuta-manual.xml:83(title)
-#, fuzzy
-msgid "Associations dialog"
-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 ""
 
-#: C/anjuta-manual.xml:94(guilabel)
-#, fuzzy
-msgid "Spec regexp"
-msgstr "Змінні регулярних виразів"
+#. (itstool) path: item/title
+#: C/project-manager-treeview.page:41
+msgid "Package"
+msgstr "Пакунок"
 
-#: C/anjuta-manual.xml:95(para)
+#. (itstool) path: item/p
+#: C/project-manager-treeview.page:42
 msgid ""
-"Shortened from \"special regular expression\". Used for defining a custom "
-"position for inserting stubs."
+"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 ""
 
-#: C/anjuta-manual.xml:101(guilabel)
-#, fuzzy
-msgid "Widget name"
-msgstr "Назва віджета"
+#. (itstool) path: item/title
+#: C/project-manager-treeview.page:47
+msgid "Folder"
+msgstr "Тека"
 
-#: C/anjuta-manual.xml:102(para)
-msgid "The name of the toplevel widget this assoctiation belongs to."
+#. (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 ""
 
-#: C/anjuta-manual.xml:107(guilabel)
-#, fuzzy
-msgid "Position type"
-msgstr "Тип DCC"
+#. (itstool) path: item/title
+#: C/project-manager-treeview.page:53
+msgid "Target"
+msgstr "Ціль"
 
-#: C/anjuta-manual.xml:108(para)
+#. (itstool) path: item/p
+#: C/project-manager-treeview.page:54
 msgid ""
-"Describes a position at which a handler stub will be inserted. "
-"<guilabel>After begin</guilabel> means after special mark (which may be "
-"entered in the <guilabel>Spec regexp</guilabel> entry) and <guilabel>before "
-"end</guilabel> means before special end mark. Default begin mark is /* "
-"window_name callbacks */ and default end mark is /* end of window_name "
-"callbacks */. window_name may be ommited."
+"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 ""
 
-#: C/anjuta-manual.xml:84(para)
+#. (itstool) path: note/p
+#: C/project-manager-treeview.page:61
 msgid ""
-"Allows you to create and manager associations. To create an association "
-"select designer and editor in the comboboxes and press <guibutton>Associate</"
-"guibutton>. You can also select the document by switching to it in document "
-"manager or windows list in the main menu. The list in the middle of the "
-"dialog shows existing associations. A couple of controls below are intended "
-"for editing association properties. Here is their description: <placeholder-"
-"1/>"
+"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 ""
 
-#: C/anjuta-manual.xml:122(title)
-#, fuzzy
-msgid "Default signal"
-msgstr "%s: невідомий сигнал %s\n"
+#. (itstool) path: item/title
+#: C/project-manager-treeview.page:68
+msgid "Source"
+msgstr "Джерело"
 
-#: C/anjuta-manual.xml:123(para)
+#. (itstool) path: item/p
+#: C/project-manager-treeview.page:69
 msgid ""
-"Double click on a widget in the design area will create a new handler for "
-"default signal using a predefined template for its naming. For example, the "
-"default signal is \"clicked\" for button, \"toggled\" for check box, etc. If "
-"<guilabel>Insert handler on edit</guilabel> option is enabled then a new "
-"handler stub will be inserted to the position which depends on "
-"<guilabel>Position type</guilabel> setting."
+"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 ""
 
-#: C/anjuta-manual.xml:134(title)
-#, fuzzy
-msgid "Inserting a stub"
-msgstr "Вставляється виноска..."
+#. (itstool) path: info/desc
+#: C/project-wizard-create.page:10
+msgid "Create a new project from scratch."
+msgstr "Створення проєкту «з нуля»."
+
+#. (itstool) path: page/title
+#: C/project-wizard-create.page:23
+msgid "Create a Project"
+msgstr "Створення проєкту"
 
-#: C/anjuta-manual.xml:135(para)
+#. (itstool) path: page/p
+#: C/project-wizard-create.page:25
 msgid ""
-"One of the most valuable goal of <application>Anjuta</application> and "
-"<application>Glade</application> integration is automatical creating of "
-"handler stubs, so you will not need to do a lot of routine work for that, it "
-"will be done automatically."
+"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 ""
 
-#: C/anjuta-manual.xml:144(para)
+#. (itstool) path: item/p
+#: C/project-wizard-create.page:32
 msgid ""
-"Automatically if <guilabel>Insert handler on edit</guilabel> option if "
-"enabled"
+"From the <gui>main menu</gui>, select <guiseq><gui>File</gui> <gui>New</"
+"gui><gui>Project</gui></guiseq>."
 msgstr ""
 
-#: C/anjuta-manual.xml:148(para)
+#. (itstool) path: item/p
+#: C/project-wizard-create.page:36
 msgid ""
-"Using <menuchoice><guimenuitem>Glade</guimenuitem><guimenuitem>Insert "
-"handler stub, autoposition</guimenuitem></menuchoice> in hte main menu"
+"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 ""
 
-#: C/anjuta-manual.xml:154(para)
+#. (itstool) path: item/p
+#: C/project-wizard-create.page:44
 msgid ""
-"Using <guilabel>Insert handler stub</guilabel> item in the context menu of "
-"text document"
+"Select the icon representing the type of the project you want to create and "
+"click on <gui>Forward</gui>."
 msgstr ""
 
-#: C/anjuta-manual.xml:141(para)
-msgid "There are several ways to create a stub: <placeholder-1/>"
+#. (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 ""
 
-#: C/anjuta-manual.xml:163(title) C/anjuta-manual.xml:3(title)
-#, fuzzy
-msgid "Preferences"
-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 ""
 
-#: C/anjuta-manual.xml:166(guilabel)
-#, fuzzy
-msgid "Insert handler on edit"
-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 ""
 
-#: C/anjuta-manual.xml:167(para)
+#. (itstool) path: note/p
+#: C/project-wizard-create.page:67
 msgid ""
-"Enables inserting a handler stub into the associated editor after entering a "
-"new handler into signal editor or creating a <link linkend=\"glade-default-"
-"signal\">default signal handler</link>"
+"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 ""
 
-#: C/anjuta-manual.xml:174(guilabel)
-#, fuzzy
-msgid "Separated designer layout"
-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 ""
 
-#: C/anjuta-manual.xml:175(para)
+#. (itstool) path: note/p
+#: C/project-wizard-create.page:85
 msgid ""
-"Detaches the design area from document manager so you can dock it separately "
-"from text editors."
+"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 ""
 
-#: C/anjuta-manual.xml:181(guilabel)
-#, fuzzy
-msgid "Automatically add resources"
-msgstr "автоматично додавати нові папки"
+#. (itstool) path: info/desc
+#: C/project-wizard-template.page:9
+msgid "Project wizard template."
+msgstr ""
 
-#: C/anjuta-manual.xml:182(para)
-msgid ""
-"When checked then all resources (e.g. images) will be added to the target in "
-"the current project. You can choose the target using project manager context "
-"menu or by entering target id in the entry below the check button."
+#. (itstool) path: page/title
+#: C/project-wizard-template.page:22
+msgid "Project wizard template"
 msgstr ""
 
-#: C/anjuta-manual.xml:190(guilabel)
-#, fuzzy
-msgid "Handler 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 ""
 
-#: C/anjuta-manual.xml:191(para)
+#. (itstool) path: page/p
+#: C/project-wizard-template.page:31
 msgid ""
-"You can choose between the two formats of automatic naming of signal handler."
+"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 ""
 
-#: C/anjuta-manual.xml:4(para)
+#. (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 ""
-"Preferences are ways to customize <application>Anjuta</application> to suit "
-"your tastes. Activate <menuchoice><guimenu>Edit</"
-"guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> to bring up the "
-"preferences dialog. Some preferences are explained below."
+"The <gui>run parameter</gui> dialog allows you to define the current program "
+"and several parameters."
 msgstr ""
 
-#: C/anjuta-manual.xml:9(title)
-#, fuzzy
-msgid "General"
-msgstr "Загальне"
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:27
+msgid "<gui>Program</gui>"
+msgstr "<gui>Програма</gui>"
 
-#: C/anjuta-manual.xml:11(para)
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:28
 msgid ""
-"<emphasis>Project Directory</emphasis> is the path where you plan to put all "
-"your projects. The application wizard creates new projects in this directory "
-"only. The default project directory is ~/Projects and generally this is fine "
-"for most people."
+"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 ""
 
-#: C/anjuta-manual.xml:17(para)
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:34
+msgid "<gui>Arguments</gui>"
+msgstr "<gui>Аргументи</gui>"
+
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:35
 msgid ""
-"<emphasis>User Info:</emphasis> Provide your name and email address here. "
-"These are not used to do software registration; rather, they are used to "
-"create ChangeLog entries and other text insertions."
+"These are the command line arguments used by your program. The drop-down "
+"list keeps an history of the last arguments used."
 msgstr ""
 
-#: C/anjuta-manual.xml:24(title)
-#, fuzzy
-msgid "File Manager"
-msgstr "Керування файлами"
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:40
+msgid "<gui>Working Directory</gui>"
+msgstr "<gui>Робочий каталог</gui>"
 
-#: C/anjuta-manual.xml:26(para)
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:41
 msgid ""
-"<emphasis>Root directory if no project is open</emphasis> is the path where "
-"the root of the file manager points if no project is currently open."
+"The working directory is the current directory when your program will be run."
 msgstr ""
 
-#: C/anjuta-manual.xml:31(para)
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:45
+msgid "<gui>Environment Variables</gui>"
+msgstr "<gui>Змінні середовища</gui>"
+
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:46
 msgid ""
-"<emphasis>File Filter:</emphasis> You can filter out some files 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."
+"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 ""
 
-#: C/anjuta-manual.xml:3(title)
-#, fuzzy
-msgid "User-defined Tools"
+#. (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 ""
-"Визначені користувачем команди:\n"
-"\n"
-"  "
 
-#: C/anjuta-manual.xml:7(para)
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:52
 msgid ""
-"You'll sometimes find the built-in 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."
+"You can click on the <gui>Edit</gui> button to change the value of the "
+"selected environment variable."
 msgstr ""
 
-#: C/anjuta-manual.xml:16(para)
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:54
 msgid ""
-"Anjuta provides a powerful framework for defining user-defined tools for "
-"extending its 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."
+"You can click on the <gui>Delete</gui> button to remove the selected "
+"environment variable."
 msgstr ""
 
-#: C/anjuta-manual.xml:24(para)
-msgid "The tools plugin has to be enabled to use this feature!"
+#. (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 ""
 
-#: C/anjuta-manual.xml:31(title)
-#, fuzzy
-msgid "Tools Examples"
-msgstr "/Сервіс/С_татус"
+#. (itstool) path: item/title
+#: C/run-parameters-dialog.page:60
+msgid "<gui>Run in Terminal</gui>"
+msgstr "<gui>Запустити у терміналі</gui>"
 
-#: C/anjuta-manual.xml:32(para)
+#. (itstool) path: item/p
+#: C/run-parameters-dialog.page:61
 msgid ""
-"This is a simple example how to use the tools plugin to integrate the GNOME "
-"ChangeLog generation script."
+"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 ""
 
-#: C/anjuta-manual.xml:38(title) C/anjuta-manual.xml:40(screeninfo)
-#, fuzzy
-msgid "The tool editor"
-msgstr "Редактор _XML..."
+#. (itstool) path: info/desc
+#: C/run-run.page:11
+msgid "Start a program without the debugger."
+msgstr "Запуск програми без засобу діагностики."
 
-#: C/anjuta-manual.xml:2(title)
-#, fuzzy
-msgid "Authors"
-msgstr "Автори"
+#. (itstool) path: page/title
+#: C/run-run.page:24
+msgid "Run a program"
+msgstr "Запустити програму"
 
-#: C/anjuta-manual.xml:3(para)
+#. (itstool) path: page/p
+#: C/run-run.page:26
 msgid ""
-"The <application>Anjuta</application> project was founded by Naba Kumar. "
-"<ulink type=\"http\" url=\"http://anjuta.org/credits\";>This page</ulink> "
-"lists all Anjuta contributors."
+"If <app>Anjuta</app> is used to start a program it checks that it is up to "
+"date and builds it if needed."
 msgstr ""
 
-#: C/anjuta-manual.xml:9(para)
+#. (itstool) path: item/p
+#: C/run-run.page:31
 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>."
+"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 ""
 
-#: C/anjuta-manual.xml:17(para)
+#. (itstool) path: page/p
+#: C/run-run.page:37
 msgid ""
-"This manual was written by Naba Kumar, Andy Piper, Biswapesh Chattopadhyay "
-"and Johannes Schmid. Please send all comments and suggestions regarding this "
-"manual to the Anjuta Devel list <email>anjuta-devel list sourceforge net</"
-"email>. Comments may also be submitted via the project trackers at "
-"SourceForge."
+"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 ""
 
-#: C/anjuta-manual.xml:2(title)
-#, fuzzy
-msgid "License"
-msgstr "Ліцензія"
-
-#: C/anjuta-manual.xml:3(para)
-#, fuzzy
+#. (itstool) path: item/p
+#: C/run-run.page:42
 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."
+"From the <gui>main menu</gui>, select <guiseq><gui>Run</gui> <gui>Program "
+"Parameters...</gui></guiseq> to display the dialog."
 msgstr ""
-"Ця програма є вільним програмним забезпеченням; ви можете розповсюджувати її "
-"ат/чи змінювати на умовах ліцензії <ulink type=\"help\" url=\"gnome-help:gpl"
-"\"><citetitle>GNU General Public License</citetitle></ulink> яка "
-"опублікована Free Software Foundation; версії 2 цієї ліцензії, або (за вашим "
-"бажанням) будь-якої більш пізньої версії."
 
-#: C/anjuta-manual.xml:10(para)
-#, fuzzy
+#. (itstool) path: note/p
+#: C/run-run.page:49
 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."
+"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 ""
-"Ця програма поширюється з надією, що буде корисною, але БЕЗ БУДЬ_ЯКИХ "
-"ГАРАНТІЙ; навіть без неявної гарантії ПРИДАТНОСТІ ДО ПРОДАЖУ або "
-"ВІДПОВІДНОСТІ ПЕВНІЙ МЕТІ. Докладніше про це дивіться у <citetitle>GNU "
-"General Public License</citetitle>."
 
-#: C/anjuta-manual.xml:16(para)
-msgid ""
-"A copy of the <citetitle>GNU General Public License</citetitle> is included "
-"as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also "
-"obtain a copy of the <citetitle>GNU General Public License</citetitle> from "
-"the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://";
-"www.fsf.org\"> their Web site</ulink> or by writing to <address> Free "
-"Software Foundation, Inc. <street>51 Franklin Street</street> Fifth Floor "
-"<city>Boston</city>, <state>MA</state><postcode>02110-1301</"
-"postcode><country>USA</country></address>"
+#. (itstool) path: info/desc
+#: C/widget-index.page:8
+msgid "All windows and dialogs."
 msgstr ""
 
-#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: C/anjuta-manual.xml:0(None)
-#, fuzzy
-msgid "translator-credits"
-msgstr ""
-"Юрій Сирота <rasta cvs gnome org>\n"
-"Максим Дзюманенко <mvd mylinux com ua>"
+#. (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]