[anjuta/gnome-2-26] Added Ukrainian translation
- From: Maxim V. Dziumanenko <mdziumanenko src gnome org>
- To: svn-commits-list gnome org
- Subject: [anjuta/gnome-2-26] Added Ukrainian translation
- Date: Fri, 29 May 2009 10:50:41 -0400 (EDT)
commit 1a8d144f0adb62ebb5ad1f5e49551c95da72cc9b
Author: Maxim V. Dziumanenko <dziumanenko gmail com>
Date: Fri May 29 17:52:18 2009 +0300
Added Ukrainian translation
---
manuals/anjuta-manual/Makefile.am | 2 +-
manuals/anjuta-manual/uk/uk.po | 4147 +++++++++++++++++++++++++++++++++++++
2 files changed, 4148 insertions(+), 1 deletions(-)
diff --git a/manuals/anjuta-manual/Makefile.am b/manuals/anjuta-manual/Makefile.am
index 58af2a3..1393d8d 100644
--- a/manuals/anjuta-manual/Makefile.am
+++ b/manuals/anjuta-manual/Makefile.am
@@ -49,4 +49,4 @@ DOC_FIGURES = figures/add_edit_macro.png \
figures/stack.png\
figures/symbol_browser.png\
figures/tool-editor.png
-DOC_LINGUAS = de el es eu oc sv
+DOC_LINGUAS = de el es eu oc sv uk
diff --git a/manuals/anjuta-manual/uk/uk.po b/manuals/anjuta-manual/uk/uk.po
new file mode 100644
index 0000000..73f2e03
--- /dev/null
+++ b/manuals/anjuta-manual/uk/uk.po
@@ -0,0 +1,4147 @@
+# 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.
+#
+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"
+"Language-Team: Ukrainian <uk li org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: C/anjuta-manual.xml:27(title)
+msgid "Anjuta IDE Manual"
+msgstr "Ð?оÑ?Ñ?бник коÑ?иÑ?Ñ?Ñ?ваÑ?а Anjuta IDE"
+
+#: C/anjuta-manual.xml:28(edition)
+msgid "v1.0.0"
+msgstr "v1.0.0"
+
+#: C/anjuta-manual.xml:30(para)
+msgid "Manual for the Anjuta IDE"
+msgstr "Ð?овÑ?дка з пÑ?огÑ?ами Anjuta IDE"
+
+#: C/anjuta-manual.xml:34(firstname)
+msgid "Naba"
+msgstr "Naba"
+
+#: C/anjuta-manual.xml:35(surname)
+msgid "Kumar"
+msgstr "Kumar"
+
+#: C/anjuta-manual.xml:38(firstname)
+msgid "Andy"
+msgstr "Andy"
+
+#: C/anjuta-manual.xml:39(surname)
+msgid "Piper"
+msgstr "Piper"
+
+#: C/anjuta-manual.xml:42(firstname)
+msgid "Biswapesh"
+msgstr "Biswapesh"
+
+#: C/anjuta-manual.xml:43(surname)
+msgid "Chattopadhyayr"
+msgstr "Chattopadhyayr"
+
+#: C/anjuta-manual.xml:46(firstname)
+msgid "Johannes"
+msgstr "Johannes"
+
+#: C/anjuta-manual.xml:47(surname)
+msgid "Schmid"
+msgstr "Schmid"
+
+#: C/anjuta-manual.xml:51(year)
+msgid "2001-2002"
+msgstr "2001-2002"
+
+#: C/anjuta-manual.xml:52(year)
+msgid "2006-2008"
+msgstr "2006-2008"
+
+#: C/anjuta-manual.xml:53(holder)
+msgid "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
+msgstr "Naba Kumar, Andy Piper, Biswapesh Chattopadhyay"
+
+#: C/anjuta-manual.xml:54(holder)
+msgid "Johannes Schmid"
+msgstr "Johannes Schmid"
+
+#: 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 "Ð?Ñ?Ñ?Ñ?п"
+
+#: C/anjuta-manual.xml:4(para)
+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."
+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)
+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 ""
+
+#: 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)
+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 "Ð?пеÑ?аÑ?Ñ?Ñ? з Ñ?айлами"
+
+#: C/anjuta-manual.xml:6(title)
+msgid "Creating a new file and inserting text"
+msgstr "СÑ?воÑ?еннÑ? нового Ñ?айлÑ? Ñ?а вÑ?Ñ?авка Ñ?екÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:8(title)
+msgid "Creating a New File"
+msgstr "СÑ?воÑ?еннÑ? нового Ñ?айлÑ?"
+
+#: C/anjuta-manual.xml:9(para)
+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."
+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)
+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/>"
+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)
+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."
+msgstr ""
+"Ð?оÑ?Ñ?Ñ?пнÑ? два Ñ?ипи макÑ?оÑ?Ñ?в: макÑ?оÑ?и Anjuta Ñ?а макÑ?оÑ?и Ñ?Ñ?воÑ?енÑ? коÑ?иÑ?Ñ?Ñ?ваÑ?ем (показÑ?Ñ?Ñ?Ñ?Ñ?Ñ? Ñ?к "
+"\"Ð?оÑ? макÑ?оÑ?и\"). Ð?акÑ?оÑ?и Anjuta незмÑ?ннÑ?, але ви можеÑ?е визнаÑ?иÑ?и Ñ?а змÑ?нÑ?ваÑ?и влаÑ?нÑ? макÑ?оÑ?и."
+
+#: C/anjuta-manual.xml:69(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:82(title)
+#, fuzzy
+msgid "Macro"
+msgstr "Ð?акÑ?о"
+
+#: C/anjuta-manual.xml:84(screeninfo)
+#, fuzzy
+msgid "The Macro dialog"
+msgstr "Ð?Ñ?дкÑ?иÑ?Ñ?Ñ? Ñ?едакÑ?оÑ?а дÑ?алоговиÑ? вÑ?кон"
+
+#: C/anjuta-manual.xml:77(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:91(title)
+#, fuzzy
+msgid "Defining Macros"
+msgstr "Ð?алаÑ?Ñ?овÑ?ваннÑ? макÑ?оÑ?Ñ?в"
+
+#: C/anjuta-manual.xml:92(para)
+msgid ""
+"From the Insert Macro window, choose <guibutton>Add</guibutton> or select "
+"<menuchoice><guisubmenu>Edit</guisubmenu><guisubmenu>Macros</"
+"guisubmenu><guimenuitem>Add Macro... </guimenuitem></menuchoice>. The Add/"
+"Edit window appears. Enter the macro name, choose or define a category and "
+"enter a shortcut. Then edit text relative to your macro. The character ' | ' "
+"will indicate the cursor position after the macro insertion. Choose "
+"<guibutton>OK</guibutton>. The macro is added to the list."
+msgstr ""
+
+#: C/anjuta-manual.xml:100(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:108(title)
+#, fuzzy
+msgid "Add/Edit Macro"
+msgstr "Ð?одаÑ?и новий макÑ?оÑ?"
+
+#: C/anjuta-manual.xml:110(screeninfo)
+#, fuzzy
+msgid "Add Edit dialog"
+msgstr "Ð?Ñ?кно додаваннÑ? Ñ?айлÑ?в"
+
+#: C/anjuta-manual.xml:104(para)
+msgid ""
+"Similarly, you can edit and modify a macro by selecting it in the list and "
+"choosing <guibutton>Edit</guibutton>. <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:117(title)
+#, fuzzy
+msgid "Macro Keywords"
+msgstr "Ð?емаÑ? клÑ?Ñ?овиÑ? Ñ?лÑ?в."
+
+#: C/anjuta-manual.xml:118(para)
+msgid ""
+"Macro keywords are available. They can be included in macro definitions. "
+"These macro keywords start and finish with the character ' @ '."
+msgstr ""
+
+#: C/anjuta-manual.xml:126(title)
+#, fuzzy
+msgid "Keyword Macro"
+msgstr "'MACRO EXPR'"
+
+#: C/anjuta-manual.xml:128(screeninfo)
+#, fuzzy
+msgid "The Keyword macro"
+msgstr "'MACRO EXPR'"
+
+#: C/anjuta-manual.xml:122(para)
+msgid ""
+"Available macro keywords are @DATE_TIME@, @DATE_YMD@, @DATE_Y@, @USER_NAME@, "
+"@FILE_NAME@, @FILE_NAME_UP@, @FILE_NAME_UP_PREFIX@, @EMAIL@, @TABSIZE@, "
+"@INDENTSIZE@, and @USETABS <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:139(title)
+#, fuzzy
+msgid "Opening and Saving Files"
+msgstr "СÑ?воÑ?еннÑ? Ñ?а видаленнÑ? Ñ?айлÑ?в"
+
+#: C/anjuta-manual.xml:151(title)
+#, fuzzy
+msgid "Open File dialog"
+msgstr "_Ð?Ñ?алог вÑ?дкÑ?иваннÑ? Ñ?айлÑ?"
+
+#: C/anjuta-manual.xml:143(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:166(title)
+#, fuzzy
+msgid "Open Multiple File dialog"
+msgstr "Ð?аголовок дÑ?алогового вÑ?кна вибоÑ?Ñ? Ñ?айла."
+
+#: C/anjuta-manual.xml:168(screeninfo)
+msgid "The Open File dialog in multiple-select mode"
+msgstr ""
+
+#: C/anjuta-manual.xml:173(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:194(screeninfo)
+#, fuzzy
+msgid "The Save As File"
+msgstr "Ð?беÑ?егÑ?и Ñ?к %s Ñ?айл:"
+
+#: C/anjuta-manual.xml:184(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:199(title)
+#, fuzzy
+msgid "File autosave"
+msgstr "Ð?вÑ?омаÑ?иÑ?но збеÑ?ежений Ñ?айл новÑ?Ñ?ий."
+
+#: C/anjuta-manual.xml:200(para)
+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>"
+msgstr ""
+
+#: C/anjuta-manual.xml:211(para)
+msgid ""
+"<emphasis>Saving a file with a different name:</emphasis> You can explicitly "
+"save a file with a new filename. To do this, choose "
+"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Save As</guimenuitem></"
+"menuchoice> from the 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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:219(title)
+#, fuzzy
+msgid "File save as overwrite"
+msgstr "Ð?апиÑ?аÑ?и Ñ?айл Ñ?к:"
+
+#: C/anjuta-manual.xml:220(para)
+msgid ""
+"When you use <guimenuitem>Save As</guimenuitem> with an existing file, the "
+"original is not deleted. It is left unchanged since the last save. If a file "
+"with the new filename already exists, a confirmation dialog will appear to "
+"ensure that you want to overwrite it. Clicking <guibutton>Yes</guibutton> "
+"will overwrite the file with the file you are saving."
+msgstr ""
+
+#: C/anjuta-manual.xml:232(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:249(title)
+#, fuzzy
+msgid "Editing Files"
+msgstr "РедагÑ?ваннÑ? PO-Ñ?айлÑ?в"
+
+#: C/anjuta-manual.xml:250(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:256(title) C/anjuta-manual.xml:265(title)
+#, fuzzy
+msgid "Editor Margins"
+msgstr "Ð?олÑ? Ñ?Ñ?оÑ?Ñ?нки"
+
+#: C/anjuta-manual.xml:267(screeninfo) C/anjuta-manual.xml:315(screeninfo)
+#, fuzzy
+msgid "The Tags toolbar"
+msgstr "select_toolbar|X"
+
+#: C/anjuta-manual.xml:257(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:272(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:281(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:294(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:302(title)
+#, fuzzy
+msgid "Invisible margin marker"
+msgstr "Ð?енÑ? видаленнÑ? маÑ?кеÑ?а"
+
+#: C/anjuta-manual.xml:313(title)
+msgid "Editor markers when the marker margin is invisible"
+msgstr ""
+
+#: C/anjuta-manual.xml:303(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:323(title)
+#, fuzzy
+msgid "Editor Guides"
+msgstr "Ð?оказÑ?ваÑ?и напÑ?Ñ?мнÑ?"
+
+#: C/anjuta-manual.xml:324(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:333(title) C/anjuta-manual.xml:335(screeninfo)
+#, fuzzy
+msgid "Editor with guides"
+msgstr "Ð?Ñ? вмонÑ?ованим Ñ?едакÑ?оÑ?ом\n"
+
+#: C/anjuta-manual.xml:341(title)
+#, fuzzy
+msgid "Syntax highlighting"
+msgstr "Ð?Ñ?дÑ?вÑ?Ñ?еннÑ? Ñ?инÑ?акÑ?иÑ?Ñ?"
+
+#: C/anjuta-manual.xml:342(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:352(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:365(title)
+#, fuzzy
+msgid "Code folding"
+msgstr "Ð?ез згоÑ?Ñ?аннÑ?"
+
+#: C/anjuta-manual.xml:366(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:374(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:380(para)
+msgid ""
+"Please note that code folding and editor guides are only available in the "
+"Scintilla-based editor."
+msgstr ""
+
+#: C/anjuta-manual.xml:387(title)
+#, fuzzy
+msgid "Auto-formatting source code"
+msgstr "Ð?иÑ?Ñ?дний код на мовÑ? Emacs Lisp"
+
+#: C/anjuta-manual.xml:388(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:401(title)
+#, fuzzy
+msgid "The Symbol Browser"
+msgstr "<b>Ð?овнÑ?Ñ?нÑ?й пеÑ?еглÑ?даÑ? 1</b>"
+
+#: C/anjuta-manual.xml:402(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:415(title) C/anjuta-manual.xml:417(screeninfo)
+#, fuzzy
+msgid "Symbol browser"
+msgstr "<b>Ð?овнÑ?Ñ?нÑ?й пеÑ?еглÑ?даÑ? 1</b>"
+
+#: C/anjuta-manual.xml:407(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:423(title)
+#, fuzzy
+msgid "Tag synchronization"
+msgstr "СинÑ?Ñ?онÑ?заÑ?Ñ?Ñ? завеÑ?Ñ?ено"
+
+#: C/anjuta-manual.xml:424(para)
+msgid ""
+"You don't have to worry about the synchronization and update of the tag "
+"database. <application>Anjuta</application> will take care of everything. "
+"You just have to decide which tag you want to go to!"
+msgstr ""
+
+#: C/anjuta-manual.xml:435(title)
+msgid "Searching for and Replacing text in files"
+msgstr ""
+
+#: C/anjuta-manual.xml:437(title)
+#, fuzzy
+msgid "Searching"
+msgstr "Ð?оÑ?Ñ?к"
+
+#: C/anjuta-manual.xml:438(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:445(para)
+msgid ""
+"Use the text box to specify the string to search for, and select whether it "
+"is a normal string or a regular expression. 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."
+msgstr ""
+
+#: C/anjuta-manual.xml:451(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:456(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:465(title)
+#, fuzzy
+msgid "Search Text dialog"
+msgstr "Ð?Ñ?Ñ?ановиÑ?и Ñ?екÑ?Ñ? дÑ?алогового вÑ?кна"
+
+#: C/anjuta-manual.xml:470(para)
+msgid "To stop a long search, press the <guibutton>Stop</guibutton> button."
+msgstr ""
+
+#: C/anjuta-manual.xml:475(title)
+#, fuzzy
+msgid "Specifying Search Range"
+msgstr "Ð?Ñ?апазон поÑ?Ñ?кÑ? непÑ?авилÑ?ний."
+
+#: C/anjuta-manual.xml:476(para)
+msgid ""
+"In the <interface>Search Target</interface> tab, define the search location "
+"and the action to be performed if the search succeeds."
+msgstr ""
+
+#: C/anjuta-manual.xml:480(para)
+msgid "You can define the maximum number of actions to be performed."
+msgstr ""
+
+#: C/anjuta-manual.xml:484(title)
+#, fuzzy
+msgid "Search Target dialog"
+msgstr "Ð?Ñ?дкÑ?иÑ?и дÑ?алог поÑ?Ñ?кÑ?"
+
+#: C/anjuta-manual.xml:489(para)
+msgid "You can select which text will be searched."
+msgstr ""
+
+#: C/anjuta-manual.xml:493(title)
+#, fuzzy
+msgid "Search Target In choice"
+msgstr "ШÑ?каÑ?и Ñ? поÑ?оÑ?номÑ? _Ñ?аÑ?Ñ?"
+
+#: C/anjuta-manual.xml:499(title)
+#, fuzzy
+msgid "Searching in Files"
+msgstr "СÑ?воÑ?еннÑ? пеÑ?елÑ?кÑ? Ñ?айлÑ?в Ñ? '%s'..."
+
+#: C/anjuta-manual.xml:500(para)
+msgid ""
+"To find text in your project, set <guilabel>Search In</guilabel> to All "
+"Project Files."
+msgstr ""
+
+#: C/anjuta-manual.xml:504(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:509(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:515(title)
+#, fuzzy
+msgid "Search File Pattern"
+msgstr " [-E | -F] [-e @var{Ñ?аблон} | -f @var{Ñ?айл}]...\n"
+
+#: C/anjuta-manual.xml:525(title)
+#, fuzzy
+msgid "Specifying a Search Action"
+msgstr "СкаÑ?Ñ?ваÑ?и оÑ?Ñ?аннÑ? опеÑ?аÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:526(para)
+msgid "You can select which action will be performed when a search succeeds."
+msgstr ""
+
+#: C/anjuta-manual.xml:529(para)
+msgid ""
+"Depending on the previous selections (<guilabel>Search In</guilabel>, "
+"<guilabel>Search Direction</guilabel> , and so on), some actions may be "
+"unavailable."
+msgstr ""
+
+#: C/anjuta-manual.xml:535(title)
+msgid "Search Target Action choice"
+msgstr ""
+
+#: C/anjuta-manual.xml:543(title) C/anjuta-manual.xml:551(title)
+#, fuzzy
+msgid "Replacing"
+msgstr "Ð?оÑ?Ñ?Ñ?бна замÑ?на"
+
+#: C/anjuta-manual.xml:544(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:556(para)
+msgid ""
+"Choose <guibutton>Replace</guibutton> to replace the matched text or "
+"<guibutton>Forward</guibutton> to jump to the next matched text."
+msgstr ""
+
+#: C/anjuta-manual.xml:563(title)
+#, fuzzy
+msgid "Search Setting"
+msgstr "Ð?алаÑ?Ñ?овÑ?ваннÑ? вÑ?Ñ?Ñ?Ñ?алÑ?ноÑ? Ñ?еки: %s"
+
+#: C/anjuta-manual.xml:564(para)
+msgid "You may also save search options."
+msgstr ""
+
+#: C/anjuta-manual.xml:567(para)
+msgid ""
+"The item highlighted in red is the active item. The default item specifies "
+"search settings which are loaded when Anjuta launches."
+msgstr ""
+
+#: C/anjuta-manual.xml:572(title)
+#, fuzzy
+msgid "Search Setting dialog"
+msgstr "Ð?Ñ?дкÑ?иÑ?и дÑ?алог поÑ?Ñ?кÑ?"
+
+#: C/anjuta-manual.xml:583(title)
+#, fuzzy
+msgid "Printing a file"
+msgstr "Ð?Ñ?Ñ?к Ñ?пиÑ?кÑ? Ñ?айлÑ?в, Ñ?кÑ? видалÑ?Ñ?Ñ?Ñ?Ñ?Ñ?."
+
+#: C/anjuta-manual.xml:592(title)
+#, fuzzy
+msgid "Print preview of a C file"
+msgstr "Ð?опеÑ?еднÑ?й виглÑ?д: Ð?еÑ?ейменÑ?ваннÑ? Ñ?айла..."
+
+#: C/anjuta-manual.xml:594(screeninfo)
+#, fuzzy
+msgid "Print preview"
+msgstr "Ð?опеÑ?еднÑ?й пеÑ?еглÑ?д дÑ?Ñ?кÑ?"
+
+#: C/anjuta-manual.xml:584(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:601(title)
+#, fuzzy
+msgid "Print Preferences"
+msgstr "X-Chat: Ð?аÑ?Ñ?Ñ?ойки"
+
+#: C/anjuta-manual.xml:603(screeninfo)
+#, fuzzy
+msgid "Print preferences"
+msgstr "X-Chat: Ð?аÑ?Ñ?Ñ?ойки"
+
+#: C/anjuta-manual.xml:608(para)
+msgid ""
+"When you are ready to print and satisfied with the preview, select "
+"<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print</guimenuitem></"
+"menuchoice> or <guibutton>Print</guibutton> from the print preview window. "
+"This will bring up the actual print dialog as shown below. Select the "
+"appropriate print parameters and press <guibutton>Print</guibutton> to print "
+"the file."
+msgstr ""
+
+#: C/anjuta-manual.xml:615(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:622(title) C/anjuta-manual.xml:624(screeninfo)
+#, fuzzy
+msgid "Print Dialog"
+msgstr "Ð?Ñ?алог дÑ?Ñ?кÑ? Ñ?еÑ?едовиÑ?а GNOME"
+
+#: C/anjuta-manual.xml:3(title)
+#, fuzzy
+msgid "Project Management"
+msgstr "Ð?еÑ?Ñ?ваннÑ? пÑ?оекÑ?ами"
+
+#: C/anjuta-manual.xml:5(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:13(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:26(title)
+#, fuzzy
+msgid "Creating a New Project"
+msgstr "СÑ?воÑ?еннÑ? нового пÑ?оекÑ?Ñ? вÑ?део-DVD."
+
+#: C/anjuta-manual.xml:28(title)
+#, fuzzy
+msgid "Creating a project from a template"
+msgstr "СÑ?воÑ?иÑ?и пÑ?авило на оÑ?новÑ? Ñ?аблона"
+
+#: C/anjuta-manual.xml:29(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:41(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:48(para)
+msgid ""
+"Select the type of application you want to create in the second page. Click "
+"on <guibutton>Next</guibutton> to proceed."
+msgstr ""
+
+#: C/anjuta-manual.xml:54(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:65(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:81(para)
+msgid ""
+"The final step is to verify the information you have just supplied. Click on "
+"<guibutton>Finish</guibutton> to start generating the project."
+msgstr ""
+
+#: C/anjuta-manual.xml:86(para)
+msgid ""
+"Once the project has been generated, you can try it out by building it and "
+"executing it."
+msgstr ""
+
+#: C/anjuta-manual.xml:92(title)
+#, fuzzy
+msgid "Importing Projects"
+msgstr "*.k3b|Ð?Ñ?оекÑ?и K3b"
+
+#: C/anjuta-manual.xml:93(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:103(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:113(title)
+#, fuzzy
+msgid "Loading and Saving Projects"
+msgstr "Ð?еÑ?еÑ?воÑ?еннÑ? Ñ?а заванÑ?аженнÑ? гÑ?аÑ?Ñ?ки"
+
+#: C/anjuta-manual.xml:115(title)
+#, fuzzy
+msgid "Loading Projects"
+msgstr "*.k3b|Ð?Ñ?оекÑ?и K3b"
+
+#: C/anjuta-manual.xml:116(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:123(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:128(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:137(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:143(title)
+#, fuzzy
+msgid "Saving Projects"
+msgstr "*.k3b|Ð?Ñ?оекÑ?и K3b"
+
+#: C/anjuta-manual.xml:144(para)
+msgid ""
+"The project is automatically saved when you close because all changes are "
+"made directly in the project structure."
+msgstr ""
+
+#: C/anjuta-manual.xml:152(title)
+#, fuzzy
+msgid "Project structure"
+msgstr "СÑ?Ñ?Ñ?кÑ?Ñ?Ñ?а вмÑ?Ñ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:158(title)
+#, fuzzy
+msgid "Project window"
+msgstr "РозмÑ?Ñ?Ñ?иÑ?и пÑ?оекÑ? Ñ? вÑ?кнÑ?"
+
+#: C/anjuta-manual.xml:160(screeninfo)
+#, fuzzy
+msgid "The Project window"
+msgstr "РозмÑ?Ñ?Ñ?иÑ?и пÑ?оекÑ? Ñ? вÑ?кнÑ?"
+
+#: C/anjuta-manual.xml:153(para)
+msgid ""
+"Here is the <interface>Project window</interface> with its context menu "
+"(accessible by clicking on the right mouse button). <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:165(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:185(para)
+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 \"/\"."
+msgstr ""
+
+#: C/anjuta-manual.xml:193(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:204(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:214(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:221(para)
+msgid ""
+"Just like the file manager, the project manager view also has convenience "
+"actions (accessible from the context menu) for source files and targets."
+msgstr ""
+
+#: C/anjuta-manual.xml:227(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:235(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:244(title)
+#, fuzzy
+msgid "Groups and targets"
+msgstr "Ð?оÑ?иÑ?Ñ?Ñ?ваÑ?Ñ? Ñ?а гÑ?Ñ?пи"
+
+#: C/anjuta-manual.xml:247(title)
+#, fuzzy
+msgid "Adding Groups"
+msgstr "додаваннÑ? гÑ?Ñ?п"
+
+#: C/anjuta-manual.xml:252(para)
+msgid ""
+"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Group</"
+"guimenuitem></menuchoice> and a dialog to add a new group will pop up."
+msgstr ""
+
+#: C/anjuta-manual.xml:259(para)
+msgid "Select the group under which to add the new group."
+msgstr ""
+
+#: C/anjuta-manual.xml:262(para)
+msgid "Enter the name of the new group and click <guibutton>Add</guibutton>."
+msgstr ""
+
+#: C/anjuta-manual.xml:248(para)
+msgid ""
+"To add a new group (which is a directory in automake-based projects): "
+"<placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:266(para)
+msgid ""
+"With automake projects, a new directory with the given name will be created "
+"under the parent group's directory."
+msgstr ""
+
+#: C/anjuta-manual.xml:271(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:279(title)
+#, fuzzy
+msgid "Removing Groups"
+msgstr "Ð?Ñ?дгоÑ?овка до видаленнÑ? гÑ?Ñ?п"
+
+#: C/anjuta-manual.xml:284(para)
+msgid ""
+"Right-click the group in the <interface>Project Manager</interface> view."
+msgstr ""
+
+#: C/anjuta-manual.xml:287(para) C/anjuta-manual.xml:426(para)
+msgid "Select <guimenuitem>Remove</guimenuitem> from the context menu."
+msgstr ""
+
+#: C/anjuta-manual.xml:280(para)
+#, fuzzy
+msgid "To remove a group: <placeholder-1/>"
+msgstr "Ð?е можна видалиÑ?и нÑ?лÑ?овÑ? гÑ?Ñ?пÑ?"
+
+#: C/anjuta-manual.xml:292(para)
+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.)"
+msgstr ""
+
+#: C/anjuta-manual.xml:300(title)
+#, fuzzy
+msgid "Adding Targets"
+msgstr "СпеÑ?Ñ?алÑ?нÑ? Ñ?Ñ?лÑ?"
+
+#: C/anjuta-manual.xml:305(para)
+msgid ""
+"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Add Target</"
+"guimenuitem></menuchoice> and a dialog to add a new target will popup."
+msgstr ""
+
+#: C/anjuta-manual.xml:310(para)
+msgid "Select the group under which to add the target."
+msgstr ""
+
+#: C/anjuta-manual.xml:313(para)
+#, fuzzy
+msgid "Select the target type."
+msgstr "/Ð?идÑ?леннÑ?/Того ж Ñ?ипÑ?"
+
+#: C/anjuta-manual.xml:316(para)
+msgid "Enter a name for the new target and click <guibutton>Add</guibutton>."
+msgstr ""
+
+#: C/anjuta-manual.xml:301(para)
+#, fuzzy
+msgid "To add a new target: <placeholder-1/>"
+msgstr "Ð?аÑ?иÑ?нÑ?Ñ?Ñ? кнопкÑ? длÑ? додаваннÑ? новоÑ? палÑ?Ñ?Ñ?и"
+
+#: C/anjuta-manual.xml:320(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:326(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:335(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:344(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:353(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:362(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:369(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:377(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:385(para)
+msgid ""
+"The <emphasis>Scripts</emphasis> target type is for grouping scripts. They "
+"will be installed in the standard executable directory."
+msgstr ""
+
+#: C/anjuta-manual.xml:391(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:398(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:408(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:331(para)
+msgid ""
+"There are several target types for automake projects. They are: <placeholder-"
+"1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:418(title)
+#, fuzzy
+msgid "Removing Targets"
+msgstr "СпеÑ?Ñ?алÑ?нÑ? Ñ?Ñ?лÑ?"
+
+#: C/anjuta-manual.xml:423(para)
+msgid ""
+"Right-click the target in the <interface>Project Manager</interface> view."
+msgstr ""
+
+#: C/anjuta-manual.xml:419(para)
+#, fuzzy
+msgid "To remove a target: <placeholder-1/>"
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:440(title)
+#, fuzzy
+msgid "Adding and Removing Files"
+msgstr "Ð?идаленнÑ? Ñ?айлÑ?в Ñ?з диÑ?ка."
+
+#: C/anjuta-manual.xml:442(title)
+#, fuzzy
+msgid "Adding Source Files"
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:459(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:472(title)
+#, fuzzy
+msgid "Removing Source Files"
+msgstr "РобиÑ?и Ñ?езеÑ?внÑ? копÑ?Ñ?"
+
+#: C/anjuta-manual.xml:473(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:478(para)
+msgid ""
+"A confirmation dialog will appear, and the file will be removed from the "
+"project."
+msgstr ""
+
+#: C/anjuta-manual.xml:483(title)
+#, fuzzy
+msgid "The file is not deleted!"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:495(title)
+#, fuzzy
+msgid "Project Configuration"
+msgstr "Ð?онÑ?Ñ?гÑ?Ñ?аÑ?Ñ?Ñ? GTK"
+
+#: 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."
+msgstr ""
+
+#: C/anjuta-manual.xml:502(para)
+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."
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:531(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:539(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:511(para)
+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/>"
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:573(para)
+msgid ""
+"Create more configure variables in the <guibutton>Variables</guibutton> page "
+"to use in group and target properties."
+msgstr ""
+
+#: C/anjuta-manual.xml:554(para)
+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/>"
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:595(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:604(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:617(para)
+msgid ""
+"Select <menuchoice><guisubmenu>Project</guisubmenu><guimenuitem>Properties</"
+"guimenuitem></menuchoice> to bring up the project properties dialog."
+msgstr ""
+
+#: C/anjuta-manual.xml:624(para)
+msgid ""
+"Select the tab <guibutton>Packages</guibutton> to bring up the Packages page."
+msgstr ""
+
+#: C/anjuta-manual.xml:628(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:638(para)
+msgid ""
+"Click <guibutton>Add Package</guibutton> to bring up the package selection "
+"dialog."
+msgstr ""
+
+#: C/anjuta-manual.xml:641(para)
+msgid "Select the package to add and click <guibutton>Add</guibutton>."
+msgstr ""
+
+#: C/anjuta-manual.xml:644(para)
+#, fuzzy
+msgid "Click <guibutton>Close</guibutton> to close the properties dialog."
+msgstr ""
+"Щоб закÑ?иÑ?и дÑ?алогове вÑ?кно <guilabel>Ð?аÑ?амеÑ?Ñ?и аплеÑ?Ñ? \"Ð?веденнÑ? погоди\"</"
+"guilabel>, наÑ?иÑ?нÑ?Ñ?Ñ? <guibutton>Ð?акÑ?иÑ?и</guibutton>."
+
+#: C/anjuta-manual.xml:613(para)
+msgid "To add a package dependency: <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:651(title)
+#, fuzzy
+msgid "Group properties"
+msgstr "Ð?лаÑ?Ñ?ивоÑ?Ñ?Ñ? гÑ?Ñ?пи"
+
+#: C/anjuta-manual.xml:658(title) C/anjuta-manual.xml:660(screeninfo)
+#, fuzzy
+msgid "Group properties dialog"
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:675(para)
+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.)"
+msgstr ""
+
+#: C/anjuta-manual.xml:685(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:695(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:666(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:710(title)
+#, fuzzy
+msgid "Target properties"
+msgstr "Ð?лаÑ?Ñ?ивоÑ?Ñ?Ñ? дÑ?Ñ?кÑ?"
+
+#: C/anjuta-manual.xml:711(para)
+msgid ""
+"Any properties set for a target apply to that target only. A target also "
+"inherits properties from its containing group."
+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 ""
+
+#: 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."
+msgstr ""
+
+#: C/anjuta-manual.xml:735(title)
+#, fuzzy
+msgid "Advanced target options"
+msgstr "Ð?икоÑ?иÑ?Ñ?аннÑ?: %s [Ð?Ð?ЮЧÐ?]... [ЦÐ?Ð?Ь]...\n"
+
+#: C/anjuta-manual.xml:736(para)
+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."
+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 ""
+
+#: C/anjuta-manual.xml:761(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:769(para)
+msgid ""
+"<emphasis>Libraries</emphasis>: Set the libraries that the target depends on."
+msgstr ""
+
+#: C/anjuta-manual.xml:3(title)
+#, fuzzy
+msgid "Building"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:10(para)
+msgid "An autotools project is built in three steps:"
+msgstr ""
+
+#: C/anjuta-manual.xml:15(para)
+#, fuzzy
+msgid "Generate"
+msgstr "&СÑ?воÑ?еннÑ?"
+
+#: C/anjuta-manual.xml:16(para)
+#, fuzzy
+msgid "Configure"
+msgstr "Ð?алаÑ?Ñ?Ñ?ваÑ?и"
+
+#: C/anjuta-manual.xml:17(para)
+#, fuzzy
+msgid "Build"
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:46(para)
+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."
+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."
+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"
+
+#: C/anjuta-manual.xml:78(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:100(para)
+msgid "Whether you want to run the generate step or not"
+msgstr ""
+
+#: C/anjuta-manual.xml:101(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:109(para)
+#, fuzzy
+msgid "The configuration name"
+msgstr "Ð?овне Ñ?м'Ñ? "
+
+#: C/anjuta-manual.xml:110(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:116(para)
+#, fuzzy
+msgid "The build directory"
+msgstr "Ð?еÑ?елÑ?к вмÑ?Ñ?Ñ?Ñ? каÑ?алогÑ?"
+
+#: C/anjuta-manual.xml:117(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:122(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:130(para)
+#, fuzzy
+msgid "Configure options"
+msgstr "Ð?аÑ?амеÑ?Ñ?и конÑ?Ñ?гÑ?Ñ?аÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:131(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:94(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:140(title)
+#, fuzzy
+msgid "Select a configuration"
+msgstr "Ð?ибÑ?Ñ? наÑ?Ñ?Ñ?ойки MS-DOS"
+
+#: C/anjuta-manual.xml:141(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:148(title)
+#, fuzzy
+msgid "Clean a configuration"
+msgstr "Ð?онÑ?Ñ?гÑ?Ñ?аÑ?Ñ?Ñ? GTK"
+
+#: C/anjuta-manual.xml:149(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:166(title)
+#, fuzzy
+msgid "Compile and Build"
+msgstr "Ð?омпÑ?лÑ?ваÑ?и й збеÑ?егÑ?и вÑ?Ñ? модÑ?лÑ?"
+
+#: C/anjuta-manual.xml:168(title)
+#, fuzzy
+msgid "Compiling a file"
+msgstr "Ð?адÑ?Ñ?лаÑ?и Ñ?айл"
+
+#: C/anjuta-manual.xml:169(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:177(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:185(title)
+#, fuzzy
+msgid "Building an executable"
+msgstr "Ð?иконÑ?ваний Ñ?айл PEF"
+
+#: C/anjuta-manual.xml:186(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:195(para)
+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."
+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 ""
+
+#: C/anjuta-manual.xml:207(para)
+msgid ""
+"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build</guimenuitem></"
+"menuchoice> will build all files in the directory of the currently active "
+"file."
+msgstr ""
+
+#: C/anjuta-manual.xml:211(para)
+msgid ""
+"<menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Build Project</"
+"guimenuitem></menuchoice> will build the whole project â?? all subdirectories "
+"are built recursively."
+msgstr ""
+
+#: C/anjuta-manual.xml:223(title)
+#, fuzzy
+msgid "Other operations"
+msgstr "Ð?пеÑ?аÑ?Ñ?Ñ? з Ñ?айÑ?ом"
+
+#: C/anjuta-manual.xml:225(title)
+#, fuzzy
+msgid "Creating a distribution package"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:234(title)
+#, fuzzy
+msgid "Installing a project"
+msgstr "Ð?Ñ?оекÑ? Glade"
+
+#: C/anjuta-manual.xml:235(para)
+msgid ""
+"Choosing the menu item <menuchoice><guisubmenu>Build</"
+"guisubmenu><guimenuitem>Install</guimenuitem></menuchoice> will install the "
+"generated application on your system."
+msgstr ""
+
+#: C/anjuta-manual.xml:241(title)
+#, fuzzy
+msgid "System-wide installation"
+msgstr "Ð?еÑ?езаванÑ?ажÑ?ваÑ?и Ñ?иÑ?Ñ?емÑ? пÑ?Ñ?лÑ? вÑ?Ñ?ановленнÑ?"
+
+#: C/anjuta-manual.xml:242(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:252(title)
+#, fuzzy
+msgid "Cleaning"
+msgstr "Ð?Ñ?иÑ?еннÑ?:"
+
+#: C/anjuta-manual.xml:253(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:263(para)
+msgid ""
+"Choose the menu item <menuchoice><guisubmenu>Build</"
+"guisubmenu><guimenuitem>Clean</guimenuitem></menuchoice> to clean only the "
+"directory of the current active file."
+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..."
+msgstr ""
+
+#: C/anjuta-manual.xml:7(para)
+msgid ""
+"Well, the <emphasis>human</emphasis> part is what this section is about. The "
+"<emphasis>divine</emphasis> part is up to you!"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:19(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:27(para)
+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."
+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"
+
+#: C/anjuta-manual.xml:41(emphasis)
+#, fuzzy
+msgid "Attaching to a process"
+msgstr "Ð?еÑ?еÑ?воÑ?иÑ?и на пÑ?оÑ?еÑ?"
+
+#: C/anjuta-manual.xml:44(para)
+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."
+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 ""
+
+#: C/anjuta-manual.xml:57(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:65(para)
+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."
+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."
+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"
+
+#: C/anjuta-manual.xml:86(para)
+#, fuzzy
+msgid "Environment variables"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:91(para)
+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\"."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:71(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:102(title)
+#, fuzzy
+msgid "Attaching to a Process"
+msgstr "Ð?еÑ?еÑ?воÑ?иÑ?и на пÑ?оÑ?еÑ?"
+
+#: C/anjuta-manual.xml:103(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:110(title) C/anjuta-manual.xml:112(screeninfo)
+#, fuzzy
+msgid "Attach to Process dialog"
+msgstr "Ð?еÑ?еÑ?Ñ?д до вÑ?кна \"Ð?Ñ?ив'Ñ?зка до Ñ?Ñ?Ñ?ки\""
+
+#: C/anjuta-manual.xml:116(para)
+msgid ""
+"Select the process to attach to and click <guibutton>OK</guibutton> to start "
+"the debugger, attach to the selected process and stop it."
+msgstr ""
+
+#: C/anjuta-manual.xml:121(para)
+msgid ""
+"It is currently not possible to load symbol information for an attached "
+"process. Symbols should be included in the process."
+msgstr ""
+
+#: C/anjuta-manual.xml:129(title)
+#, fuzzy
+msgid "Stopping the Debugger"
+msgstr "Ð?алагоджÑ?ваÑ? Ñ?Ñ?енаÑ?Ñ?Ñ?в"
+
+#: C/anjuta-manual.xml:130(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:140(title)
+#, fuzzy
+msgid "Adding source directories"
+msgstr "Ð?аÑ?алоги джеÑ?ела/пÑ?изнаÑ?еннÑ?"
+
+#: C/anjuta-manual.xml:141(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:146(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:162(title)
+#, fuzzy
+msgid "Execution"
+msgstr "Ð?иконаннÑ? %s не вдалоÑ?Ñ?"
+
+#: 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."
+msgstr ""
+
+#: C/anjuta-manual.xml:170(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:177(title)
+#, fuzzy
+msgid "Single stepping (step in)"
+msgstr "Ð?изнаÑ?еннÑ? дÑ?апазонÑ?в однÑ?Ñ?Ñ? дÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:178(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:184(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:191(para)
+msgid ""
+"If the <interface>Disassembly window</interface> has the focus when this "
+"command is selected, it executes only one assembler instruction."
+msgstr ""
+
+#: C/anjuta-manual.xml:198(title)
+msgid "Single stepping (step over)"
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:210(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:216(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:225(title)
+#, fuzzy
+msgid "Single stepping (step out)"
+msgstr "Ð?менÑ?иÑ?и на кÑ?ок"
+
+#: C/anjuta-manual.xml:226(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:242(title)
+#, fuzzy
+msgid "Run/Continue"
+msgstr "</B/24>Ð?Ñ?одовжиÑ?и"
+
+#: 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 ""
+
+#: C/anjuta-manual.xml:249(para)
+msgid ""
+"This option continues the execution of the program until a breakpoint is "
+"encountered, or the program exits."
+msgstr ""
+
+#: C/anjuta-manual.xml:256(title)
+#, fuzzy
+msgid "Run To"
+msgstr ""
+"Ð?еможливо запÑ?Ñ?Ñ?иÑ?и:\n"
+"%s"
+
+#: C/anjuta-manual.xml:257(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:271(title)
+#, fuzzy
+msgid "Stop Program"
+msgstr "Ð?апÑ?Ñ?каÑ?Ñ?Ñ?Ñ?Ñ? пÑ?огÑ?ама \"%s\" ...\n"
+
+#: C/anjuta-manual.xml:272(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:287(title)
+#, fuzzy
+msgid "Breakpoints"
+msgstr "Ð?идалиÑ?и вÑ?Ñ? Ñ?оÑ?ки зÑ?пинки"
+
+#: C/anjuta-manual.xml:288(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:298(title)
+#, fuzzy
+msgid "Listing Breakpoints"
+msgstr "Ð?еÑ?елÑ?к вмÑ?Ñ?Ñ?Ñ? каÑ?алогÑ?"
+
+#: C/anjuta-manual.xml:299(para)
+msgid ""
+"The <interface>Breakpoint list window</interface> can be opened by choosing "
+"<menuchoice><guisubmenu>View</guisubmenu><guimenuitem>Breakpoints</"
+"guimenuitem></menuchoice>"
+msgstr ""
+
+#: C/anjuta-manual.xml:306(title) C/anjuta-manual.xml:308(screeninfo)
+#, fuzzy
+msgid "Breakpoint view"
+msgstr "Ð?еÑ?еглÑ?нÑ?Ñ?и _жÑ?Ñ?нал"
+
+#: C/anjuta-manual.xml:317(term) C/anjuta-manual.xml:413(term)
+#, fuzzy
+msgid "Location"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:327(term)
+#, fuzzy
+msgid "Address"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:336(term)
+#, fuzzy
+msgid "Type"
+msgstr "Тип"
+
+#: C/anjuta-manual.xml:338(para)
+msgid ""
+"This always displays \"breakpoint\". It will be used in a future release "
+"supporting different kinds of breakpoints."
+msgstr ""
+
+#: C/anjuta-manual.xml:345(term) C/anjuta-manual.xml:440(term)
+#, fuzzy
+msgid "Condition"
+msgstr "Умова"
+
+#: C/anjuta-manual.xml:347(para)
+msgid ""
+"This is the breakpoint condition. It is empty if no condition is defined."
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:367(term)
+#, fuzzy
+msgid "State"
+msgstr "Ð?блаÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:372(para)
+msgid "Pending: the breakpoint is not set in your program."
+msgstr ""
+
+#: C/anjuta-manual.xml:373(para)
+msgid ""
+"Permanent: the breakpoint is set (its id number in given inside parentheses)."
+msgstr ""
+
+#: C/anjuta-manual.xml:374(para)
+msgid "Temporary: the breakpoint is set but will be deleted if reached."
+msgstr ""
+
+#: C/anjuta-manual.xml:369(para)
+msgid "This is the state of the breakpoint. It may be <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:313(para)
+msgid "The view has the following columns: <placeholder-1/>"
+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."
+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 ""
+
+#: C/anjuta-manual.xml:400(title) C/anjuta-manual.xml:402(screeninfo)
+#, fuzzy
+msgid "Breakpoint add dialog"
+msgstr "Ð?Ñ?кно додаваннÑ? Ñ?айлÑ?в"
+
+#: 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:"
+msgstr ""
+
+#: C/anjuta-manual.xml:421(para)
+#, fuzzy
+msgid "File_name:Line_number"
+msgstr "!Ñ?м'Ñ?_Ñ?айлÑ?,номеÑ?_Ñ?Ñ?лÑ?Ñ?Ñ?а"
+
+#: C/anjuta-manual.xml:422(para)
+#, fuzzy
+msgid "Function_name"
+msgstr "Ð?епÑ?ипÑ?Ñ?Ñ?име Ñ?м'Ñ? Ñ?Ñ?нкÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:423(para)
+#, fuzzy
+msgid "File:Function_name"
+msgstr "Ð?епÑ?ипÑ?Ñ?Ñ?име Ñ?м'Ñ? Ñ?Ñ?нкÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:426(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:442(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:449(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:455(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:462(term)
+#, fuzzy
+msgid "Pass Count"
+msgstr " (%(count)d з %(total)d)"
+
+#: C/anjuta-manual.xml:464(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:474(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:407(para)
+msgid ""
+"Enter the location and, optionally, the break condition and the pass count; "
+"then click <guibutton>OK</guibutton> to set the breakpoint. <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:482(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:491(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:500(title)
+#, fuzzy
+msgid "Editing Breakpoints"
+msgstr "Ð?овÑ?оÑ?иÑ?и попеÑ?еднÑ? дÑ?Ñ?"
+
+#: C/anjuta-manual.xml:501(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:506(para)
+msgid ""
+"Edit the entries as required and click on <guibutton>OK</guibutton> to "
+"commit the changes."
+msgstr ""
+
+#: C/anjuta-manual.xml:513(title)
+#, fuzzy
+msgid "Deleting Breakpoints"
+msgstr "Ð?идалÑ?Ñ?Ñ?Ñ?Ñ?Ñ? каÑ?алог"
+
+#: C/anjuta-manual.xml:514(para)
+msgid ""
+"Select the breakpoint in the breakpoint list view and click on "
+"<menuchoice><guimenuitem>Remove Breakpoint</guimenuitem></menuchoice> to "
+"delete it."
+msgstr ""
+
+#: C/anjuta-manual.xml:518(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:527(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:536(title)
+msgid "Enabling or Disabling Breakpoints"
+msgstr ""
+
+#: C/anjuta-manual.xml:537(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:543(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:554(title)
+#, fuzzy
+msgid "Expressions"
+msgstr "РегÑ?лÑ?Ñ?нÑ? виÑ?ази"
+
+#: C/anjuta-manual.xml:557(title)
+#, fuzzy
+msgid "Listing local variables"
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:572(title) C/anjuta-manual.xml:574(screeninfo)
+#, fuzzy
+msgid "Local variables"
+msgstr "Ð?_ивеÑ?Ñ?и змÑ?ннÑ?"
+
+#: C/anjuta-manual.xml:564(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:579(para)
+msgid ""
+"The value of a local variable can be modified by selecting it and clicking "
+"in the <guilabel>Value</guilabel> column."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:594(title)
+#, fuzzy
+msgid "Listing watched expressions"
+msgstr "Ð?амÑ?на Ñ?егÑ?лÑ?Ñ?ниÑ? виÑ?азÑ?в"
+
+#: C/anjuta-manual.xml:595(para)
+msgid ""
+"Inspecting or evaluating an expression provides the result only once. To "
+"continuously monitor some variables or expressions, use <emphasis>expression "
+"watches</emphasis>."
+msgstr ""
+
+#: C/anjuta-manual.xml:599(para)
+msgid ""
+"Choose the menu item <menuchoice><guisubmenu>View</"
+"guisubmenu><guimenuitem>Watches</guimenuitem></menuchoice> to display the "
+"<interface>Watches window</interface>."
+msgstr ""
+
+#: C/anjuta-manual.xml:606(title)
+#, fuzzy
+msgid "Adding an expression to watch"
+msgstr "Ð?иÑ?аз запиÑ?Ñ? длÑ? аналÑ?зÑ?"
+
+#: C/anjuta-manual.xml:607(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:616(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:625(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:634(title)
+#, fuzzy
+msgid "Removing a watched expression"
+msgstr "Ñ? виÑ?азÑ? оÑ?Ñ?кÑ?вавÑ?Ñ? \"?\""
+
+#: C/anjuta-manual.xml:635(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:640(para)
+msgid ""
+"All watches can be removed by choosing <guimenuitem>Remove All</guimenuitem> "
+"in the context menu of the <interface>Watches window</interface>."
+msgstr ""
+
+#: C/anjuta-manual.xml:647(title)
+#, fuzzy
+msgid "Evaluating expressions"
+msgstr "РегÑ?лÑ?Ñ?нÑ? виÑ?ази"
+
+#: C/anjuta-manual.xml:648(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:657(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:670(title)
+msgid "Inspecting expressions in editor window"
+msgstr ""
+
+#: C/anjuta-manual.xml:671(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:677(para)
+msgid ""
+"This capability is currently working only for simple variables, not for "
+"structures or arrays."
+msgstr ""
+
+#: C/anjuta-manual.xml:686(title)
+#, fuzzy
+msgid "Stack Trace"
+msgstr "Ð?Ñ?овеÑ?Ñ?и векÑ?оÑ?изаÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:689(title)
+#, fuzzy
+msgid "Stack Window"
+msgstr "Ð?Ñ?кно Ñ?еÑ?веÑ?а..."
+
+#: C/anjuta-manual.xml:690(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:698(para)
+msgid ""
+"Choose the menu item <menuchoice><guisubmenu>View </"
+"guisubmenu><guimenuitem>Stack</guimenuitem></menuchoice> to open the stack "
+"trace for the program being debugged."
+msgstr ""
+
+#: C/anjuta-manual.xml:705(title) C/anjuta-manual.xml:707(screeninfo)
+#, fuzzy
+msgid "Stack trace window"
+msgstr "Ð?Ñ?дкÑ?иÑ?и дÑ?алогове вÑ?кно"
+
+#: C/anjuta-manual.xml:712(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:722(title)
+#, fuzzy
+msgid "Setting the current frame"
+msgstr "Ð?идаленнÑ? поÑ?оÑ?ноÑ? Ñ?амки"
+
+#: C/anjuta-manual.xml:723(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:731(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:741(title)
+#, fuzzy
+msgid "Thread"
+msgstr "ЦÑ?вка"
+
+#: C/anjuta-manual.xml:744(title)
+#, fuzzy
+msgid "Thread Window"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:750(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:759(title)
+#, fuzzy
+msgid "Setting the current thread"
+msgstr "видÑ?лиÑ?и поÑ?оÑ?нÑ? беÑ?Ñ?дÑ?"
+
+#: C/anjuta-manual.xml:760(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:768(para)
+msgid ""
+"Changing the thread changes the value of CPU registers and the current stack "
+"frame, so the <interface>Locals window</interface> changes too."
+msgstr ""
+
+#: C/anjuta-manual.xml:777(title)
+#, fuzzy
+msgid "CPU"
+msgstr "ЦÐ?"
+
+#: C/anjuta-manual.xml:780(title)
+#, fuzzy
+msgid "Register window"
+msgstr "Ð?Ñ?кно Ñ?еÑ?веÑ?а..."
+
+#: C/anjuta-manual.xml:781(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:788(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:796(title)
+#, fuzzy
+msgid "Memory window"
+msgstr "Ð?Ñ?кно Ñ?еÑ?веÑ?а..."
+
+#: C/anjuta-manual.xml:797(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:802(para)
+msgid ""
+"The first column displays memory addresses in hexadecimal, the second "
+"displays memory contents in hexadecimal and the last column shows memory "
+"contents in ASCII."
+msgstr ""
+
+#: C/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."
+msgstr ""
+
+#: C/anjuta-manual.xml:816(title)
+#, fuzzy
+msgid "Disassembly window"
+msgstr "Ð?Ñ?кно Ñ?еÑ?веÑ?а..."
+
+#: C/anjuta-manual.xml:817(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:822(para)
+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 ""
+
+#: C/anjuta-manual.xml:827(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:840(title)
+#, fuzzy
+msgid "Others"
+msgstr "Ð?нÑ?Ñ?"
+
+#: C/anjuta-manual.xml:842(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:848(title)
+#, fuzzy
+msgid "Dynamically loaded Libraries"
+msgstr "РобоÑ?е Ñ?еÑ?едовиÑ?е KDE - Ð?Ñ?блÑ?оÑ?еки"
+
+#: C/anjuta-manual.xml:849(para)
+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)."
+msgstr ""
+
+#: C/anjuta-manual.xml:859(title) C/anjuta-manual.xml:861(screeninfo)
+#, fuzzy
+msgid "Shared Libraries window"
+msgstr "Ð?иÑ?е LAMELib|LAMELib|СпÑ?лÑ?нÑ? бÑ?блÑ?оÑ?еки (*)|*"
+
+#: C/anjuta-manual.xml:869(title)
+#, fuzzy
+msgid "Kernel Signals"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:879(title) C/anjuta-manual.xml:881(screeninfo)
+#, fuzzy
+msgid "Kernel Signals window"
+msgstr "Ð?Ñ?дкÑ?иÑ?и дÑ?алогове вÑ?кно"
+
+#: C/anjuta-manual.xml:886(para)
+msgid ""
+"There are three columns which specify what to do when a signal is received:"
+msgstr ""
+
+#: C/anjuta-manual.xml:892(para)
+msgid ""
+"<emphasis>Stop</emphasis> â?? this tells the debugger whether to stop the "
+"program execution (and return control) when the program receives this signal."
+msgstr ""
+
+#: C/anjuta-manual.xml:898(para)
+msgid ""
+"<emphasis>Print</emphasis> â?? this tells the debugger whether to display the "
+"received signal."
+msgstr ""
+
+#: C/anjuta-manual.xml:903(para)
+msgid ""
+"<emphasis>Pass</emphasis> â?? this tells the debugger whether to pass the "
+"signal to the program."
+msgstr ""
+
+#: C/anjuta-manual.xml:909(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:928(title)
+#, fuzzy
+msgid "Information about debugged program"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:938(title)
+#, fuzzy
+msgid "Information about kernel structure"
+msgstr "Ð?нÑ?оÑ?маÑ?Ñ?Ñ? пÑ?о GThumb"
+
+#: C/anjuta-manual.xml:939(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:948(title)
+#, fuzzy
+msgid "Information about global variables"
+msgstr "Ð?нÑ?оÑ?маÑ?Ñ?Ñ? пÑ?о GThumb"
+
+#: C/anjuta-manual.xml:949(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:958(title)
+#, fuzzy
+msgid "Information about the current frame"
+msgstr "Ð?оказаÑ?и Ñ?нÑ?оÑ?маÑ?Ñ?Ñ? пÑ?о поÑ?оÑ?ний Ñ?айл"
+
+#: C/anjuta-manual.xml:959(para)
+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."
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:978(title)
+#, fuzzy
+msgid "User command"
+msgstr "Ð?иÑ?Ñ?д за вимогоÑ? коÑ?иÑ?Ñ?Ñ?ваÑ?а."
+
+#: C/anjuta-manual.xml:979(para)
+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>."
+msgstr ""
+
+#: C/anjuta-manual.xml:987(para)
+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."
+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;"
+msgstr ""
+
+#: C/anjuta-manual.xml:13(para)
+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;"
+msgstr ""
+
+#: C/anjuta-manual.xml:19(para)
+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>;"
+msgstr ""
+
+#: C/anjuta-manual.xml:28(para)
+msgid ""
+"Check <menuchoice><guimenuitem>View</guimenuitem><guimenuitem>Designer</"
+"guimenuitem></menuchoice> flag and move this window to a better place;"
+msgstr ""
+
+#: C/anjuta-manual.xml:36(para)
+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>;"
+msgstr ""
+
+#: C/anjuta-manual.xml:42(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:6(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:52(title)
+msgid "Glade general usage questions"
+msgstr ""
+
+#: C/anjuta-manual.xml:53(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:66(title)
+#, fuzzy
+msgid "Editor and designer association"
+msgstr "РедакÑ?оÑ? Ñ?а Ñ?иÑ?Ñ?ема кеÑ?Ñ?ваннÑ? веб-Ñ?Ñ?оÑ?Ñ?нками"
+
+#: C/anjuta-manual.xml:67(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:83(title)
+#, fuzzy
+msgid "Associations dialog"
+msgstr "Ð?нопки дÑ?алогÑ?в..."
+
+#: C/anjuta-manual.xml:94(guilabel)
+#, fuzzy
+msgid "Spec regexp"
+msgstr "Ð?мÑ?ннÑ? Ñ?егÑ?лÑ?Ñ?ниÑ? виÑ?азÑ?в"
+
+#: C/anjuta-manual.xml:95(para)
+msgid ""
+"Shortened from \"special regular expression\". Used for defining a custom "
+"position for inserting stubs."
+msgstr ""
+
+#: C/anjuta-manual.xml:101(guilabel)
+#, fuzzy
+msgid "Widget name"
+msgstr "Ð?азва вÑ?джеÑ?а"
+
+#: C/anjuta-manual.xml:102(para)
+msgid "The name of the toplevel widget this assoctiation belongs to."
+msgstr ""
+
+#: C/anjuta-manual.xml:107(guilabel)
+#, fuzzy
+msgid "Position type"
+msgstr "Тип DCC"
+
+#: C/anjuta-manual.xml:108(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:84(para)
+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/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:122(title)
+#, fuzzy
+msgid "Default signal"
+msgstr "%s: невÑ?домий Ñ?игнал %s\n"
+
+#: C/anjuta-manual.xml:123(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:134(title)
+#, fuzzy
+msgid "Inserting a stub"
+msgstr "Ð?Ñ?Ñ?авлÑ?Ñ?Ñ?Ñ?Ñ?Ñ? виноÑ?ка..."
+
+#: C/anjuta-manual.xml:135(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:144(para)
+msgid ""
+"Automatically if <guilabel>Insert handler on edit</guilabel> option if "
+"enabled"
+msgstr ""
+
+#: C/anjuta-manual.xml:148(para)
+msgid ""
+"Using <menuchoice><guimenuitem>Glade</guimenuitem><guimenuitem>Insert "
+"handler stub, autoposition</guimenuitem></menuchoice> in hte main menu"
+msgstr ""
+
+#: C/anjuta-manual.xml:154(para)
+msgid ""
+"Using <guilabel>Insert handler stub</guilabel> item in the context menu of "
+"text document"
+msgstr ""
+
+#: C/anjuta-manual.xml:141(para)
+msgid "There are several ways to create a stub: <placeholder-1/>"
+msgstr ""
+
+#: C/anjuta-manual.xml:163(title) C/anjuta-manual.xml:3(title)
+#, fuzzy
+msgid "Preferences"
+msgstr "Ð?аÑ?амеÑ?Ñ?и"
+
+#: C/anjuta-manual.xml:166(guilabel)
+#, fuzzy
+msgid "Insert handler on edit"
+msgstr "Ð?Ñ?Ñ?авка обÑ?обника подÑ?Ñ?"
+
+#: C/anjuta-manual.xml:167(para)
+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>"
+msgstr ""
+
+#: C/anjuta-manual.xml:174(guilabel)
+#, fuzzy
+msgid "Separated designer layout"
+msgstr "Ð?едÑ?Ñ?кованÑ? &Ñ?имволи"
+
+#: C/anjuta-manual.xml:175(para)
+msgid ""
+"Detaches the design area from document manager so you can dock it separately "
+"from text editors."
+msgstr ""
+
+#: C/anjuta-manual.xml:181(guilabel)
+#, fuzzy
+msgid "Automatically add resources"
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:190(guilabel)
+#, fuzzy
+msgid "Handler template"
+msgstr "Ð?лаÑ?ний _Ñ?аблон:"
+
+#: C/anjuta-manual.xml:191(para)
+msgid ""
+"You can choose between the two formats of automatic naming of signal handler."
+msgstr ""
+
+#: C/anjuta-manual.xml:4(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:9(title)
+#, fuzzy
+msgid "General"
+msgstr "Ð?агалÑ?не"
+
+#: C/anjuta-manual.xml:11(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:17(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:24(title)
+#, fuzzy
+msgid "File Manager"
+msgstr "Ð?еÑ?Ñ?ваннÑ? Ñ?айлами"
+
+#: C/anjuta-manual.xml:26(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:31(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:3(title)
+#, fuzzy
+msgid "User-defined Tools"
+msgstr ""
+"Ð?изнаÑ?енÑ? коÑ?иÑ?Ñ?Ñ?ваÑ?ем команди:\n"
+"\n"
+" "
+
+#: C/anjuta-manual.xml:7(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:16(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:24(para)
+msgid "The tools plugin has to be enabled to use this feature!"
+msgstr ""
+
+#: C/anjuta-manual.xml:31(title)
+#, fuzzy
+msgid "Tools Examples"
+msgstr "/СеÑ?вÑ?Ñ?/С_Ñ?аÑ?Ñ?Ñ?"
+
+#: C/anjuta-manual.xml:32(para)
+msgid ""
+"This is a simple example how to use the tools plugin to integrate the GNOME "
+"ChangeLog generation script."
+msgstr ""
+
+#: C/anjuta-manual.xml:38(title) C/anjuta-manual.xml:40(screeninfo)
+#, fuzzy
+msgid "The tool editor"
+msgstr "РедакÑ?оÑ? _XML..."
+
+#: C/anjuta-manual.xml:2(title)
+#, fuzzy
+msgid "Authors"
+msgstr "Ð?вÑ?оÑ?и"
+
+#: C/anjuta-manual.xml:3(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:9(para)
+msgid ""
+"For more information on <application>Anjuta</application>, please visit the "
+"project website at <ulink type=\"http\" url=\"http://anjuta.org/\";>http://";
+"anjuta.org</ulink>. Bug reports should be made using the Bug Tracker at the "
+"project development site <ulink type=\"http\" url=\"http://www.sourceforge.";
+"net/projects/anjuta\"> http://www.sourceforge.net/projects/anjuta</ulink>."
+msgstr ""
+
+#: C/anjuta-manual.xml:17(para)
+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."
+msgstr ""
+
+#: C/anjuta-manual.xml:2(title)
+#, fuzzy
+msgid "License"
+msgstr "Ð?Ñ?Ñ?ензÑ?Ñ?"
+
+#: C/anjuta-manual.xml:3(para)
+#, fuzzy
+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."
+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
+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."
+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>"
+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>"
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
