summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAzamat H. Hackimov <azamat.hackimov@gmail.com>2011-01-21 01:47:46 +0500
committerAzamat H. Hackimov <azamat.hackimov@gmail.com>2011-01-21 01:47:46 +0500
commitc759c7e5a40021796d178ca812c249a2cd54c928 (patch)
treee42648484baa2f342141fdd0fd4eb3f2f62d753e /doc
parentSync with CVS, update po (diff)
downloadgentoo-doc-translations-c759c7e5a40021796d178ca812c249a2cd54c928.tar.gz
gentoo-doc-translations-c759c7e5a40021796d178ca812c249a2cd54c928.tar.bz2
gentoo-doc-translations-c759c7e5a40021796d178ca812c249a2cd54c928.zip
Greek templates to translate
Diffstat (limited to 'doc')
-rw-r--r--doc/gettext/el/alsa-guide.xml.po1138
-rw-r--r--doc/gettext/el/altinstall.xml.po1030
-rw-r--r--doc/gettext/el/anothertest.xml.po71
-rw-r--r--doc/gettext/el/apache-troubleshooting.xml.po55
-rw-r--r--doc/gettext/el/apache-upgrading.xml.po55
-rw-r--r--doc/gettext/el/arm-requirements.xml.po114
-rw-r--r--doc/gettext/el/ati-faq.xml.po355
-rw-r--r--doc/gettext/el/bind-guide.xml.po535
-rw-r--r--doc/gettext/el/bluetooth-guide.xml.po869
-rw-r--r--doc/gettext/el/bugzilla-howto.xml.po1985
-rw-r--r--doc/gettext/el/change-chost.xml.po518
-rw-r--r--doc/gettext/el/conky-howto.xml.po275
-rw-r--r--doc/gettext/el/cron-guide.xml.po923
-rw-r--r--doc/gettext/el/cross-compiling-distcc.xml.po274
-rw-r--r--doc/gettext/el/cvs-tutorial.xml.po1204
-rw-r--r--doc/gettext/el/desktop.xml.po64
-rw-r--r--doc/gettext/el/devfs-guide.xml.po588
-rw-r--r--doc/gettext/el/diskless-howto.xml.po1686
-rw-r--r--doc/gettext/el/distcc.xml.po565
-rw-r--r--doc/gettext/el/doc-languages.xml.po43
-rw-r--r--doc/gettext/el/dri-howto.xml.po497
-rw-r--r--doc/gettext/el/ebuild-submit.xml.po252
-rw-r--r--doc/gettext/el/faq.xml.po997
-rw-r--r--doc/gettext/el/fluxbox-config.xml.po879
-rw-r--r--doc/gettext/el/gcc-optimization.xml.po724
-rw-r--r--doc/gettext/el/gcc-upgrading.xml.po637
-rw-r--r--doc/gettext/el/genkernel.xml.po1075
-rw-r--r--doc/gettext/el/gentoo-alpha-faq.xml.po673
-rw-r--r--doc/gettext/el/gentoo-alpha-install.xml.po59
-rw-r--r--doc/gettext/el/gentoo-amd64-faq.xml.po474
-rw-r--r--doc/gettext/el/gentoo-freebsd.xml.po1194
-rw-r--r--doc/gettext/el/gentoo-hppa-install.xml.po59
-rw-r--r--doc/gettext/el/gentoo-kernel.xml.po570
-rw-r--r--doc/gettext/el/gentoo-mips-faq.xml.po725
-rw-r--r--doc/gettext/el/gentoo-mips-install.xml.po59
-rw-r--r--doc/gettext/el/gentoo-ppc-faq.xml.po1552
-rw-r--r--doc/gettext/el/gentoo-ppc-install.xml.po63
-rw-r--r--doc/gettext/el/gentoo-security.xml.po63
-rw-r--r--doc/gettext/el/gentoo-sparc-faq.xml.po777
-rw-r--r--doc/gettext/el/gentoo-sparc-install.xml.po63
-rw-r--r--doc/gettext/el/gentoo-sparc-netboot-howto.xml.po865
-rw-r--r--doc/gettext/el/gentoo-sparc-obpreference.xml.po606
-rw-r--r--doc/gettext/el/gentoo-upgrading.xml.po842
-rw-r--r--doc/gettext/el/gentoo-x86+raid+lvm2-quickinstall.xml.po561
-rw-r--r--doc/gettext/el/gentoo-x86-install.xml.po63
-rw-r--r--doc/gettext/el/gentoo-x86-quickinstall-after-reboot.xml.po311
-rw-r--r--doc/gettext/el/gentoo-x86-quickinstall-media.xml.po240
-rw-r--r--doc/gettext/el/gentoo-x86-quickinstall-stage.xml.po217
-rw-r--r--doc/gettext/el/gentoo-x86-quickinstall-system.xml.po338
-rw-r--r--doc/gettext/el/gentoo-x86-quickinstall.xml.po256
-rw-r--r--doc/gettext/el/gentoo-x86-tipsntricks.xml.po658
-rw-r--r--doc/gettext/el/gentoolkit.xml.po1015
-rw-r--r--doc/gettext/el/gnome-config.xml.po348
-rw-r--r--doc/gettext/el/gnupg-user.xml.po1195
-rw-r--r--doc/gettext/el/gpm.xml.po272
-rw-r--r--doc/gettext/el/grub-error-guide.xml.po841
-rw-r--r--doc/gettext/el/guide-localization.xml.po780
-rw-r--r--doc/gettext/el/guide-to-mutt.xml.po742
-rw-r--r--doc/gettext/el/home-router-howto.xml.po1151
-rw-r--r--doc/gettext/el/hpc-howto.xml.po1430
-rw-r--r--doc/gettext/el/index.xml.po100
-rw-r--r--doc/gettext/el/info-guide.xml.po532
-rw-r--r--doc/gettext/el/inserts.xml.po237
-rw-r--r--doc/gettext/el/ipv6.xml.po1342
-rw-r--r--doc/gettext/el/java.xml.po889
-rw-r--r--doc/gettext/el/jffnms.xml.po556
-rw-r--r--doc/gettext/el/kde-config.xml.po60
-rw-r--r--doc/gettext/el/kde-split-ebuilds.xml.po74
-rw-r--r--doc/gettext/el/kernel-config.xml.po818
-rw-r--r--doc/gettext/el/kernel-upgrade.xml.po568
-rw-r--r--doc/gettext/el/keychain-guide.xml.po500
-rw-r--r--doc/gettext/el/ldap-howto.xml.po666
-rw-r--r--doc/gettext/el/list.xml.po65
-rw-r--r--doc/gettext/el/liveusb.xml.po408
-rw-r--r--doc/gettext/el/logcheck.xml.po309
-rw-r--r--doc/gettext/el/ltsp.xml.po712
-rw-r--r--doc/gettext/el/lvm2.xml.po698
-rw-r--r--doc/gettext/el/lxde-howto.xml.po348
-rw-r--r--doc/gettext/el/macos-guide.xml.po64
-rw-r--r--doc/gettext/el/mailfilter-guide.xml.po2630
-rw-r--r--doc/gettext/el/man-guide.xml.po601
-rw-r--r--doc/gettext/el/management-structure.xml.po399
-rw-r--r--doc/gettext/el/metadoc.xml.po1869
-rw-r--r--doc/gettext/el/migration-to-2.6.xml.po1595
-rw-r--r--doc/gettext/el/mips-requirements.xml.po599
-rw-r--r--doc/gettext/el/multipath.xml.po525
-rw-r--r--doc/gettext/el/mysql-howto.xml.po1359
-rw-r--r--doc/gettext/el/mysql-upgrade-slotted.xml.po101
-rw-r--r--doc/gettext/el/mysql-upgrading.xml.po600
-rw-r--r--doc/gettext/el/nagios-guide.xml.po572
-rw-r--r--doc/gettext/el/nano-basics-guide.xml.po205
-rw-r--r--doc/gettext/el/new-upgrade-to-gentoo-1.4.xml.po327
-rw-r--r--doc/gettext/el/nvidia-guide.xml.po777
-rw-r--r--doc/gettext/el/openafs.xml.po1763
-rw-r--r--doc/gettext/el/openbox.xml.po1160
-rw-r--r--doc/gettext/el/openrc-migration.xml.po745
-rw-r--r--doc/gettext/el/overview.xml.po35
-rw-r--r--doc/gettext/el/portage-utils.xml.po356
-rw-r--r--doc/gettext/el/postgres-howto.xml.po1013
-rw-r--r--doc/gettext/el/power-management-guide.xml.po2220
-rw-r--r--doc/gettext/el/prelink-howto.xml.po551
-rw-r--r--doc/gettext/el/printing-howto.xml.po1329
-rw-r--r--doc/gettext/el/qmail-howto.xml.po825
-rw-r--r--doc/gettext/el/quick-samba-howto.xml.po1263
-rw-r--r--doc/gettext/el/rsync.xml.po625
-rw-r--r--doc/gettext/el/shoutcast-config.xml.po1452
-rw-r--r--doc/gettext/el/source_mirrors.xml.po340
-rw-r--r--doc/gettext/el/sudo-guide.xml.po615
-rw-r--r--doc/gettext/el/test.xml.po83
-rw-r--r--doc/gettext/el/udev-guide.xml.po695
-rw-r--r--doc/gettext/el/uml.xml.po680
-rw-r--r--doc/gettext/el/usb-guide.xml.po630
-rw-r--r--doc/gettext/el/utf-8.xml.po1115
-rw-r--r--doc/gettext/el/vdr-guide.xml.po936
-rw-r--r--doc/gettext/el/vi-guide.xml.po833
-rw-r--r--doc/gettext/el/virt-mail-howto.xml.po1588
-rw-r--r--doc/gettext/el/vpnc-howto.xml.po1174
-rw-r--r--doc/gettext/el/vserver-howto.xml.po77
-rw-r--r--doc/gettext/el/xen-guide.xml.po741
-rw-r--r--doc/gettext/el/xfce-config.xml.po767
-rw-r--r--doc/gettext/el/xml-guide.xml.po1483
-rw-r--r--doc/gettext/el/xorg-config.xml.po981
-rw-r--r--doc/gettext/el/zsh.xml.po658
123 files changed, 84308 insertions, 0 deletions
diff --git a/doc/gettext/el/alsa-guide.xml.po b/doc/gettext/el/alsa-guide.xml.po
new file mode 100644
index 0000000..0225d71
--- /dev/null
+++ b/doc/gettext/el/alsa-guide.xml.po
@@ -0,0 +1,1138 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(guide:link):6
+msgid "/doc/en/alsa-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):7
+msgid "Gentoo Linux ALSA Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(author:title):12
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail:link):10
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail):10
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail:link):13
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail):13
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(author:title):15
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail:link):16
+msgid "flameeyes@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(mail):16
+msgid "Diego Pettenò"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(abstract):19
+msgid "This document helps a user setup ALSA on Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(version):27
+msgid "2.25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(date):28
+msgid "2009-08-05"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):33
+msgid "What is ALSA?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):36
+msgid ""
+"ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides "
+"audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality "
+"to the Linux operating system. ALSA is the default sound subsystem in the "
+"2.6 kernel thereby replacing OSS (<e>Open Sound System</e>), which was used "
+"in the 2.4 kernels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):44
+msgid ""
+"ALSA's main features include efficient support for all types of audio "
+"interfaces ranging from consumer sound cards to professional sound "
+"equipment, fully modularized drivers, SMP and thread safety, backward "
+"compatibility with OSS and a user-space library <c>alsa-lib</c> to make "
+"application development a breeze."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):55
+msgid "ALSA on Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):58
+msgid ""
+"Historically, Gentoo offered two ways to get ALSA up and running: the <e>in-"
+"kernel</e> driver and the external <c>alsa-driver</c> package. The two "
+"solutions essentially do the same thing; this made supporting the external "
+"package extremely difficult and time-consuming. The Gentoo maintainers "
+"decided to discontinue support for the <c>alsa-driver</c> package, "
+"concentrating their resources on the ALSA drivers available within the Linux "
+"kernel. This guide will focus solely on configuring ALSA via the in-kernel "
+"driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):68
+msgid ""
+"If you still require the <c>alsa-driver</c> package, please email the <mail "
+"link=\"alsa-bugs@gentoo.org\">Gentoo ALSA maintainers</mail> with why the in-"
+"kernel drivers don't work for you. Be sure to include detailed error logs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):79
+msgid "Installing ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):81
+msgid "Before you proceed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):84
+msgid ""
+"First, you need to know what drivers your sound card uses. In most cases, "
+"sound cards (onboard and otherwise) are PCI based and <c>lspci</c> will help "
+"you in digging out the required information. Please <c>emerge sys-apps/"
+"pciutils</c> to get <c>lspci</c>, if you don't have it installed already. In "
+"case you have a USB sound card, <c>lsusb</c> from <c>sys-apps/usbutils</"
+"c><e>might</e> be of help. For ISA cards, try using <c>sys-apps/isapnptools</"
+"c>. Also, the following pages <e>may</e> help users with ISA based sound "
+"cards:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri:link):96
+msgid "http://www.roestock.demon.co.uk/isapnptools/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri):96
+msgid "The ISAPNPTOOLS Page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri:link):100
+msgid "http://www2.linuxjournal.com/article/3269"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri):100
+msgid "LinuxJournal PnP Article"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri:link):104
+msgid "http://www.tldp.org/HOWTO/Sound-HOWTO/x320.html"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri):104
+msgid "TLDP Sound HowTo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):109
+msgid ""
+"For ease of use/explanation, we assume the user has a PCI based sound card "
+"for the remainder of this guide."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):114
+msgid "We now proceed to find out details about the sound card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):118
+msgid "Soundcard Details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):118
+#, no-wrap
+msgid ""
+"\n"
+"# <i>lspci -v | grep -i audio</i>\n"
+"0000:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):123
+msgid ""
+"We now know that the sound card on the machine is a Sound Blaster Live! and "
+"the card manufacturer is Creative Labs. Head over to the <uri link=\"http://"
+"bugtrack.alsa-project.org/main/index.php/Matrix:Main\">ALSA Soundcard "
+"Matrix</uri> page and select Creative Labs from the list. You will be taken "
+"to the Creative Labs matrix page where you can see that the SB Live! uses "
+"the <c>emu10k1</c> module. That is the information we need for now. If you "
+"are interested in detailed information, you can click on the link next to "
+"the \"Details\" and that will take you to the <c>emu10k1</c> specific page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):134
+msgid ""
+"If you intend to use MIDI, then you should add <c>midi</c> to your USE flags "
+"in <path>/etc/make.conf</path> before emerging any ALSA packages. Later in "
+"the guide, we will show you how to set up <uri link=\"#midi\">MIDI support</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):143
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):146
+msgid ""
+"Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. "
+"Please check that your kernel is a 2.6 series kernel. This method will "
+"<e>not</e> work on a 2.4 kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):152
+msgid "Let us now configure the kernel to enable ALSA."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(impo):156
+msgid ""
+"<c>genkernel</c> users should now run <c>genkernel --menuconfig all</c> and "
+"then follow the instructions in <uri link=\"#doc_chap2_pre3\">Kernel Options "
+"for ALSA</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):162
+msgid "Heading over to the source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):162
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):167
+msgid ""
+"The above example assumes that <path>/usr/src/linux</path> symlink points to "
+"the kernel sources you want to use. Please ensure the same before proceeding."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):172
+msgid ""
+"Now we will look at some of the options we will have to enable in the 2.6 "
+"kernel to ensure proper ALSA support for our sound card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):177
+msgid ""
+"Please note that for ease of use, all examples show ALSA built as modules. "
+"It is advisable to follow the same as it then allows the use of <c>alsaconf</"
+"c> which is a boon when you want to configure your card. Please do <e>not</"
+"e> skip the <uri link=\"#alsa-config\">Configuration</uri> section of this "
+"document. If you still like to have options built-in, ensure that you make "
+"changes to your config accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):186
+msgid "Kernel Options for ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):186
+#, no-wrap
+msgid ""
+"\n"
+"Device Drivers ---&gt;\n"
+" Sound ---&gt;\n"
+" \n"
+"<comment>(This needs to be enabled)</comment>\n"
+"&lt;M&gt; Sound card support\n"
+"\n"
+"<comment>(Make sure OSS is disabled)</comment>\n"
+"Open Sound System ---&gt;\n"
+" &lt; &gt; Open Sound System (DEPRECATED)\n"
+"\n"
+"<comment>(Move one step back and enter ALSA)</comment>\n"
+"Advanced Linux Sound Architecture ---&gt;\n"
+" &lt;M&gt; Advanced Linux Sound Architecture\n"
+" <comment>(Select this if you want MIDI sequencing and routing)</comment>\n"
+" &lt;M&gt; Sequencer support\n"
+" <comment>(Old style /dev/mixer* and /dev/dsp* support. Recommended.)</comment>\n"
+" &lt;M&gt; OSS Mixer API\n"
+" &lt;M&gt; OSS PCM (digital audio) API \n"
+"\n"
+"<comment>(You now have a choice of devices to enable support for. Generally,\n"
+"you will have one type of device and not more. If you have more than one\n"
+"sound card, please enable them all here.)</comment>\n"
+"\n"
+"<comment>(Mostly for testing and development purposes, not needed for normal\n"
+"users unless you know what you are doing.)</comment>\n"
+"Generic devices ---&gt;\n"
+" \n"
+"<comment>(For ISA Sound cards)</comment>\n"
+"ISA devices ---&gt;\n"
+"<comment>(IF you had the Gravis, you would select this option)</comment>\n"
+" &lt;M&gt; Gravis UltraSound Extreme\n"
+"\n"
+"<comment>(Move one level back and into PCI devices. Most sound cards today are\n"
+"PCI devices)</comment>\n"
+"PCI devices ---&gt;\n"
+" <comment>(We now select the emu10k1 driver for our card)</comment>\n"
+" &lt;M&gt; Emu10k1 (SB Live!, Audigy, E-mu APS)\n"
+" <comment>(Or an Intel card would be)</comment>\n"
+" &lt;M&gt; Intel/SiS/nVidia/AMD/ALi AC97 Controller\n"
+" <comment>(Or if you have a VIA Card)</comment>\n"
+" &lt;M&gt; VIA 82C686A/B, 8233/8235 AC97 Controller\n"
+"\n"
+"<comment>(Move one level back and select in case you have an USB sound card)</comment>\n"
+"USB Devices ---&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):233
+msgid ""
+"Now that your options are set, you can (re)compile the kernel and ALSA "
+"support for your card should be functional once you reboot into the new "
+"kernel. Don't forget to update your GRUB configuration to use the newly "
+"built kernel. You can now proceed to <uri link=\"#alsa-utilities\">ALSA "
+"Utilities</uri> and see if everything is working as it should."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):246
+msgid "Configuring/Testing ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):248
+msgid "ALSA Utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):251
+msgid ""
+"<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of "
+"programs that are highly useful, including the ALSA Initscripts. Hence we "
+"strongly recommend that you install <c>alsa-utils</c>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):257
+msgid "Install alsa-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):257
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge alsa-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):261
+msgid ""
+"If you did <e>not</e> compile ALSA as modules, please proceed to the <uri "
+"link=\"#initscript\">ALSA Initscript</uri> section. The rest of you need to "
+"configure ALSA. This is made very easy by the existence of the <c>alsaconf</"
+"c> tool provided by <c>alsa-utils</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):271
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):274
+msgid ""
+"Recent versions of <c>udev</c> (<c>&gt;=udev-103</c>) provide some degree of "
+"kernel-level autoconfiguration of your sound card. If possible, try to rely "
+"on just letting your kernel automatically setup your sound card for you. "
+"Otherwise, use <c>alsaconf</c> to configure your card, as shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):281
+msgid ""
+"Please shut down any programs that <e>might</e> access the sound card while "
+"running <c>alsaconf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):286
+msgid ""
+"To configure your sound card just type <c>alsaconf</c> in a shell as root."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):290
+msgid "Invoking alsaconf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>alsaconf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):294
+msgid ""
+"You will now see a neat menu guided interface that will automatically probe "
+"your devices and try to find out your sound card. You will be asked to pick "
+"your sound card from a list. Once that's done, it will ask you permission to "
+"automatically make required changes to <path>/etc/modprobe.d/alsa.conf</"
+"path>. It will then adjust your volume settings to optimum levels, run "
+"<c>update-modules</c> and start the <path>/etc/init.d/alsasound</path> "
+"service. Once <c>alsaconf</c> exits, you can proceed with setting up the "
+"ALSA initscript."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):308
+msgid "ALSA Initscript"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):311
+msgid ""
+"We're now almost all setup. Whichever method you chose to install ALSA, "
+"you'll need to have something load your modules or initialize ALSA and "
+"restore your volume settings when your system comes up. The ALSA Initscript "
+"handles all of this for you and is called <c>alsasound</c>. Add it to the "
+"boot runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):318
+msgid "Adding ALSA to the boot runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):318
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add alsasound boot</i>\n"
+" * alsasound added to runlevel boot\n"
+" * rc-update complete.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):324
+msgid ""
+"Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that "
+"SAVE_ON_STOP variable is set to yes. This saves your sound settings when you "
+"shutdown your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):333
+msgid "Audio Group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):336
+msgid ""
+"Before we move on to testing, there's one last <e>important</e> thing that "
+"needs to be setup. Rule of thumb in a *nix OS: Do not run as root unless "
+"needed. This applies here as well ;) How? Well, most of the times you should "
+"be logged in as a user and would like to listen to music or access your "
+"soundcard. For that to happen, you need to be in the \"audio\" group. At "
+"this point, we'll add users to the audio group, so that they won't have any "
+"issues when they want to access sound devices. We'll use <c>gpasswd</c> here "
+"and you need to be logged in as root for this to work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):347
+msgid "Adding users to the audio group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):347
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Substitute &lt;username&gt; with your user)</comment>\n"
+"# <i>gpasswd -a &lt;username&gt; audio </i>\n"
+"Adding user &lt;username&gt; to group audio\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):356
+msgid "Volume Check!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):359
+msgid ""
+"We've completed all the setups and prerequisites, so let's fire up ALSA. If "
+"you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> "
+"already does this for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):365
+msgid "Start the service"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):365
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/alsasound start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):369
+msgid ""
+"Now that the required things have been taken care of, we need to check up on "
+"the volume as in certain cases, it is muted. We use <c>alsamixer</c> for "
+"this purpose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):375
+msgid "Starting alsamixer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):375
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Opens up a console program. Only required settings are shown)</comment>\n"
+"# <i>alsamixer</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):380
+msgid ""
+"This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay "
+"attention to the Master and PCM channels which both have an MM below them. "
+"That means they are muted. If you try to play anything with <c>alsamixer</c> "
+"in this state, you will not hear anything on your speakers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:link):387
+msgid "/images/docs/alsa-mixermuted.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:short):387
+msgid "AlsaMixer Muted"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:caption):387
+msgid "The Alsa Mixer Main Window, Muted"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):389
+msgid "Now, we shall unmute the channels, and set volume levels as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(warn):393
+msgid ""
+"Both Master <e>and</e> PCM need to be unmuted and set to audible volume "
+"levels if you want to hear some output on your speakers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(li):399
+msgid ""
+"To move between channels, use your left and right arrow keys. (&lt;- &amp; -"
+"&gt;)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(li):403
+msgid ""
+"To toggle mute, move to the specific channel, for example Master and press "
+"the <e>m</e> key on the keyboard."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(li):407
+msgid ""
+"To increase and decrease the volume levels, use the up and down arrow keys "
+"respectively."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):413
+msgid ""
+"Be careful when setting your Bass and Treble values. 50 is usually a good "
+"number for both. Extremely high values of Bass may cause <e>jarring</e> on "
+"speakers that are not designed to handle them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):419
+msgid ""
+"After you're all done, your ALSA Mixer should look similar to the one below. "
+"Note the 00 instead of the MM and also the volume levels for some optimum "
+"settings."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:link):425
+msgid "/images/docs/alsa-mixerunmuted.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:short):425
+msgid "AlsaMixer Unmuted"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(figure:caption):425
+msgid "Alsa Mixer ready to roll"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):430
+msgid "Sound Check!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):433
+msgid ""
+"Finally. Some music. If everything above is perfect, you should now be able "
+"to listen to some good music. A quick way to test is to use a command line "
+"tool like <c>media-sound/madplay</c>. You could also use something more well "
+"known like <c>mpg123</c>. If you are an ogg fan, you could use <c>ogg123</c> "
+"provided by <c>media-sound/vorbis-tools</c>. Use any player you are "
+"comfortable with. As always, <c>emerge</c> what you need."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):442
+msgid "Getting the software"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):442
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Install the applications you want)</comment>\n"
+"# <i>emerge madplay mpg123</i>\n"
+"<comment>(To play .ogg files)</comment>\n"
+"# <i>emerge vorbis-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):449
+msgid "And then play your favorite sound track..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):453
+msgid "Playing Music"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):453
+#, no-wrap
+msgid ""
+"\n"
+"# <i>madplay -v /mnt/shyam/Music/Paul\\ Oakenfold\\ -\\ Dread\\ Rock.mp3</i>\n"
+"MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.\n"
+" Title: Dread Rock\n"
+" Artist: Paul Oakenfold\n"
+" Album: Matrix Reloaded\n"
+" Year: 2003\n"
+" Genre: Soundtrack\n"
+" Soundtrack\n"
+" 00:04:19 Layer III, 160 kbps, 44100 Hz, joint stereo (MS), no CRC\n"
+"\n"
+"# <i>ogg123 Paul\\ Oakenfold\\ -\\ Dread\\ Rock.ogg</i>\n"
+"Audio Device: Advanced Linux Sound Architecture (ALSA) output\n"
+"\n"
+"Playing: Paul Oakenfold - Dread Rock.ogg\n"
+"Ogg Vorbis stream: 2 channel, 44100 Hz\n"
+"Genre: Soundtrack\n"
+"Transcoded: mp3;160\n"
+"Title: Dread Rock\n"
+"Artist: Paul Oakenfold\n"
+"Date: 2003\n"
+"Album: Matrix Reloaded\n"
+"Time: 00:11.31 [04:28.75] of 04:40.06 (200.6 kbps) Output Buffer 96.9%\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):481
+msgid "ALSA and USE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):484
+msgid ""
+"You can now add the <c>alsa</c> use flag to <path>/etc/make.conf</path> to "
+"ensure that your applications that support ALSA get built with it. Some "
+"architectures like x86 and amd64 have the flag enabled by default."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):493
+msgid "Issues?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):496
+msgid ""
+"If for some reason you're unable to hear sound, the first thing to do would "
+"be to check your <uri link=\"#doc_chap3_pre6\">alsamixer</uri> settings. 80% "
+"of the issues lie with muted channels or low volume. Also check your Window "
+"Manager's sound applet and verify that volumes are set to audible levels."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):503
+msgid ""
+"<path>/proc</path> is your friend. And in this case, <path>/proc/asound</"
+"path> is your best friend. We shall just take a short look at how much info "
+"is made available to us there."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):509
+msgid "Fun with /proc/asound"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):509
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has\n"
+"picked up your sound card fine.)</comment>\n"
+"# <i>cat /proc/asound/cards</i>\n"
+"0 [Live ]: EMU10K1 - Sound Blaster Live!\n"
+" Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11\n"
+"\n"
+"<comment>(This displays the current running ALSA version)</comment>\n"
+"# <i>cat /proc/asound/version</i>\n"
+"Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 2005 UTC).\n"
+"\n"
+"<comment>(ALSA OSS emulation details)</comment>\n"
+"# <i>cat /proc/asound/oss/sndstat</i>\n"
+"Sound Driver:3.8.1a-980706 (ALSA v1.0.8 emulation code)\n"
+"Kernel: Linux airwolf.zion 2.6.11ac1 #2 Wed May 4 00:35:08 IST 2005 i686\n"
+"Config options: 0\n"
+"\n"
+"Installed drivers:\n"
+"Type 10: ALSA emulation\n"
+"\n"
+"Card config:\n"
+"Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11\n"
+"\n"
+"Audio devices:\n"
+"0: EMU10K1 (DUPLEX)\n"
+"\n"
+"Synth devices: NOT ENABLED IN CONFIG\n"
+"\n"
+"Midi devices:\n"
+"0: EMU10K1 MPU-401 (UART)\n"
+"\n"
+"Timers:\n"
+"7: system timer\n"
+"\n"
+"Mixers:\n"
+"0: SigmaTel STAC9721/23\n"
+msgstr ""
+
+#. TODO: remove this a few months after alsa-driver leaves the tree
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):549
+msgid ""
+"The other most common issue users face is the dreaded \"Unknown symbol in "
+"module\" error. An example of the same is shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):554
+msgid "Unknown Symbol in module error"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):554
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/alsasound start</i>\n"
+" * Loading ALSA modules ...\n"
+" * Loading: snd-card-0 ... [ ok ]\n"
+" * Loading: snd-pcm-oss ...\n"
+"WARNING: Error inserting snd_mixer_oss\n"
+"(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown\n"
+"symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting\n"
+"snd_pcm_oss\n"
+"(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-pcm-oss.ko): Unknown\n"
+"symbol in module, or unknown parameter (see dmesg) \n"
+" [ !! ]\n"
+" * Loading: snd-mixer-oss ...\n"
+"FATAL: Error inserting snd_mixer_oss\n"
+"(/lib/modules/2.6.12-gentoo-r6/kernel/sound/core/oss/snd-mixer-oss.ko): Unknown\n"
+"symbol in module, or unknown parameter (see dmesg) \n"
+" [ !! ]\n"
+" * Loading: snd-seq ... [ ok ]\n"
+" * Loading: snd-emu10k1-synth ... [ ok ]\n"
+" * Loading: snd-seq-midi ... [ ok ]\n"
+" * Restoring Mixer Levels ... [ ok ]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):577
+msgid ""
+"And when you take a look at <c>dmesg</c> as suggested, you're quite likely "
+"to see:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):582
+msgid "dmesg output"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):582
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Only relevant portions are shown below)</comment>\n"
+"# <i>dmesg | less</i>\n"
+"ACPI: PCI Interrupt 0000:02:06.0[A] -&gt; Link [APC3] -&gt; GSI 18 (level, low) -&gt; IRQ 209\n"
+"snd_mixer_oss: Unknown symbol snd_unregister_oss_device\n"
+"snd_mixer_oss: Unknown symbol snd_register_oss_device\n"
+"snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback\n"
+"snd_mixer_oss: Unknown symbol snd_oss_info_register\n"
+"snd_pcm_oss: Unknown symbol snd_unregister_oss_device\n"
+"snd_pcm_oss: Unknown symbol snd_register_oss_device\n"
+"snd_pcm_oss: Unknown symbol snd_mixer_oss_ioctl_card\n"
+"snd_pcm_oss: Unknown symbol snd_oss_info_register\n"
+"snd_mixer_oss: Unknown symbol snd_unregister_oss_device\n"
+"snd_mixer_oss: Unknown symbol snd_register_oss_device\n"
+"snd_mixer_oss: Unknown symbol snd_mixer_oss_notify_callback\n"
+"snd_mixer_oss: Unknown symbol snd_oss_info_register\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):600
+msgid ""
+"The above issue is caused when you switch from the <c>alsa-driver</c> to in-"
+"kernel ALSA because when you unmerge <c>alsa-driver</c> the module files are "
+"config protected and hence get left behind. So, when you switch to in-kernel "
+"drivers, running <c>modprobe</c> gives you a mix of <c>alsa-driver</c> and "
+"in-kernel modules thus causing the above errors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):608
+msgid ""
+"The solution is quite easy. We just need to manually remove the problem "
+"causing directory after you unmerge <c>alsa-driver</c>. Be sure to remove "
+"the correct kernel version and not the current one!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):614
+msgid "Removing the alsa-driver modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):614
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm -rf /lib/modules/$(uname -r)/alsa-driver</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):618
+msgid ""
+"Another reason for error messages similar to the ones above could be a file "
+"in <path>/etc/modprobe.d</path> supplying a <c>device_mode</c> parameter "
+"when it isn't required. Confirm that this is indeed the issue and find out "
+"which file is the culprit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):625
+msgid "Confirming and searching for device_mode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):625
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check dmesg to confirm)</comment>\n"
+"# <i>dmesg | grep device_mode</i>\n"
+"snd: Unknown parameter `device_mode'\n"
+"<comment>(Now, to get to the source of the issue)</comment>\n"
+"# <i>grep device_mode /etc/modprobe.d/*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):633
+msgid ""
+"Usually it is a file called <path>alsa</path> with the line <c>options snd "
+"device_mode=0666</c>. Remove this line and restart the <c>alsasound</c> "
+"service and that should take care of this issue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):646
+msgid "Other things ALSA"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):648
+msgid "Setting up MIDI support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):651
+msgid ""
+"First, check to make sure that you enabled the <c>midi</c> USE flag in "
+"<path>/etc/make.conf</path>. If you didn't, go ahead and add it now. You "
+"will also need to re-emerge any ALSA packages that use the <c>midi</c> flag, "
+"such as <c>alsa-lib</c> and <c>alsa-utils</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):658
+msgid ""
+"If your sound card is one of those that come with on-board MIDI synthesizers "
+"and you would like to listen to some .mid files, you have to install "
+"<c>awesfx</c> which is basically a set of utilities for controlling the "
+"AWE32 driver. We need to install it first. If you don't have a hardware "
+"synthesizer, you can use a virtual one. Please see the section on <uri link="
+"\"#vsynth\">Virtual Synthesizers</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):667
+msgid "Installing awesfx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):667
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge awesfx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):671
+msgid ""
+"You will need to copy over SoundFont (SF2) files from your sound card's "
+"driver CD or a Windows installation into <path>/usr/share/sounds/sf2/</"
+"path>. For example a sound font file for the Creative SBLive! card would be "
+"8MBGMSFX.SF2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):677
+msgid ""
+"After copying over the Soundfont files, we can then play a midi file as "
+"shown. You can also add the <c>asfxload</c> command to <path>/etc/conf.d/"
+"local.start</path>, so that the sound font is loaded every time the system "
+"starts up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(note):684
+msgid ""
+"<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</"
+"e> be the same in your machine. They are just an example. Please be careful "
+"to change the path to suit your machine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):690
+msgid "Loading Soundfonts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):690
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(First, copy the Soundfont)</comment>\n"
+"# <i>cp /mnt/win2k/Program\\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i> \n"
+"<comment>(Or get it from your SoundBlaster CD)</comment>\n"
+"# <i>cp /mnt/cdrom/AUDIO/ENGLISH/SFBANK/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>\n"
+"<comment>(We load the specific Soundfont)</comment>\n"
+"# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):699
+msgid ""
+"You can now play midi files using a program like <c>aplaymidi</c>. Run "
+"<c>aplaymidi -l</c> to get a list of available ports and then pick one to "
+"play the file on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):705
+msgid "Playing MIDI"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):705
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check open ports)</comment>\n"
+"# <i>aplaymidi -l</i>\n"
+" Port Client name Port name\n"
+" 64:0 EMU10K1 MPU-401 (UART) EMU10K1 MPU-401 (UART)\n"
+" 65:0 Emu10k1 WaveTable Emu10k1 Port 0\n"
+" 65:1 Emu10k1 WaveTable Emu10k1 Port 1\n"
+" 65:2 Emu10k1 WaveTable Emu10k1 Port 2\n"
+" 65:3 Emu10k1 WaveTable Emu10k1 Port 3\n"
+"<comment>(Pick a port, and play a mid file)</comment>\n"
+"# <i> aplaymidi --port=65:0 /mnt/shyam/music/midi/mi2.mid</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):721
+msgid "Virtual Synthesizers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):724
+msgid ""
+"If your sound card lacks a hardware synthesizer, you could use a virtual one "
+"like <c>timidity++</c>. Installation is a breeze."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):729
+msgid "Installing timidity++"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):729
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge timidity++</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):733
+msgid ""
+"For timidity to play sounds, it needs a sound font. Fortunately, the ebuild "
+"will install some sound font packages for you. There are a few other font "
+"packages available in Portage, such as <c>timidity-freepats</c> and "
+"<c>timidity-eawpatches</c>. You can have multiple sound font configurations "
+"installed, and you can place your own in <path>/usr/share/timidity/</path>. "
+"To switch between different timidity configurations, you should use "
+"<c>eselect</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):743
+msgid "Changing configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):743
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect timidity list</i>\n"
+"# <i>eselect timidity set eawpatches</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):748
+msgid "Don't forget to add <c>timidity</c> to the default runlevel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):752
+msgid "Adding timidity to the default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):752
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add timidity default</i>\n"
+"# <i>/etc/init.d/timidity start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):757
+msgid ""
+"You can now try out <uri link=\"#doc_chap4_pre3\">Playing MIDI</uri> files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):764
+msgid "Tools and Firmware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):767
+msgid ""
+"Some specific sound cards can benefit from certain tools provided by the "
+"<c>alsa-tools</c> and <c>alsa-firmware</c> packages. You may install either "
+"with a simple <c>emerge</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):773
+msgid "Installing ALSA Tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):773
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge alsa-tools</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):780
+msgid "Multiple sound cards"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):783
+msgid ""
+"You can have more than one sound card in your system simultaneously, "
+"provided that you have built ALSA as modules in your kernel. You just need "
+"to specify which should be started first in <path>/etc/modprobe.d/alsa.conf</"
+"path>. Your cards are identified by their driver names inside this file. 0 "
+"is the first card, 1 is the second, and so on. Here's an example for a "
+"system with two sound cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):791
+msgid "Two sound cards in /etc/modprobe.d/alsa.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):791
+#, no-wrap
+msgid ""
+"\n"
+"options snd-emu10k1 index=0\n"
+"options snd-via82xx index=1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):796
+msgid ""
+"Or, if you have two cards that use the same driver, you specify them on the "
+"same line, using comma-separated numbers. Here's an example for a system "
+"with three sound cards, two of which are the same Intel High Definition "
+"Audio card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):802
+msgid "Multiple sound cards in /etc/modprobe.d/alsa.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):802
+#, no-wrap
+msgid ""
+"\n"
+"options snd-ymfpci index=0\n"
+"options snd-hda-intel index=1,2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):810
+msgid "Plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):813
+msgid ""
+"You may want to install some plugins for extra functionality. <c>alsa-"
+"plugins</c> is a collection of useful plugins, which include: PulseAudio "
+"output, a sample rate converter, jack (a low-latency audio server), and an "
+"encoder that lets you output 6-channel audio through digital S/PDIF "
+"connections (both optical and coaxial). You can choose which of its plugins "
+"you want installed by adding their USE flags to <path>/etc/portage/package."
+"use</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre:caption):822
+msgid "Installing alsa-plugins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(pre):822
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -avt alsa-plugins</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):829
+msgid "A big thank you to..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(p):832
+msgid ""
+"Everyone who contributed to the earlier version of the Gentoo ALSA Guide: "
+"Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston, John P. "
+"Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(title):841
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri:link):845
+msgid "http://www.alsa-project.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri):845
+msgid "The ALSA Project"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri:link):846
+msgid "http://linux-sound.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(uri):846
+msgid "Linux Sound/MIDI Software"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//alsa-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/altinstall.xml.po b/doc/gettext/el/altinstall.xml.po
new file mode 100644
index 0000000..9205643
--- /dev/null
+++ b/doc/gettext/el/altinstall.xml.po
@@ -0,0 +1,1030 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2011-01-21 01:40+0500\n"
+"PO-Revision-Date: 2011-01-21 01:40+0500\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):6
+msgid "The Gentoo Linux alternative installation method HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):17
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):23
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):26
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):29
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):9
+msgid "gerrynjr@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):9
+msgid "Gerald Normandin Jr."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):12
+msgid "lordviram@rebelpacket.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):12
+msgid "Travis Tilley"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):15
+msgid "volontir@yahoo.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):15
+msgid "Oleg Raisky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):18
+msgid "luminousit@hotmail.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):18
+msgid "Alex Garbutt"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):21
+msgid "alex@openvs.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):21
+msgid "Alexandre Georges"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):24
+msgid "vargen@b0d.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):24
+msgid "Magnus Backanda"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):27
+msgid "davoid@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):27
+msgid "Faust A. Tanasescu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):30
+msgid "aliz@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):30
+msgid "Daniel Ahlberg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):32
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):38
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):41
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):44
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):47
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):33
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):33
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author:title):35
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(author):35
+msgid "Ken Nowack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):39
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):39
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):42
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):42
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):45
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail):45
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(mail:link):48
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(abstract):51
+msgid ""
+"This HOWTO is meant to be a repository of alternative Gentoo installation "
+"methods, for those with special installation needs such as lack of a cdrom "
+"or a computer that can't boot cds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(version):61
+msgid "7"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(date):62
+msgid "2010-10-31"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):65
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):69
+msgid ""
+"If the standard boot-from-CD install method doesn't work for you (or you "
+"just don't like it), help is now here. This document serves to provide a "
+"repository of alternative Gentoo Linux installation techniques to those who "
+"need them. Or, if you prefer, it serves as a place to put your wacky "
+"installation methods. If you have an installation method that you yourself "
+"find useful, or you have devised an amusing way of installing Gentoo, please "
+"don't hesitate to write something up and post it on <uri link=\"http://bugs."
+"gentoo.org\">Bugzilla</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):84
+msgid "Booting the Install CD with Smart BootManager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):88
+msgid ""
+"Download Smart BootManager available from <uri>http://btmgr.sourceforge.net/"
+"download.html</uri>. Linux source or binary format and windows .exe versions "
+"are available as well as many language packs. However, at this time, the "
+"preferred method would be to use the binary format, as the source will not "
+"compile with newer versions of NASM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):97
+msgid ""
+"Either compile the package from source or just grab the binary. There are "
+"several options that can be utilized while creating your boot floppy, as "
+"seen below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):103
+msgid "Smart BootManager Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):103
+#, no-wrap
+msgid ""
+"\n"
+"sbminst [-t theme] [-d drv] [-b backup_file] [-u backup_file]\n"
+"\n"
+" -t theme select the theme to be used, in which the theme could be:\n"
+" us = English theme de = German theme\n"
+" hu = Hungarian theme zh = Chinese theme\n"
+" ru = Russian theme cz = Czech theme\n"
+" es = Spanish theme fr = French theme\n"
+" pt = Portuguese theme\n"
+"\n"
+"\n"
+" -d drv set the drive that you want to install Smart BootManager on;\n"
+" for Linux:\n"
+" /dev/fd0 is the first floppy driver,\n"
+" /dev/hda is the first IDE harddisk driver.\n"
+" /dev/sda is the first SCSI harddisk driver.\n"
+" for DOS:\n"
+" 0 is the first floppy drive\n"
+" 128 is the first hard drive;\n"
+"\n"
+" -c disable CD-ROM booting feature;\n"
+"\n"
+" -b backup_file backup the data that will be overwritten for\n"
+" future uninstallation;\n"
+"\n"
+" -u backup_file uninstall Smart BootManager, should be used alone;\n"
+"\n"
+" -y do not ask any question or warning.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):133
+msgid "Using sbminst to build the boot floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):133
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sbminst -t us -d /dev/fd0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):137
+msgid ""
+"Replace <path>fd0</path> with your respective floppy device name if yours is "
+"different."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):142
+msgid ""
+"Now simply place the floppy in the floppy drive of the computer you'd like "
+"to boot the Install CD on, as well as placing the Install CD in the CD-ROM "
+"and boot the computer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):148
+msgid ""
+"You'll be greeted with the Smart BootManager dialog. Select your CD-ROM and "
+"press ENTER to boot the Install CD. Once booted proceed with the standard "
+"installation instructions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):154
+msgid ""
+"Further information on Smart BootManager may be found at <uri>http://btmgr."
+"sourceforge.net/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):164
+msgid "Installation from non-Gentoo LiveCDs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):166
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(impo):169
+msgid ""
+"The Gentoo developers cannot support you if something goes wrong with a non-"
+"Gentoo LiveCD, as there's no way to fix, troubleshoot, or document every "
+"quirk of every LiveCD out there. Only Gentoo LiveCDs are officially "
+"supported. If you run into problems with alternative installation media, "
+"please visit the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> "
+"for community help."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):177
+msgid ""
+"It is possible to boot some other LiveCD besides the Gentoo-provided CDs. "
+"This will give you a functional environment to use while you're compiling "
+"and installing Gentoo. The instructions provided here should work in "
+"principle with just about any other LiveCD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):184
+msgid ""
+"There are too many LiveCDs out there to <uri link=\"http://distrowatch.com/"
+"search.php\">list</uri>, but you might try <uri link=\"http://www.knoppix."
+"org/\">Knoppix</uri>. It provides a full graphical desktop, with office "
+"applications, web browsers, and games to keep you busy. Knoppix is only "
+"available for x86 users, so depending on your needs you may need to find a "
+"different LiveCD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(warn):193
+msgid ""
+"Be aware that if you save anything in your LiveCD's home directory while "
+"waiting for your Gentoo system to install, it will not be available when you "
+"reboot into Gentoo. Be sure to save important files on the hard disk or on "
+"some other computer!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):203
+msgid "Installation instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):206
+msgid ""
+"Boot from your LiveCD. Open a terminal and run <c>su -</c> so you can change "
+"your password. This lets you set the root password for the CD. You can now "
+"configure <c>sshd</c> for remote login, if you need to install Gentoo "
+"remotely. Next, you'll need to create the <path>/mnt/gentoo</path> "
+"mountpoint."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):213
+msgid "Creating the /mnt/gentoo mountpoint"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):213
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):217
+msgid ""
+"At this point, you can pick up with the standard install documentation at "
+"<uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=4\">part 4</"
+"uri>. However, when you are asked to mount the proc system, issue the "
+"following command instead:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):224
+msgid "Bind-mounting the proc pseudo filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount -o bind /proc /mnt/gentoo/proc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):228
+msgid ""
+"When you're ready to unpack the stage tarball in <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml?part=1&amp;chap=5#doc_chap2_sect2\">part 5</uri>, "
+"you will need to use a different <c>tar</c> command to ensure that proper "
+"group IDs are enforced on the unpacked stage:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):235
+msgid "Unpacking the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tar --numeric-owner -xvjpf stage3-*.tar.bz2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):239
+msgid ""
+"Once you're ready to chroot into your unpacked stage in <uri link=\"/doc/en/"
+"handbook/handbook-x86.xml?part=1&amp;chap=6#doc_chap1\">part 6</uri>, you "
+"will need to use a different chroot command sequence. This ensures that your "
+"environment variables are properly setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):246
+msgid "Chrooting into the new environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):246
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Some LiveCDs use a funny environment setup, hence the -i option for\n"
+"cleaning it up to a reasonable state.)</comment>\n"
+"# <i>chroot /mnt/gentoo /bin/env -i TERM=$TERM /bin/bash</i>\n"
+"# <i>env-update</i>\n"
+"# <i>source /etc/profile</i>\n"
+"# <i>export PS1=\"(chroot) $PS1\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):255
+msgid ""
+"Finally, know that some Portage FEATURES may not work in your LiveCD. "
+"Especially watch out for <c>userpriv</c> and <c>usersandbox</c>. If you find "
+"yourself getting errors, it might be wise to disable some or all of the "
+"optional FEATURES."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):290
+msgid "Diskless install using PXE boot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):292
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):555
+msgid "Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):295
+msgid ""
+"You will need a network card on the diskless client that uses the PXE "
+"protocol to boot, like many 3com cards. You will also need a BIOS that "
+"supports booting from PXE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):304
+msgid "Server base setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):307
+msgid ""
+"Create directories: The first thing to do is to create the directories where "
+"your diskless system will be stored. Create a directory called <path>/"
+"diskless</path> which houses a directory for each diskless client. For the "
+"rest of this howto we'll be working on the client 'eta'."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):314
+msgid "Directory setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):314
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /diskless</i>\n"
+"# <i>mkdir /diskless/eta</i>\n"
+"# <i>mkdir /diskless/eta/boot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):320
+msgid ""
+"DHCP and TFTP setup: The client will get boot informations using DHCP and "
+"download all the required files using TFTP."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):325
+msgid ""
+"For dhcpd, just run <c>emerge dhcp</c> (or any other DHCP server of your "
+"choice). Make sure that the correct interface is selected in <path>/etc/conf."
+"d/dhcpd</path>, and configure it for your basic needs. Then, add the "
+"following on <path>/etc/dhcp/dhcpd.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):332
+msgid ""
+"This provides a static IP address for the client and the path of a PXE boot "
+"image, here <path>pxegrub</path>. You have to replace the MAC address of the "
+"ethernet card of the client and the directory where you will put the client "
+"files with the one you use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):339
+msgid "dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):339
+#, no-wrap
+msgid ""
+"\n"
+"option option-150 code 150 = text ;\n"
+"ddns-update-style none ;\n"
+"host eta {\n"
+"hardware ethernet 00:00:00:00:00:00;\n"
+"fixed-address <i>ip.add.re.ss</i>;\n"
+"option option-150 \"/eta/boot/grub.lst\";\n"
+"filename \"/eta/boot/pxegrub\";\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):350
+msgid ""
+"Next you'll need to configure your interface in <path>/etc/conf.d/net</path> "
+"so that it doesn't get cleared at bootup. See <path>/etc/conf.d/net.example</"
+"path> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):356
+msgid "/etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):356
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace eth0 with the correct interface)</comment>\n"
+"config_eth0=( \"noop\" )\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):361
+msgid ""
+"For TFTP, emerge <c>app-admin/tftp-hpa</c>. In <path>/etc/conf.d/in.tftpd</"
+"path>, put the following :"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):366
+msgid "in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):366
+#, no-wrap
+msgid ""
+"\n"
+"INTFTPD_PATH=\"/diskless\"\n"
+"INTFTPD_USER=\"nobody\"\n"
+"INTFTPD_OPTS=\"-u ${INTFTPD_USER} -l -vvvvvv -p -c -s ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):372
+msgid ""
+"Setup GRUB: To provide PXE booting I use GRUB with the <c>netboot</c> USE "
+"flag enabled. Once GRUB is compiled, copy the PXE image to the diskless "
+"client's boot directory. Then edit its <path>grub.lst</path> config file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):378
+msgid "Grub setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):378
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"sys-boot/grub netboot\" &gt;&gt; /etc/portage/package.use</i>\n"
+"# <i>emerge -av grub</i>\n"
+"# <i>cp /usr/lib/grub/pxegrub /diskless/eta/boot/pxegrub</i>\n"
+"# <i>nano -w /diskless/eta/boot/grub.lst</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):385
+msgid "grub.lst"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):385
+#, no-wrap
+msgid ""
+"\n"
+"default 0\n"
+"timeout 30\n"
+"\n"
+"title=Diskless Gentoo\n"
+"root (nd)\n"
+"kernel /eta/bzImage ip=dhcp root=/dev/nfs nfsroot=<i>ip.add.re.ss</i>:/diskless/eta\n"
+"\n"
+"<comment># For the nfsroot option, the IP address is the one of the server and\n"
+"the directory is the one where your diskless client files are located (on the server).</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):397
+msgid ""
+"Setup NFS: NFS is quite easy to configure. The only thing you have to do is "
+"to add a line on the <path>/etc/exports</path> config file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):402
+msgid "/etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):402
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/exports</i>\n"
+"# /etc/exports: NFS file systems being exported. See exports(5).\n"
+"/diskless/eta eta(rw,sync,no_root_squash)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):408
+msgid ""
+"Update your hosts: One important thing to do now is to modify your <path>/"
+"etc/hosts</path> file to fit your needs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):413
+msgid "/etc/hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):413
+#, no-wrap
+msgid ""
+"\n"
+"127.0.0.1 localhost\n"
+"\n"
+"192.168.1.10 eta.example.com eta\n"
+"192.168.1.20 sigma.example.com sigma\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):423
+msgid "Creating the system on the server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):426
+msgid ""
+"You might want to reboot the server with a Gentoo Install CD, although you "
+"can very well continue immediately if you know how to proceed with the "
+"Gentoo Installation Instructions from an existing installation. Follow the "
+"standard install procedure as explained in the <uri link=\"/doc/en/handbook/"
+"\">Gentoo Handbook</uri> BUT with the following differences: When you mount "
+"the file system, do the following (where <path>hdaX</path> is the partition "
+"where you created the <path>/diskless</path> directory). You do not need to "
+"mount any other partitions as all of the files will reside in the <path>/"
+"diskless/eta</path> directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):438
+msgid "Mounting the filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):438
+#, no-wrap
+msgid ""
+"\n"
+"#<i> mount /dev/hdaX /mnt/gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):442
+msgid ""
+"Stage tarballs and chroot: This example uses a stage3 tarball. Mount <path>/"
+"proc</path> to your diskless directory and chroot into it to continue with "
+"the install. Then follow the installation manual until kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(warn):449
+msgid ""
+"Be very careful where you extract your stage tarball. You don't want to end "
+"up extracting over your existing installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):454
+msgid "Extracting the stage tarball"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):454
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /mnt/gentoo/diskless/eta/</i>\n"
+"# <i>tar -xvjpf /mnt/cdrom/gentoo/stage3-*.tar.bz2</i>\n"
+"# <i>mount -t proc /proc /mnt/gentoo/diskless/eta/proc</i>\n"
+"# <i>cp /etc/resolv.conf /mnt/gentoo/diskless/eta/etc/resolv.conf</i>\n"
+"# <i>chroot /mnt/gentoo/diskless/eta/ /bin/bash</i>\n"
+"# <i>env-update</i>\n"
+"# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):464
+msgid ""
+"Kernel configuration: When you do the <c>make menuconfig</c> of your kernel "
+"configuration, don't forget to enable the following options with the others "
+"recommended into the install howto."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):470
+msgid "menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):470
+#, no-wrap
+msgid ""
+"\n"
+"- Your network card device support\n"
+"<comment>(In the kernel, *not* as a module!)</comment>\n"
+"\n"
+"- Under \"Networking options\" :\n"
+"\n"
+"[*] TCP/IP networking\n"
+"[*] IP: kernel level autoconfiguration\n"
+"[*] IP: DHCP support\n"
+"[*] IP: BOOTP support\n"
+"\n"
+"\n"
+"- Under \"File systems --&gt; Network File Systems\" :\n"
+"\n"
+"&lt;*&gt; NFS file system support\n"
+"[*] Provide NFSv3 client support\n"
+"[*] Root file system on NFS\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):489
+msgid ""
+"Save the kernel in your chrooted <path>/</path> (not in <path>/boot</path>) "
+"according to the pxegrub setting defined earlier. Next configure your "
+"diskless client's <path>/etc/fstab</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):495
+msgid "/etc/fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):495
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/fstab</i>\n"
+"/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0\n"
+"proc /proc proc defaults 0 0\n"
+"tmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):502
+msgid "You also need to prevent the client to run a filesystem check:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):506
+msgid "Preventing the client to run a filesystem check"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):506
+#, no-wrap
+msgid ""
+"\n"
+"# <i>touch /fastboot</i>\n"
+"# <i>echo \"touch /fastboot\" &gt;&gt; /etc/conf.d/local.start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):511
+msgid "Install <c>nfs-utils</c> since your client will heavily depend on it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):515
+msgid "Installing nfs-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):515
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge nfs-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):519
+msgid ""
+"Bootloader. Don't install another bootloader because we already have one - "
+"pxegrub. Simply finish the install and restart the server. Start the "
+"services you'll need to boot the new client: DHCP, TFTPD, and NFS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):525
+msgid "Starting services"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):525
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dhcp start</i>\n"
+"# <i>/etc/init.d/in.tftpd start</i>\n"
+"# <i>/etc/init.d/nfs start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):534
+msgid "Booting the new client"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):537
+msgid ""
+"For the new client to boot properly, you'll need to configure the bios and "
+"the network card to use PXE as the first boot method - before CD-ROM or "
+"floppy. For help with this consult your hardware manuals or manufacturers "
+"website. The network card should get an IP address using DHCP and download "
+"the GRUB PXE image using TFTP. Then, you should see a nice black and white "
+"GRUB bootmenu where you will select the kernel to boot and press Enter. If "
+"everything is ok the kernel should boot, mount the root filesystem using NFS "
+"and provide you with a login prompt. Enjoy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):553
+msgid "Installing Gentoo from an existing Linux distribution"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):558
+msgid ""
+"In order to install Gentoo from your existing Linux distribution you need to "
+"have chroot command installed, and have a copy of the Gentoo installation "
+"tarball or ISO you want to install. A network connection would be preferable "
+"if you want more than what's supplied in your tarball. (by the way, a "
+"tarball is just a file ending in .tbz or .tar.gz). The author used RedHat "
+"Linux 7.3 as the \"host\" operating system, but it is not very important. "
+"Let's get started!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):570
+msgid "Overview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):573
+msgid ""
+"We will first allocate a partition to Gentoo by resizing our existing Linux "
+"partition, mount the partition, untar the tarball to the partition that is "
+"mounted, chroot inside the pseudo-system and start building. Once the "
+"bootstrap process is done, we will do some final configuration on the system "
+"so as to make sure it boots, then we are ready to reboot and use Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):584
+msgid "How should we make space for Gentoo?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):587
+msgid ""
+"The root partition is the filesystem mounted under <path>/</path>. A quick "
+"run of <c>mount</c> on my system shows what I am talking about. We well also "
+"use <c>df</c> (disk free) to see how much space I have left and how I will "
+"be resizing. Note that it is not mandatory to resize your root partition! "
+"You could be resizing anything else supported by our resizer, but let's talk "
+"about that later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):596
+msgid "Filesystem information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):596
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount</i>\n"
+"/dev/hdb2 on / type ext3 (rw)\n"
+"none on /proc type proc (rw)\n"
+"none on /dev/pts type devpts (rw,gid=5,mode=620)\n"
+"none on /dev/shm type tmpfs (rw,nodev,nosuid,noexec)\n"
+"# <i>df -h </i>\n"
+"Filesystem Size Used Avail Use% Mounted on\n"
+"/dev/hdb2 4.0G 1.9G 2.4G 82% /\n"
+"none 38M 0 38M 0% /dev/shm\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):608
+msgid ""
+"As we can see, the partition mounted as <path>/</path> named <path>/dev/"
+"hdb2</path> has 2.4 gigabytes free. In my case, I think I will resize it as "
+"to leave 400Megs free of space, therefore allocating 2 gigabytes for Gentoo. "
+"Not bad, I could have quite some stuff installed. However, I think that even "
+"one gigabyte is enough for most users. So let's partition this thing!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(title):619
+msgid "Building parted to resize partition"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):622
+msgid ""
+"Parted is an utility supplied by the GNU foundation, an old and respectable "
+"huge project whose software you are using in this very moment. There is one "
+"tool, however, that is extremely useful for us at the moment. It's called "
+"parted, partition editor and we can get it from <uri>http://www.gnu.org/"
+"software/parted/</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):630
+msgid ""
+"There are other tools for doing resize of partitions as well, but the author "
+"is unsure/uninterested whether PartitionMagic(tm) or other software of the "
+"kind do the job. It's the reader's job to check them out"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):636
+msgid ""
+"Look up on that page the type of filesystem you want to resize and see if "
+"parted can do it. If not, you're out of luck, you will have to destroy some "
+"partition to make space for Gentoo, and reinstall back. Go ahead by "
+"downloading the software, install it. Here we have a problem. We want to "
+"resize our Linux root partition, therefore we must boot from a floppy disk a "
+"minimal linux system and use previously-compiled parted copied to a diskette "
+"in order to resize <path>/</path>. However, if you can unmount the partition "
+"while still in Linux you are lucky, you don't need to do what follows. Just "
+"compile parted and run it on an unmounted partition you chose to resize. "
+"Here's how I did it for my system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(impo):649
+msgid ""
+"Make sure that the operations you want to do on your partition are supported "
+"by parted!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):654
+msgid ""
+"Get the mininux boot/root disk (a 2.4-powered mini Linux distribution on a "
+"floppy - free of charge) from <uri>http://mininux.free.fr/uk/</uri>, create "
+"a floppy as suggested in the Documentation that accompanies the software "
+"package and insert a new floppy in the drive for the next step."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(note):661
+msgid ""
+"Note again that Linux is synonym of \"There's one more way to do it\". Your "
+"objective is to run parted on an unmounted partition so it can do its work. "
+"You might use some boot/root diskset other than mininux. You might not even "
+"need to do this step at all, ie. you might only have umount the filesystem "
+"you want to repartition in your Linux session and run parted on it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):669
+msgid "Utility disk creation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):669
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkfs.minix /dev/fd0</i>\n"
+"480 inodes\n"
+"1440 blocks\n"
+"Firstdatazone=19 (19)\n"
+"Zonesize=1024\n"
+"Maxsize=268966912\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):678
+msgid ""
+"We will now proceed with the build of parted. If it's not already downloaded "
+"and untarred, do so now and <c>cd</c> into the corresponding directory. Now "
+"run the following set of commands to build the utility and copy it to your "
+"floppy disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):685
+msgid "Building the utility floppy"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):685
+#, no-wrap
+msgid ""
+"\n"
+"# <i> mkdir /floppy; mount -t minix /dev/fd0 /floppy &amp;&amp;\n"
+"export CFLAGS=\"-O3 -pipe -fomit-frame-pointer -static\" &amp;&amp; ./configure\n"
+"&amp;&amp; make &amp;&amp; cp parted/parted /floppy &amp;&amp; umount /floppy </i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):691
+msgid ""
+"Congratulations, you are ready to reboot and resize your partition. Do this "
+"only after taking a quick look at the parted documentation on the GNU "
+"website. The resize should take under 30 minutes for the largest hard-"
+"drives, be patient. Reboot your system with the mininux boot disk (just pop "
+"it inside), and once you are logged in, switch the disk in the drive with "
+"your utility disk we have created above and type <c>mount /dev/fd0 /floppy</"
+"c> to have parted under <path>/floppy</path>. There you go. Run parted and "
+"you will be able to resize your partition. Once this lenghty process done, "
+"we are ready to have the real fun, by installing Gentoo. Reboot back into "
+"your old Linux system for now. The drive you wish to operate on is the drive "
+"containing the partition we want to resize. For example, if we want to "
+"resize /dev/hda3, the drive is /dev/hda."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):705
+msgid "Commands to run once logged into mininux system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):705
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mount /dev/fd0 /floppy </i>\n"
+"# <i>cd /floppy; ./parted [drive you wish to operate on]</i>\n"
+"(parted) <i> print </i>\n"
+"Disk geometry for /dev/hdb: 0.000-9787.148 megabytes\n"
+"Disk label type: msdos\n"
+"Minor Start End Type Filesystem Flags\n"
+"1 0.031 2953.125 primary ntfs\n"
+"3 2953.125 3133.265 primary linux-swap\n"
+"2 3133.266 5633.085 primary ext3\n"
+"4 5633.086 9787.148 extended\n"
+"5 5633.117 6633.210 logical\n"
+"6 6633.242 9787.148 logical ext3\n"
+"(parted) <i> help resize </i>\n"
+" resize MINOR START END resize filesystem on partition MINOR\n"
+"\n"
+" MINOR is the partition number used by Linux. On msdos disk labels, the\n"
+" primary partitions number from 1-4, and logical partitions are 5\n"
+" onwards.\n"
+" START and END are in megabytes\n"
+"(parted) <i> resize 2 3133.266 4000.000 </i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(impo):728
+msgid ""
+"Be patient! The computer is working! Just look at the harddrive LED on your "
+"case to see that it is really working. This should take between 2 and 30 "
+"minutes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):733
+msgid ""
+"Once you have resized, boot back into your old linux as described. Then go "
+"to <uri link=\"/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=4\">The "
+"Gentoo Handbook: Preparing the Disks</uri> and follow the instructions. When "
+"chrooting, use the following command to flush your environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre:caption):740
+msgid "Flushing the environment during chroot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(pre):740
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env -i HOME=$HOME TERM=$TERM chroot /mnt/gentoo /bin/bash</i>\n"
+"# <i>/usr/sbin/env-update</i>\n"
+"# <i>source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(p):746
+msgid "Enjoy!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//altinstall.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/anothertest.xml.po b/doc/gettext/el/anothertest.xml.po
new file mode 100644
index 0000000..895c2ff
--- /dev/null
+++ b/doc/gettext/el/anothertest.xml.po
@@ -0,0 +1,71 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(guide:link):5
+msgid "/doc/en/test.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(title):6
+msgid "Testfile"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(mail:link):9
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(mail):9
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(abstract):12
+msgid ""
+"This is a testfile with some guidexml content. The main purpose is to test "
+"our DTD-checker on the CVS-server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(version):19
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(date):20
+msgid "2006-03-04"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(title):23
+msgid "Sample Chapter 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(title):25
+msgid "Sample Section 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(p):28
+msgid "Some text. Some more text."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(title):36
+msgid "Sample Section 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(p):39
+msgid "<b>Some bold text</b> and <e>emphasised</e>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//anothertest.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/apache-troubleshooting.xml.po b/doc/gettext/el/apache-troubleshooting.xml.po
new file mode 100644
index 0000000..4b90998
--- /dev/null
+++ b/doc/gettext/el/apache-troubleshooting.xml.po
@@ -0,0 +1,55 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(guide:redirect):5
+msgid "/proj/en/apache/doc/troubleshooting.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(title):6
+msgid "Troubleshooting Apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(mail):9
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(abstract):12
+msgid ""
+"This document covers a number of ways to figure out how to fix your Apache "
+"installation when things are not working correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(version):21
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(date):22
+msgid "2008-03-23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(title):25
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(p):29
+msgid "See <uri>/proj/en/apache/doc/troubleshooting.xml</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//apache-troubleshooting.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/apache-upgrading.xml.po b/doc/gettext/el/apache-upgrading.xml.po
new file mode 100644
index 0000000..7e2d16c
--- /dev/null
+++ b/doc/gettext/el/apache-upgrading.xml.po
@@ -0,0 +1,55 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(guide:redirect):5
+msgid "/proj/en/apache/doc/upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(title):6
+msgid "Troubleshooting Apache"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(mail):9
+msgid "neysx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(abstract):12
+msgid ""
+"This document describes the procedure end-users should follow to safely "
+"upgrade their apache installation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(version):21
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(date):22
+msgid "2008-03-23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(title):25
+msgid "Moved"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(p):29
+msgid "See <uri>/proj/en/apache/doc/upgrading.xml</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//apache-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/arm-requirements.xml.po b/doc/gettext/el/arm-requirements.xml.po
new file mode 100644
index 0000000..d2e9c2e
--- /dev/null
+++ b/doc/gettext/el/arm-requirements.xml.po
@@ -0,0 +1,114 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(guide:link):5
+msgid "/doc/en/arm-requirements.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(title):6
+msgid "Gentoo ARM Hardware Requirements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(mail:link):9
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(mail):9
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(abstract):12
+msgid ""
+"This document lists the different ARM environments Gentoo has been tested on "
+"and what you can expect in terms of hardware support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(version):21
+msgid "1.1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(date):22
+msgid "2004-07-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(title):25
+msgid "Tested Hardware"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(p):29
+msgid ""
+"The following table lists all the tested ARM CPU's and the systems that they "
+"were found in. Generally, if the CPU is supported, then the system doesn't "
+"really matter. The generic ARM target can (in theory) run on any ARM CPU, it "
+"just won't be optimized for it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(p):36
+msgid ""
+"Anything listed in [...] means it is in the works. Anything listed in (...) "
+"means it should work but no one has bother testing it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(th):43
+msgid "CPU"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(th):44
+msgid "Systems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(th):45
+msgid "Libraries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(th):46
+msgid "Kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):50
+msgid "Generic ARM"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):51
+msgid "Any system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):52
+msgid "glibc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):53
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):60
+msgid "(2.4), 2.6.4+"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):57
+msgid "StrongARM110"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):58
+msgid "Netwinder"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(ti):59
+msgid "glibc, [uClibc]"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//arm-requirements.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/ati-faq.xml.po b/doc/gettext/el/ati-faq.xml.po
new file mode 100644
index 0000000..d8747fc
--- /dev/null
+++ b/doc/gettext/el/ati-faq.xml.po
@@ -0,0 +1,355 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):6
+msgid "Gentoo Linux ATI FAQ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail:link):9
+msgid "lu_zero@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail):9
+msgid "Luca Barbato"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(author:title):17
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail:link):12
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail):12
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail:link):15
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail):15
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail:link):18
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(mail):18
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(abstract):21
+msgid ""
+"This FAQ should help users avoid some common installation and configuration "
+"issues related to DRI and X11 for ATI boards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(version):30
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(date):31
+msgid "2010-08-02"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):34
+msgid "Hardware Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):36
+msgid "Is my ATI board supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):39
+msgid ""
+"Many ATI boards (but not all) are supported by <uri link=\"http://www."
+"freedesktop.org/Software/xorg\">xorg-x11</uri>, at least for the 2D "
+"accelerated features. The 3D support is provided either by xorg-x11, or by "
+"ATI's <uri link=\"http://mirror.ati.com/support/drivers/linux/radeon-linux."
+"html\">closed source drivers</uri>. ATI's closed source driver only supports "
+"R600 and newer GPUs. Older GPUs will use the mature open source xorg-x11 "
+"driver."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(th):51
+msgid "GPU"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(th):52
+msgid "Common Name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(th):53
+msgid "Support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):56
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):57
+msgid "Rage128"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):58
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):63
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):68
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):73
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):78
+msgid "xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):61
+msgid "R100"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):62
+msgid "Radeon7xxx, Radeon64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):66
+msgid "R200, R250, R280"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):67
+msgid "Radeon8500, Radeon9000, Radeon9200"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):71
+msgid "R300, R400"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):72
+msgid "Radeon 9500 - x850"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):76
+msgid "R500"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):77
+msgid "Radeon X1300 and higher"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):81
+msgid "R600"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):82
+msgid "RadeonHD 2000 series"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):83
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):88
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):93
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):98
+msgid "ATI DRI, xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):86
+msgid "RV670"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):87
+msgid "RadeonHD 3000 series"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):91
+msgid "RV770"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):92
+msgid "RadeonHD 4000 series"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):96
+msgid "R800"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(ti):97
+msgid "RadeonHD 5000 series, \"Evergreen\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):105
+msgid ""
+"I have an All-In-Wonder/Vivo board. Are the multimedia features supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):110
+msgid ""
+"You don't need to use anything special for the board's multimedia features; "
+"<c>x11-drivers/xf86-video-ati</c> will work just fine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):118
+msgid "I'm not using an x86-based architecture. What are my options?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):121
+msgid ""
+"X11 support on the PPC or Alpha platforms is quite similar to x86 X11 "
+"support. However, ATI's closed source Catalyst drivers are not supported on "
+"the PPC or Alpha, so you will have to use the open source drivers. The "
+"Catalyst drivers are only available for x86 and AMD64. The open source xorg-"
+"x11 drivers should work well on all architectures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(impo):129
+msgid ""
+"To enable agpgart support for certain old AMD64 chipsets, you have to "
+"disable support for the K8 IOMMU."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):137
+msgid "I have a laptop. Is my ATI Mobility model supported?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):140
+msgid ""
+"It should be, but you may have a configuration issue due to the OEM PCI id "
+"that such chips may have. In such cases, you may have to write the "
+"configuration file yourself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):151
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):153
+msgid "Packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):156
+msgid "There are two ways of getting drivers for your ATI card:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(li):161
+msgid "The <c>xorg-x11</c> ebuild provides the X11 implementation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(li):162
+msgid ""
+"The <c>ati-drivers</c> ebuild provides the ATI closed source X drivers and "
+"kernel modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):168
+msgid ""
+"If you want to use ATI's <e>internal</e> agpgart support instead of the "
+"Linux kernel one, the agpgart driver and the chip set specific driver (in "
+"your kernel configuration) must be built as modules or not at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(note):174
+msgid ""
+"Please read the <uri link=\"/doc/en/dri-howto.xml\">Hardware Acceleration "
+"Guide</uri> for more information on installing drivers for your ATI graphics "
+"card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):183
+msgid "Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):186
+msgid ""
+"You may not need to manually create <path>xorg.conf</path> or modify it. Try "
+"running without it first. You can also use the Xorg auto configuration "
+"option:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(pre:caption):191
+msgid "Autoconfiguring X"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"# <i>X -configure</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):195
+msgid ""
+"For more information on how to get a basic <c>xorg.conf</c> configuration "
+"file, please refer to the <uri link=\"/doc/en/xorg-config.xml\">Gentoo X "
+"Server HowTo</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(note):201
+msgid ""
+"PPC, AMD64, and x86 users can use the <c>xac</c> stand-alone X configuration "
+"tool by emerging <c>x11-misc/xac</c>, but isn't required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(note):206
+msgid ""
+"You can use <c>aticonfig</c> if you have installed the <c>ati-drivers</c> "
+"package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(impo):211
+msgid ""
+"If you're using <c>ati-drivers</c>, then you'll need to disable <c>radeonfb</"
+"c> (and probably any other framebuffer drivers) in your kernel config, as it "
+"conflicts with the built-in framebuffer in <c>ati-drivers</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):220
+msgid "Switching to OpenGL"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):223
+msgid ""
+"Once X is installed, configured, and running, it can use the ATI OpenGL "
+"libraries:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(pre:caption):228
+msgid "Running eselect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(pre):228
+#, no-wrap
+msgid ""
+"\n"
+"# <i>eselect opengl set ati</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(title):236
+msgid "More Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):240
+msgid ""
+"Please read the <uri link=\"/doc/en/dri-howto.xml\">Hardware Acceleration "
+"Guide</uri> for more information on configuring your ATI graphics card."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(p):245
+msgid ""
+"More information on Gentoo Linux and the ATI Radeon binary drivers can be "
+"found on the <uri link=\"http://odin.prohosting.com/wedge01/gentoo-radeon-"
+"faq.html\">Wedge Unofficial Gentoo ATI Radeon FAQ</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ati-faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/bind-guide.xml.po b/doc/gettext/el/bind-guide.xml.po
new file mode 100644
index 0000000..1175f93
--- /dev/null
+++ b/doc/gettext/el/bind-guide.xml.po
@@ -0,0 +1,535 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):6
+msgid "Gentoo BIND Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(mail:link):9
+msgid "peratu@carrosses.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(mail):9
+msgid "Vicente Olivert Riera"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(mail:link):12
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(abstract):15
+msgid ""
+"This guide will teach you how install and configure BIND for your domain and "
+"your local network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(version):20
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(date):21
+msgid "2009-08-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):24
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):28
+msgid ""
+"This tutorial will show you how to install and configure BIND, the most used "
+"DNS server on Internet. We will configure <c>bind</c> for your domain using "
+"different configurations, one for your local network and one for the rest of "
+"the world. We will use views to do that. One view for your internal zone "
+"(your local network) and other view for the external zone (rest of the "
+"world)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):41
+msgid "Data used in the examples"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(th):47
+msgid "Keyword"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(th):48
+msgid "Explanation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(th):49
+msgid "Example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):52
+msgid "YOUR_DOMAIN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):53
+msgid "Your domain name"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):54
+msgid "gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):57
+msgid "YOUR_PUBLIC_IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):58
+msgid "The public ip that ISP gives to you"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):59
+msgid "204.74.99.100"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):62
+msgid "YOUR_LOCAL_IP"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):63
+msgid "The local ip address"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):64
+msgid "192.168.1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):67
+msgid "YOUR_LOCAL_NETWORK"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):68
+msgid "The local network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):69
+msgid "192.168.1.0/24"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):72
+msgid "SLAVE_DNS_SERVER"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):73
+msgid "The ip address of the slave DNS server for your domain."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):74
+msgid "209.177.148.228"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):77
+msgid "ADMIN"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):78
+msgid "The DNS server administrator's name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):79
+msgid "root"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):82
+msgid "MODIFICATION"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):83
+msgid "The modification date of the file zone, with a number added"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(ti):84
+msgid "2009062901"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(figure:link):88
+msgid "/images/docs/local-network-map.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(figure:short):88
+msgid "network"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(figure:caption):88
+msgid "Network example"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):95
+msgid "Configuring BIND"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):97
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):100
+msgid "First, install <c>net-dns/bind</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):104
+msgid "Installing bind"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):104
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge net-dns/bind</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):111
+msgid "Configuring /etc/bind/named.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):114
+msgid ""
+"The first thing to configure is <path>/etc/bind/named.conf</path>. The first "
+"part of this step is specifying bind's root directory, the listening port "
+"with the IPs, the pid file, and a line for ipv6 protocol."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):120
+msgid "options section"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):120
+#, no-wrap
+msgid ""
+"\n"
+"options {\n"
+" directory \"/var/bind\";\n"
+"\n"
+" listen-on-v6 { none; };\n"
+" listen-on port 53 { 127.0.0.1; YOUR_LOCAL_IP; };\n"
+"\n"
+" pid-file \"/var/run/named/named.pid\";\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):131
+msgid ""
+"The second part of <path>named.conf</path> is the internal view used for our "
+"local network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):136
+msgid "Internal view"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):136
+#, no-wrap
+msgid ""
+"\n"
+"view \"internal\" {\n"
+" match-clients { YOUR_LOCAL_NETWORK; localhost; };\n"
+" recursion yes;\n"
+"\n"
+" zone \"YOUR_DOMAIN\" {\n"
+" type master;\n"
+" file \"pri/YOUR_DOMAIN.internal\";\n"
+" allow-transfer { any; };\n"
+" };\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):149
+msgid ""
+"The third part of <path>named.conf</path> is the external view used to "
+"resolve our domain name for the rest of the world and to resolve all other "
+"domain names for us (and anyone who wants to use our DNS server)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):155
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):185
+msgid "External view"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):155
+#, no-wrap
+msgid ""
+"\n"
+"view \"external\" {\n"
+" match-clients { any; };\n"
+" recursion no;\n"
+"\n"
+" zone \".\" IN {\n"
+" type hint;\n"
+" file \"named.ca\";\n"
+" };\n"
+"\n"
+" zone \"127.in-addr.arpa\" IN {\n"
+" type master;\n"
+" file \"pri/127.zone\";\n"
+" allow-update { none; };\n"
+" notify no;\n"
+" };\n"
+"\n"
+" zone \"YOUR_DOMAIN\" {\n"
+" type master;\n"
+" file \"pri/YOUR_DOMAIN.external\";\n"
+" allow-query { any; };\n"
+" allow-transfer { SLAVE_DNS_SERVER; };\n"
+" };\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):181
+msgid "The final part of <path>named.conf</path> is the logging policy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):185
+#, no-wrap
+msgid ""
+"\n"
+"logging {\n"
+" channel default_syslog {\n"
+" file \"/var/log/named/named.log\" versions 3 size 5m;\n"
+" severity debug;\n"
+" print-time yes;\n"
+" print-severity yes;\n"
+" print-category yes;\n"
+" };\n"
+" category default { default_syslog; };\n"
+"};\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):198
+msgid ""
+"The <path>/var/log/named/</path> directory must be exist and belong to "
+"<c>named</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):203
+msgid "Creating the log file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):203
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir -p /var/log/named/</i>\n"
+"# <i>chmod 770 /var/log/named/</i>\n"
+"# <i>touch /var/log/named/named.log</i>\n"
+"# <i>chmod 660 /var/log/named/named.log</i>\n"
+"# <i>chown -R named /var/log/named/</i>\n"
+"# <i>chgrp -R named /var/log/named/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):215
+msgid "Creating the internal zone file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):218
+msgid ""
+"We use the hostnames and IP adresses of the picture network example. Note "
+"that almost all (not all) domain names finish with \".\" (dot)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):223
+msgid "/var/bind/pri/YOUR_DOMAIN.internal"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):223
+#, no-wrap
+msgid ""
+"\n"
+"$TTL 2d\n"
+"@\tIN SOA\tns.YOUR_DOMAIN.\tADMIN.YOUR_DOMAIN. (\n"
+"\tMODIFICATION\t; serial\n"
+"\t3h\t; refresh\n"
+"\t1h\t; retry\n"
+"\t1w\t; expiry\n"
+"\t1d )\t; minimum\n"
+"\n"
+"YOUR_DOMAIN.\t\tIN MX\t0 mail.YOUR_DOMAIN.\n"
+"YOUR_DOMAIN.\t\tIN TXT\t\"v=spf1 ip4:YOUR_PUBLIC_IP/32 mx ptr mx:mail.YOUR_DOMAIN ~all\"\n"
+"YOUR_DOMAIN.\t\tIN NS\tns.YOUR_DOMAIN.\n"
+"YOUR_DOMAIN.\t\tIN NS\tSLAVE_DNS_SERVER\n"
+"www.YOUR_DOMAIN.\tIN A\t192.168.1.3\n"
+"ns.YOUR_DOMAIN.\t\tIN A\t192.168.1.5\n"
+"mail.YOUR_DOMAIN.\tIN A\t192.168.1.3\n"
+"router.YOUR_DOMAIN.\tIN A\t192.168.1.1\n"
+"hell.YOUR_DOMAIN.\tIN A\t192.168.1.3\n"
+"heaven.YOUR_DOMAIN.\tIN A\t192.168.1.5\n"
+"desktop.YOUR_DOMAIN.\tIN A\t192.168.1.4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):248
+msgid "Creating the external zone file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):251
+msgid ""
+"Here we only have the subdomains we want for external clients (www, mail and "
+"ns)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):256
+msgid "/var/bind/pri/YOUR_DOMAIN.external"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):256
+#, no-wrap
+msgid ""
+"\n"
+"$TTL 2d\n"
+"@\tIN SOA\tns.YOUR_DOMAIN.\tADMIN.YOUR_DOMAIN. (\n"
+"\tMODIFICATION\t;serial\n"
+"\t3h\t;refresh\n"
+"\t1h\t;retry\n"
+"\t1w\t;expiry\n"
+"\t1d )\t;minimum\n"
+"\n"
+"YOUR_DOMAIN.\t\tIN MX\t0 mail.YOUR_DOMAIN.\n"
+"YOUR_DOMAIN.\t\tIN TXT\t\"v=spf1 ip4:YOUR_PUBLIC_IP/32 mx ptr mx:mail.YOUR_DOMAIN ~all\"\n"
+"YOUR_DOMAIN.\t\tIN NS\tns.YOUR_DOMAIN.\n"
+"YOUR_DOMAIN.\t\tIN NS\tSLAVE_DNS_SERVER\n"
+"www.YOUR_DOMAIN.\tIN A\tYOUR_PUBLIC_IP\n"
+"ns.YOUR_DOMAIN.\t\tIN A\tYOUR_PUBLIC_IP\n"
+"mail.YOUR_DOMAIN.\tIN A\tYOUR_PUBLIC_IP\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):277
+msgid "Finishing configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):280
+msgid "You'll need to add <c>named</c> to the default runlevel:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):284
+msgid "Add to default runlevel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):284
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add named default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):293
+msgid "Configuring clients"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):297
+msgid ""
+"Now you can use your own DNS server in all machines of your local network to "
+"resolve domain names. Modify the <path>/etc/resolv.conf</path> file of all "
+"machines of your local network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):303
+msgid "Editing /etc/resolv.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):303
+#, no-wrap
+msgid ""
+"\n"
+"search YOUR_DOMAIN\n"
+"nameserver YOUR_DNS_SERVER_IP\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):308
+msgid ""
+"Note that YOUR_DNS_SERVER_IP is the same as YOUR_LOCAL_IP we used in this "
+"document. In the picture the example is 192.168.1.5."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):318
+msgid "Testing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):322
+msgid ""
+"We are able to test our new DNS server. First, we need to start the service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):326
+msgid "Starting the service manually"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):326
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/named start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):330
+msgid ""
+"Now, we are going to make some <c>host</c> commands to some domains. We can "
+"use any computer of our local network to do this test. If you don't have "
+"<c>net-dns/host</c> installed you can use <c>ping</c> instead. Otherwise, "
+"first run <c>emerge host</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):337
+msgid "Performing the test"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):337
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>host www.gentoo.org</i>\n"
+"www.gentoo.org has address 209.177.148.228\n"
+"www.gentoo.org has address 209.177.148.229\n"
+"\n"
+"$ <i>host hell</i>\n"
+"hell.YOUR_DOMAIN has address 192.168.1.3\n"
+"\n"
+"$ <i>host router</i>\n"
+"router.YOUR_DOMAIN has address 192.168.1.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(title):354
+msgid "Protecting the server with iptables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(p):358
+msgid ""
+"If you use iptables to protect your server, you can add these rules for DNS "
+"service."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre:caption):363
+msgid "Iptables rules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(pre):363
+#, no-wrap
+msgid ""
+"\n"
+"iptables -A INPUT -p udp --sport 53 -m state --state ESTABLISHED,RELATED -j ACCEPT\n"
+"iptables -A INPUT -p udp --dport 53 -j ACCEPT\n"
+"iptables -A INPUT -p tcp --sport 53 -j ACCEPT\n"
+"iptables -A INPUT -p tcp --dport 53 -j ACCEPT\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//bind-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/bluetooth-guide.xml.po b/doc/gettext/el/bluetooth-guide.xml.po
new file mode 100644
index 0000000..52139ee
--- /dev/null
+++ b/doc/gettext/el/bluetooth-guide.xml.po
@@ -0,0 +1,869 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):6
+msgid "Gentoo Linux Bluetooth Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):8
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):17
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):9
+msgid "deathwing00@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail):9
+msgid "Ioannis Aslanidis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):14
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):12
+msgid "puggy@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail):12
+msgid "Douglas Russell"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):15
+msgid "marcel@holtmann.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail):15
+msgid "Marcel Holtmann"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):18
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail):18
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):20
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(author:title):23
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):21
+msgid "rane@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail):21
+msgid "Łukasz Damentko"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(mail:link):24
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(abstract):27
+msgid ""
+"This guide will explain how to successfully install a host Bluetooth device, "
+"configure the kernel properly, explain all the possibilities that the "
+"Bluetooth interconnection offers and how to have some fun with Bluetooth."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(version):37
+msgid "1.11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(date):38
+msgid "2009-07-16"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):41
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):504
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):43
+msgid "What is Bluetooth?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):46
+msgid ""
+"Bluetooth is an industrial specification that provides users a way to "
+"connect and exchange information between devices like personal computers, "
+"PDAs or mobile phones. Using the Bluetooth technology, users can achieve "
+"wireless voice and data transmission between devices at a low cost. "
+"Bluetooth also offers the possibility to create small wireless LANs and to "
+"synchronize devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):57
+msgid "About the content of this guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):60
+msgid ""
+"The first part of this guide explains how to configure the system kernel, "
+"identify the Bluetooth devices installed on the system and detected by the "
+"kernel and install the necessary basic Bluetooth tools."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):66
+msgid ""
+"The second part covers how to detect remote devices and how to establish a "
+"connection from or to them by either setting up radio frequency "
+"communication (RFCOMM)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):72
+msgid ""
+"The last part of the guide lists in detail applications that can take "
+"advantage of all the possibilities offered by the Bluetooth technology."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):82
+msgid "Configuring the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):84
+msgid "Kernel Configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):87
+msgid ""
+"As the latest Linux stable kernel is 2.6, the configuration will be done for "
+"these series of the kernel. Most Bluetooth devices are connected to a USB "
+"port, so USB will be enabled too. Please refer to the <uri link=\"/doc/en/"
+"usb-guide.xml\">Gentoo Linux USB Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):94
+msgid "Configuration for 2.6 kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):94
+#, no-wrap
+msgid ""
+"\n"
+"Networking ---&gt;\n"
+"\n"
+"&lt;*&gt; Bluetooth subsystem support ---&gt;\n"
+"\n"
+"--- Bluetooth subsystem support\n"
+"&lt;M&gt; L2CAP protocol support\n"
+"&lt;M&gt; SCO links support\n"
+"&lt;M&gt; RFCOMM protocol support\n"
+"[*] RFCOMM TTY support\n"
+"&lt;M&gt; BNEP protocol support\n"
+"[*] Multicast filter support\n"
+"[*] Protocol filter support\n"
+"&lt;M&gt; HIDP protocol support\n"
+"\n"
+"Bluetooth device drivers ---&gt;\n"
+"&lt;M&gt; HCI USB driver\n"
+"[*] SCO (voice) support\n"
+"&lt;M&gt; HCI UART driver\n"
+"[*] UART (H4) protocol support\n"
+"[*] BCSP protocol support\n"
+"[*] Transmit CRC with every BCSP packet\n"
+"&lt;M&gt; HCI BCM203x USB driver\n"
+"&lt;M&gt; HCI BPA10x USB driver\n"
+"&lt;M&gt; HCI BlueFRITZ! USB driver\n"
+"<comment>(The four drivers below are for PCMCIA Bluetooth devices and will only\n"
+"show up if you have also selected PCMCIA support in your kernel.)</comment>\n"
+"&lt;M&gt; HCI DTL1 (PC Card) driver\n"
+"&lt;M&gt; HCI BT3C (PC Card) driver\n"
+"&lt;M&gt; HCI BlueCard (PC Card) driver\n"
+"&lt;M&gt; HCI UART (PC Card) device driver\n"
+"<comment>(The driver below is intended for HCI Emulation software.)</comment>\n"
+"&lt;M&gt; HCI VHCI (Virtual HCI device) driver\n"
+"\n"
+"<comment>(Move back three levels to Device Drives and then check if USB is\n"
+"enabled. This is required if you use a Bluetooth dongle, which are mostly USB\n"
+"based.)</comment>\n"
+"USB support ---&gt;\n"
+"\n"
+"&lt;*&gt; Support for Host-side USB\n"
+"--- USB Host Controller Drivers\n"
+"&lt;M&gt; EHCI HCD (USB 2.0) support\n"
+"[ ] Full speed ISO transactions (EXPERIMENTAL)\n"
+"[ ] Root Hub Transaction Translators (EXPERIMENTAL)\n"
+"&lt;*&gt; OHCI HCD support\n"
+"&lt;*&gt; UHCI HCD (most Intel and VIA) support\n"
+"&lt; &gt; SL811HS HCD support\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):143
+msgid ""
+"Now we'll reboot with our new kernel. If everything went fine, we will have "
+"a system that is Bluetooth ready."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(impo):148
+msgid ""
+"Your USB device may have two modes the default of which may not be HCI, but "
+"HID. If this is your case, use <c>hid2hci</c> to switch to HCI mode. Your "
+"system will not remember this change when you next reboot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):154
+msgid "Checking the Bluetooth devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):154
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(One way to check for the device)</comment>\n"
+"# <i>cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1</i>\n"
+"<comment>(The Cls=e0(unk. ) identifies the Bluetooth adapter.)</comment>\n"
+"T: Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0\n"
+"D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1\n"
+"P: Vendor=0a12 ProdID=0001 Rev= 5.25\n"
+"<comment>(Some might show up on lsusb from sys-apps/usbutils)</comment>\n"
+"# <i>lsusb</i>\n"
+"Bus 003 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse\n"
+"Bus 003 Device 001: ID 0000:0000\n"
+"Bus 002 Device 002: ID 0db0:1967 Micro Star International Bluetooth Dongle\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):173
+msgid "BlueZ - The Bluetooth Stack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):175
+msgid "Installing BlueZ"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):178
+msgid ""
+"Now that the device is detected by the kernel, we need a layer that lets "
+"applications communicate with the Bluetooth device. BlueZ provides the "
+"official Linux Bluetooth stack. The ebuilds that provide what we need are "
+"<c>bluez-libs</c> and <c>bluez-utils</c>. Devices that need Broadcom "
+"firmware files or the like may need <c>bluez-firmware</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):186
+msgid "Installing bluez-libs and bluez-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):186
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge net-wireless/bluez-libs net-wireless/bluez-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):193
+msgid "BlueZ configuration and PIN pairing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):196
+msgid ""
+"Now it's time to see if the Bluetooth device is being picked up correctly by "
+"the system. We start up the required Bluetooth services first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):201
+msgid "Running hciconfig"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):201
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Start up Bluetooth)</comment>\n"
+"# <i>/etc/init.d/bluetooth start</i>\n"
+"* Starting Bluetooth ...\n"
+"* Starting hcid ... [ ok ]\n"
+"* Starting sdpd ... [ ok ]\n"
+"* Starting rfcomm ... [ ok ]\n"
+"\n"
+"# <i>hciconfig</i>\n"
+"hci0: Type: USB\n"
+" BD Address: 00:01:02:03:04:05 ACL MTU: 192:8 SCO MTU: 64:8\n"
+" DOWN\n"
+" RX bytes:131 acl:0 sco:0 events:18 errors:0\n"
+" TX bytes:565 acl:0 sco:0 commands:17 errors:0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):217
+msgid ""
+"This shows that the Bluetooth device has been recognised. As you might have "
+"noticed the device is <e>DOWN</e>. Let's configure it so that we can bring "
+"it up. The configuration file is at <path>/etc/bluetooth/hcid.conf</path>. "
+"The required changes to the config file are shown below. For additional "
+"details please refer to <c>man hcid.conf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):225
+msgid "Editing /etc/bluetooth/hcid.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):225
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Recommended changes to be made to the file are shown)</comment>\n"
+"\n"
+"# HCId options\n"
+"options {\n"
+" # Automatically initialize new devices\n"
+" autoinit yes;\n"
+"\n"
+"<comment>(Change security to \"auto\")</comment>\n"
+" # Security Manager mode\n"
+" # none - Security manager disabled\n"
+" # auto - Use local PIN for incoming connections\n"
+" # user - Always ask user for a PIN\n"
+" #\n"
+" security auto;\n"
+"\n"
+" # Pairing mode\n"
+" pairing multi;\n"
+"\n"
+"<comment>(You only need a pin helper if you are using &lt;=bluez-libs-2.x and &lt;=bluez-utils-2.x)\n"
+"(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>\n"
+" # PIN helper\n"
+" pin_helper /etc/bluetooth/pin-helper;\n"
+"}\n"
+"\n"
+"# Default settings for HCI devices\n"
+"device {\n"
+"<comment>(Set your device name here, you can call it anything you want)</comment>\n"
+" # Local device name\n"
+" # %d - device id\n"
+" # %h - host name\n"
+" name \"BlueZ at %h (%d)\";\n"
+"\n"
+" # Local device class\n"
+" class 0x3e0100;\n"
+"\n"
+" # Inquiry and Page scan\n"
+" iscan enable; pscan enable;\n"
+"\n"
+" # Default link mode\n"
+" lm accept;\n"
+"\n"
+" # Default link policy\n"
+" lp rswitch,hold,sniff,park;\n"
+"\n"
+"<comment>(Leave as is, if you don't know what exactly these do)</comment>\n"
+" # Authentication and Encryption (Security Mode 3)\n"
+" #auth enable;\n"
+" #encrypt enable;\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):277
+msgid ""
+"After that, we have to configure the Bluetooth device PIN. That will help in "
+"pairing this device with another one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):282
+msgid "Editing /etc/bluetooth/pin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Replace 123456 with your desired pin number.)</comment>\n"
+"123456\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(impo):287
+msgid ""
+"This number (of your choice) must be the same in all your hosts with "
+"Bluetooth devices so they can be paired. This number must also be kept "
+"secret since anyone with knowledge of this number can essentially establish "
+"connections with your devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(note):294
+msgid ""
+"Beginning with <c>&gt;=bluez-libs-3.x</c> and <c>&gt;=bluez-utils-3.x</c>, "
+"pin helpers have been replaced by passkey agents. There are a few different "
+"graphical passkey agents available to help manage your PIN, such as <c>bluez-"
+"gnome</c> and <c>kdebluetooth</c>. You can also use <c>passkey-agent</c> "
+"(found in <c>bluez-utils</c>) from the command line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):305
+msgid "Services configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):308
+msgid ""
+"Now that we have concluded with the configuration of BlueZ, it's time to "
+"restart the necessary services."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):313
+msgid "Starting the Bluetooth daemons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):313
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/bluetooth restart</i>\n"
+"<comment>(We can also add it to the default runlevel.)</comment>\n"
+"# <i>rc-update add bluetooth default</i>\n"
+" * bluetooth added to runlevel default\n"
+" * rc-update complete.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):321
+msgid ""
+"Let's be sure that the Bluetooth daemons started correctly. If we can see "
+"that both <c>hcid</c> and <c>sdpd</c> are running, then we configured "
+"Bluetooth the right way. After that, we can see if the devices are now up "
+"and running with the configured options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):328
+msgid "Checking whether Bluetooth daemons started correctly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):328
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Check to see if the services are running)</comment>\n"
+"# <i>ps -ae | grep hcid</i>\n"
+"26050 ? 00:00:00 hcid\n"
+"# <i>ps -ae | grep sdpd</i>\n"
+"26054 ? 00:00:00 sdpd\n"
+"\n"
+"# <i>hciconfig -a</i>\n"
+"hci0: Type: USB\n"
+" BD Address: 00:0A:0B:0C:0D:0E ACL MTU: 192:8 SCO MTU: 64:8\n"
+" UP RUNNING PSCAN ISCAN\n"
+" RX bytes:125 acl:0 sco:0 events:17 errors:0\n"
+" TX bytes:565 acl:0 sco:0 commands:17 errors:0\n"
+" Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00\n"
+" Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3\n"
+" Link policy: RSWITCH HOLD SNIFF PARK\n"
+" Link mode: SLAVE ACCEPT\n"
+" Name: 'BlueZ at bluehat (0)'\n"
+" Class: 0x3e0100\n"
+" Service Classes: Networking, Rendering, Capturing, Object Transfer,\n"
+" Audio\n"
+" Device Class: Computer, Uncategorized\n"
+" HCI Ver: 1.1 (0x1) HCI Rev: 0x1e7 LMP Ver: 1.1 (0x1) LMP Subver: 0x1e7\n"
+" Manufacturer: Cambridge Silicon Radio (10)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):359
+msgid "Detecting and Connecting to Remote Devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):361
+msgid "Detecting Bluetooth devices in other hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):364
+msgid ""
+"At this point we are now ready to detect Bluetooth devices installed in "
+"other machines. This is independent of the host Operating System. We will "
+"make use of the <c>hcitool</c> command for the same."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):370
+msgid "Checking for local devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):370
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hcitool dev</i>\n"
+"Devices:\n"
+" hci0 00:01:02:03:04:05\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):376
+msgid "Scanning for remote devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):376
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hcitool scan</i>\n"
+"Scanning ...\n"
+" 00:0A:0B:0C:0D:0E Grayhat\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):382
+msgid "Inquiring remote devices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):382
+#, no-wrap
+msgid ""
+"\n"
+"# <i>hcitool inq</i>\n"
+"Inquiring ...\n"
+" 00:0A:0B:0C:0D:0E clock offset: 0x5579 class: 0x72010c\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):388
+msgid ""
+"Now that we know the MAC address of the remote Bluetooth devices, we can "
+"check if we paired them correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):393
+msgid "Running l2ping"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):393
+#, no-wrap
+msgid ""
+"\n"
+"# <i>l2ping 00:0A:0B:0C:0D:0E</i>\n"
+"Ping: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ...\n"
+"20 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms\n"
+"20 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms\n"
+"20 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms\n"
+"20 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms\n"
+"4 sent, 4 received, 0% loss\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):406
+msgid "Setting up Radio Frequency Communication (RFCOMM)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(note):409
+msgid "Please note that setting up radio frequency communication is optional."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):413
+msgid ""
+"We can establish a radio frequency connection to another Bluetooth device "
+"using the <c>rfcomm</c> command. To make things a little easier especially "
+"for users with multiple devices that support Bluetooth, it is advisable to "
+"make a few changes to the default rfcomm config at <path>/etc/bluetooth/"
+"rfcomm.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):420
+msgid ""
+"The whole segment of the config starting from <c>rfcomm0 {</c> and ending "
+"with <c>}</c> is the config for the device that will establish a connection "
+"at <path>/dev/rfcomm0</path>. In this case, we will only show one example, "
+"rfcomm0. You can add more devices as you see fit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):427
+msgid "Editing /etc/bluetooth/rfcomm.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):427
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Only changes that might be needed are shown)</comment>\n"
+"rfcomm0 {\n"
+" # Automatically bind the device at startup\n"
+" <comment>(Creates the device node, /dev/rfcomm0 at start up)</comment>\n"
+" bind yes;\n"
+"\n"
+" # Bluetooth address of the device\n"
+" <comment>(Enter the address of the device you want to connect to)</comment>\n"
+" device 00:0A:0B:0C:0D:0E;\n"
+"\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):441
+msgid ""
+"After configuring RFCOMM, we can connect to any device. Since we've made the "
+"required settings to the <path>/etc/bluetooth/rfcomm.conf</path> file, we "
+"just issue the command shown below. In case you've not made changes to the "
+"config file, an alternative method is also shown in the code listing that "
+"follows"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):448
+msgid "Establishing an RFCOMM connection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):448
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(The 0 refers to the rfcomm0 in the config file)</comment>\n"
+"# <i>rfcomm connect 0 </i>\n"
+"Connected /dev/rfcomm0 to 00:0A:0B:0C:0D:0E on channel 1\n"
+"Press CTRL-C for hangup\n"
+"\n"
+"<comment>(If you did not edit /etc/bluetooth/rfcomm.conf)</comment>\n"
+"# <i>rfcomm connect 0 00:0A:0B:0C:0D:0E 1</i>\n"
+"Connected /dev/rfcomm0 to 00:0F:DE:69:50:24 on channel 1\n"
+"Press CTRL-C for hangup\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):460
+msgid ""
+"The first parameter after the connect command is the RFCOMM TTY device node "
+"that will be used (usually 0). The second parameter is the MAC address of "
+"the remote device. The third parameter is optional and specifies the channel "
+"to be used. Please, note that in order to connect to a device, that device "
+"must be listening for incoming connections. To do that, we have to "
+"explicitly tell it to listen. We can cancel the communication at any moment "
+"by just hitting CTRL+C."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):470
+msgid "Listening for incoming RFCOMM connections"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):470
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rfcomm listen 0 1</i>\n"
+"Waiting for connection on channel 1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):475
+msgid ""
+"In a similar way to the connect command, the listen command can receive two "
+"parameters. The first one explicits the RFCOMM TTY device node (usually 0) "
+"that will be used to accept a connection, while the second is the channel "
+"that will be used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):482
+msgid ""
+"Each time you call the <c>rfcomm</c> command, you can also specify the "
+"physical device you want to use. Below you can see a small example "
+"specifiying the physical device on the above two commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):488
+msgid "RFCOMM connections specifying physical device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):488
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rfcomm -i hci0 listen 0 1</i>\n"
+"Waiting for connection on channel 1\n"
+"<comment>(To listen to a determined device) </comment>\n"
+"# <i>rfcomm -i hci0 connect 0 00:0A:0B:0C:0D:0E 1</i>\n"
+"<comment>(To use a determined device when connecting to another one)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):502
+msgid "Desktop Applications for Bluetooth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):507
+msgid ""
+"We have quite a few Bluetooth applications that run on the desktop and this "
+"chapter has been divided into 3 parts, one each for Gnome, KDE and "
+"Miscellaneous applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):516
+msgid "For Gnome"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):519
+msgid ""
+"If you are a gnome user, you will most probably go with <c>gnome-bluetooth</"
+"c>. It provides the most basic yet most used functionalities, as you can see "
+"below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):525
+msgid "<c>gnome-bluetooth-manager</c>: To manage Bluetooth remote devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):526
+msgid "<c>gnome-obex-send</c>: To send files to other devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):527
+msgid "<c>gnome-obex-server</c>: To receive files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):530
+msgid "Installing gnome-bluetooth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):530
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gnome-bluetooth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):534
+msgid ""
+"This adds menu entries under Applications &gt; System Tools from where you "
+"can easily start up the manager or File sharing to transfer files between "
+"devices."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):539
+msgid "To transfer files (the easy way):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):544
+msgid ""
+"From the Phone to the Computer - Send the file from the phone via Bluetooth "
+"and it will be picked up and saved to your <path>/home</path> always."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):558
+msgid ""
+"<c>gnome-phone-manager</c> is a nifty app that you can use to send and "
+"receive messages to and from your phone, using only your system. You do not "
+"have to touch your phone to read or send messages since all that happens "
+"through the application. You are also notified of a new message on your "
+"screen if the option is enabled under Preferences. Installation is a breeze "
+"as always."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):566
+msgid "Installing gnome-phone-manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):566
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gnome-phone-manager</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):573
+msgid "For KDE"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):576
+msgid ""
+"KDE makes use of <c>kdebluetooth</c> and provides more utilities than its "
+"Gnome counterpart as seen below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):582
+msgid "<c>kbluetoothd</c>: Bluetooth Meta Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):583
+msgid "<c>kbtsearch</c>: Bluetooth device/service search utility."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):584
+msgid "<c>khciconfig</c>: KDE Bluetooth Monitor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):585
+msgid "<c>kioclient</c>: KIO command line client."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):586
+msgid "<c>qobexclient</c>: Swiss army knife for obex testing/development."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):587
+msgid "<c>kbtobexclient</c>: A KDE Bluetooth Framework Application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):590
+msgid "<c>kbemusedsrv</c>: KDE Bemused Server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):591
+msgid "<c>kbtobexsrv</c>: KDE OBEX Push Server for Bluetooth."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):592
+msgid "<c>kbluepin</c>: A KDE KPart Application."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):593
+msgid ""
+"<c>auth-helper</c>: A helper program for kbtobexsrv that sends an "
+"authentication request for a given ACL link."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre:caption):599
+msgid "Installing kdebluetooth"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(pre):599
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge kdebluetooth</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):606
+msgid "Other Interesting Applications"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):610
+msgid ""
+"<c>app-mobilephone/obexftp</c>: File transfer over OBEX for mobile phones"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):613
+msgid ""
+"<c>app-mobilephone/bemused</c>: Bemused is a system which allows you to "
+"control your music collection from your phone, using Bluetooth."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):617
+msgid ""
+"<c>app-pda/multisync</c>: Multisync allows you to sync contacts, calendar "
+"entries and notes from your mobile phone with your computer, over a "
+"Bluetooth connection (amongst other things). It includes such features as "
+"backing up this information and restoring it later, and syncing with the "
+"Evolution e-mail client. You will need the <c>irmc</c> USE flag set to "
+"ensure that <c>multisync</c> has Bluetooth support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(li):625
+msgid ""
+"<c>net-wireless/opd</c> and <c>net-wireless/ussp-push</c> are command line "
+"tools (server and client) that can be used to send files to your mobile "
+"phone."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(title):637
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(p):641
+msgid ""
+"Special thanks to <mail link=\"marcel@holtmann.org\">Marcel Holtmann</mail> "
+"for his time and dedication to the Bluetooth development and for reviewing "
+"this guide. And big thanks to <mail link=\"puggy@gentoo.org\">Douglas "
+"Russell</mail> for performing additional hardware tests and improving this "
+"guide."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//bluetooth-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/bugzilla-howto.xml.po b/doc/gettext/el/bugzilla-howto.xml.po
new file mode 100644
index 0000000..fcca4ea
--- /dev/null
+++ b/doc/gettext/el/bugzilla-howto.xml.po
@@ -0,0 +1,1985 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):6
+msgid "Gentoo Bug Reporting Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail:link):9
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail):9
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail:link):12
+msgid "fox2mike@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail):12
+msgid "Shyam Mani"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(abstract):15
+msgid "This document shows the proper method of reporting bugs using Bugzilla."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(version):23
+msgid "1.15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(date):24
+msgid "2010-02-27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):27
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):104
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):344
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):422
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):584
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):756
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):29
+msgid "Preface"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):32
+msgid ""
+"One of the factors that delay a bug being fixed is the way it is reported. "
+"By creating this guide, we hope to help improve the communication between "
+"developers and users in bug resolution. Getting bugs fixed is an important, "
+"if not crucial part of the quality assurance for any project and hopefully "
+"this guide will help make that a success."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):43
+msgid "Bugs!!!!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):46
+msgid ""
+"You're emerge-ing a package or working with a program and suddenly the worst "
+"happens -- you find a bug. Bugs come in many forms like emerge failures or "
+"segmentation faults. Whatever the cause, the fact still remains that such a "
+"bug must be fixed. Here is a few examples of such bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):53
+msgid "A run time error"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):53
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):179
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>./bad_code `perl -e 'print \"A\"x100'`</i>\n"
+"Segmentation fault\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):58
+msgid "An emerge failure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):58
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):605
+#, no-wrap
+msgid ""
+"\n"
+"/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/g++-v3/backward/backward_warning.h:32:2:\n"
+"warning: #warning This file includes at least one deprecated or antiquated\n"
+"header. Please consider using one of the 32 headers found in section 17.4.1.2 of\n"
+"the C++ standard. Examples include substituting the &lt;X&gt; header for the &lt;X.h&gt;\n"
+"header for C++ includes, or &lt;sstream&gt; instead of the deprecated header\n"
+"&lt;strstream.h&gt;. To disable this warning use -Wno-deprecated.\n"
+"In file included from main.cc:40:\n"
+"menudef.h:55: error: brace-enclosed initializer used to initialize `\n"
+"OXPopupMenu*'\n"
+"menudef.h:62: error: brace-enclosed initializer used to initialize `\n"
+"OXPopupMenu*'\n"
+"menudef.h:70: error: brace-enclosed initializer used to initialize `\n"
+"OXPopupMenu*'\n"
+"menudef.h:78: error: brace-enclosed initializer used to initialize `\n"
+"OXPopupMenu*'\n"
+"main.cc: In member function `void OXMain::DoOpen()':\n"
+"main.cc:323: warning: unused variable `FILE*fp'\n"
+"main.cc: In member function `void OXMain::DoSave(char*)':\n"
+"main.cc:337: warning: unused variable `FILE*fp'\n"
+"make[1]: *** [main.o] Error 1\n"
+"make[1]: Leaving directory\n"
+"`/var/tmp/portage/xclass-0.7.4/work/xclass-0.7.4/example-app'\n"
+"make: *** [shared] Error 2\n"
+"\n"
+"!!! ERROR: x11-libs/xclass-0.7.4 failed.\n"
+"!!! Function src_compile, Line 29, Exitcode 2\n"
+"!!! 'emake shared' failed\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):88
+msgid ""
+"These errors can be quite troublesome. However, once you find them, what do "
+"you do? The following sections will look at two important tools for handling "
+"run time errors. After that, we'll take a look at compile errors, and how to "
+"handle them. Let's start out with the first tool for debugging run time "
+"errors -- <c>gdb</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):102
+msgid "Debugging using GDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):107
+msgid ""
+"GDB, or the (G)NU (D)e(B)ugger, is a program used to find run time errors "
+"that normally involve memory corruption. First off, let's take a look at "
+"what debugging entails. One of the main things you must do in order to debug "
+"a program is to <c>emerge</c> the program with <c>FEATURES=\"nostrip\"</c>. "
+"This prevents the stripping of debug symbols. Why are programs stripped by "
+"default? The reason is the same as that for having gzipped man pages -- "
+"saving space. Here's how the size of a program varies with and without debug "
+"symbol stripping."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):117
+msgid "Filesize Comparison"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):117
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(debug symbols stripped)</comment>\n"
+"-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code\n"
+"<comment>(debug symbols intact)</comment>\n"
+"-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):124
+msgid ""
+"Just for reference, <e>bad_code</e> is the program we'll be debugging with "
+"<c>gdb</c> later on. As you can see, the program without debugging symbols "
+"is 3140 bytes, while the program with them is 6374 bytes. That's close to "
+"double the size! Two more things can be done for debugging. The first is "
+"adding <c>ggdb</c> to your CFLAGS and CXXFLAGS. This flag adds more "
+"debugging information than is generally included. We'll see what that means "
+"later on. This is how <path>/etc/make.conf</path><e>might</e> look with the "
+"newly added flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):134
+msgid "make.conf settings"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):134
+#, no-wrap
+msgid ""
+"\n"
+"CFLAGS=\"-O1 -pipe -ggdb\"\n"
+"CXXFLAGS=\"${CFLAGS}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):139
+msgid ""
+"Lastly, you can also add debug to the package's USE flags. This can be done "
+"with the <path>package.use</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):144
+msgid "Using package.use to add debug USE flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):144
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"category/package debug\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):148
+msgid ""
+"The directory <path>/etc/portage</path> does not exist by default and you "
+"may have to create it, if you have not already done so. If the package "
+"already has USE flags set in <path>package.use</path>, you will need to "
+"manually modify them in your favorite editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):155
+msgid ""
+"Then we re-emerge the package with the modifications we've done so far as "
+"shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):160
+msgid "Re-emergeing a package with debugging"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):160
+#, no-wrap
+msgid ""
+"\n"
+"# <i>FEATURES=\"nostrip\" emerge package</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):164
+msgid ""
+"Now that debug symbols are setup, we can continue with debugging the program."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):171
+msgid "Running the program with GDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):174
+msgid ""
+"Let's say we have a program here called \"bad_code\". Some person claims "
+"that the program crashes and provides an example. You go ahead and test it "
+"out:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):179
+msgid "Breaking The Program"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):184
+msgid ""
+"It seems this person was right. Since the program is obviously broken, we "
+"have a bug at hand. Now, it's time to use <c>gdb</c> to help solve this "
+"matter. First we run <c>gdb</c> with <c>--args</c>, then give it the full "
+"program with arguments like shown:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):191
+msgid "Running Our Program Through GDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):191
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>gdb --args ./bad_code `perl -e 'print \"A\"x100'`</i>\n"
+"GNU gdb 6.3\n"
+"Copyright 2004 Free Software Foundation, Inc.\n"
+"GDB is free software, covered by the GNU General Public License, and you are\n"
+"welcome to change it and/or distribute copies of it under certain conditions.\n"
+"Type \"show copying\" to see the conditions.\n"
+"There is absolutely no warranty for GDB. Type \"show warranty\" for details.\n"
+"This GDB was configured as \"i686-pc-linux-gnu\"...Using host libthread_db library \"/lib/libthread_db.so.1\".\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):202
+msgid ""
+"One can also debug with core dumps. These core files contain the same "
+"information that the program would produce when run with gdb. In order to "
+"debug with a core file with bad_code, you would run <c>gdb ./bad_code core</"
+"c> where core is the name of the core file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):209
+msgid ""
+"You should see a prompt that says \"(gdb)\" and waits for input. First, we "
+"have to run the program. We type in <c>run</c> at the command and receive a "
+"notice like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):214
+msgid "Running the program in GDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):214
+#, no-wrap
+msgid ""
+"\n"
+"(gdb) <i>run</i>\n"
+"Starting program: /home/chris/bad_code\n"
+"\n"
+"Program received signal SIGSEGV, Segmentation fault.\n"
+"0xb7ec6dc0 in strcpy () from /lib/libc.so.6\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):222
+msgid ""
+"Here we see the program starting, as well as a notification of SIGSEGV, or "
+"Segmentation Fault. This is GDB telling us that our program has crashed. It "
+"also gives the last run function it could trace when the program crashes. "
+"However, this isn't too useful, as there could be multiple strcpy's in the "
+"program, making it hard for developers to find which one is causing the "
+"issue. In order to help them out, we do what's called a backtrace. A "
+"backtrace runs backwards through all the functions that occurred upon "
+"program execution, to the function at fault. Functions that return (without "
+"causing a crash) will not show up on the backtrace. To get a backtrace, at "
+"the (gdb) prompt, type in <c>bt</c>. You will get something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):235
+msgid "Program backtrace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"(gdb) <i>bt</i>\n"
+"#0 0xb7ec6dc0 in strcpy () from /lib/libc.so.6\n"
+"#1 0x0804838c in run_it ()\n"
+"#2 0x080483ba in main ()\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):242
+msgid ""
+"You can notice the trace pattern clearly. main() is called first, followed "
+"by run_it(), and somewhere in run_it() lies the strcpy() at fault. Things "
+"such as this help developers narrow down problems. There are a few "
+"exceptions to the output. First off is forgetting to enable debug symbols "
+"with <c>FEATURES=\"nostrip\"</c>. With debug symbols stripped, the output "
+"looks something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):251
+msgid "Program backtrace With debug symbols stripped"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"(gdb) <i>bt</i>\n"
+"#0 0xb7e2cdc0 in strcpy () from /lib/libc.so.6\n"
+"#1 0x0804838c in ?? ()\n"
+"#2 0xbfd19510 in ?? ()\n"
+"#3 0x00000000 in ?? ()\n"
+"#4 0x00000000 in ?? ()\n"
+"#5 0xb7eef148 in libgcc_s_personality () from /lib/libc.so.6\n"
+"#6 0x080482ed in ?? ()\n"
+"#7 0x080495b0 in ?? ()\n"
+"#8 0xbfd19528 in ?? ()\n"
+"#9 0xb7dd73b8 in __guard_setup () from /lib/libc.so.6\n"
+"#10 0xb7dd742d in __guard_setup () from /lib/libc.so.6\n"
+"#11 0x00000006 in ?? ()\n"
+"#12 0xbfd19548 in ?? ()\n"
+"#13 0x080483ba in ?? ()\n"
+"#14 0x00000000 in ?? ()\n"
+"#15 0x00000000 in ?? ()\n"
+"#16 0xb7deebcc in __new_exitfn () from /lib/libc.so.6\n"
+"#17 0x00000000 in ?? ()\n"
+"#18 0xbfd19560 in ?? ()\n"
+"#19 0xb7ef017c in nullserv () from /lib/libc.so.6\n"
+"#20 0xb7dd6f37 in __libc_start_main () from /lib/libc.so.6\n"
+"#21 0x00000001 in ?? ()\n"
+"#22 0xbfd195d4 in ?? ()\n"
+"#23 0xbfd195dc in ?? ()\n"
+"#24 0x08048201 in ?? ()\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):280
+msgid ""
+"This backtrace contains a large number of ?? marks. This is because without "
+"debug symbols, <c>gdb</c> doesn't know how the program was run. Hence, it is "
+"crucial that debug symbols are <e>not</e> stripped. Now remember a while ago "
+"we mentioned the -ggdb flag. Let's see what the output looks like with the "
+"flag enabled:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):288
+msgid "Program backtrace with -ggdb"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):288
+#, no-wrap
+msgid ""
+"\n"
+"(gdb) <i>bt</i>\n"
+"#0 0xb7e4bdc0 in strcpy () from /lib/libc.so.6\n"
+"#1 0x0804838c in run_it (input=0x0) at bad_code.c:7\n"
+"#2 0x080483ba in main (argc=1, argv=0xbfd3a434) at bad_code.c:12\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):295
+msgid ""
+"Here we see that a lot more information is available for developers. Not "
+"only is function information displayed, but even the exact line numbers of "
+"the source files. This method is the most preferred if you can spare the "
+"extra space. Here's how much the file size varies between debug, strip, and -"
+"ggdb enabled programs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):303
+msgid "Filesize differences With -ggdb flag"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):303
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(debug symbols stripped)</comment>\n"
+"-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code\n"
+"<comment>(debug symbols enabled)</comment>\n"
+"-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code\n"
+"<comment>(-ggdb flag enabled)</comment>\n"
+"-rwxr-xr-x 1 chris users 19552 6/28 13:11 bad_code\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):312
+msgid ""
+"As you can see, -ggdb adds about <e>13178</e> more bytes to the file size "
+"over the one with debugging symbols. However, as shown above, this increase "
+"in file size can be worth it if presenting debug information to developers. "
+"The backtrace can be saved to a file by copying and pasting from the "
+"terminal (if it's a non-x based terminal, you can use gpm. To keep this doc "
+"simple, I recommend you read up on the <uri link=\"/doc/en/gpm."
+"xml#doc_chap4\">documentation for gpm</uri> to see how to copy and paste "
+"with it). Now that we're done with <c>gdb</c>, we can quit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):323
+msgid "Quitting GDB"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):323
+#, no-wrap
+msgid ""
+"\n"
+"(gdb) <i>quit</i>\n"
+"The program is running. Exit anyway? (y or n) <i>y</i>\n"
+"$\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):329
+msgid ""
+"This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, we hope that you "
+"will be able to use it to create better bug reports. However, there are "
+"other types of errors that can cause a program to fail during run time. One "
+"of the other ways is through improper file access. We can find those using a "
+"nifty little tool called <c>strace</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):342
+msgid "Finding file access errors using strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):347
+msgid ""
+"Programs often use files to fetch configuration information, access hardware "
+"or write logs. Sometimes, a program attempts to reach such files "
+"incorrectly. A tool called <c>strace</c> was created to help deal with this. "
+"<c>strace</c> traces system calls (hence the name) which include calls that "
+"use the memory and files. For our example, we're going to take a program "
+"foobar2. This is an updated version of foobar. However, during the change "
+"over to foobar2, you notice all your configurations are missing! In foobar "
+"version 1, you had it setup to say \"foo\", but now it's using the default "
+"\"bar\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):358
+msgid "Foobar2 With an invalid configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):358
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>./foobar2</i>\n"
+"Configuration says: bar\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):363
+msgid ""
+"Our previous configuration specifically had it set to foo, so let's use "
+"<c>strace</c> to find out what's going on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):371
+msgid "Using strace to track the issue"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):374
+msgid ""
+"We make <c>strace</c> log the results of the system calls. To do this, we "
+"run <c>strace</c> with the -o[file] arguments. Let's use it on foobar2 as "
+"shown."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):379
+msgid "Running foobar2 through strace"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):379
+#, no-wrap
+msgid ""
+"\n"
+"# <i>strace -ostrace.log ./foobar2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):383
+msgid ""
+"This creates a file called <path>strace.log</path> in the current directory. "
+"We check the file, and shown below are the relevant parts from the file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):388
+msgid "A Look At the strace Log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):388
+#, no-wrap
+msgid ""
+"\n"
+"open(\".foobar2/config\", O_RDONLY) = 3\n"
+"read(3, \"bar\", 3) = 3\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):393
+msgid ""
+"Aha! So There's the problem. Someone moved the configuration directory to "
+"<path>.foobar2</path> instead of <path>.foobar</path>. We also see the "
+"program reading in \"bar\" as it should. In this case, we can recommend the "
+"ebuild maintainer to put a warning about it. For now though, we can copy "
+"over the config file from <path>.foobar</path> and modify it to produce the "
+"correct results."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):405
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):740
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1456
+msgid "Conclusion"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):408
+msgid ""
+"Now we've taken care of finding run time bugs. These bugs prove to be "
+"problematic when you try and run your programs. However, run time errors are "
+"the least of your concerns if your program won't compile at all. Let's take "
+"a look at how to address <c>emerge</c> compile errors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):420
+msgid "Handling emerge Errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):425
+msgid ""
+"<c>emerge</c> errors, such as the one displayed earlier, can be a major "
+"cause of frustration for users. Reporting them is considered crucial for "
+"maintaining the health of Gentoo. Let's take a look at a sample ebuild, "
+"foobar2, which contains some build errors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):435
+msgid "Evaluating emerge Errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):438
+msgid "Let's take a look at this very simple <c>emerge</c> error:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):442
+msgid "emerge Error (long lines are manually wrapped to fit the window)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):442
+#, no-wrap
+msgid ""
+"\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-7.o foobar2-7.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-8.o foobar2-8.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-9.o foobar2-9.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2.o foobar2.c\n"
+"foobar2.c:1:17: ogg.h: No such file or directory\n"
+"make: *** [foobar2.o] Error 1\n"
+"\n"
+"!!! ERROR: sys-apps/foobar2-1.0 failed.\n"
+"!!! Function src_compile, Line 19, Exitcode 2\n"
+"!!! Make failed!\n"
+"!!! If you need support, post the topmost build error, NOT this status message\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):460
+msgid ""
+"The program is compiling smoothly when it suddenly stops and presents an "
+"error message. This particular error can be split into 3 different sections, "
+"The compile messages, the build error, and the emerge error message as shown "
+"below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):466
+msgid "Parts of the error (long lines are manually wrapped to fit the window)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):466
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Compilation Messages)</comment>\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-7.o foobar2-7.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-8.o foobar2-8.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2-9.o foobar2-9.c\n"
+"gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n"
+" -c -o foobar2.o foobar2.c\n"
+"\n"
+"<comment>(Build Error)</comment>\n"
+"foobar2.c:1:17: ogg.h: No such file or directory\n"
+"make: *** [foobar2.o] Error 1\n"
+"\n"
+"<comment>(emerge Error)</comment>\n"
+"!!! ERROR: sys-apps/foobar2-1.0 failed.\n"
+"!!! Function src_compile, Line 19, Exitcode 2\n"
+"!!! Make failed!\n"
+"!!! If you need support, post the topmost build error, NOT this status message\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):488
+msgid ""
+"The compilation messages are what lead up to the error. Most often, it's "
+"good to at least include 10 lines of compile information so that the "
+"developer knows where the compilation was at when the error occurred."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):494
+msgid ""
+"Please make sure you always include error messages in English, even when "
+"your system language is set to something else. You can temporarily switch to "
+"English locale by prepending <c>LC_ALL=C</c> to the emerge command like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):500
+msgid "Temporarily switching locale to English"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):500
+#, no-wrap
+msgid ""
+"\n"
+"# <i>LC_ALL=C emerge sys-apps/foobar2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):504
+msgid ""
+"This is also about the only time you should use the <c>LC_ALL</c> "
+"environmental variable for specifying locale settings. If you are looking "
+"for a way to switch your system's language, then please consult our <uri "
+"link=\"guide-localization.xml\">Localization Guide</uri> instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):511
+msgid ""
+"Make errors are the actual error and the information the developer needs. "
+"When you see \"make: ***\", this is often where the error has occurred. "
+"Normally, you can copy and paste 10 lines above it and the developer will be "
+"able to address the issue. However, this may not always work and we'll take "
+"a look at an alternative shortly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):519
+msgid ""
+"The emerge error is what <c>emerge</c> throws out as an error. Sometimes, "
+"this might also contain some important information. Often people make the "
+"mistake of posting the emerge error and that's all. This is useless by "
+"itself, but with make error and compile information, a developer can get "
+"what application and what version of the package is failing. As a side note, "
+"make is commonly used as the build process for programs (<b>but not always</"
+"b>). If you can't find a \"make: ***\" error anywhere, then simply copy and "
+"paste 20 lines before the emerge error. This should take care of most all "
+"build system error messages. Now let's say the errors seem to be quite "
+"large. 10 lines won't be enough to catch everything. That's where "
+"PORT_LOGDIR comes into play."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):535
+msgid "emerge and PORT_LOGDIR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):538
+msgid ""
+"PORT_LOGDIR is a portage variable that sets up a log directory for separate "
+"emerge logs. Let's take a look and see what that entails. First, run your "
+"emerge with PORT_LOGDIR set to your favorite log location. Let's say we have "
+"a location <path>/var/log/portage</path>. We'll use that for our log "
+"directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):545
+msgid ""
+"In the default setup, <path>/var/log/portage</path> does not exist, and you "
+"will most likely have to create it. If you do not, portage will fail to "
+"write the logs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):551
+msgid "emerge-ing With PORT_LOGDIR"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):551
+#, no-wrap
+msgid ""
+"\n"
+"# <i>PORT_LOGDIR=/var/log/portage emerge cate-gory/foobar2</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):555
+msgid ""
+"Now the emerge fails again. However, this time we have a log we can work "
+"with, and attach to the bug later on. Let's take a quick look at our log "
+"directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):560
+msgid "PORT_LOGDIR Contents"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):560
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -la /var/log/portage</i>\n"
+"total 16\n"
+"drwxrws--- 2 root root 4096 Jun 30 10:08 .\n"
+"drwxr-xr-x 15 root root 4096 Jun 30 10:08 ..\n"
+"-rw-r--r-- 1 root root 7390 Jun 30 10:09 cate-gory:foobar2-1.0:20090110-213217.log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):568
+msgid ""
+"The log files have the format [category]:[package name]-[version]:[date]."
+"log. A quick look at the log file will show the entire emerge process. This "
+"can be attached later on as we'll see in the bug reporting section. Now that "
+"we've safely obtained our information needed to report the bug we can "
+"continue to do so. However, before we get started on that, we need to make "
+"sure no one else has reported the issue. Let's take a look at searching for "
+"bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):582
+msgid "Searching Using Bugzilla"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):587
+msgid ""
+"<uri link=\"http://www.bugzilla.org\">Bugzilla</uri> is what we at Gentoo "
+"use to handle bugs. Gentoo's Bugzilla is reachable by HTTPS and HTTP. HTTPS "
+"is available for those on insecure networks or simply paranoid :). For the "
+"sake of consistency, we will be using the HTTPS version in the examples to "
+"follow. Head over to <uri link=\"https://bugs.gentoo.org\">Gentoo Bugs</uri> "
+"to see how it looks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):596
+msgid ""
+"One of the most frustrating things for developers and bug-wranglers is "
+"finding duplicate bug reports. These cost them valuable time that they could "
+"otherwise use to work on more important bugs. Often, this can be prevented "
+"by a few simple search methods. So we're going to see how to search for bugs "
+"and find out if you have one that's similar. For this example, we're going "
+"to use the xclass emerge error that was used earlier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):605
+msgid "xclass emerge error"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):635
+msgid ""
+"So to begin searching, we head over to the <uri link=\"https://bugs.gentoo."
+"org/\">Bugzilla Homepage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):640
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):764
+msgid "/images/docs/bugzie-homepage.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):640
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):764
+msgid "Bugzilla Homepage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):642
+msgid ""
+"We'll click on \"Query Existing bug reports\". The reason why we choose this "
+"over the basic bug search is because the basic bug search tends to give "
+"vague results and often hinders users from looking through the results and "
+"finding the duplicate bug. Once we click on the query screen, we reach the "
+"next page:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):649
+msgid "/images/docs/bugzie-search.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):649
+msgid "Bugzilla Search Page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):651
+msgid ""
+"If you've used the Advanced Search before, you'll most likely see that "
+"screen instead."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):656
+msgid ""
+"Proceed by clicking on the \"Advanced Search\" link to bring up the Advanced "
+"Search page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):661
+msgid "/images/docs/bugzie-adv-search.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):661
+msgid "Advanced Search Page"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):663
+msgid ""
+"This is how the Advanced Search Page looks like. While it may seem "
+"overwhelming at first, we're going to look at a few simple areas to narrow "
+"down the rather vague searches bugzilla returns."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):669
+msgid "/images/docs/bugzie-content.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):669
+msgid "Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):671
+msgid ""
+"The first field is the summary of the bug. Here we're simply going to put "
+"the name of the package that's crashing. If bugzie doesn't return results, "
+"try removing the package name, just in case someone didn't put that in the "
+"summary (highly unlikely, but we've seen a fair share of strange bug "
+"reports)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):678
+msgid ""
+"Product, Component, and Version should all be set to the default. This "
+"prevents us from being too specific and missing all the bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):683
+msgid ""
+"Comment is the important part. Use the comment field to list what appears to "
+"be a specific instance of the error. Basically, don't use anything like the "
+"beginning of the build error, find a line that's before it stating a true "
+"error. Also, you'll want to filter out any punctuation to prevent bugzilla "
+"from interpreting the results the comment the wrong way. Example from the "
+"xclass emerge error:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):692
+msgid "Comment Line Content"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):692
+#, no-wrap
+msgid ""
+"\n"
+"menudef.h:78: error: brace-enclosed initializer used to initialize `OXPopupMenu'\n"
+"<comment>(Remove the quotes ' ')</comment>\n"
+"menudef.h 78 error brace-enclosed initializer used to initialize OXPopupMenu\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):698
+msgid ""
+"The above is specific enough to where we'll find the bug without wading "
+"through other xclass compile failure candidates."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):703
+msgid ""
+"URI, Whiteboard, and Keywords can all be left alone. What we've entered so "
+"far should be enough to find our bug. Let's take a look at what we have "
+"filled out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):708
+msgid "/images/docs/bugzie-comp-search.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):708
+msgid "Completed Search Form"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):710
+msgid "Now we click on the Search button and here come the results..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):714
+msgid "/images/docs/bugzie-search-result.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):714
+msgid "Search Results"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):716
+msgid ""
+"Only 2 bugs! That's a lot easier to deal with. We click on the first one to "
+"check, and sure enough it's the one we're looking for."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):721
+msgid "/images/docs/bugzie-located.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):721
+msgid "Bug Located"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):723
+msgid ""
+"Not only is it the one we want, but it has also been resolved. By checking "
+"the last comment we see the solution and know what to do in order to resolve "
+"it. Now, let's see what would have happened if we had not used the advanced "
+"search."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):729
+msgid "/images/docs/bugzie-basic-search-result.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):729
+msgid "Basic Search Results"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):731
+msgid ""
+"4 more bugs to deal with! It gets even worse with larger packages. However, "
+"with these simple tools, we're able to significantly narrow down the search "
+"to try and locate a specific bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):743
+msgid ""
+"Let's say that you have searched and searched but still can't find a bug. "
+"You've found yourself a new bug. Let's take a look at the bug reporting "
+"process for submitting your new bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):754
+msgid "Reporting Bugs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):759
+msgid ""
+"In this chapter, we'll figure out how to use Bugzilla to file a shiny, new "
+"bug. Head over to <uri link=\"https://bugs.gentoo.org\">Gentoo Bugs</uri> "
+"and..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):766
+msgid "Click on \"Report a Bug - Using the guided format\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):770
+msgid "/images/docs/bugzie-prod-select.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):770
+msgid "Product Selection"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):772
+msgid ""
+"As you can see, <b>major</b> emphasis has been placed on putting your bug in "
+"the right place. Gentoo Linux is where a large majority of bugs go."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):777
+msgid ""
+"Despite this, some people will file ebuild bugs in portage development "
+"(assumption that portage team handles the portage tree) or infra (assumption "
+"that infra has access to mirrors and rsync and can fix it directly). This is "
+"simply not how things work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):784
+msgid ""
+"Another common misconception occurs with our Documentation bugs. For "
+"example, a user finds a bug with the <uri link=\"/proj/en/releng/catalyst/"
+"\">Catalyst Docs</uri>. The general tendency is to file a bug under Docs-"
+"user, which gets assigned to the <uri link=\"http://gdp.gentoo.org\">GDP</"
+"uri>, when it should actually go to a member of the <uri link=\"/proj/en/"
+"releng/\">Release Engineering</uri> team. As a rule of thumb, only "
+"documentation under <path>http://www.gentoo.org/doc/*</path> is under the "
+"GDP. Anything under <path>http://www.gentoo.org/proj/*</path> is under the "
+"respective teams."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):795
+msgid ""
+"We would rather see a bug whose product was not supposed to be Gentoo Linux "
+"but has been filed under the same rather than seeing a bug which belongs the "
+"Gentoo Linux product and filed elsewhere. While neither is preferred, the "
+"former is more acceptable and understandable (except website bugs.. we might "
+"have an issue with that...)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):803
+msgid ""
+"Our bug goes in Gentoo Linux as it's an ebuild bug. We head over there and "
+"are presented with the multi-step bug reporting process. Let us now proceed "
+"with Step 1..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):809
+msgid "/images/docs/bugzie-guide-step1.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):809
+msgid "Guided Format Step 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):811
+msgid ""
+"The first step here is really important (as the red text tells you). This is "
+"where you search to see that someone else hasn't hit the same bug you have, "
+"yet. If you do skip this step and a bug like yours already exists, it will "
+"be marked as a DUPLICATE thus wasting a large amount of QA effort. To give "
+"you an idea, the bug numbers that are struck out above are duplicate bugs. "
+"Now comes step 2, where we give the information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):823
+msgid "Required Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):826
+msgid "/images/docs/bugzie-basic.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):826
+msgid "Basic Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):828
+msgid "Let us take a closer look at what's what."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):833
+msgid ""
+"First, there's the Product. The product will narrow down the bug to a "
+"specific area of Gentoo like Bugzilla (for bugs relating to bugs.gentoo."
+"org), Docs-user(for User Documentation) or Gentoo Linux (for ebuilds and the "
+"like)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):839
+msgid ""
+"Component is where exactly the problem occurs, more specifically which part "
+"of selected product the bug comes under. This makes classification easier."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):843
+msgid ""
+"Hardware platform is what architecture you're running. If you were running "
+"SPARC, you would set it to SPARC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):847
+msgid ""
+"Operating System is what Operating System you're using. Because Gentoo is "
+"considered a \"Meta-distribution\", it can run on other operating systems "
+"beside Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):854
+msgid "So, for our example bug, we have :"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):859
+msgid "Product - Gentoo Linux (Since it is an ebuild issue)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):860
+msgid "Component - Application (It is an application at fault, foobar2)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):861
+msgid "Hardware Platform - All (This error could occur across architectures)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):862
+msgid "Operation System - All (It could occur on all types of systems)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):865
+msgid "/images/docs/bugzie-basic-comp.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):865
+msgid "Completed Basic Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):868
+msgid ""
+"Build Identifier is basically the User Agent of the browser that is being "
+"used to report the bugs (for logging purposes). You can just leave this as "
+"is."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):873
+msgid ""
+"URL is optional and is used to point to relevant information on another site "
+"(upstream bugzilla, release notes on package homepage etc.). You should "
+"never use URL to point to pastebins for error messages, logs, <c>emerge --"
+"info</c> output, screenshots or similar information. Instead, these should "
+"always be attached to the bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):880
+msgid "In the Summary, you should put the package category, name, and number."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):885
+msgid ""
+"Not including the category in the summary really isn't too bad, but it's "
+"recommended. If you don't include the package name, however, we won't know "
+"what you're filling a bug for, and will have to ask you about it later. The "
+"version number is important for people searching for bugs. If 20 people "
+"filed bugs and not one put a version number, how would people looking for "
+"similar bugs be able to tell if one was there's? They'd have to look through "
+"every single bug, which isn't too hard, but if there are say, 200 bugs.. "
+"it's not that easy. After all the package information, you'll want to "
+"include a small description of the incident. Here's an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):897
+msgid "/images/docs/bugzie-summary.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):897
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):899
+msgid ""
+"These simple rules can make handling bugs a lot easier. Next are the "
+"details. Here we put in the information about the bug. We'll demonstrate "
+"with an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):904
+msgid "/images/docs/bugzie-details.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):904
+msgid "Details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):906
+msgid ""
+"Now the developer knows why we're filing the bug. They can then try to "
+"reproduce it. Reproducibility tells us how often we were able to make the "
+"problem recur. In this example, we can reproduce it any time simply by "
+"running foobar2. Let's put that information in."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):913
+msgid "/images/docs/bugzie-reprod.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):913
+msgid "Reproduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):915
+msgid ""
+"We have explained how we found the bug. The next step is to explain what "
+"were the results we got and what we think they should actually be."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):920
+msgid "/images/docs/bugzie-results.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):920
+msgid "Results"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):922
+msgid ""
+"We could then provide additional information. This could be things such as "
+"stack traces, <b>sections</b> (since the whole log is usually big and of not "
+"much use) of strace logs, but most importantly, your <c>emerge --info</c> "
+"output. Here's an example."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):929
+msgid "/images/docs/bugzie-addl-info.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):929
+msgid "Additional Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):931
+msgid ""
+"Lastly we select the severity of the bug. Please look this over carefully. "
+"In most cases it's OK to leave it as is and someone will raise/lower it for "
+"you. However, if you raise the severity of the bug, please make sure you "
+"read it over carefully and make sure you're not making a mistake. A run down "
+"of the various levels is given below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):940
+msgid ""
+"Blocker - The program just plain doesn't want to emerge or is a major "
+"hinderance to the system. For example a <c>baselayout</c> issue which "
+"prevents a system from booting up would be a sure candidate to be labelled "
+"blocker."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):946
+msgid ""
+"Critical - The program has loss of data or severe memory leaks during "
+"runtime. Again, an important program like say <c>net-tools</c> failing to "
+"compile could be labelled critical. It won't prevent the system from "
+"starting up, but is quite essential for day to day stuff."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):952
+msgid ""
+"Major - The program crashes, but nothing that causes your system severe "
+"damage or information loss."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):956
+msgid "Minor - Your program crashes here and there with apparent workarounds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):959
+msgid ""
+"Normal - The default. If you're not sure leave it here unless it's a new "
+"build or cosmetic change, then read below for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):963
+msgid "Trivial - Things such as a mispelled word or whitespace clean up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):964
+msgid ""
+"Enhancement - A request to enable a new feature in a program, or more "
+"specifically <e>new ebuilds</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):970
+msgid "/images/docs/bugzie-sev.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):970
+msgid "Severity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):972
+msgid "Here, we'll set it to Normal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):976
+msgid ""
+"Now we can submit the bug report by clicking on the Submit Bug Report box. "
+"You will now see your new bug come up. See <uri link=\"https://bugs.gentoo."
+"org/show_bug.cgi?id=97265\">Bug 97561</uri> for what the result looks like. "
+"We've reported our bug! Now let's see how it's dealt with."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):987
+msgid "Zero-day bump requests"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):990
+msgid ""
+"So far, we've shown what to do when filing a bug. Now let's take a look at "
+"what <e>not</e> to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):995
+msgid ""
+"Suppose that you've eagerly been following an upstream project's schedule, "
+"and when you check their homepage, guess what? They just released a new "
+"version a few minutes ago! Most users would immediately rush over to "
+"Gentoo's bugzilla to report the new version is available; please bump the "
+"existing version and add it to Portage, etc. However, this is exactly what "
+"you should <b>not</b> do. These kinds of requests are called zero-day (or 0-"
+"day) bump requests, as they're made the same day that a new version is "
+"released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(impo):1005
+msgid ""
+"<b>Please wait <e>at least</e> 48 hours before reporting a new release on "
+"our bugzilla.</b> Also, you <e>must</e> check bugzilla before posting your "
+"request to make sure that someone else hasn't already reported it, or that "
+"the Gentoo maintainers haven't already dealt with the new version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1012
+msgid ""
+"Why should you wait? First, it's quite rude to demand that Gentoo developers "
+"drop everything they're doing just to add a new release that came out 15 "
+"minutes ago. Your zero-day bump request could be marked as INVALID or LATER, "
+"as developers have plenty of pressing issues to keep them busy. Second, "
+"developers are usually aware of pending new releases well in advance of "
+"users, as they must follow upstream quite closely. They already know a new "
+"version is on its way. In many cases, they will have already opened a bug, "
+"or might even already added it in Portage as a masked package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1023
+msgid ""
+"Be smart when testing and requesting new versions of packages. Search "
+"bugzilla before posting your bump request -- is there already a bug open? "
+"Have you synced lately; is it already in Portage? Has it actually been "
+"released by upstream? Basic common sense will go a long way, and will endear "
+"you to developers that already have a lot to do. If it's been several days "
+"since release and you're sure that there are no open requests for it (and "
+"that it's not in Portage), then you can open up a new bug. Be sure to "
+"mention that it compiles and runs well on your arch. Any other helpful "
+"information you provide is most welcome."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1034
+msgid ""
+"Want to see the newest version of your favorite package in Portage? File "
+"smart bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1044
+msgid "Working With Your Bug"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1048
+msgid ""
+"Looking at the bug, we see the information we provided earlier. You will "
+"notice that the bug has been assigned to bug-wranglers@gentoo.org. This is "
+"the default location for Application component bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1054
+msgid "/images/docs/bugzie-new-basic.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1054
+msgid "New Bug Basic Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1056
+msgid "The details we entered about the bug are available as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1060
+msgid "/images/docs/bugzie-new-details.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1060
+msgid "New Bug Details"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1062
+msgid ""
+"However, bug-wranglers (usually) won't fix our bugs, so we'll reassign it to "
+"someone that can (you can let bug-wranglers re-assign it for you as well). "
+"For this we use the package's metadata.xml. You can normally find them in "
+"<path>/usr/portage/category/package/metadata.xml</path>. Here's one I've "
+"made up for foobar2."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1070
+msgid ""
+"You have to be the reporter of the bug or a member of certain Gentoo "
+"Bugzilla groups (like Gentoo Developers) to be able to reassign bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1075
+msgid "metadata.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1075
+#, no-wrap
+msgid ""
+"\n"
+"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
+"&lt;!DOCTYPE pkgmetadata SYSTEM \"http://www.gentoo.org/dtd/metadata.dtd\"&gt;\n"
+"&lt;pkgmetadata&gt;\n"
+"&lt;herd&gt;chriswhite&lt;/herd&gt;\n"
+"&lt;maintainer&gt;\n"
+"&lt;email&gt;chriswhite@gentoo.org&lt;/email&gt;\n"
+"&lt;name&gt;Chris White&lt;/name&gt;\n"
+"&lt;/maintainer&gt;\n"
+"&lt;longdescription lang=\"en\"&gt;\n"
+"Foobar2 is a package that uses a configuration file to display a word.\n"
+"&lt;/longdescription&gt;\n"
+"&lt;/pkgmetadata&gt;\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1090
+msgid ""
+"Notice the maintainer section. This lists the maintainer of the package, "
+"which in this case is myself, Chris White. The email listed is "
+"chriswhite@gentoo.org. We will use this to re-assign the bug to the proper "
+"person. To do this, click the bubble next to Reassign bug to, then fill in "
+"the email."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1097
+msgid ""
+"A bug for a package without a metadata.xml file should be re-assigned to "
+"maintainer-needed@gentoo.org and a package that needs a Gentoo Developer to "
+"maintain should be assigned to maintainer-wanted@gentoo.org."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1103
+msgid "/images/docs/bugzie-reassign.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1103
+msgid "Bug Reassignment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1105
+msgid ""
+"Then hit the Commit button for the changes to take place. The bug has been "
+"reassigned to me. Shortly afterward, you notice (by email usually) that I've "
+"responded to your bug. I've stated that I'd like to see an strace log to "
+"figure out how the program is trying to reach your configuration file. You "
+"follow the previous instructions on using strace and obtain an strace log. "
+"Now you need to attach it to the bug. In order to do this, click on \"Create "
+"A New Attachment\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1114
+msgid "/images/docs/bugzie-new-attach.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1114
+msgid "New Attachment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1116
+msgid "Now we have to attach the log. Let's go throught it step wise."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1121
+msgid ""
+"File - This is the location of the file in your machine. In this example, "
+"the location of <path>strace.log</path>. You can use the \"Browse...\" "
+"button to select the file, or enter the path directly in the text field."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1126
+msgid ""
+"Description - A short one liner, or a few wors describing the attachment. "
+"We'll just enter strace.log here, since that's quite self-explanatory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1130
+msgid "Content Type - This is the type of the file we're attaching to the bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1133
+msgid ""
+"Obsoletes - If there were attachements submitted to the bug before the "
+"current one, you have an option of declaring them obsoleted by yours. Since "
+"we have no prior attachments to this bug, we need not bother."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1138
+msgid ""
+"Comment - Enter comments that will be visible along with the attachments. "
+"You could elaborate on the attachment here, if needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1144
+msgid ""
+"With respect to Content Type, here are a few more details. You can check the "
+"\"patch\" checkbox if you're submitting a patch. Otherwise, you could ask "
+"Bugzilla to \"auto-detect\" the file type (not advisable). The other options "
+"are \"select from list\", which is most frequently used. Use plain text "
+"(text/plain) for <e>most</e> attachments except binary files like images "
+"(which can use image/gif, image/jpeg or image/png depending on type) or "
+"compressed files like .tar.bz2 which would use application/octet-stream as "
+"content type."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1155
+msgid "/images/docs/bugzie-new-attach-comp.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1155
+msgid "New Attachment Completed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1157
+msgid ""
+"We submit <path>strace.log</path> and it is reflected on the bug report."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1161
+msgid "/images/docs/bugzie-strace.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1161
+msgid "Attached strace log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1163
+msgid ""
+"We've mentioned before that sometimes ebuilds will tell you to attach a file "
+"in the emerge error. An example can be seen below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1168
+msgid "Example File Attachment Request"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1168
+#, no-wrap
+msgid ""
+"\n"
+"configure: error: PNG support requires ZLIB. Use --with-zlib-dir=&lt;DIR&gt;\n"
+"\n"
+"!!! Please attach the config.log to your bug report:\n"
+"!!! /var/tmp/portage/php-5.0.3-r1/work/php-5.0.3/config.log\n"
+"\n"
+"!!! ERROR: dev-php/php-5.0.3-r1 failed.\n"
+"!!! Function econf, Line 485, Exitcode 0\n"
+"!!! econf failed\n"
+"!!! If you need support, post the topmost build error, NOT this status message.\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1180
+msgid "Please attach any file mentioned like this to your bug report."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1184
+msgid ""
+"Sometimes a developer might ask you to attach a diff or patch for a file. "
+"Standard diff files can be obtained through:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1189
+msgid "Standard Diff Creation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1189
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>cp file file.old</i>\n"
+"$ <i>nano file</i>\n"
+"$ <i>diff -u file.old file</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1195
+msgid ""
+"For C/C++ source files, the <b>-p</b> flag is added to show what function "
+"calls the diff applies to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1200
+msgid "Diff-ing C/C++ source"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1200
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>cp file.c file.c.old</i>\n"
+"$ <i>nano file.c</i>\n"
+"$ <i>diff -up file.c.old file.c</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1206
+msgid ""
+"The documentation team will require the flag combination <b>-Nt</b> as well "
+"as <b>-u</b>. This mainly has to do with tab expansion. You can create such "
+"a diff with:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1212
+msgid "Documentation diffs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1212
+#, no-wrap
+msgid ""
+"\n"
+"$<i> cp file.xml file.xml.old</i>\n"
+"$<i> nano file.xml</i>\n"
+"$<i> diff -Nut file.xml.old file.xml</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1218
+msgid ""
+"And your diff is created. While we're doing all this, suppose another person "
+"finds your bug by searching through bugzilla and is curious to keep track of "
+"the bug, they may do so by putting their email in the Add CC field of the "
+"bug as shown below. You could also keep track of other bugs by following the "
+"same method."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1226
+msgid "/images/docs/bugzie-add-email.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1226
+msgid "Adding Email To CC:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1228
+msgid ""
+"Email addresses must be registered with Gentoo Bugzilla. In order to CC "
+"multiple addresses, simply separate them with commas or spaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1233
+msgid ""
+"After all this work, the bug can undergo various status markings. This is "
+"usually done by the Gentoo Developers and sometimes by the reporter. The "
+"following are the various possible states a bug may go through during its "
+"lifetime."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1241
+msgid ""
+"UNCONFIRMED - You're generally not going to see this too often. This means "
+"that a bug reporter has opened a bug using the advanced method and is "
+"uncertain his or her bug is an actual bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1246
+msgid "NEW - Bugs that are first opened are considered new."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1247
+msgid ""
+"ASSIGNED - When the person you've assigned the bug too validates your bug, "
+"it will often receive ASSIGNED status while they figure out the issue. This "
+"lets you know that they've accepted your bug as a real bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1252
+msgid ""
+"REOPENED - Someone has resolved a bug and you think the solution is not "
+"feasible or the problem still persists. At this point, you may re-open the "
+"bug. Please <b>do not abuse this</b>. If a developer closes the bug a second "
+"or third time, chances are that your bug is closed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1258
+msgid ""
+"RESOLVED - A firm decision has been taken on the bug. Usually goes onto "
+"FIXED to indicate the bug is solved and the matter closed although various "
+"other resolutions are possible. We'll look into those a little later."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1263
+msgid ""
+"VERIFIED - The steps take to work the bug are correct. This is usually a QA "
+"thing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1267
+msgid ""
+"CLOSED - Basically means RIP for the bug and it's buried under the never "
+"ending flow of new bugs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1273
+msgid ""
+"Now shortly afterward, we find the error in the strace log and fix the bug "
+"and mark it as RESOLVED FIXED and mention that there was a change in the "
+"location of configuration files, and that I will update the ebuild with a "
+"warning about it. The bug now becomes resolved, and you are shown the "
+"following."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1280
+msgid "/images/docs/bugzie-reso.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1280
+msgid "Resolved Bug"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1282
+msgid "A little below, you'll see the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1286
+msgid "/images/docs/bugzie-options.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1286
+msgid "Bug Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1288
+msgid ""
+"This gives you the option of Reopening the bug if you wish to (i.e. the "
+"developer thinks it's resolved but it's really not to your standards). Now "
+"our bug is fixed! However, different resolutions can occur. Here's a small "
+"list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1295
+msgid ""
+"FIXED - The bug is fixed, follow the instructions to resolve your issue."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1298
+msgid ""
+"INVALID - You did not do something specifically documented, causing the bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1302
+msgid "DUPLICATE - You didn't use this guide and reported a duplicate bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1303
+msgid ""
+"WORKSFORME - Developer/person assigned the bug cannot reproduce your error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1306
+msgid ""
+"CANTFIX - Somehow the bug cannot be solved because of certain circumstances. "
+"These circumstances will be noted by the person taking the bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1311
+msgid ""
+"WONTFIX - This is usually applied to new ebuilds or feature requests. "
+"Basically the developer does not want to add a certain feature because it is "
+"not needed, a better alternative exists, or it's just plain broken. "
+"Sometimes you may be given a solution to get said issue resolved."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1317
+msgid ""
+"UPSTREAM - The bug cannot be fixed by the Gentoo development team, and have "
+"requested you take the problem upstream (the people that actually made the "
+"program) for review. Upstream has a few ways of handling bugs. These include "
+"mailing lists, irc channels, and even bug reporting systems. If you're not "
+"sure how to contact them, ask in the bug and someone will point you to the "
+"right direction."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1327
+msgid ""
+"Sometimes, before the bug can be resolved, a developer may request that you "
+"test an updated ebulid. In the next chapter we'll take a look at testing "
+"ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1338
+msgid "Testing Ebuilds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1340
+msgid "Getting The Files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1343
+msgid ""
+"Let's say that you reported a bug for the foobar2 compile fix from earlier. "
+"Now developers might find out what the problem is and might need you to test "
+"the ebuild for them to be sure it works for you as well:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1349
+msgid "/images/docs/bugzie-ebuild-request.png"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1349
+msgid "Ebuild Test Request"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1351
+msgid ""
+"Some rather confusing vocabulary is used here. First off, let's see what an "
+"overlay is. An overlay is a special directory like <path>/usr/portage</"
+"path>, the difference being that when you <c>emerge sync</c>, files "
+"contained within it will not be deleted. Luckily, a special <path>/usr/local/"
+"portage</path> directory is created for that purpose. Let's go ahead and set "
+"our portage overlay in<path>/etc/make.conf</path>. Open make.conf up in your "
+"favorite editor and add this towards the end."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1361
+msgid "Setting Up PORTDIR_OVERLAY"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1361
+#, no-wrap
+msgid ""
+"\n"
+"PORTDIR_OVERLAY=\"/usr/local/portage\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1365
+msgid ""
+"Now we'll want to create the appropriate directories to put our test ebuild "
+"files in. In this case, we're supposed to put them in sys-apps/foobar2. "
+"You'll notice that the second comment asks for a <path>files</path> "
+"directory for the patch. This directory holds other required files that "
+"aren't included with the standard source archive (patches, init.d scripts, "
+"etc). This is a subdir in the package directory called <path>files</path>. "
+"Go ahead and create these directories:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1375
+msgid "Setting Up The Category And Package Directories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1375
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir -p /usr/local/portage/sys-apps/foobar2/files</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1379
+msgid ""
+"The -p in mkdir creates not only the directory you want but also any missing "
+"parent directories as well (sys-apps and foobar2 in this case)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1384
+msgid ""
+"Ok now, we can go ahead and download the files. First, download the ebuild "
+"into <path>/usr/local/portage/sys-apps/foobar2</path>, and then add the "
+"patch to <path>/usr/local/portage/sys-apps/foobar2/files</path>. Now that we "
+"have the files, we can begin working on testing the ebuild."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1394
+msgid "Testing The ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1397
+msgid ""
+"The process to create an ebuild that can be used by emerge is fairly simple. "
+"You must create a Manifest file for the ebuild. This can be done with the "
+"ebuild command. Run it as shown."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1403
+msgid "Creating the Manifest file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1403
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ebuild foobar2-1.0.ebuild manifest</i>\n"
+"&gt;&gt;&gt; Creating Manifest for /usr/local/portage/sys-apps/foobar2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1408
+msgid "Now let's test to see if it works as it should."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1412
+msgid "Testing With emerge -pv"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1412
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -pv foobar2</i>\n"
+"\n"
+"These are the packages that I would merge, in order:\n"
+"\n"
+"Calculating dependencies ...done!\n"
+"[ebuild N ] sys-apps/foobar2-1.0 0 kB [1]\n"
+"\n"
+"Total size of downloads: 0 kB\n"
+"Portage overlays:\n"
+" [1] /usr/local/portage\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1425
+msgid ""
+"It does seem to have worked! You'll notice the [1] next to the [ebuild] "
+"line. That points to <path>/usr/local/portage</path>, which is the overlay "
+"we created earlier. Now we go ahead and emerge the package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1431
+msgid "Emerge Result"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1431
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge foobar2</i>\n"
+" Calculating dependencies ...done!\n"
+"<comment>(compile info snipped)</comment>\n"
+"&gt;&gt;&gt; Unpacking foobar2-1.0.tar.bz2 to /var/tmp/portage/foobar2-1.0/work\n"
+" * Applying foobar2-1.0-Makefile.patch ... [ ok ]\n"
+"<comment>(compile info snipped)</comment>\n"
+"&gt;&gt;&gt; Merging sys-apps/foobar2-1.0 to /\n"
+"&gt;&gt;&gt; chris +sandbox(preinst)\n"
+"--- /usr/\n"
+"--- /usr/bin/\n"
+"&gt;&gt;&gt; /usr/bin/foobar2\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1445
+msgid ""
+"In the first section we see that the emerge started off as it should. The "
+"second section shows our patch being applied successfully by the \"[ ok ]\" "
+"status message to the right. The last section tells us the program compiled "
+"ok. The patch works! Now we can go and let the developer know that their "
+"patch works fine, and that they can commit the fix to portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1459
+msgid ""
+"This concludes the howto on working with Bugzilla. I hope you find this "
+"useful. If you have any questions, comments, or ideas regarding this "
+"document, please send them to me at <mail>chriswhite@gentoo.org</mail>. "
+"Special thanks go to moreon for his notes on -g flags and compile errors, "
+"the people at #gentoo-bugs for helping out with bug-wrangling, Griffon26 for "
+"his notes on maintainer-needed, robbat2 for general suggestions and fox2mike "
+"for fixing up the doc and adding stuff as needed."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/change-chost.xml.po b/doc/gettext/el/change-chost.xml.po
new file mode 100644
index 0000000..6e25c29
--- /dev/null
+++ b/doc/gettext/el/change-chost.xml.po
@@ -0,0 +1,518 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(guide:link):5
+msgid "/doc/en/change-chost.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(guide:lang):5
+msgid "en"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):7
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):59
+msgid "Changing the CHOST variable"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail:link):10
+msgid "amne@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail):10
+msgid "Wernfried Haas"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(author:title):12
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail:link):13
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail):13
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(author:title):15
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail:link):16
+msgid "chriswhite@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(mail):16
+msgid "Chris White"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(abstract):19
+msgid ""
+"This document explains how to change the CHOST variable of an existing "
+"system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(version):27
+msgid "3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(date):28
+msgid "2008-07-29"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):35
+msgid ""
+"Changing the CHOST is a big issue that can seriously screw up your system - "
+"so why is there a guide for that it at all?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):40
+msgid ""
+"There are certain situations where changing the CHOST is inevitable, e.g. if "
+"you want to upgrade to glibc 2.4 which only supports nptl and you find out "
+"that your CHOST is i386, which makes it impossible to use nptl. In this "
+"case, you don't have a lot of options, and changing CHOST is one of them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):47
+msgid ""
+"Even if following these instructions, problems may arise, so please make "
+"sure you read and execute them very carefully. In this example the CHOST "
+"will be changed from i386 to i686, if you do another change, please change "
+"the commands accordingly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):61
+msgid "Building the packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):64
+msgid ""
+"To start out with the CHOST change, edit the <path>/etc/make.conf</path> "
+"file and change <b>CHOST</b> value to suit your needs. Then, rebuild the "
+"following packages in this order:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):70
+msgid "Rebuilding important system tools"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):70
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av1 binutils gcc glibc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(impo):74
+msgid ""
+"Please be aware that major gcc upgrades at the same time as changing CHOST "
+"(e.g. starting with gcc 3.3, CHOST i386 and switching to gcc 4.1, CHOST "
+"i686) can lead to severe side effects. While it may not be impossible to do "
+"so, it is hard to predict which potential problems may arise and document "
+"them in this guide. As a consequence, please do one thing at a time, e.g. "
+"upgrade gcc first according to our <uri link=\"/doc/en/gcc-upgrading.xml"
+"\">gcc upgrade guide</uri> and change your CHOST afterwards. If you are on a "
+"system with CHOST=i386, you will need to mask glibc 2.4 (or newer) during "
+"the gcc upgrade as it cannot be used with i386 and unmask it once you're "
+"done."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):89
+msgid "Verifying things work"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):92
+msgid ""
+"Now it is time to make sure that your <c>gcc-config</c> and <c>binutils-"
+"config</c> settings are sane and you do not have any leftovers in <path>/etc/"
+"env.d/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):98
+msgid ""
+"The output of <c>gcc-config</c> and <c>binutils-config</c> should look like "
+"this (may differ according to your gcc version and chost, gcc 4.1.1 and i686 "
+"here):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):104
+msgid "Verifying a sane setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):104
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gcc-config -l</i>\n"
+" [1] i686-pc-linux-gnu-4.1.1 *\n"
+"# <i>gcc-config -c</i>\n"
+"i686-pc-linux-gnu-4.1.1\n"
+"\n"
+"# <i>binutils-config -l</i>\n"
+" [1] i686-pc-linux-gnu-2.16.1 *\n"
+"# <i>binutils-config -c</i>\n"
+"i686-pc-linux-gnu-2.16.1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):116
+msgid ""
+"Next, check to see if there are references to the old CHOST in <path>/etc/"
+"env.d/</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):121
+msgid "Checking for old CHOST references"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):121
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/env.d/</i>\n"
+"# <i>grep 386 *</i>\n"
+"05gcc-i386-pc-linux-gnu:PATH=\"/usr/i386-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+"05gcc-i386-pc-linux-gnu:ROOTPATH=\"/usr/i386-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(note):128
+msgid ""
+"This may not happen to you, but in this case 05gcc-i386-pc-linux-gnu "
+"contains references to the old CHOST. Things may look differently on your "
+"system depending on which CHOST you are changing to/from, or even be just "
+"fine. The name may also be 05gcc-your_new_CHOST-pc-linux-gnu."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):135
+msgid "Before deleting the file, let's check for files with the updated CHOST:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):139
+msgid "Checking for files with the updated CHOST"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):139
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grep 686 *</i>\n"
+"05binutils:MANPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/man\n"
+"05binutils:INFOPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/info\n"
+"05binutils:LDPATH=/usr/i686-pc-linux-gnu/lib\n"
+"05gcc:PATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+"05gcc:ROOTPATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+"05gcc:MANPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man\"\n"
+"05gcc:INFOPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info\"\n"
+"05gcc:LDPATH=\"/usr/lib/gcc/i686-pc-linux-gnu/4.1.1\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):151
+msgid ""
+"This one looks good as there should always be only one file for <c>gcc</c> "
+"in <path>/etc/env.d/</path> (05gcc in this example), so let's delete the one "
+"with the wrong references:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):157
+msgid "Removing the files with incorrect references"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):157
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm 05gcc-i386-pc-linux-gnu</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):161
+msgid ""
+"The same also applies to <c>binutils</c> - if there's an extra one, see "
+"which is the outdated one and delete it. Next, check your <path>/etc/env.d/"
+"binutils/</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):167
+msgid "Checking for correct binutils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):167
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/env.d/binutils/</i>\n"
+"# <i>ls -la</i>\n"
+"total 8\n"
+"-rw-r--r-- 1 root root 15 Sep 3 13:48 config-i686-pc-linux-gnu\n"
+"-rw-r--r-- 1 root root 126 Sep 3 13:48 i686-pc-linux-gnu-2.16.1\n"
+"\n"
+"# <i>cat config-i686-pc-linux-gnu</i>\n"
+"CURRENT=2.16.1\n"
+"# <i>cat i686-pc-linux-gnu-2.16.1</i>\n"
+"TARGET=\"i686-pc-linux-gnu\"\n"
+"VER=\"2.16.1\"\n"
+"LIBPATH=\"/usr/lib/binutils/i686-pc-linux-gnu/2.16.1\"\n"
+"FAKE_TARGETS=\"i686-pc-linux-gnu\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):183
+msgid ""
+"That one looks good, those two files actually should be there. Time to move "
+"on to the gcc directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):188
+msgid "Checking for correct gcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):188
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /etc/env.d/gcc</i>\n"
+"# <i>ls -la</i>\n"
+"total 12\n"
+"-rw-r--r-- 1 root root 32 Sep 3 16:43 config\n"
+"-rw-r--r-- 1 root root 32 Aug 3 14:25 config-i386-pc-linux-gnu\n"
+"-rw-r--r-- 1 root root 292 Sep 3 16:43 i686-pc-linux-gnu-4.1.1\n"
+"\n"
+"# <i>cat config</i>\n"
+"CURRENT=i686-pc-linux-gnu-4.1.1\n"
+"\n"
+"# <i>cat config-i386-pc-linux-gnu</i>\n"
+"CURRENT=i386-pc-linux-gnu-4.1.1\n"
+"\n"
+"# <i>cat i686-pc-linux-gnu-4.1.1</i>\n"
+"PATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+"ROOTPATH=\"/usr/i686-pc-linux-gnu/gcc-bin/4.1.1\"\n"
+"LDPATH=\"/usr/lib/gcc/i686-pc-linux-gnu/4.1.1\"\n"
+"GCCBITS=\"32\"\n"
+"MANPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man\"\n"
+"INFOPATH=\"/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info\"\n"
+"STDCXX_INCDIR=\"g++-v4\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):212
+msgid ""
+"<path>config</path> and <path>i686-pc-linux-gnu-4.1.1</path> are fine, but "
+"<path>config-i386-pc-linux-gnu</path> is another leftover that needs removal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(note):217
+msgid ""
+"Again, the name of the file containing references to an outdated gcc version "
+"may have a different name, e.g. config-i686-pc-linux-gnu even though you are "
+"changing to i686. It is important you identify the file on its content, not "
+"only the name."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):224
+msgid "Removing the incorrect gcc config file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm config-i386-pc-linux-gnu</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):228
+msgid "Now run the following commands to update your environment:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):232
+msgid "Updating the environment"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):232
+#, no-wrap
+msgid ""
+"\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):236
+msgid "Then verify everything is fixed:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):240
+msgid "Verifying refernces to the old CHOST are removed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):240
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grep -r 386 /etc/env.d/</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):244
+msgid ""
+"If you still find something, you must have missed some file, try to track it "
+"down before going on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):252
+msgid "Finishing The Change"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):255
+msgid ""
+"Now it is necessary to re-emerge <c>libtool</c> and run <c>/usr/share/gcc-"
+"data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh</c>. Make sure to use "
+"the correct gcc version (your current one, 4.1.1 here, and the old "
+"architecture, i386 here). Replace $CHOST with your new CHOST, and &lt;gcc-"
+"version&gt; with your gcc version. This example assumes a CHOST of i686."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):264
+msgid "Ensuring library sanity"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):264
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av1 libtool</i>\n"
+"# <i>/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/fix_libtool_files.sh 4.1.1 --oldarch i386-pc-linux-gnu</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):269
+msgid "You may want to rebuild all your packages:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):273
+msgid "Rebuilding world"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):273
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):277
+msgid ""
+"Now, in theory it should not be necessary to do so, but it can not be 100% "
+"guaranteed that this is actually the case. If you do not recompile the world "
+"target, I have been told at least some packages need recompiling, so you "
+"should do:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):284
+msgid "Remerging python"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):284
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av1 python</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):288
+msgid ""
+"All packages using perl install to the CHOST directory and hence need "
+"remerging. In case you haven't installed <c>qfile</c>, you will need to "
+"install <c>app-portage/portage-utils</c> first."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):294
+msgid "Remerging perl packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):294
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av portage-utils</i>\n"
+"# <i>emerge -av1 `qfile /usr/lib/perl* -Cq | sort -u`</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):299
+msgid ""
+"If you encounter other packages that need recompiling, please let the author "
+"of this document know."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):307
+msgid "Common problems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):310
+msgid ""
+"When upgrading from gcc 3.3 to 4.1 at the same time as changing the CHOST "
+"(please don't do that anyway), a couple of users reported broken packages "
+"that need recompiling, such as groff and courier:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre:caption):316
+msgid "Error messsage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(pre):316
+#, no-wrap
+msgid ""
+"\n"
+"error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):320
+msgid ""
+"This happens because during the upgrade, the CHOST doesn't exactly match "
+"CTARGET and the compiler assumes cross-compiling. As a consequence, LDPATH "
+"isn't inserted into <path>ld.so.conf</path>, resulting in this error."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):326
+msgid ""
+"Please see our <uri link=\"/doc/en/gcc-upgrading.xml\">gcc upgrade guide</"
+"uri> for what needs to be rebuilt after a gcc upgrade."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):331
+msgid ""
+"In some rare cases, this can break old versions of python, too. This may be "
+"fixed by adding <path>/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.6</path> "
+"(change accordingly to your old chost and gcc version) to <path>/etc/ld.so."
+"conf</path>, running <c>ldconfig</c> and then <c>emerge libstdc++-v3</c>. "
+"However, as you can see, you really should avoid running into this problem - "
+"don't change CHOST and your gcc version at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(title):343
+msgid "Feedback"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(p):346
+msgid ""
+"That should be all, feedback (both if it worked, failed or other problems "
+"were encountered) is welcome, please send an email to <mail>amne@gentoo.org</"
+"mail> or post to <uri link=\"http://forums.gentoo.org/viewtopic-t-494147.html"
+"\">this forums thread</uri>. Much in this howto comes from vapier, thanks "
+"for your help!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//change-chost.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/conky-howto.xml.po b/doc/gettext/el/conky-howto.xml.po
new file mode 100644
index 0000000..912fe73
--- /dev/null
+++ b/doc/gettext/el/conky-howto.xml.po
@@ -0,0 +1,275 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(guide:link):4
+msgid "/doc/en/conky-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):5
+msgid "Gentoo Linux Conky Howto"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(mail:link):8
+msgid "admin@sdesign.us"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(mail):8
+msgid "Bill Woodford"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(author:title):10
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(mail:link):11
+msgid "brenden@rty.ca"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(mail):11
+msgid "Brenden Matthews"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(mail:link):14
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(abstract):17
+msgid ""
+"This document describes how to install and configure the system monitor "
+"known as Conky."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(version):26
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(date):27
+msgid "2009-07-19"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):30
+msgid "Background"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):32
+msgid "Introduction to Conky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):35
+msgid ""
+"So you have a Gentoo machine, and have already learned 30 different commands "
+"to monitor different aspects of what your computer is doing at the current "
+"moment. What do you do from here? Isn't there an easier way to monitor "
+"system performance and see what it's doing, as well as the resources it's "
+"using to perform all those tasks? This is what a system monitor, such as "
+"Conky, provides."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):47
+msgid "What it does"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):50
+msgid ""
+"Unlike other system monitors such as top, Conky can run as a window in an X "
+"session, or by drawing to the root window (there is also an option to have "
+"Conky display information to stdout, but we won't discuss that here). It "
+"displays the information it has gathered through the use of both text, "
+"progress bars, and graphs. Also, unlike top, the way it is formatted is "
+"completely user-configurable. In addition to monitoring the system itself, "
+"Conky can also give you information about several music players (such as "
+"Music Player Daemon and Audacious Media Player), tell you how many new "
+"messages are in your mail spool, and plenty more. If the functionality you "
+"require isn't in Conky yet, it is a simple matter of writing a script to get "
+"the information you would like - some examples of this, which have already "
+"been done are RSS feeds, POP3 e-mail message count, local weather, boinc "
+"status, and even the status of Portage."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):70
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre:caption):104
+msgid "Installing Conky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):72
+msgid "Base install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):75
+msgid ""
+"Gentoo provides an ebuild to quickly and easily install Conky. Pay "
+"particular attention to the USE flags. You'll most likely want X11 support "
+"(<c>X</c>), and make sure you select the USE flags for any music players "
+"(other than MPD) which you want, such as Audacious (<c>audacious</c>). If "
+"you want to use the TCP port monitor, be SURE to disable the <c>ipv6</c> use "
+"flag, as the port monitor is for ipv4 systems only."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):84
+msgid ""
+"In addition, the <c>truetype</c> USE flag compiles support for TrueType "
+"fonts with the use of Xft. Most users will want this as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):89
+msgid ""
+"You can add syntax highlighting for Conky's configuration file with the "
+"<c>vim-syntax</c> and <c>nano-syntax</c> USE flags, depending on your "
+"preferred editor."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre:caption):95
+msgid "/etc/portage/package.use"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre):95
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Use the following as an example)</comment>\n"
+"# <i>echo app-admin/conky truetype audacious -ipv6 &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):100
+msgid ""
+"Once you have your USE flags correctly set up, it's time to install Conky!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre):104
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -av conky</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):108
+msgid ""
+"You can test Conky to see how it will look by running the command <c>conky</"
+"c> in a terminal. This will likely give you a good reference to how it will "
+"look and what you want to change, add or even remove."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre:caption):114
+msgid "Running Conky for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre):114
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>conky</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(note):118
+msgid ""
+"Conky needs Double Buffer Extension (DBE) support from X server to prevent "
+"flickering, because it can't update window fast enough without it. It can be "
+"enabled in <path>/etc/X11/xorg.conf</path> with <c>Load \"dbe\"</c> line in "
+"<b>Section \"Module\"</b>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):125
+msgid ""
+"Once you have an idea of how Conky looks, you can now move on to configuring "
+"it!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):133
+msgid "Configuring Conky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):136
+msgid ""
+"By default, Conky will look for a configuration file in the user's home "
+"directory located at <path>~/.conkyrc</path>. This file contains all the "
+"configuration options, and the static text, colors and other variables which "
+"control what data is shown to the user. Conky also provides a great sample "
+"configuration, located at <path>/etc/conky/conky.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre:caption):144
+msgid "Copying the sample configuration to your home directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre):144
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>cp /etc/conky/conky.conf ~/.conkyrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):148
+msgid ""
+"Now, open up the sample configuration in the text editor of your choice. You "
+"may notice that there are two separate sections of the configuration file. "
+"The first section of the file, contains the program configuration options "
+"and controls how it acts. This includes things such as the "
+"<c>update_interval</c>, or how often Conky will update the information on "
+"the screen. The second section contains the actual text, graphs, and "
+"variables which are rendered on the screen. This includes things such as the "
+"system uptime (<c>$uptime</c>), cpu usage (<c>$cpu</c>) and anything else "
+"you want to be shown. The first section of the file starts right from the "
+"beginning, the second section consists of everything after the line which "
+"says <c>TEXT</c>. Comments in the file start with <c>#</c>, but keep in mind "
+"that even if a line is commented out in the second section of the file, the "
+"text will still be rendered to the screen."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):164
+msgid ""
+"Lists of all the available configuration options and variables are kept at "
+"<uri>http://conky.sourceforge.net/config_settings.html</uri> and <uri>http://"
+"conky.sourceforge.net/variables.html</uri>. Besides, there are a few great "
+"screenshots along with sample configurations and scripts at <uri>http://"
+"conky.sourceforge.net/screenshots.html</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):177
+msgid "Extending Conky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(title):179
+msgid "Beyond the built-in variables"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(p):182
+msgid ""
+"So you've gotten this far, and have scoured the Conky documentation for that "
+"extra variable which Conky just doesn't seem to have... You're in luck! "
+"Conky provides several variables for just this reason! <c>$exec</c> Will run "
+"a command every time Conky updates, <c>$execi</c> will run a command at a "
+"specified interval and <c>$texeci</c> will run a command in its own thread "
+"at a specified interval."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(pre:caption):191
+msgid "Scripting examples"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(note):197
+msgid ""
+"While any command which works in a command shell will work in any of these "
+"variables, it is important to keep in mind that the commands must exit. This "
+"means that commands like <c>tail -f</c> which keep running will <e>not</e> "
+"work properly."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//conky-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/cron-guide.xml.po b/doc/gettext/el/cron-guide.xml.po
new file mode 100644
index 0000000..3151c35
--- /dev/null
+++ b/doc/gettext/el/cron-guide.xml.po
@@ -0,0 +1,923 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2011-01-21 01:40+0500\n"
+"PO-Revision-Date: 2011-01-21 01:40+0500\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):6
+msgid "Gentoo Linux Cron Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(mail:link):9
+msgid "eric.brown@dnbrown.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(mail):9
+msgid "Eric Brown"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(mail:link):12
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(mail):12
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(abstract):18
+msgid "This guide describes how to setup and use cron."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(version):26
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(date):27
+msgid "2010-11-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):30
+msgid "Cron basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):32
+msgid "What cron does"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):35
+msgid ""
+"Cron is a daemon that runs scheduled tasks based on input from the command "
+"<c>crontab</c>. It accomplishes this task by waking up every minute and "
+"checking to see if there are any cron-jobs to run in any of the user "
+"crontabs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):41
+msgid ""
+"Notice that <e>crontab</e> is both the name of a list of cron-jobs as well "
+"as the name of the command to edit that list."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):49
+msgid "The de facto cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):52
+msgid ""
+"There are a few cron implementations for you to choose from in Portage. All "
+"of them offer a similar interface, namely the use of <c>crontab</c> or a "
+"similar command. There is also a related utility called Anacron which is "
+"meant to work with cron on systems that are not continuously running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):59
+msgid ""
+"It is also worth noting that all of the available cron packages depend on "
+"<c>sys-process/cronbase</c>. This package is not technically depended on by "
+"any of the cron packages, but it does provide cron-like functionality that "
+"most users can appreciate."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):66
+msgid ""
+"Before we get started working with cron, you will have to choose which "
+"implementation you want to use. For your convenience, I have collected "
+"information about each one below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):77
+msgid "Which cron is right for you?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):79
+msgid "Vixie cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):82
+msgid ""
+"Vixie cron is a full featured cron implementation based on SysV cron. Each "
+"user has his own crontab and is allowed to specify environment variables "
+"within that crontab. Unlike the other cron variants, it also offers support "
+"for SELinux and PAM. It supports fewer architectures than Dcron, but more "
+"than Fcron."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):90
+msgid "Features of <c>sys-process/vixie-cron</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):95
+msgid "Support for SELinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):96
+msgid "Support for PAM <path>/etc/security/limits.conf</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):97
+msgid "Setting of environment variables in crontabs (PATH, SHELL, HOME, etc.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):100
+msgid ""
+"Each user can have his own crontab; access is controlled by <path>cron."
+"allow</path> and <path>cron.deny</path>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):109
+msgid "Dillon's Cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):112
+msgid ""
+"Dcron aims to be a simple, elegant and secure implementation of cron. It "
+"does not allow the specification of environment variables in crontabs and "
+"all cron-jobs are run from <path>/bin/sh</path>. Like Vixie cron, each user "
+"has his own crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):119
+msgid "Features of <c>sys-process/dcron</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):124
+msgid "Fast, simple and free of unnecessary features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):125
+msgid ""
+"Access to <c>crontab</c> is limited to the cron group, i.e. it doesn't rely "
+"on any external faculties"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):134
+msgid "Fcron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):137
+msgid ""
+"Fcron aims at replacing Vixie cron and Anacron. It is designed to work on "
+"systems that are not continuously running and it is packed with extra "
+"features. It has job startup constraints, job serialization controls, the "
+"ability to assign nice values to jobs and the ability to schedule jobs to "
+"run at system startup. See <uri link=\"http://fcron.free.fr/\">fcron's home "
+"page</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):146
+msgid "Features of <c>sys-process/fcron</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):151
+msgid ""
+"Designed to work on systems that are not continuously running, i.e. it can "
+"run a job after restarting if it was missed"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):155
+msgid "Setting of environment variables and many other options in crontabs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):156
+msgid ""
+"Each user can have his own crontab, access is controlled by cron.allow and "
+"cron.deny"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):160
+msgid "Enhanced crontab syntax with support for many new features"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):166
+msgid "bcron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):169
+msgid ""
+"bcron is a new cron system designed with secure operations in mind. To do "
+"this, the system is divided into several separate programs, each responsible "
+"for a separate task, with strictly controlled communications between them. "
+"The user interface is a drop-in replacement for similar systems (such as "
+"vixie-cron), but the internals differ greatly. For more information, see the "
+"bcron homepage at <uri>http://untroubled.org/bcron/</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):178
+msgid "Features of <c>sys-process/bcron</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):183
+msgid "Drop-in replacement for vixie-cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):184
+msgid "Multiprocess design"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):185
+msgid "Native daylight savings time support"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):191
+msgid "Anacron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):194
+msgid ""
+"Anacron is not a cron daemon, it is something that usually works in "
+"conjunction with one. It executes commands at intervals specified in days "
+"and it does not assume that the system is running continuously; it will run "
+"jobs that were missed while the system was down. Anacron usually relies on a "
+"cron daemon to run it each day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):207
+msgid "Using cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):209
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):212
+msgid "Select the cron implementation you like the most, and then emerge it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):216
+msgid "Installing cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):216
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dcron</i>\n"
+"# <i>/etc/init.d/dcron start</i>\n"
+"# <i>rc-update add dcron default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):222
+msgid ""
+"Optionally, if you have not installed Fcron, you may also want to install "
+"Anacron."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):227
+msgid "Installing anacron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):227
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge anacron</i>\n"
+"# <i>/etc/init.d/anacron start</i>\n"
+"# <i>rc-update add anacron default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):236
+msgid "System crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):239
+msgid ""
+"The post install messages from some of these cron packages tell you to run "
+"<c>crontab /etc/crontab</c>. The <path>/etc/crontab</path> file is your "
+"<e>system crontab</e>. A cron installation can use it in conjunction with "
+"<c>sys-process/cronbase</c> to run the scripts in <path>/etc/cron.{daily,"
+"hourly,weekly,monthly}</path>. Note that only Vixie-cron schedules jobs in "
+"<path>/etc/crontab</path> automatically. Dcron and Fcron users will need to "
+"run <c>crontab /etc/crontab</c> every time they make changes to <path>/etc/"
+"crontab</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):250
+msgid ""
+"Please note that jobs scheduled in the system crontab might not show up in "
+"the list of cron-jobs displayed by <c>crontab -l</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):255
+msgid ""
+"Of course, you can choose not to use any system crontab at all. If you chose "
+"Dcron or Fcron, do <e>not</e> run <c>crontab /etc/crontab</c>. If you chose "
+"vixie-cron or bcron, you should comment all lines in <path>/etc/crontab</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):261
+msgid "Commenting all lines in /etc/crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):261
+#, no-wrap
+msgid ""
+"\n"
+"# <i>sed -i -e \"s/^/#/\" /etc/crontab</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):268
+msgid "Giving trusted users access to cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):271
+msgid ""
+"If you want users other than root to have access to the cron daemon, you'll "
+"want to read this section, otherwise, you can proceed to the next section, "
+"<uri link=\"#scheduling\">scheduling cron-jobs</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):277
+msgid ""
+"Giving another user access to crontab does not let him run cron-jobs as "
+"root. If you want a user to be able to edit the root crontab, you should "
+"look into <c>sudo</c>. Please read our <uri link=\"/doc/en/sudo-guide.xml"
+"\">Gentoo Sudo(ers) Guide</uri> for more details."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):284
+msgid ""
+"No matter which cron package you use, if you want to allow a user to use "
+"crontab, he will first have to be in the cron group. As an example, if you "
+"wanted to add the user <e>wepy</e> to the cron group you would run:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):290
+msgid "Adding a user to the cron group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):290
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gpasswd -a wepy cron</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):294
+msgid ""
+"When adding a user to the cron group, make sure that the user log out and "
+"back in for the group change to take effect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):299
+msgid ""
+"If you're using <b>Dcron</b>, that's all you have to do to give a user "
+"access to crontab. Dcron users may proceed to the next section <uri link="
+"\"#scheduling\">scheduling cron-jobs</uri>, all others will want to keep "
+"reading."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):306
+msgid ""
+"If you're using <b>Fcron</b>, you'll want to edit <path>/etc/fcron/fcron."
+"deny</path> and <path>/etc/fcron/fcron.allow</path>. The most secure way is "
+"to first deny everyone in <path>/etc/fcron/fcron.deny</path>, and then "
+"explicitly allow users in <path>/etc/fcron/fcron.allow</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(impo):313
+msgid ""
+"<b>If neither <path>/etc/fcron/fcron.allow</path> nor <path>/etc/fcron/fcron."
+"deny</path> exist, all users in the cron group will be allowed to use "
+"crontab</b>. fcron comes with a default <path>fcron.allow</path> which "
+"<b>allows all users</b> in the cron group access to fcrontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):321
+msgid "Permissions in fcron.deny"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):321
+#, no-wrap
+msgid ""
+"\n"
+"all\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):325
+msgid ""
+"Now, say we have a user <e>wepy</e> who should be able to schedule his own "
+"cron-jobs. We would add him to <path>/etc/fcron/fcron.allow</path> as "
+"follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):330
+msgid "Permissions in fcron.allow"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):330
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):352
+#, no-wrap
+msgid ""
+"\n"
+"wepy\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):334
+msgid ""
+"If you chose <b>Vixie cron</b>, you'll probably just want to edit <path>/etc/"
+"cron.allow</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(impo):339
+msgid ""
+"It is important to note that if only <path>/etc/cron.allow</path> exists, "
+"then only the cron group users listed there will have access, but if only an "
+"empty <path>/etc/cron.deny</path> exists, then all cron group users will be "
+"allowed! <b>Do not leave an empty <path>/etc/cron.deny</path> if you have no "
+"<path>/etc/cron.allow</path>.</b>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):347
+msgid ""
+"For example, if you wanted to allow access to the user <e>wepy</e>, you "
+"would add him to <path>/etc/cron.allow</path> as follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):352
+msgid "Permissions in /etc/cron.allow"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):359
+msgid "Scheduling cron-jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):362
+msgid ""
+"The process of editing crontabs is different for each package, but they all "
+"support the same basic set of commands: adding and replacing crontabs, "
+"editing crontabs, deleting crontabs, and listing cron-jobs in crontabs. The "
+"following list shows you how to run those commands for each package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(th):371
+msgid "Version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(th):372
+msgid "Edit crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(th):373
+msgid "Remove crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(th):374
+msgid "New crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(th):375
+msgid "List cron-jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(ti):378
+msgid "dcron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):380
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):387
+msgid "[user]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):381
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):388
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):395
+msgid "file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(ti):385
+msgid "fcron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(ti):392
+msgid "vixie-cron &amp; bcron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(e):394
+msgid "-u [user]"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):400
+msgid ""
+"When using the remove command, if no argument is supplied, it deletes the "
+"current user's crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):405
+msgid "Fcron also has a symlink from <c>crontab</c> to <c>fcrontab</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):409
+msgid ""
+"Before we can use any of these commands though, you first need to understand "
+"the crontab itself. Each line in a crontab needs to specify five time fields "
+"in the following order: the minutes (0-59), hours (0-23), days of the month "
+"(1-31), months (1-12), and days of the week (0-7, Monday is 1, Sunday is 0 "
+"and 7). The days of the weeks and months can be specified by three-letter "
+"abbreviations like mon, tue, jan, feb, etc. Each field can also specify a "
+"range of values (e.g. 1-5 or mon-fri), a comma separated list of values (e."
+"g. 1,2,3 or mon,tue,wed) or a range of values with a <e>step</e> (e.g. 1-6/2 "
+"as 1,3,5)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):421
+msgid ""
+"That sounds a little confusing, but with a few examples, you will see that "
+"it is not as complicated as it sounds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):426
+msgid "Examples"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):426
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Run /bin/false every minute year round</comment>\n"
+"* * * * * /bin/false\n"
+"\n"
+"<comment># Run /bin/false at 1:35 on the mon,tue,wed and the 4th of every month</comment>\n"
+"35 1 4 * mon-wed /bin/false\n"
+"\n"
+"<comment># Run /bin/true at 22:25 on the 2nd of March</comment>\n"
+"25 22 2 3 * /bin/true\n"
+"\n"
+"<comment># Run /bin/false at 2:00 every Monday, Wednesday and Friday</comment>\n"
+"0 2 * * 1-5/2 /bin/false\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):440
+msgid ""
+"Notice how you have to specify specific days of the week and days of the "
+"month before they are combined. If you have * for only one of them, the "
+"other takes precedence, while * for both just means every day."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):446
+msgid ""
+"To test what we have just learned, let's go through the steps of actually "
+"inputting a few cron-jobs. First, create a file called <path>crons.cron</"
+"path> and make it look like the this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):452
+msgid "Editing crons.cron"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):452
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>nano crons.cron</i>\n"
+"<comment>#Mins Hours Days Months Day of the week</comment>\n"
+"10 3 1 1 * /bin/echo \"I don't really like cron\"\n"
+"30 16 * 1,2 * /bin/echo \"I like cron a little\"\n"
+"* * * 1-12/2 * /bin/echo \"I really like cron\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):460
+msgid ""
+"Now we can add that crontab to the system with the \"new command\" from the "
+"table above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):465
+msgid "A new crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):465
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab crons.cron</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):469
+msgid ""
+"You won't actually see the output from these echo commands unless you use "
+"redirection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):474
+msgid ""
+"To verify the cron-jobs you scheduled, we'll use the proper <e>list command</"
+"e> from the table above."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):479
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):564
+msgid "Listing cron-jobs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):479
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab -l</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):483
+msgid ""
+"You should see a list resembling <path>crons.cron</path>, if not, maybe you "
+"used the wrong command to input your new crontab."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):488
+msgid ""
+"This crontab should echo \"I really like cron\" every minute of every hour "
+"of every day every other month. Obviously you would only do that if you "
+"really liked cron. The crontab will also echo \"I like cron a little\" at "
+"16:30 every day in January and February. It will also echo \"I don't really "
+"like cron\" at 3:10 on the January 1st."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):496
+msgid ""
+"If you are using Anacron, you should keep reading this section. Otherwise, "
+"proceed to the next section on <uri link=\"#editing\">editing crontabs</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):501
+msgid ""
+"Anacron users will want to edit <path>/etc/anacrontab</path>. This file has "
+"four fields: the number of days between each run, the delay in minutes after "
+"which it runs, the name of the job, and the command to run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):507
+msgid ""
+"For example, to have it run <c>echo \"I like anacron\"</c> every 5 days, 10 "
+"minutes after Anacron is started, you would have:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):512
+msgid "/etc/anacrontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):512
+#, no-wrap
+msgid ""
+"\n"
+"5 10 wasting-time /bin/echo \"I like anacron\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):516
+msgid ""
+"Anacron exits after all of the jobs in anacrontab are done, so if we want it "
+"to check these jobs every day, we will need to use cron. The instructions at "
+"the end of the next section tell you how to do that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):525
+msgid "Editing crontabs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):528
+msgid ""
+"Let's be realistic though, you don't want your system telling you how much "
+"you like cron every minute. As a step forward, let's remove that crontab "
+"using the corresponding <e>remove command</e> from the table above. We will "
+"also list the cron-jobs after, just to make sure it worked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):535
+msgid "Removing a crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):535
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab -d</i>\n"
+"# <i>crontab -l</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):540
+msgid ""
+"You should see no cron-jobs in the output from <c>crontab -l</c>. If you do "
+"see jobs listed, that means we failed to remove the crontab, and that you "
+"should make sure that you used the correct <e>remove command</e> for your "
+"cron package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):546
+msgid ""
+"Now that we have a clean slate, let's put something useful into the <b>root</"
+"b> crontab. Most people will want to run <c>updatedb</c> on a weekly basis "
+"to make sure that <c>mlocate</c> works properly. To add that to your "
+"crontab, let's first edit <path>crons.cron</path> again so that it looks "
+"like the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):554
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):588
+msgid "A real crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):554
+#, no-wrap
+msgid ""
+"\n"
+"22 2 * * 1 /usr/bin/updatedb\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):558
+msgid ""
+"That would make cron run updatedb at 2:22 A.M. on Monday morning every week. "
+"You should now input the crontab with the proper <e>new command</e> from the "
+"table above, and check the list again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):564
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab crons.cron</i>\n"
+"# <i>crontab -l</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):569
+msgid ""
+"Now let's say that you also want to add <c>emerge --sync</c> to your daily "
+"schedule. You could do this by first editing <path>crons.cron</path> and "
+"then using <c>crontab crons.cron</c> just as we did before, or you could use "
+"the proper <e>edit command</e> from the table above. This gives you a way to "
+"edit your user's crontab in situ, without depending on external files like "
+"<path>crons.cron</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):578
+msgid "Editing a crontab in place"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):578
+#, no-wrap
+msgid ""
+"\n"
+"# <i>crontab -e</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):582
+msgid ""
+"That should open your user's crontab with an editor. We want to have "
+"<c>emerge --sync</c> run every day at 6:30 A.M., so we'll make it look "
+"something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):588
+#, no-wrap
+msgid ""
+"\n"
+"22 2 * * 1 /usr/bin/updatedb\n"
+"30 6 * * * /usr/bin/emerge --sync\n"
+"<comment>(if you're using anacron, add this line)</comment>\n"
+"30 7 * * * /usr/sbin/anacron -s\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):595
+msgid ""
+"Again, check the cron-jobs list as we did in the previous examples to make "
+"sure the jobs are scheduled. If they are all there, then you're all set."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):605
+msgid "Using cronbase"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):609
+msgid ""
+"As mentioned earlier, all of the available cron packages depend on <c>sys-"
+"process/cronbase</c>. The cronbase package creates <path>/etc/cron.{hourly,"
+"daily,weekly,monthly}</path>, and a script called <c>run-crons</c>. You "
+"might have noticed that the default <path>/etc/crontab</path> contains "
+"something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre:caption):617
+msgid "Default system crontab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(pre):617
+#, no-wrap
+msgid ""
+"\n"
+"*/15 * * * * test -x /usr/sbin/run-crons &amp;&amp; /usr/sbin/run-crons\n"
+"0 * * * * rm -f /var/spool/cron/lastrun/cron.hourly\n"
+"0 3 * * * rm -f /var/spool/cron/lastrun/cron.daily\n"
+"15 4 * * 6 rm -f /var/spool/cron/lastrun/cron.weekly\n"
+"30 5 1 * * rm -f /var/spool/cron/lastrun/cron.monthly\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):625
+msgid ""
+"To avoid going into much detail, we can just assume that these commands will "
+"effectively run your hourly, daily, weekly and monthly scripts. This method "
+"of scheduling cron-jobs has some important advantages:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):632
+msgid ""
+"They will run even if your computer was off when they were scheduled to run"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):635
+msgid ""
+"It is easy for package maintainers to place scripts in those well defined "
+"places"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):639
+msgid ""
+"You know exactly where your cron-jobs and your crontab are stored, making it "
+"easy for you to backup and restore this part of your system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(note):645
+msgid ""
+"Again, it is useful to point out that Vixie cron and bcron automatically "
+"read <path>/etc/crontab</path>, while dcron and fcron do not. Please read "
+"the <uri link=\"#systemtab\">System crontab</uri> section to learn more "
+"about this."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):656
+msgid "Final Notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(title):658
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):661
+msgid ""
+"If you're having problems getting cron to work properly, you might want to "
+"go through this quick checklist."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):667
+msgid ""
+"<b>Is cron running?</b> Run <c>ps ax | grep cron</c> and make sure it shows "
+"up!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):671
+msgid ""
+"<b>Is cron working?</b> Try: * * * * * /bin/echo \"foobar\" &gt;&gt; /"
+"file_you_own and make sure it works"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):675
+msgid ""
+"<b>Is your command working?</b> Try: * * * * * /bin/foobar &gt; /"
+"file_you_own 2&gt;&amp;1 and look for errors in /file_you_own"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):679
+msgid ""
+"<b>Can cron run your job?</b> Check the cron log, usually <path>/var/log/"
+"cron.log</path> or <path>/var/log/messages</path> for errors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(li):683
+msgid ""
+"<b>Are there any <path>dead.letter</path>s?</b> cron usually sends mail when "
+"there's a problem; check your mail and also look for <path>~/dead.letter</"
+"path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):690
+msgid ""
+"Remember, each cron package is different and the range of features varies "
+"greatly. Be sure to consult the man pages for crontab, fcrontab or "
+"anacrontab, depending on what you use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(p):696
+msgid "Good luck!"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//cron-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/cross-compiling-distcc.xml.po b/doc/gettext/el/cross-compiling-distcc.xml.po
new file mode 100644
index 0000000..248622d
--- /dev/null
+++ b/doc/gettext/el/cross-compiling-distcc.xml.po
@@ -0,0 +1,274 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(guide:link):5
+msgid "/doc/en/cross-compiling-distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):6
+msgid "DistCC Cross-compiling Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(mail:link):9
+msgid "agaffney@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(mail):9
+msgid "Andrew Gaffney"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(mail:link):12
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(mail):12
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(abstract):15
+msgid ""
+"This guide shows you how to set up distcc for cross-compiling across "
+"different processor architectures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(version):24
+msgid "1.3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(date):25
+msgid "2006-02-17"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):28
+msgid "Cross-compiling with distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):30
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):33
+msgid ""
+"<c>distcc</c> is a tool that lets you share the burden of software compiling "
+"across several networked computers. As long as the networked boxes are all "
+"using the same toolchain built for the same processor architecture, no "
+"special <c>distcc</c> setup is required. But what do you do if you need to "
+"compile for a different architecture using differing computers? This guide "
+"will show you how to configure <c>distcc</c> to compile for different "
+"architectures."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):45
+msgid "Emerge the needed utilities"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):48
+msgid ""
+"First, you will need to emerge <c>crossdev</c> on all the machines that will "
+"be involved in the compiling process. <c>crossdev</c> is a tool that makes "
+"building cross-architecture toolchains easy. It was originally written by "
+"<mail link=\"kumba@gentoo.org\">Joshua Kinard</mail> and was re-written from "
+"the ground up by <mail link=\"vapier@gentoo.org\">Mike Frysinger</mail>. Its "
+"usage is straightforward: <c>crossdev -t sparc</c> will build a full cross-"
+"toolchain targetting the Sparc architecture. This includes binutils, gcc, "
+"glibc, and linux-headers. If you need more help, try running <c>crossdev --"
+"help</c>. Obviously, you will need to emerge the proper cross-toolchain on "
+"all the helper boxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):61
+msgid ""
+"Next, you will need to emerge <c>distcc</c> on all the machines that will be "
+"involved in the process. This includes the box that will run emerge and the "
+"boxes with the cross-compilers. Please see the <uri link=\"/doc/en/distcc.xml"
+"\">Gentoo Distcc Documentation</uri> for more information on setting up and "
+"using <c>distcc</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):72
+msgid "Arch-specific notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):75
+msgid ""
+"If you are cross-compiling between different subarchitectures for Intel x86 "
+"(e.g. i586 and i686), you must still build a full cross-toolchain for the "
+"desired CHOST, or else the compilation will fail. This is because i586 and "
+"i686 are actually different CHOSTs, despite the fact that they are both "
+"considered \"x86.\" Please keep this in mind when you build your cross-"
+"toolchains. For example, if the target box is i586, this means that you must "
+"build i586 cross-toolchains on your i686 helper boxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):88
+msgid "Configuring distcc to cross-compile correctly"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):91
+msgid ""
+"In the default distcc setup, cross-compiling will <e>not</e> work properly. "
+"The problem is that many builds just call <c>gcc</c> instead of the full "
+"compiler name (e.g. <c>sparc-unknown-linux-gnu-gcc</c>). When this compile "
+"gets distributed to a distcc helper box, the native compiler gets called "
+"instead of your shiny new cross-compiler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):99
+msgid ""
+"Fortunately, there is a workaround for this little problem. All it takes is "
+"a wrapper script and a few symlinks on the box that will be running "
+"<c>emerge</c>. I'll use my Sparc box as an example. Wherever you see "
+"<c>sparc-unknown-linux-gnu</c> below, you will want to insert your own CHOST "
+"(<c>x86_64-pc-linux-gnu</c> for an AMD64 box, for example). When you first "
+"emerge distcc, the <path>/usr/lib/distcc/bin</path> directory looks like "
+"this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(note):108
+msgid ""
+"The following instructions are to be performed only on the box running the "
+"emerge. Do not perform these steps on the helper boxes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre:caption):113
+msgid "Available compilers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre):113
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/lib/distcc/bin</i>\n"
+"# <i>ls -l</i>\n"
+"total 0\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 c++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 cc -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 g++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 gcc -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 sparc-unknown-linux-gnu-c++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 sparc-unknown-linux-gnu-g++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Dec 23 20:13 sparc-unknown-linux-gnu-gcc -&gt; /usr/bin/distcc\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):126
+msgid "Here is what you want to do:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre:caption):130
+msgid "Modifying distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre):130
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm c++ g++ gcc cc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):134
+msgid ""
+"Next, we'll create the new script on this box. Fire up your favorite editor "
+"and create a file with the following text in it, then save it as <path>sparc-"
+"unknown-linux-gnu-wrapper</path>. Remember to change the CHOST (in this "
+"case, <c>sparc-unknown-linux-gnu</c>) to the actual CHOST of the box that "
+"will be running the emerge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre:caption):142
+msgid "The new wrapper script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre):142
+#, no-wrap
+msgid ""
+"\n"
+"#!/bin/bash\n"
+"exec /usr/lib/distcc/bin/sparc-unknown-linux-gnu-g${0:$[-2]} \"$@\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):147
+msgid "Next, we'll make the script executable and create the proper symlinks:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre:caption):151
+msgid "Creating the symlinks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre):151
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod a+x sparc-unknown-linux-gnu-wrapper</i>\n"
+"# <i>ln -s sparc-unknown-linux-gnu-wrapper cc</i>\n"
+"# <i>ln -s sparc-unknown-linux-gnu-wrapper gcc</i>\n"
+"# <i>ln -s sparc-unknown-linux-gnu-wrapper g++</i>\n"
+"# <i>ln -s sparc-unknown-linux-gnu-wrapper c++</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):159
+msgid "When you're done, <path>/usr/lib/distcc/bin</path> will look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre:caption):163
+msgid "A proper set of compilers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(pre):163
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l</i>\n"
+"total 4\n"
+"lrwxrwxrwx 1 root root 25 Jan 18 14:20 c++ -&gt; sparc-unknown-linux-gnu-wrapper\n"
+"lrwxrwxrwx 1 root root 25 Jan 18 14:20 cc -&gt; sparc-unknown-linux-gnu-wrapper\n"
+"lrwxrwxrwx 1 root root 25 Jan 18 14:20 g++ -&gt; sparc-unknown-linux-gnu-wrapper\n"
+"lrwxrwxrwx 1 root root 25 Jan 18 14:20 gcc -&gt; sparc-unknown-linux-gnu-wrapper\n"
+"lrwxrwxrwx 1 root root 15 Nov 21 10:42 sparc-unknown-linux-gnu-c++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Nov 21 10:42 sparc-unknown-linux-gnu-g++ -&gt; /usr/bin/distcc\n"
+"lrwxrwxrwx 1 root root 15 Jul 27 10:52 sparc-unknown-linux-gnu-gcc -&gt; /usr/bin/distcc\n"
+"-rwxr-xr-x 1 root root 70 Jan 18 14:20 sparc-unknown-linux-gnu-wrapper\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):176
+msgid "Congratulations; you now have a (hopefully) working cross-distcc setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(title):183
+msgid "How this works"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(p):186
+msgid ""
+"When <c>distcc</c> is called, it checks to see what it was called as (e.g. "
+"<c>i686-pc-linux-gnu-gcc</c>, <c>sparc-unknown-linux-gnu-g++</c>, etc.) When "
+"distcc then distributes the compile to a helper box, it passes along the "
+"name it was called as. The distcc daemon on the other helper box then looks "
+"for a binary with that same name. If it sees just <c>gcc</c>, it will look "
+"for <c>gcc</c>, which is likely to be the native compiler on the helper box, "
+"if it is not the same architecture as the box running <c>emerge</c>. When "
+"the <e>full</e> name of the compiler is sent (e.g. <c>sparc-unknown-linux-"
+"gnu-gcc</c>), there is no confusion."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//cross-compiling-distcc.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/cvs-tutorial.xml.po b/doc/gettext/el/cvs-tutorial.xml.po
new file mode 100644
index 0000000..00eb666
--- /dev/null
+++ b/doc/gettext/el/cvs-tutorial.xml.po
@@ -0,0 +1,1204 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(guide:link):6
+msgid "/doc/en/cvs-tutorial.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):8
+msgid "Gentoo Linux CVS Tutorial"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(author:title):10
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(mail:link):11
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(mail):11
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(author:title):13
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(mail:link):14
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(mail):14
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(abstract):17
+msgid ""
+"This tutorial introduces readers to CVS, the Concurrent Versions System, "
+"used by developers around the world to develop software in a flexible and "
+"collaborative manner. Intended for those new to CVS, this tutorial will get "
+"both general users and new developers up to speed quickly. Whether you'd "
+"like to use CVS to \"check out\" the latest sources of a particular software "
+"package, or whether you'd like to begin using CVS as a full-fledged "
+"developer, this tutorial is for you."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(version):27
+msgid "1.9"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(date):28
+msgid "2008-05-20"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):33
+msgid "Tutorial layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):36
+msgid ""
+"This tutorial has two parts. The first shows you how to use CVS as a non-"
+"developer, i.e. how to get sources from CVS and keep them updated. The "
+"second part introduces you to using CVS as a developer, showing you how to "
+"modify, add and remove files on CVS and perform other developer-related "
+"tasks. If you are new to CVS, it's recommended that you begin in the first "
+"section and proceed to the second section; if you have some basic CVS "
+"experience but are going to be using CVS as a full-fledged developer for the "
+"first time, you should find everything you need in the second section, but "
+"you may want to go through the first section as a review."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):51
+msgid "What is CVS and what does it do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):54
+msgid ""
+"CVS is a client/server system allowing developers to store their projects in "
+"a central location, called a repository. Using the cvs client tools, "
+"developers can make changes to the contents of the repository. In turn, the "
+"cvs repository tracks every change made to every file, creating a complete "
+"history of the evolution of the development project. Developers can request "
+"older versions of a particular source file, view a log of changes, and "
+"perform other useful tasks as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):67
+msgid "The role of CVS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):70
+msgid ""
+"A lot of open software projects have their own CVS servers, which are used "
+"by the project developers as a central repository for all their work. "
+"Developers often make improvements to the sources in the CVS repository on a "
+"daily basis; and often, these developers are scattered around the world, yet "
+"CVS provides the necessary mechanism to unite their project into a "
+"centralized, cohesive whole. CVS creates the \"organizational glue\" that "
+"allows these developers to make improvements to the code without stepping on "
+"each other's toes, losing important data or missing each other's critical "
+"updates to particular source files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):85
+msgid "CVS -- the latest developer sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):88
+msgid ""
+"When the developers are ready, they'll roll some their current work on CVS "
+"into a .tar.gz file and release it as a new official version of their "
+"software package. However, the latest official release sometimes isn't "
+"recent enough, for a variety of possible reasons. In the first section of "
+"this tutorial, I'll show you how to use CVS for this purpose -- acquiring "
+"the latest and greatest developer version of the sources for your own "
+"personal use."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):100
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):107
+msgid "Installing CVS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):103
+msgid "To install cvs, just type in <c>emerge cvs</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):107
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge cvs</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):114
+msgid "The CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):117
+msgid ""
+"Before we begin, there are a few CVS fundamentals that you need to know. The "
+"first is that in order to connect to a CVS repository, you first need to "
+"know a path called the \"CVSROOT\". The CVSROOT is a string, like a URL, "
+"that tells the cvs command where the remote repository is and how we'd like "
+"to connect to it. Just to make things interesting, CVS has a number of "
+"CVSROOT formats, depending on whether the CVS repository is local or remote "
+"and what method you're going to use to connect to it. Here are some example "
+"CVSROOTs, along with explanations..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):131
+msgid "A local CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):134
+msgid "Setting CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):134
+#, no-wrap
+msgid ""
+"\n"
+"CVSROOT=/var/cvsroot\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):138
+msgid ""
+"This is an example of a local CVSROOT path; you'd use a CVSROOT like this if "
+"you wanted to connect to a local repository that exists at /var/cvsroot; or "
+"maybe you have a repository mounted via NFS at /var/cvsroot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):147
+msgid "A remote password server CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):150
+msgid "Setting CVSROOT with authentification"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):150
+#, no-wrap
+msgid ""
+"\n"
+"CVSROOT=:pserver:cvs@foo.bar.com:/var/cvsroot\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):154
+msgid ""
+"Here's an example of a CVSROOT for a remote repository that exists on the "
+"foo.bar.com host and lives in the /var/cvsroot directory on that machine. "
+"The leading \":pserver:\" part tells our client to connect to this remote "
+"machine using the CVS password server protocol, a protocol that's built-in "
+"to CVS. Typically, public CVS repositories use the password server protocol "
+"to allow access to anonymous users."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):166
+msgid "A remote rsh/ssh CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):169
+msgid "RSH/SSH CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):169
+#, no-wrap
+msgid ""
+"\n"
+"CVSROOT=drobbins@foo.bar.com:/data/cvs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):173
+msgid ""
+"Here's an example of a CVSROOT that uses the RSH or SSH protocol; in this "
+"example, the CVS server will attempt to access the repository on foo.bar.com "
+"using the drobbins account. If the CVS_RSH environment variable is set to "
+"\"ssh\", then our cvs client will attempt to use ssh to connect; otherwise "
+"rsh will be used. The ssh access method is popular with those who are "
+"concerned about security; however, neither the RSH or SSH method provides a "
+"way for anonymous users to get the sources. In order to use this method, you "
+"must have a login account at foo.bar.com."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):187
+msgid "A few more things..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):190
+msgid ""
+"In addition to the CVSROOT, you'll also need to know the name of the module "
+"(collection of sources) that you'd like to check out, as well as an "
+"anonymous password that you'll need to log in to the CVS password server. "
+"Unlike anonymous ftp, there is no \"standard\" format for the anonymous "
+"password, so you'll need to get the specific password from the developer web "
+"site or the developers themselves. Once you have all this info, you're ready "
+"to begin."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):202
+msgid "Interacting with CVS, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):205
+msgid ""
+"Grabbing the sources is a two-stage process. First, we log in to the "
+"password server. Then, we grab the sources with a <c>checkout</c> command. "
+"Here's an example set of commands that can be used to check out the latest "
+"Samba sources, a popular UNIX/Windows integration project:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):212
+msgid "Setting up CVSROOT"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):212
+#, no-wrap
+msgid ""
+"\n"
+"# <i>export CVSROOT=:pserver:cvs@pserver.samba.org:/cvsroot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):216
+msgid ""
+"This first command sets the CVSROOT environment variable. If you don't set "
+"this variable, the following two commands will require an additional <c>-d :"
+"pserver:cvs@pserver.samba.org:/cvsroot</c> following the <c>cvs</c> command. "
+"Exporting the CVSROOT saves a us bit of typing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):226
+msgid "Interacting with CVS, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):229
+msgid ""
+"Here are the commands needed to get a current copy of the developer sources. "
+"You may want to jump forward to the next panel to read the explanation of "
+"these commands, and then jump back here:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):235
+msgid "Checking out sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs login</i>\n"
+"(Logging in to cvs@pserver.samba.org)\n"
+"CVS password: <comment>(enter password here)</comment>\n"
+"\n"
+"# <i>cvs -z5 co samba</i>\n"
+"U samba/COPYING\n"
+"U samba/Manifest\n"
+"U samba/README\n"
+"U samba/Read-Manifest-Now\n"
+"U samba/Roadmap\n"
+"U samba/WHATSNEW.txt\n"
+"<comment>(this is just a snippet of the complete cvs co output)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):253
+msgid "Interacting with CVS -- the explanation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):256
+msgid ""
+"The first cvs command above logs us in to the pserver, and the second tells "
+"our CVS client to check out (\"co\") the samba module using a gzip "
+"compression level of 5 (\"-z5\") to speed up the transfer over a slow link. "
+"For every new file that is created locally, cvs prints out a \"U [path]\" "
+"indicating that this particular file has been updated on disk."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):267
+msgid "Checkout complete"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):270
+msgid ""
+"Once the checkout command completes, you'll see a \"samba\" directory in "
+"your current working directory that contains the latest sources. You'll also "
+"notice that all the directories have a \"CVS\" directory inside them -- CVS "
+"stores accounting information inside these directories, and they can safely "
+"be ignored. From this point forward, we don't need to worry about having the "
+"CVSROOT environment variable set nor do we need to specify it on the command "
+"line because it's now cached inside all those extra \"CVS\" directories. "
+"Remember -- you only need to have the CVSROOT set for the initial login and "
+"checkout."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):284
+msgid "Updating the sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):287
+msgid ""
+"Well, there you are -- fresh sources! Now that you have the sources, you can "
+"go ahead and compile and install them, inspect them, or do whatever you like "
+"with them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):293
+msgid ""
+"Every now and then, you may want to bring your checked-out source directory "
+"in-sync with the current version on CVS. To do this, you don't need to log "
+"in to the pserver again; your authentication info is also cached by cvs "
+"inside those \"CVS\" accounting directories. First, enter the main checked-"
+"out directory (in this case \"samba\"), and type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):301
+msgid "Updating your sources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):301
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):358
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs update -dP</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):308
+msgid "Looking at \"cvs update\", part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):311
+msgid ""
+"If there are any new files, cvs will output \"U [path]\" lines for each one "
+"as it updates them. Also, if you compiled the sources, you will probably see "
+"a lot of \"? [path]\" lines; these are object files that cvs notices are not "
+"from the remote repository."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):321
+msgid "Looking at \"cvs update\", part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):324
+msgid ""
+"Also, notice the two command-line options we used for \"cvs update\". \"-d\" "
+"tells cvs to create any new directories that may have been added to the "
+"repository (this doesn't happen by default), and \"-P\" tells cvs to remove "
+"any empty directories from your locally checked-out copy of the sources. \"-P"
+"\" is a good idea, because cvs has a tendency to collect a lot of empty "
+"(once used, but now abandoned) directory trees over time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):333
+msgid ""
+"When it comes to simply grabbing the latest sources, that's about all you "
+"need to know. Now, we take a look at how to interact with CVS as a developer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):343
+msgid "CVS for developers"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):345
+msgid "Modifying files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):348
+msgid ""
+"As a developer, you'll need to modify files on CVS. To do this, simply make "
+"the appropriate changes to your local copy of the repository. The changes "
+"you make to the sources are not applied to the remote repository until you "
+"explictly tell cvs to \"commit\" your changes. When you've tested all your "
+"modifications to ensure that they work properly and you're ready to apply "
+"your changes to the repository, follow this two-step process. First, update "
+"your sources by typing the following command in your main source directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):358
+msgid "Updating sources and directories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):365
+msgid "CVS merges others' changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):368
+msgid ""
+"As we've seen earlier, \"cvs update\" will bring your sources up-to-date "
+"with the current version in the repository -- but what happens to the "
+"changes you've made? Don't worry, they aren't thrown away. If another "
+"developer made changes to a file that you haven't touched, your local file "
+"will be updated so that it's in-sync with the version on the repository."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):376
+msgid ""
+"And, if you modified lines 1-10 of a local file, and another developer "
+"deleted lines 40-50, added 12 new lines at the end of the file, modified "
+"lines 30-40 and then committed their changes to the repository before you, "
+"cvs will intelligently merge these changes into your locally modified copy "
+"so that none of your changes are lost. This allows two or more developers to "
+"work on different parts of the same file at the same time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):388
+msgid "Merging isn't perfect"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):391
+msgid ""
+"However, if two or more developers have made changes to the <e>same region "
+"of the same file</e>, then things get a bit more complicated. If that "
+"happens, then cvs will tell you that there's been a conflict. No work will "
+"be lost, but a bit of manual intervention will be required, since cvs now "
+"requires your input on how to merge the conflicting changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):402
+msgid "The commit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):405
+msgid ""
+"We'll look at exactly how conflicts can be resolved in just a little bit, "
+"but for now, let's assume that there are no conflicts after you typed \"cvs "
+"update -dP\" -- there usually aren't. With no conflicts, your local sources "
+"are up-to-date, and you're ready to commit your changes to the repository by "
+"typing the following command in your main source directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):413
+msgid "Committing changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):413
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs commit</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):420
+msgid "What commit does"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):423
+msgid ""
+"\"cvs commit\" doesn't <e>just</e> apply your changes to the repository. "
+"Before actually committing your changes to the remote repository, cvs will "
+"fire up your default editor so that you can type in a description of your "
+"modifications. Once you've entered your comments, saved the file and exited "
+"the editor, your changes (and comments) will be applied to the remote "
+"repository and will be available to the other developers in your team."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):435
+msgid "Viewing the log"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):438
+msgid ""
+"It's really easy to view the complete history of a particular file, along "
+"with any comments that the developers (including you) may have made when "
+"committing. To view this information, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):444
+msgid "View log information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):444
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs log myfile.c</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):448
+msgid ""
+"The \"cvs log\" command is recursive, so if you want to see the complete log "
+"for an entire directory tree, just enter the directory and type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):453
+msgid "View log information with a pager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):453
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs log | less</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):460
+msgid "Commit options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):463
+msgid ""
+"You may want to use another editor than the one cvs starts by default when "
+"you type \"cvs commit\". If so, simply set the EDITOR environment variable "
+"to the name of the editor you want to use. Putting a setting such as this "
+"one in your <path>~/.bashrc</path> would be a good idea:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):470
+msgid "Setting your editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):470
+#, no-wrap
+msgid ""
+"\n"
+"export EDITOR=jpico\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):474
+msgid ""
+"Alternatively, you can also specify a log message as a command line option "
+"so that cvs doesn't need to load up an editor in the first place:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):479
+msgid "Committing changes with a small log information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):479
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs commit -m 'I fixed a few silly bugs in portage.py'</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):486
+msgid "The .cvsrc file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):489
+msgid ""
+"Before we continue looking at more cvs commands, I recommend setting up a "
+"<path>~/.cvsrc</path> file. By creating a <path>.cvsrc</path> file in your "
+"home directory, you can tell cvs to use preferred command-line options by "
+"default so that you don't have to remember to type them in each time. Here's "
+"a recommended default <path>.cvsrc</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):497
+msgid "Recommended defaults"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):497
+#, no-wrap
+msgid ""
+"\n"
+"cvs -q\n"
+"diff -u -b -B\n"
+"checkout -P\n"
+"update -d -P\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):507
+msgid "The .cvsrc file, continued"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):510
+msgid ""
+"In addition to setting useful options for a bunch of cvs commands, the first "
+"line of the <path>.cvsrc</path> puts cvs into quiet mode, which has the "
+"primary benefit of making the <c>cvs update</c> output more consise and "
+"readable. Also, once you have this .cvsrc in place, you can type <c>cvs "
+"update</c> instead of typing <c>cvs update -dP</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):521
+msgid "Adding a file to the repository"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):524
+msgid ""
+"It's really easy to add a source file to CVS. First, create the file with "
+"your favorite text editor. Then, type the following:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):529
+msgid "Adding a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):529
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs add myfile.c</i>\n"
+"cvs server: use 'cvs commit' to add this file permanently\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):534
+msgid ""
+"This will tell cvs to add this file to the repository the next time you do a "
+"<c>cvs commit</c>. Until then, other developers won't be able to see it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):542
+msgid "Adding a directory to the repository"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):545
+msgid "The process of adding a directory to CVS is similar:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):549
+msgid "Adding a directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):549
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir foo</i>\n"
+"# <i>cvs add foo</i>\n"
+"Directory /var/cvsroot/mycode/foo added to the repository\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):555
+msgid ""
+"Unlike adding a file, when you add a directory it appears on the repository "
+"immediately; a cvs commit isn't required. Once you add a local directory to "
+"cvs, you'll notice that a \"CVS\" directory will be created inside it to "
+"serve as a container for cvs accounting data. Thus, you can easily tell if a "
+"particluar directory has been added to cvs by looking inside it for a \"CVS"
+"\" directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):566
+msgid "\"cvs add\" notes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):569
+msgid ""
+"Oh, and as you might guess, before you add a file or directory to the "
+"repository, you must make sure that its parent directory has already been "
+"added to CVS. Otherwise, you'll get an error that looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):575
+msgid "Adding a file, but receive a failure"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):575
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs add myfile.c</i>\n"
+"cvs add: cannot open CVS/Entries for reading: No such file or directory\n"
+"cvs [add aborted]: no repository\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):584
+msgid "Getting familiar with \"cvs update\", part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):587
+msgid ""
+"Before we take a look at how to resolve conflicts, let's get familiar with "
+"the output of the \"cvs update\" command. If you created a ~/.cvsrc file "
+"that contains a \"cvs -q\" line, you'll find \"cvs update\" output a lot "
+"easier to read. \"cvs update\" informs you of what it does and sees by "
+"printing out a single character, a space, and a filename; as an example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):595
+msgid "Updating CVS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):595
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cvs update -dP</i>\n"
+"? distfiles\n"
+"? packages\n"
+"? profiles\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):605
+msgid "Getting familiar with \"cvs update\", part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):608
+msgid ""
+"\"cvs update\" uses the \"?\" character to tell you that it doesn't know "
+"anything about these particular files that it finds in the local copy of "
+"your repository. They're not officially part of the repository, nor have "
+"they been scheduled for addition. Here's a list of all the other single-"
+"character informational messages that CVS uses:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):616
+msgid "Informational message: U"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):616
+#, no-wrap
+msgid ""
+"\n"
+"U [path]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):620
+msgid ""
+"Used when a new file is created in your local repository, or an untouched "
+"(by you) file has been updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):625
+msgid "Informational message: A"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):625
+#, no-wrap
+msgid ""
+"\n"
+"A [path]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):629
+msgid ""
+"This file is scheduled for addition and will be officially added to the "
+"repository when you do a <c>cvs commit</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):637
+msgid "Getting familiar with \"cvs update\", part 3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):640
+msgid "Informational message: R"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):640
+#, no-wrap
+msgid ""
+"\n"
+"R [path]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):644
+msgid ""
+"Like \"A\", an \"R\" lets you know that this file is scheduled for removal. "
+"The file will be removed from the repository as soon as you <c>cvs commit</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):649
+msgid "Informational message: M"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):649
+#, no-wrap
+msgid ""
+"\n"
+"M [path]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):653
+msgid ""
+"This means that this file has been modified by you; additionally, it's "
+"possible that new changes from the repository were merged into this file "
+"successfully."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):658
+msgid "Informational message: C"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):658
+#, no-wrap
+msgid ""
+"\n"
+"C [path]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):662
+msgid ""
+"The \"C\" character indicates that this file has a conflict and requires "
+"manual fixing before you can \"cvs commit\" your changes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):670
+msgid "Resolving conflicts intro"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):673
+msgid ""
+"Now, let's take a look at how to resolve a conflict. I'm very involved in "
+"the Gentoo Linux project, and we have our own cvs server set up at cvs."
+"gentoo.org. We developers spend most of our time hacking away at the sources "
+"inside the \"gentoo-x86\" module. Inside the gentoo-x86 module, we have a "
+"file called \"ChangeLog\" that houses (you guessed it) a description of the "
+"major changes we make to the files in the repository."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):685
+msgid "An example conflict"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):688
+msgid ""
+"Because this file is modified nearly every time a developer makes a major "
+"change to CVS, it's a primary source of conflicts -- here's an example "
+"conflict. Let's say I add the following lines to the top of the ChangeLog:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):695
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):778
+msgid "ChangeLog entry"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):695
+#, no-wrap
+msgid ""
+"\n"
+"date 25 Feb 2001\n"
+"\n"
+"This is the thing I added myself\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):701
+msgid ""
+"However, let's say that before I'm able to commit these three new lines, "
+"another developer adds these lines to the top of the ChangeLog and commits "
+"their changes:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):707
+msgid "ChangeLog entry 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):707
+#, no-wrap
+msgid ""
+"\n"
+"date 25 Feb 2001\n"
+"\n"
+"This is the part added by another developer\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):717
+msgid "An example conflict, continued"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):720
+msgid ""
+"Now, when I run <c>cvs update -dP</c> (as you should before every commit), "
+"cvs isn't able to merge the changes into my local copy of ChangeLog because "
+"we both have added lines to the exact same part of the file -- how is cvs to "
+"know which version to use? So, I get the following error from CVS:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):727
+msgid "CVS error"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):727
+#, no-wrap
+msgid ""
+"\n"
+"RCS file: /var/cvsroot/gentoo-x86/ChangeLog,v\n"
+"retrieving revision 1.362\n"
+"retrieving revision 1.363\n"
+"Merging differences between 1.362 and 1.363 into ChangeLog\n"
+"rcsmerge: warning: conflicts during merge\n"
+"cvs server: conflicts found in ChangeLog\n"
+"C ChangeLog\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):740
+msgid "Conflict resolution, part 1"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):743
+msgid ""
+"Argh -- a conflict! Fortunately, fixing conflicts is easy. If I fire up my "
+"favorite text editor, I see the following text at the top of the ChangeLog "
+"file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):749
+msgid "ChangeLog conflict"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):749
+#, no-wrap
+msgid ""
+"\n"
+"&lt;&lt;&lt;&lt;&lt;&lt;&lt; ChangeLog\n"
+"date 25 Feb 2001\n"
+"\n"
+"This is the thing I added myself\n"
+"\n"
+"=======\n"
+"date 25 Feb 2001\n"
+"\n"
+"This is the part added by another developer\n"
+"\n"
+"&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1.363\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):767
+msgid "Conflict resolution, part 2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):770
+msgid ""
+"Instead of choosing one version over the other, cvs has added both versions "
+"to the ChangeLog file, and surrounded them with special separators to "
+"clearly mark the conflict in question. Now, it's up to me to replace this "
+"region with the text that <e>should</e> appear in ChangeLog; in this case, "
+"the replacement text is neither one or the other version but a combination "
+"of both:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):778
+#, no-wrap
+msgid ""
+"\n"
+"date 25 Feb 2001\n"
+"\n"
+"This is the thing I added myself\n"
+"\n"
+"This is the part added by another developer\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):786
+msgid ""
+"Now that I've replaced the conflicting region of the file with the "
+"appropriate text (and removed the \"=======\", etc markers), I can now "
+"commit my changes to cvs without any problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):795
+msgid "Conflict resolution tips"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):798
+msgid ""
+"Whenever you need to edit a file for conflicts, make sure that you scan the "
+"entire file so that you catch all of them; if you forget to address a "
+"particular conflict, cvs won't allow you to commit until it's resolved! It's "
+"also obviously very important to remove the special markers that cvs added "
+"to the conflicting file. Another tip -- if you make a mistake while fixing "
+"the conflict and then (\"D'oh!\") accidentally save your changes, you can "
+"find an original copy of your version in the file \".#filename.version\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):811
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):821
+msgid "Removing a file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):814
+msgid ""
+"Now, it's time to learn our final CVS skill -- removing files from the "
+"repository. Removing a file is a two-stage process. First, delete the file "
+"from your local copy of the sources, and then execute the appropriate <c>cvs "
+"remove</c> command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):821
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm myoldfile.c</i>\n"
+"# <i>cvs remove myoldfile.c</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):829
+msgid "Removing a file, continued"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):832
+msgid ""
+"The file will then be scheduled for removal from the repository the next "
+"time you do a commit. Once committed, the file will be officially deleted "
+"from the current version of the repository. However, cvs won't throw this "
+"file away, and will still keep a complete record of its contents and its "
+"history, just in case you need it back in the future. This is just one of "
+"the many ways that cvs protects your valuable source code."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):841
+msgid ""
+"<c>cvs remove</c> is recursive, which means that you can delete a bunch of "
+"files, and then run the <c>cvs remove</c> command with no other arguments "
+"from a parent directory. Doing this will cause all of the deleted files to "
+"be tagged for removal at the next commit."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):851
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):859
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):882
+msgid "Removing a directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):854
+msgid ""
+"If you'd like to remove an entire directory, I recommend the following "
+"process. First, physically delete and \"cvs remove\" all files in the "
+"directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):859
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rm *.c</i>\n"
+"# <i>cvs remove</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):867
+msgid "Removing a directory, continued"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):870
+msgid "Then, perform a commit:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):874
+msgid "Commit your changes"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):874
+#, no-wrap
+msgid ""
+"\n"
+"# cvs commit\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):878
+msgid ""
+"Here comes the trick. Perform the following steps to delete the directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):882
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd ..</i>\n"
+"# <i>cvs remove mydir</i>\n"
+"# <i>rm -rf mydir</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):888
+msgid ""
+"Notice that removing the directory didn't require another commit -- "
+"directories are added to and removed from the repository in real-time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):896
+msgid "Retrieving an older version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):899
+msgid ""
+"CVS wouldn't be a good versioning system if you can't retrieve older "
+"versions from the repository. You can pull back files based on a specific "
+"date, but of course also on the revision number. The next example pulls back "
+"revision 1.202 of <path>filename</path> and overwrites the current "
+"<path>filename</path> with this version:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre:caption):907
+msgid "Retrieving a file based on the revision number"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(pre):907
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>cvs update -p -r 1.202 filename &gt; filename</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):911
+msgid ""
+"If you want to pull back files based on their date, use the <c>-D</c> "
+"argument. You can use entire date/timestamps, but also relative names such "
+"as <e>yesterday</e> or <e>last week</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):920
+msgid "Complete!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):923
+msgid ""
+"Your introduction to CVS is complete -- I hope that this tutorial has been "
+"helpful. There's much more to CVS than I've been able to cover in this "
+"introductory tutorial, but thankfully there are a bunch of great CVS "
+"resources you can use to further expand your CVS knowledge:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(li):931
+msgid ""
+"<uri>http://www.cvshome.org</uri> is the home of CVS development, and offers "
+"a bunch of documentation on CVS, including the <uri link=\"http://www."
+"cvshome.org/docs/manual\">official CVS documentation online</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(li):937
+msgid ""
+"The <uri link=\"http://www.durak.org/cvswebsites/\">CVS Version Control for "
+"Web Site Projects site</uri> has good info on how to use CVS for developing "
+"web sites"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(li):942
+msgid ""
+"Karl Fogel has written a book called <uri link=\"http://cvsbook.red-bean.com/"
+"\">Open Source Development with CVS</uri>. A number of chapters are "
+"available for free from the website."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(li):947
+msgid ""
+"<uri link=\"http://www.freebsd.org/projects/cvsweb.html\">cvsweb</uri> is a "
+"really great CGI script that provides a web interface to your CVS "
+"repository; excellent for browsing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(li):952
+msgid ""
+"The <uri link=\"http://www.loria.fr/~molli/cvs-index.html\">CVS Bubbles</"
+"uri> site has a bunch of good resources including a CVS FAQ-o-matic."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(title):961
+msgid "About this document"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(p):964
+msgid ""
+"The original version of this article was first published on IBM "
+"developerWorks, and is property of Westtech Information Services. This "
+"document is an updated version of the original article, and contains various "
+"improvements made by the Gentoo Linux documentation team."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//cvs-tutorial.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/desktop.xml.po b/doc/gettext/el/desktop.xml.po
new file mode 100644
index 0000000..133c46f
--- /dev/null
+++ b/doc/gettext/el/desktop.xml.po
@@ -0,0 +1,64 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(guide:link):4
+msgid "desktop.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(guide:redirect):4
+msgid "index.xml?catid=desktop#doc_chap2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(title):5
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(title):15
+msgid "Gentoo Desktop Documentation Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(author:title):6
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(mail:link):7
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(mail):7
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(abstract):10
+msgid "Replaced by metadoc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(version):11
+msgid "1.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(date):12
+msgid "2005-01-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(title):17
+msgid "Information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(p):20
+msgid ""
+"Please use the new <uri link=\"/doc/en/index.xml?catid=desktop\">Gentoo "
+"Desktop Documentation Resources</uri> page."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//desktop.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/devfs-guide.xml.po b/doc/gettext/el/devfs-guide.xml.po
new file mode 100644
index 0000000..32b34d3
--- /dev/null
+++ b/doc/gettext/el/devfs-guide.xml.po
@@ -0,0 +1,588 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(guide:link):6
+msgid "/doc/en/devfs-guide.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):7
+msgid "Device File System Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(mail:link):9
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(mail):9
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(author:title):11
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(mail:link):12
+msgid "seemant@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(mail):12
+msgid "Seemant Kulleen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(abstract):15
+msgid ""
+"In this document you'll find information on what devfs is really about and "
+"how to work with it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(version):24
+msgid "0.8"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(date):25
+msgid "2007-11-15"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):28
+msgid "What is devfs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):30
+msgid "The (good?) old days"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(warn):33
+msgid ""
+"devfs is <e>obsolete</e> and has been removed from the stable 2.6 tree in "
+"the 2.6.13 release. Users on 2.6 kernels are hereby advised to switch to "
+"udev. For further information on udev, please refer to the <uri link=\"/doc/"
+"en/udev-guide.xml\">Gentoo udev Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):40
+msgid ""
+"Traditional Linux implementations provide their users with an abstract "
+"device path, called <path>/dev</path>. Inside this path the user finds "
+"<e>device nodes</e>, special files that represent devices inside their "
+"system. For instance, <path>/dev/hda</path> represents the first IDE device "
+"in their system. By providing device files to the users, they can create "
+"programs that interact with hardware as if the hardware was a regular file "
+"instead of using special APIs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):50
+msgid ""
+"The device files are split in two groups, called <e>character</e> devices "
+"and <e>block</e> devices. The first group consists of hardware of which read/"
+"writes are not buffered. The second group naturally consists of hardware of "
+"which read/writes are buffered. Both devices can be read one character at a "
+"time, or in blocks. Therefore, the naming might sound confusing and in fact "
+"is wrong."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):59
+msgid ""
+"If you take a look at a certain device file, you might find something like "
+"this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):64
+msgid "Checking the information of a device file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):64
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l /dev/hda</i>\n"
+"brw-rw---- 1 root disk 3, 0 Jul 5 2000 /dev/hda\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):69
+msgid ""
+"In the previous example we see that <path>/dev/hda</path> is a block device. "
+"However, more importantly, it has two special numbers assigned to it: <b>3, "
+"0</b>. This pair is called the <e>major-minor</e> pair. It is used by the "
+"kernel to map a device file to a real device. The major corresponds with a "
+"certain device, the minor with a subdevice. Seems confusing? It isn't."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):78
+msgid ""
+"Two examples are <path>/dev/hda4</path> and <path>/dev/tty5</path>. The "
+"first device file corresponds with the fourth partition on the first IDE "
+"device. Its major-minor pair is <b>3, 4</b>. In other words, the minor "
+"corresponds with the partition where the major corresponds with the device. "
+"The second example has <b>4, 5</b> as major-minor pair. In this case, the "
+"major corresponds with the terminal driver, while the minor corresponds with "
+"the terminal number (in this case, the fifth terminal)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):92
+msgid "The problems"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):95
+msgid ""
+"If you do a quick check in such a <path>/dev</path>, you'll find out that "
+"not only all your devices are listed, but <e>all</e> possible devices that "
+"you can imagine. In other words, you have device files for devices you don't "
+"have. Managing such a device group is cumbersome to say the least. Imagine "
+"having to change the permissions of all device files that have a "
+"corresponding device in your system, and leaving the rest of the device "
+"files as they are."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):105
+msgid ""
+"When you add new hardware to your system, and this hardware didn't have a "
+"device file previously, you would have to create one. Advanced users know "
+"that this task can be accomplished with <c>./MAKEDEV</c> inside the <path>/"
+"dev</path> tree, but do you immediately know what device you have to create?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):113
+msgid ""
+"When you have programs interacting with hardware using the device files, you "
+"can't have the root partition mounted read only, while there is no further "
+"need to have it mounted read-write. And you can't have <path>/dev</path> on "
+"a seperate partition, since <c>mount</c> needs <path>/dev</path> to mount "
+"partitions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):124
+msgid "The solutions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):127
+msgid ""
+"As you can imagine, the kernel hackers have found quite a number of "
+"solutions to the aforementioned problems. However, many of them had other "
+"flaws as described in <uri>http://www.atnf.csiro.au/people/rgooch/linux/docs/"
+"devfs.html#faq-why</uri>. We are not going to talk about these "
+"implementations, but focus on the one implementation that did make it to the "
+"official kernel sources: devfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):140
+msgid "devfs as all-round winner ?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):143
+msgid ""
+"devfs tackles all listed problems. It only provides the user with existing "
+"devices, adds new nodes when new devices are found, and makes it possible to "
+"mount the root filesystem read only. And it tackles more problems we haven't "
+"discussed previously because they are less interesting for users..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):151
+msgid ""
+"For instance, with devfs, you don't have to worry about major/minor pairs. "
+"It is still supported (for backwards compatibility), but isn't needed. This "
+"makes it possible for Linux to support even more devices, since there are no "
+"limits anymore (numbers always have boundaries :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):158
+msgid ""
+"Yet devfs does come with it's own problems; for the end users these issues "
+"aren't really visible, but for the kernel maintainers the problems are big "
+"enough to mark devfs <e>obsolete</e> in favor of <uri link=\"udev-guide.xml"
+"\">udev</uri>, which Gentoo supports and uses by default on most "
+"architectures since the 2005.0 release when using a 2.6 kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):166
+msgid ""
+"For more information as to why devfs is marked obsolete, please read the "
+"<uri link=\"http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ"
+"\">udev FAQ</uri> and <uri link=\"http://www.kernel.org/pub/linux/utils/"
+"kernel/hotplug/udev_vs_devfs\">udev versus devfs document</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):179
+msgid "Navigating through the device tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):181
+msgid "Directories"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):184
+msgid ""
+"One of the first things you might notice is that devfs uses directories to "
+"group devices together. This improves readability, as now all related "
+"devices are inside a common directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):190
+msgid ""
+"For instance, all IDE-related devices are inside the <path>/dev/ide/</path> "
+"device directory, and SCSI-related devices are inside <path>/dev/scsi/</"
+"path>. SCSI and IDE disks are seen in the same way, meaning they both have "
+"the same subdirectory structure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):197
+msgid ""
+"IDE and SCSI disks are controlled by an adapter (on-board or a seperate "
+"card), called the <e>host</e>. Every adapter can have several channels. A "
+"channel is called a <e>bus</e>. On each channel, you can have several IDs. "
+"Such an ID identifies a disk. This ID is called the <e>target</e>. Some SCSI "
+"devices can have multiple luns (<e>Logical Unit Numbers</e>), for instance "
+"devices that handle multiple media simultaneously (hi-end tapedrives). You "
+"mostly have only a single lun, <path>lun0/</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):207
+msgid ""
+"So, whereas <path>/dev/hda4</path> was used previously, we now have <path>/"
+"dev/ide/host0/bus0/target0/lun0/part4</path>. This is far more easy... no, "
+"don't argue with me... it <e>is</e> easier... ah whatever! :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(note):214
+msgid ""
+"You can also use more Unix-like device file naming for hard disks, such as "
+"<path>c0b0t0u0p2</path>. They can be found in <path>/dev/ide/hd</path>, "
+"<path>/dev/scsi/hd</path> etc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):220
+msgid ""
+"To give you an idea on the directories, this is a listing of the directories "
+"which I have on my laptop:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):225
+msgid "Directories in /dev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):225
+#, no-wrap
+msgid ""
+"\n"
+"cdroms/ cpu/ discs/ floppy/\n"
+"ide/ input/ loop/ misc/\n"
+"netlink/ printers/ pts/ pty/\n"
+"scsi/ sg/ shm/ sound/\n"
+"sr/ usb/ vc/ vcc/\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):236
+msgid "Backwards compatibility using devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):239
+msgid ""
+"Using this new scheme sounds fun, but several tools and programs make use of "
+"the previous, old scheme. To make sure no system is broken, <c>devfsd</c> is "
+"created. This daemon creates symlinks with the old names, pointing to the "
+"new device files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):246
+msgid "Created symlinks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):246
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>ls -l /dev/hda4</i>\n"
+"lr-xr-xr-x 1 root root 33 Aug 25 12:08 /dev/hda4 -&gt; ide/host0/bus0/target0/lun0/part4\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):251
+msgid ""
+"With <c>devfsd</c>, you can also set the permissions, create new device "
+"files, define actions etc. All this is described in the next chapter."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):261
+msgid "Administrating the device tree"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):263
+msgid "Restarting devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):266
+msgid ""
+"When you alter the <path>/etc/devfsd.conf</path> file, and you want the "
+"changes to be forced onto the system, you don't have to reboot. Depending on "
+"what you want, you can use any of the two following signals:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):273
+msgid ""
+"<b>SIGHUP</b> will have <c>devfsd</c> reread the configuration file, reload "
+"the shared objects and generate the REGISTER events for each leaf node in "
+"the device tree."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):279
+msgid "<b>SIGUSR1</b> will do the same, but won't generate REGISTER events."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):283
+msgid "To send a signal, simply use <c>kill</c> or <c>killall</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):287
+msgid "Sending the SIGHUP signal to devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):287
+#, no-wrap
+msgid ""
+"\n"
+"# <i>kill -s SIGHUP `pidof devfsd`</i>\n"
+"<comment>or</comment>\n"
+"# <i>killall -s SIGHUP devfsd</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):296
+msgid "Removing compatibility symlinks"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(warn):299
+msgid "Currently, Gentoo cannot live without the compatibility symlinks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):303
+msgid ""
+"If you want the compatibility symlinks that clutter up <path>/dev</path> "
+"removed from your Gentoo system (Gentoo activates it per default), edit "
+"<path>/etc/devfsd.conf</path> and remove the following two lines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):309
+msgid "/etc/devfsd.conf for backwards compatibility"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):309
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Comment the following two lines out to remove the symlinks</comment>\n"
+"REGISTER .* MKOLDCOMPAT\n"
+"UNREGISTER .* RMOLDCOMPAT\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):315
+msgid "You need to reboot your system for the changes to take affect."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):322
+msgid "Removing autoload functionality"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):325
+msgid ""
+"When you load a module, devfs will automatically create the device files. If "
+"you don't want this behaviour, remove the following line from <path>/etc/"
+"devfsd.conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):331
+msgid "/etc/devfsd.conf, autoload functionality"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):331
+#, no-wrap
+msgid ""
+"\n"
+"LOOKUP .* MODLOAD\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):340
+msgid "Permission Related Items"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):342
+msgid "Set/change permissions with devfsd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(impo):345
+msgid ""
+"These instructions are valid as long as pam_console is disabled in <path>/"
+"etc/pam.d/system-auth</path>. If you enabled pam_console there, then PAM has "
+"the final word on permissions. You shouldn't be using pam_console anyway, as "
+"it has been <uri link=\"http://www.gentoo.org/proj/en/base/pam/upgrade-0.99."
+"xml\">removed from Portage</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):354
+msgid ""
+"If you want to set permissions using <path>/etc/devfsd.conf</path>, then use "
+"the syntax used in the following example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):359
+msgid "Permissions in /etc/devfsd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):359
+#, no-wrap
+msgid ""
+"\n"
+"REGISTER ^cdroms/.* PERMISSIONS root.cdrom 0660\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):363
+msgid ""
+"The second field is the device group, starting from <path>/dev</path>. It is "
+"a regular expression, meaning you can select several device files in one "
+"rule."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):369
+msgid ""
+"The fourth field is the ownership of the device file, and the fifth field "
+"contains the permissions of the device file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):377
+msgid "Manually set permissions and have devfsd save it"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):380
+msgid ""
+"This is the default behaviour for Gentoo: if you <c>chown</c> (CHange OWNer) "
+"and <c>chmod</c> (CHange MODe) some device files, <c>devfsd</c> will save "
+"the information so that it will persist across reboots. This is because the "
+"<path>/etc/devfsd.conf</path> file contains the following lines:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):388
+msgid "/etc/devfsd.conf for saving permissions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):388
+#, no-wrap
+msgid ""
+"\n"
+"REGISTER ^pt[sy]/.* IGNORE\n"
+"CHANGE ^pt[sy]/.* IGNORE\n"
+"CREATE ^pt[sy]/.* IGNORE\n"
+"DELETE ^pt[sy] IGNORE\n"
+"REGISTER ^log IGNORE\n"
+"CHANGE ^log IGNORE\n"
+"CREATE ^log IGNORE\n"
+"DELETE ^log IGNORE\n"
+"REGISTER .* COPY /lib/dev-state/$devname $devpath\n"
+"CHANGE .* COPY $devpath /lib/dev-state/$devname\n"
+"CREATE .* COPY $devpath /lib/dev-state/$devname\n"
+"DELETE .* CFUNCTION GLOBAL unlink\n"
+"/lib/dev-state/$devname\n"
+"RESTORE /lib/dev-state\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):405
+msgid ""
+"In other words, changed device files are copied over to <path>/lib/dev-"
+"state</path> as soon as the change happens, and are copied over to <path>/"
+"dev</path> when booting the system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):411
+msgid ""
+"Another possibility is to mount <path>/lib/dev-state</path> on <path>/dev</"
+"path> at boot-time. To do this, you must make sure that devfs is not mounted "
+"automatically (meaning you'll have to recompile your kernel) and that <path>/"
+"dev/console</path> exists. Then, somewhere at the beginning of the "
+"bootscripts of your system, you place:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre:caption):419
+msgid "Mounting /lib/dev-state on top of /dev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(pre):419
+#, no-wrap
+msgid ""
+"\n"
+"mount --bind /dev /lib/dev-state\n"
+"mount -t devfs none /dev\n"
+"devfsd /dev\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(title):430
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):434
+msgid "For more information on devfs, check out the following resources."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):438
+msgid ""
+"The devfsd.conf manpage explains the syntax of the <path>/etc/devfsd.conf</"
+"path> file. To view it, type <c>man devfsd.conf</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):444
+msgid ""
+"The <uri link=\"http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html"
+"\">devfs FAQ</uri> explains everything about devfs. It also contains "
+"information about the internal devfs structure and how drivers can support "
+"devfs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):451
+msgid ""
+"On <uri link=\"http://www.linuxjournal.com\">LinuxJournal</uri> there is an "
+"interesting article on <uri link=\"http://www.linuxjournal.com/article.php?"
+"sid=6035\">devfs for Management and Administration</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(p):458
+msgid ""
+"Daniel Robbins has written a set of articles for IBM's DeveloperWorks about "
+"Advanced filesystems. Three of them are about devfs:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri:link):465
+msgid "http://www-106.ibm.com/developerworks/linux/library/l-fs4/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri):465
+msgid "Introduction to devfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri:link):469
+msgid "http://www-106.ibm.com/developerworks/linux/library/l-fs5/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri):469
+msgid "Setting up devfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri:link):473
+msgid "http://www-106.ibm.com/developerworks/linux/library/l-fs6/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(uri):473
+msgid "Implementing devfs"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//devfs-guide.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/diskless-howto.xml.po b/doc/gettext/el/diskless-howto.xml.po
new file mode 100644
index 0000000..c24c64b
--- /dev/null
+++ b/doc/gettext/el/diskless-howto.xml.po
@@ -0,0 +1,1686 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(guide:link):5
+msgid "/doc/en/diskless-howto.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):6
+msgid "Diskless Nodes with Gentoo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(author:title):8
+msgid "Researcher"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail:link):9
+msgid "ma53@drexel.edu"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail):9
+msgid "Michael Andrews"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(author:title):11
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail:link):12
+msgid "unsolo@sysrq.no"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail):12
+msgid "Kristian Jerpetjoen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(author:title):14
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(author:title):17
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail:link):15
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail):15
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail:link):18
+msgid "neysx@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(mail):18
+msgid "Xavier Neys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(abstract):21
+msgid "This HOWTO will help you create setup diskless nodes with Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(version):29
+msgid "1.27"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(date):30
+msgid "2009-01-25"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):33
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):35
+msgid "About this HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):38
+msgid ""
+"This HOWTO will help you setup <e>diskless</e> workstations based on the "
+"Gentoo Linux distribution. We intend to make this as user friendly as "
+"possible and cater to the Linux newbie, because every one of us was one at a "
+"certain point :) While an experienced user could easily tie the multiple "
+"HOWTOs available on diskless nodes and networking together we hope that this "
+"guide can ease the installation for all interested users, geeks or not."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):50
+msgid "What is a diskless machine?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):53
+msgid ""
+"A diskless machine is a PC without any of the usual boot devices such as "
+"hard disks, floppy drives or CD-ROMs. The diskless node boots off the "
+"network and needs a server that will provide it with storage space as a "
+"local hard disk would. From now on we call the server the <e>master</e>, "
+"while the diskless machine gets called the <e>slave</e> (what's in a "
+"name :). The slave node needs a network adapter that supports PXE booting or "
+"Etherboot; check <uri link=\"http://www.etherboot.org\">Etherboot.org</uri> "
+"for support listings. Most modern cards support PXE and many built-in "
+"adapters on motherboards will also work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):68
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):993
+msgid "Before you start"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):71
+msgid ""
+"You should have Gentoo installed on your master node and enough space on the "
+"master to store the file systems of the slave nodes you want to host. Also "
+"make sure you have one interface to the internet separated from the local "
+"area connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):83
+msgid "Configuring the master and the slaves"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):85
+msgid "About kernels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):88
+msgid ""
+"The kernel is the software that sits between your hardware and all other "
+"software you have loaded on your machine, essentially the heart of a kernel "
+"based operating system. When your computer is started, the BIOS executes the "
+"instructions found at the reserved boot space of your hard drive. These "
+"instructions are typically a boot loader that loads your kernel. After your "
+"kernel has been loaded all processes are handled by the kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):97
+msgid ""
+"For more information on kernels and kernel configuration you might want to "
+"check out the <uri link=\"http://www.tldp.org/HOWTO/Kernel-HOWTO.html"
+"\">kernel HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):106
+msgid "Configuring the master kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):109
+msgid ""
+"The master kernel can be as large and as customized as you would like but "
+"there are a few required kernel options you need to select. Go into your "
+"kernel configuration menu by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):115
+msgid "Editing the master's kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):115
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):235
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):120
+msgid ""
+"You should get a grey and blue GUI that offers a safe alternative to "
+"manually editing the <path>/usr/src/linux/.config</path> file. If your "
+"kernel is currently functioning well you might want to save the current "
+"configuration file by exiting the GUI and type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):127
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):215
+msgid "Backing up the master's kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):127
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp .config .config_working</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):131
+msgid ""
+"Go into the following sub-menus and make sure the listed items are checked "
+"as built-in (and <e>NOT</e> as modular). The options show below are taken "
+"from the 2.6.10 kernel version. If you use a different version, the text or "
+"sequence might differ. Just make sure you select at least those shown below."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):138
+msgid "master's kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):138
+#, no-wrap
+msgid ""
+"\n"
+"Code maturity level options ---&gt;\n"
+" [*] Prompt for development and/or incomplete code/drivers\n"
+"\n"
+"Device Drivers ---&gt;\n"
+" Networking options ---&gt;\n"
+" &lt;*&gt; Packet socket\n"
+" &lt;*&gt; Unix domain sockets\n"
+" [*] TCP/IP networking\n"
+" [*] IP: multicasting\n"
+" [ ] Network packet filtering (replaces ipchains)\n"
+"\n"
+"File systems ---&gt;\n"
+" Network File Systems ---&gt;\n"
+" &lt;*&gt; NFS server support\n"
+" [*] Provide NFSv3 server support\n"
+"\n"
+"<comment>\n"
+"If you want to access the internet through your master node and/or have a\n"
+"secure firewall make sure to add support for iptables\n"
+"</comment>\n"
+" [*] Network packet filtering (replaces ipchains)\n"
+" IP: Netfilter Configuration ---&gt;\n"
+" &lt;*&gt; Connection tracking (required for masq/NAT)\n"
+" &lt;*&gt; IP tables support (required for filtering/masq/NAT)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):165
+msgid ""
+"If you want to use packet filtering, you can add the rest as modules later. "
+"Make sure to read the <uri link=\"/doc/en/security/security-handbook.xml?"
+"part=1&amp;chap=12\">Gentoo Security Handbook Chapter about Firewalls</uri> "
+"on how to set this up properly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):172
+msgid ""
+"These kernel configuration options should only be added to your system "
+"specific configuration options and are not meant to completely replace your "
+"kernel configuration."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):178
+msgid ""
+"After you have re-configured the master's kernel you will want to rebuild it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):182
+msgid "Recompiling the master's kernel and modules"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):182
+#, no-wrap
+msgid ""
+"\n"
+"# <i>make &amp;&amp; make modules_install</i>\n"
+"<comment>(Make sure /boot is mounted before copying to it)</comment>\n"
+"# <i>cp arch/i386/boot/bzImage /boot/bzImage-master</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):188
+msgid ""
+"Then add an entry for that new kernel into <path>lilo.conf</path> or "
+"<path>grub.conf</path> depending on which bootloader you are using and make "
+"the new kernel the default one. Now that the new bzImage has been copied "
+"into your boot directory all you will have to do is reboot the system in "
+"order to load these new options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):199
+msgid "About the slave kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):202
+msgid ""
+"It is recommended that you compile the slave kernel without any modules, "
+"since loading and setting them up via remote boot is a difficult and "
+"unnecessary process. Additionally, the slave kernel should be as small and "
+"compact as possible in order to efficiently boot from the network. We are "
+"going to compile the slave's kernel in the same place where the master was "
+"configured."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):210
+msgid ""
+"To avoid confusion and wasting time it is probably a good idea to backup the "
+"master's configuration file by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):215
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /usr/src/linux/.config /usr/src/linux/.config_master</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):219
+msgid ""
+"Now we will want to configure the slave's kernel in the same fashion we "
+"configured the master's kernel. If you want to start with a fresh "
+"configuration file you can always recover the default <path>/usr/src/linux/."
+"config</path> file by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):226
+msgid "Getting a clean kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):226
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>cp .config_master .config</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):231
+msgid "Now go into the configuration GUI by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):235
+msgid "Editing the slave's kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):240
+msgid ""
+"You will want to make sure you select the following options as built-in and "
+"<e>NOT</e> as kernel modules:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):245
+msgid "slave's kernel options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):245
+#, no-wrap
+msgid ""
+"\n"
+"Code maturity level options ---&gt;\n"
+" [*] Prompt for development and/or incomplete code/drivers\n"
+"\n"
+"Device Drivers ---&gt;\n"
+" [*] Networking support\n"
+" Networking options ---&gt;\n"
+" &lt;*&gt; Packet socket\n"
+" &lt;*&gt; Unix domain sockets\n"
+" [*] TCP/IP networking\n"
+" [*] IP: multicasting\n"
+" [*] IP: kernel level autoconfiguration\n"
+" [*] IP: DHCP support (NEW)\n"
+"\n"
+"File systems ---&gt;\n"
+" Network File Systems ---&gt;\n"
+" &lt;*&gt; file system support\n"
+" [*] Provide NFSv3 client support\n"
+" [*] Root file system on NFS\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):266
+msgid "An alternative to having an dhcp server is setting up a BOOTP server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(impo):270
+msgid ""
+"It is important that you add your network adapter into the kernel (and not "
+"as a module) on the nodes. Using modules however is generally not a problem "
+"for diskless nodes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):276
+msgid ""
+"Now the slave's kernel needs to be compiled. You have to be careful here "
+"because you don't want to mess up the modules (if any) you have built for "
+"the master:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):282
+msgid "Compiling the slave kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):282
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):287
+msgid ""
+"Now create the directory on the master that will be used to hold slaves' "
+"files and required system files. We use <path>/diskless</path> but you may "
+"choose any location you like. Now copy the slave's bzImage into the <path>/"
+"diskless</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):294
+msgid ""
+"If you are using different architectures you might want to save each config "
+"into <path>.config_arch</path>. Do the same with the images: save them into "
+"the <path>/diskless</path> as <path>bzImage_arch</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):300
+msgid "Copying the slave kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):300
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /diskless</i>\n"
+"# <i>cp /usr/src/linux/arch/i386/boot/bzImage /diskless</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):308
+msgid "Configuring a preliminary slave file system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):311
+msgid ""
+"The master and slave filesystems can be tweaked and changed a lot. Right now "
+"we are only interested in getting a preliminary filesystem of appropriate "
+"configuration files and mount points. First we need to create a directory "
+"within <path>/diskless</path> for the first slave. Each slave needs it's own "
+"root file system because sharing certain system files will cause permission "
+"problems and hard crashes. You can call these directories anything you want "
+"but I suggest using the slaves IP addresses as they are unique and not "
+"confusing. The static IP of our first slave will be, for instance, "
+"<c>192.168.1.21</c>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):322
+msgid "Creating a remote root directory"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):322
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /diskless/192.168.1.21</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):326
+msgid ""
+"Various configuration files in <path>/etc</path> need to be altered to work "
+"on the slave. Copy the master's <path>/etc</path> directory onto your new "
+"slave root by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):332
+msgid "Creating /etc for the slave's filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):332
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp -r /etc /diskless/192.168.1.21/etc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):336
+msgid ""
+"Still this filesystem isn't ready because it needs various mount points and "
+"directories. To create them, type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):341
+msgid "Creating mount points and directories in the slave's filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):341
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkdir /diskless/192.168.1.21/home</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/dev</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/proc</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/tmp</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/mnt</i>\n"
+"# <i>chmod a+w /diskless/192.168.1.21/tmp</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/mnt/.initd</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/root</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/sys</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var/empty</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var/lock</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var/log</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var/run</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/var/spool</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/usr</i>\n"
+"# <i>mkdir /diskless/192.168.1.21/opt</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):361
+msgid ""
+"Most of these \"stubs\" should be recognizable to you; stubs like <path>/"
+"dev</path>, <path>/proc</path> or <path>/sys</path> will be populated when "
+"the slave starts, the others will be mounted later. You should also change "
+"the <path>/diskless/192.168.1.21/etc/conf.d/hostname</path> file to reflect "
+"the hostname of the slave. Binaries, libraries and other files will be "
+"populated later in this HOWTO right before you attempt to boot the slave."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):370
+msgid ""
+"Even though <path>/dev</path> is populated by <c>udev</c> later on, you need "
+"to create the <path>console</path> entry. If not, you will receive the error "
+"\"unable to open initial console\"."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):376
+msgid "Creating console entry in the /dev"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):376
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mknod /diskless/192.168.1.21/dev/console c 5 1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):385
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):459
+msgid "Configuring the DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):387
+msgid "About the DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):390
+msgid ""
+"DHCP stands for Dynamic Host Configuration Protocol. The DHCP server is the "
+"first computer the slaves will communicate with when they PXE boot. The "
+"primary purpose of the DHCP server is to assign IP addresses. The DHCP "
+"server can assign IP addresses based on hosts ethernet MAC addresses. Once "
+"the slave has an IP address, the DHCP server will tell the slave where to "
+"get its initial file system and kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):402
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):766
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):869
+msgid "Before you get started"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):405
+msgid ""
+"There are several things you will want to make sure are working before you "
+"begin. First check your network connectivity:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):410
+msgid "Checking networking configurations"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):410
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ifconfig eth0 multicast</i>\n"
+"# <i>ifconfig -a</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):415
+msgid ""
+"You will want to make sure you have have an <e>eth0</e> device running. It "
+"should look something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):420
+msgid "A properly working eth0 device"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):420
+#, no-wrap
+msgid ""
+"\n"
+"eth0 Link encap:Ethernet HWaddr 00:E0:83:16:2F:D6\n"
+" inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0\n"
+" UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1\n"
+" RX packets:26460491 errors:0 dropped:0 overruns:2 frame:0\n"
+" TX packets:32903198 errors:0 dropped:0 overruns:0 carrier:1\n"
+" collisions:0 txqueuelen:100\n"
+" RX bytes:2483502568 (2368.4 Mb) TX bytes:1411984950 (1346.5 Mb)\n"
+" Interrupt:18 Base address:0x1800\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):431
+msgid ""
+"It's important that it says <e>MULTICAST</e>, if it doesn't then you will "
+"have to recompile your kernel to include multicast support."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):439
+msgid "Installing the DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):442
+msgid ""
+"If your network does not already have a DHCP server installed you will need "
+"to install one:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):447
+msgid "Installing the dhcp server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):447
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge dhcp</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):451
+msgid ""
+"If your network already has a DHCP server installed you will have to edit "
+"the configuration file to get the PXE boot to function correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):462
+msgid ""
+"There is only one configuration file you will have to edit before starting "
+"the DHCP server: <path>/etc/dhcp/dhcpd.conf</path>. Copy and edit the "
+"provided sample file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):468
+msgid "Editing the dhcp server's configuration file"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):468
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /etc/dhcp/dhcpd.conf.sample /etc/dhcp/dhcpd.conf</i>\n"
+"# <i>nano -w /etc/dhcp/dhcpd.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):473
+msgid ""
+"The general layout of the file is set up in an indented fashion and looks "
+"like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):478
+msgid "Sample dhcpd.conf layout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):478
+#, no-wrap
+msgid ""
+"\n"
+"<comment># global options here</comment>\n"
+"ddns-update-style none;\n"
+"shared-network LOCAL-NET {\n"
+"<comment># shared network options here</comment>\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"<comment> # subnet network options here</comment>\n"
+" host slave{\n"
+"<comment> # host specific options here</comment>\n"
+" }\n"
+" group {\n"
+"<comment> # group specific options here</comment>\n"
+" }\n"
+"}\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):495
+msgid ""
+"The <c>shared-network</c> block is optional and should be used for IPs you "
+"want to assign that belong to the same network topology. At least one "
+"<c>subnet</c> must be declared and the optional <c>group</c> block allows "
+"you to group options between items. A good example of <path>dhcpd.conf</"
+"path> looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):502
+msgid "Sample dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):502
+#, no-wrap
+msgid ""
+"\n"
+"#\n"
+"# Sample dhcpd.conf for diskless clients\n"
+"#\n"
+"\n"
+"# Disable dynamic DNS\n"
+"ddns-update-style none;\n"
+"\n"
+"# Assume one default gateway for IP traffic will do\n"
+"option routers 192.168.1.1;\n"
+"\n"
+"# Provide DNS info to clients\n"
+"option domain-name-servers 192.168.1.1;\n"
+"option domain-name \"mydomain.com\";\n"
+"\n"
+"# Specify the TFTP server to be used\n"
+"next-server 192.168.1.1;\n"
+"\n"
+"# Declare a vendor-specific option buffer for PXE clients:\n"
+"# Code 1: Multicast IP address of boot file server\n"
+"# Code 2: UDP port that client should monitor for MTFTP responses\n"
+"# Code 3: UDP port that MTFTP servers are using to listen for MTFTP requests\n"
+"# Code 4: Number of seconds a client must listen for activity before trying\n"
+"# to start a new MTFTP transfer\n"
+"# Code 5: Number of seconds a client must listen before trying to restart\n"
+"# a MTFTP transfer\n"
+"\n"
+"option space PXE;\n"
+"option PXE.mtftp-ip code 1 = ip-address;\n"
+"option PXE.mtftp-cport code 2 = unsigned integer 16;\n"
+"option PXE.mtftp-sport code 3 = unsigned integer 16;\n"
+"option PXE.mtftp-tmout code 4 = unsigned integer 8;\n"
+"option PXE.mtftp-delay code 5 = unsigned integer 8;\n"
+"option PXE.discovery-control code 6 = unsigned integer 8;\n"
+"option PXE.discovery-mcast-addr code 7 = ip-address;\n"
+"\n"
+"# Declare the subnet where our diskless nodes will live\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"\n"
+" # Provide PXE clients with appropriate information\n"
+" class \"pxeclient\" {\n"
+" match if substring(option vendor-class-identifier, 0, 9) = \"PXEClient\";\n"
+" vendor-option-space PXE;\n"
+"\n"
+" # At least one of the vendor-specific PXE options must be set in\n"
+" # order for the client boot ROMs to realize that we are a PXE-compliant\n"
+" # server. We set the MCAST IP address to 0.0.0.0 to tell the boot ROM\n"
+" # that we can't provide multicast TFTP.\n"
+"\n"
+" option PXE.mtftp-ip 0.0.0.0;\n"
+"\n"
+" # This is the name of the file the boot ROMs should download.\n"
+" filename \"pxelinux.0\";\n"
+" }\n"
+"\n"
+" # Provide Etherboot clients with appropriate information\n"
+" class \"etherboot\" {\n"
+" match if substring(option vendor-class-identifier, 0, 9) = \"Etherboot\";\n"
+" filename \"vmlinuz_arch\";\n"
+" }\n"
+"\n"
+" # Add one host declaration for each diskless host\n"
+" host slave21 {\n"
+" hardware ethernet 00:02:A5:04:3B:66;\n"
+" fixed-address 192.168.1.21;\n"
+" }\n"
+"}\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):571
+msgid ""
+"There is nothing prohibiting the use of both PXE boot and Etherboot "
+"together. The above Code Listing is merely an example; if you have issues, "
+"please consult the DHCPd documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):577
+msgid ""
+"The IP address after <c>next-server</c> will be asked for the specified "
+"<c>filename</c>. This IP address should be the IP of the tftp server, "
+"usually the same as the master's IP address. The <c>filename</c> is relative "
+"to the <path>/diskless</path> directory (this is due to the tftp server "
+"specific options which will be covered later). Inside the <c>host</c> block, "
+"the <c>hardware ethernet</c> option specifies a MAC address, and <c>fixed-"
+"address</c> assigns a fixed IP address to that particular MAC address. There "
+"is a pretty good man page on <path>dhcpd.conf</path> with options that are "
+"beyond the scope of this HOWTO. You can read it by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):589
+msgid "Viewing the man pages for dhcpd.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):589
+#, no-wrap
+msgid ""
+"\n"
+"# <i>man dhcpd.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):596
+msgid "Starting the DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):599
+msgid ""
+"Before you start the dhcp initialisation script edit the <path>/etc/conf.d/"
+"dhcp</path> file so that it looks something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):604
+msgid "Sample /etc/conf.d/dhcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):604
+#, no-wrap
+msgid ""
+"\n"
+"IFACE=\"eth0\"\n"
+"<comment># insert any other options needed</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):609
+msgid ""
+"The <c>IFACE</c> variable is the device you wish to run your DHCP server on, "
+"in our case <c>eth0</c>. Adding more arguments to the <c>IFACE</c> variable "
+"can be useful for a complex network topology with multiple Ethernet cards. "
+"To start the dhcp server type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):616
+msgid "Starting the dhcp server on the master"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):616
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dhcp start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):620
+msgid "To add the dhcp server to your start-up scripts type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):624
+msgid "Adding the dhcp server to the master's default run level"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):624
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add dhcp default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):631
+msgid "Troubleshooting the DHCP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):634
+msgid ""
+"To see if a node boots you can take a look at <path>/var/log/messages</"
+"path>. If the node successfully boots, the <path>messages</path> file should "
+"have some lines at the bottom looking like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):640
+msgid "Sample log file entries created by dhcp"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):640
+#, no-wrap
+msgid ""
+"\n"
+"DHCPDISCOVER from 00:00:00:00:00:00 via eth0\n"
+"DHCPOFFER on 192.168.1.21 to 00:00:00:00:00:00 via eth0\n"
+"DHCPREQUEST for 192.168.1.21 from 00:00:00:00:00:00 via eth0\n"
+"DHCPACK on 192.168.1.21 to 00:00:00:00:00:00 via eth0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):647
+msgid "This log file can also help you discover the slaves' MAC addresses."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):651
+msgid ""
+"If you get the following message it probably means there is something wrong "
+"in the configuration file but that the DHCP server is broadcasting correctly."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):656
+msgid "Sample dhpc server error"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):656
+#, no-wrap
+msgid ""
+"\n"
+"no free leases on subnet LOCAL-NET\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):660
+msgid ""
+"Every time you change the configuration file you must restart the DHCP "
+"server. To restart the server type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):665
+msgid "Restarting the dhcp server on the master"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):665
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/dhcpd restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):674
+msgid "Configuring the TFTP server and PXE Linux Bootloader and/or Etherboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):676
+msgid "About the TFTP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):679
+msgid ""
+"TFTP stands for Trivial File Transfer Protocol. The TFTP server is going to "
+"supply the slaves with a kernel and an initial filesystem. All of the slave "
+"kernels and filesystems will be stored on the TFTP server, so it's probably "
+"a good idea to make the master the TFTP server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):689
+msgid "Installing the TFTP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):692
+msgid ""
+"A highly recommended tftp server is available as the tftp-hpa package. This "
+"tftp server happens to be written by the author of SYSLINUX and it works "
+"very well with pxelinux. To install simply type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):698
+msgid "Installing the tfp server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):698
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge tftp-hpa</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):705
+msgid "Configuring the TFTP server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):708
+msgid ""
+"Edit <path>/etc/conf.d/in.tftpd</path>. You need to specify the tftproot "
+"directory with <c>INTFTPD_PATH</c> and any command line options with "
+"<c>INTFTPD_OPTS</c>. It should look something like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):714
+msgid "Sample /etc/conf.d/in.tftpd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):714
+#, no-wrap
+msgid ""
+"\n"
+"INTFTPD_PATH=\"/diskless\"\n"
+"INTFTPD_OPTS=\"-l -v -s ${INTFTPD_PATH}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):719
+msgid ""
+"The <c>-l</c> option indicates that this server listens in stand alone mode "
+"so you don't have to run inetd. The <c>-v</c> indicates that log/error "
+"messages should be verbose. The <c>-s /diskless</c> specifies the root of "
+"your tftp server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):729
+msgid "Starting the the TFTP Server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):732
+msgid "To start the tftp server type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):736
+msgid "Starting the master's tftp server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):736
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/in.tftpd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):740
+msgid ""
+"This should start the tftp server with the options you specified in the "
+"<path>/etc/conf.d/in.tftpd</path>. If you want this server to be "
+"automatically started at boot type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):746
+msgid "Adding the tftp server to the master's default run level"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):746
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add in.tftpd default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):753
+msgid "About PXELINUX"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):756
+msgid ""
+"This section is not required if you are only using Etherboot. PXELINUX is "
+"the network bootloader equivalent to LILO or GRUB and will be served via "
+"TFTP. It is essentially a tiny set of instructions that tells the client "
+"where to locate its kernel and initial filesystem and allows for various "
+"kernel options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):769
+msgid ""
+"You will need to get the pxelinux.0 file which comes in the SYSLINUX package "
+"by H. Peter Anvin. You can install this package by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):774
+msgid "Installing syslinux"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):774
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge syslinux</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):781
+msgid "Setting up PXELINUX"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):784
+msgid "This isn't needed for Etherboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):788
+msgid ""
+"Before you start your tftp server you need to setup pxelinux. First copy the "
+"pxelinux binary into your <path>/diskless</path> directory:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):793
+msgid "Setting up the remote bootloader"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):793
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cp /usr/share/syslinux/pxelinux.0 /diskless</i>\n"
+"# <i>mkdir /diskless/pxelinux.cfg</i>\n"
+"# <i>touch /diskless/pxelinux.cfg/default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):799
+msgid ""
+"This will create a default bootloader configuration file. The binary "
+"<path>pxelinux.0</path> will look in the <path>pxelinux.cfg</path> directory "
+"for a file whose name is the client's IP address in hexadecimal. If it does "
+"not find that file it will remove the rightmost digit from the file name and "
+"try again until it runs out of digits. Versions 2.05 and later of syslinux "
+"first perform a search for a file named after the MAC address. If no file is "
+"found, it starts the previously mentioned discovery routine. If none is "
+"found, the <path>default</path> file is used."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):810
+msgid "Files that PXE looks for in pxelinux.cfg/ in sequence"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):810
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Leading 01 means Ethernet, next bytes match our slave's MAC address)</comment>\n"
+"01-00-40-63-c2-ca-c9\n"
+"\n"
+"<comment>(Assigned IP in hexadecimal)</comment>\n"
+"C0A80115\n"
+"C0A8011\n"
+"C0A801\n"
+"C0A80\n"
+"C0A8\n"
+"C0A\n"
+"C0\n"
+"C\n"
+"\n"
+"default\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):827
+msgid "These are all in lowercase."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):831
+msgid "Let's start with the <path>default</path> file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):835
+msgid "Sample pxelinux.cfg/default"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):835
+#, no-wrap
+msgid ""
+"\n"
+"DEFAULT /bzImage\n"
+"APPEND ip=dhcp root=/dev/nfs nfsroot=192.168.1.1:/diskless/192.168.1.21\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):840
+msgid ""
+"The <c>DEFAULT</c> tag directs pxelinux to the kernel bzImage that we "
+"compiled earlier. The <c>APPEND</c> tag appends kernel initialisation "
+"options. Since we compiled the slave kernel with <c>NFS_ROOT_SUPPORT</c>, we "
+"will specify the nfsroot here. The first IP is the master's IP and the "
+"second IP is the directory that was created in <path>/diskless</path> to "
+"store the slave's initial filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):853
+msgid "About Etherboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):856
+msgid "This isn't required if you are using PXE boot."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):860
+msgid ""
+"Etherboot boots network boot images from a TFTP server. As the PXE this is "
+"equivalent to LILO or GRUB. The <c>mknbi</c> utility enables you to create "
+"different images using different options."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):872
+msgid ""
+"You will need to get the <c>mknbi</c> (utility for making tagged kernel "
+"images useful for netbooting) package to create your Etherboot images. This "
+"tool will create a preconfigured kernel image from your original kernel. "
+"This contains the boot options as shown further down."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):879
+msgid "Installing mknbi"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):879
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge mknbi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):886
+msgid "Setting up Etherboot"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):889
+msgid ""
+"In this section we will create a simple etherboot image. As the dhcp server "
+"gives out the clients root-path in the \"option root-path\" dhcp.conf, we do "
+"not have to include this here. More details can be found in the mknbi manual."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):895
+msgid "mknbi manual"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):895
+#, no-wrap
+msgid ""
+"\n"
+"# <i>man mknbi</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):899
+msgid ""
+"Making the boot images. This will create a ELF bootable image capable of "
+"passing dhcp and the rootpath to the kernel. Also forcing the kernel to "
+"browse the network for a dhcp server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):905
+msgid "making netboot images"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):905
+#, no-wrap
+msgid ""
+"\n"
+"# <i>mkelf-linux -ip=dhcp /diskless/bzImage &gt; /diskless/vmlinuz </i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):909
+msgid ""
+"For the arch specific images you have to type <c>bzImage_arch</c> and "
+"<c>vmlinuz_arch</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):917
+msgid "Troubleshooting the network boot process"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):920
+msgid ""
+"There are a few things you can do to debug the network boot process. "
+"Primarily you can use a tool called <c>tcpdump</c>. To install <c>tcpdump</"
+"c> type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):925
+msgid "Installing tcpdump"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):925
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge tcpdump</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):929
+msgid ""
+"Now you can listen to various network traffic and make sure your client/"
+"server interactions are functioning. If something isn't working there are a "
+"few things you might want to check. First make sure that the client/server "
+"is physically connected properly and that the networking cables are not "
+"damaged. If your client/server is not receiving requests on a particular "
+"port make sure that there is no firewall interference. To listen to "
+"interaction between two computers type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):939
+msgid "Listening to client and server interaction via tcpdump"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):939
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tcpdump host </i><comment>client_ip</comment><i> and </i><comment>server_ip</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):943
+msgid ""
+"You can also use <c>tcpdump</c> to listen on particular port such as the "
+"tftp port by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):948
+msgid "Listening to the tftp server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):948
+#, no-wrap
+msgid ""
+"\n"
+"# <i>tcpdump port 69</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):952
+msgid ""
+"A common error you might receive is: \"PXE-E32: TFTP open time-out\". This "
+"is probably due to firewall issues. If you are using <c>TCPwrappers</c>, you "
+"might want to check <path>/etc/hosts.allow</path> and <path>etc/hosts.deny</"
+"path> and make sure that they are configured properly. The client should be "
+"allowed to connect to the server."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):965
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1047
+msgid "Configuring the NFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):967
+msgid "About the NFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):970
+msgid ""
+"NFS stands for Network File System. The NFS server will be used to serve "
+"directories to the slave. This part can be somewhat personalized later, but "
+"right now all we want is a preliminary slave node to boot diskless."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):979
+msgid "About Portmapper"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):982
+msgid ""
+"Various client/server services do not listen on a particular port, but "
+"instead rely on RPCs (Remote Procedure Calls). When the service is "
+"initialised it listens on a random port and then registers this port with "
+"the Portmapper utility. NFS relies on RPCs and thus requires Portmapper to "
+"be running before it is started."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):996
+msgid ""
+"The NFS Server needs kernel level support so if you don't have this you "
+"should recompile your master's kernel. To double check your master's kernel "
+"configuration type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1002
+msgid "Checking for NFS specific options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1002
+#, no-wrap
+msgid ""
+"\n"
+"# <i>grep NFS /usr/src/linux/.config_master</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1006
+msgid ""
+"You should see output that looks something like this if your kernel has been "
+"properly configured:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1011
+msgid "Proper NFS specific options in the master's kernel configuration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1011
+#, no-wrap
+msgid ""
+"\n"
+"CONFIG_PACKET=y\n"
+"# CONFIG_PACKET_MMAP is not set\n"
+"# CONFIG_NETFILTER is not set\n"
+"CONFIG_NFS_FS=y\n"
+"CONFIG_NFS_V3=y\n"
+"# CONFIG_NFS_V4 is not set\n"
+"# CONFIG_NFS_DIRECTIO is not set\n"
+"CONFIG_NFSD=y\n"
+"CONFIG_NFSD_V3=y\n"
+"# CONFIG_NFSD_V4 is not set\n"
+"# CONFIG_NFSD_TCP is not set\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1028
+msgid "Installing the NFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1031
+msgid "The NFS package that can be acquired through portage by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1035
+msgid "Installing nfs-utils"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1035
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge nfs-utils</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1039
+msgid ""
+"This package will emerge a portmapping utility, nfs server, and nfs client "
+"utilities and will automatically handle initialisation dependencies."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1050
+msgid "There are three major configuration files you will have to edit:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1054
+msgid "Nfs configuration files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1054
+#, no-wrap
+msgid ""
+"\n"
+"/etc/exports\n"
+"/diskless/192.168.1.21/etc/fstab\n"
+"/etc/conf.d/nfs\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1060
+msgid ""
+"The <path>/etc/exports</path> file specifies how, to who and what to export "
+"through NFS. The slave's fstab will be altered so that it can mount the NFS "
+"filesystems that the master is exporting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1066
+msgid ""
+"A typical <path>/etc/exports</path> for the master should look something "
+"like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1071
+msgid "Sample master /etc/exports"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1071
+#, no-wrap
+msgid ""
+"\n"
+"<comment># one line like this for each slave</comment>\n"
+"/diskless/192.168.1.21 192.168.1.21(sync,rw,no_root_squash,no_all_squash)\n"
+"<comment># common to all slaves</comment>\n"
+"/opt 192.168.1.0/24(sync,ro,no_root_squash,no_all_squash)\n"
+"/usr 192.168.1.0/24(sync,ro,no_root_squash,no_all_squash)\n"
+"/home 192.168.1.0/24(sync,rw,no_root_squash,no_all_squash)\n"
+"<comment># if you want to have a shared log</comment>\n"
+"/var/log 192.168.1.21(sync,rw,no_root_squash,no_all_squash)\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1082
+msgid ""
+"The first field indicates the directory to be exported and the next field "
+"indicates to who and how. This field can be divided in two parts: who should "
+"be allowed to mount that particular directory, and what the mounting client "
+"can do to the filesystem: <c>ro</c> for read only, <c>rw</c> for read/write; "
+"<c>no_root_squash</c> and <c>no_all_squash</c> are important for diskless "
+"clients that are writing to the disk, so that they don't get \"squashed\" "
+"when making I/O requests. The slave's fstab file, <path>/"
+"diskless/192.168.1.21/etc/fstab</path>, should look like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1093
+msgid "Sample slave fstab"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1093
+#, no-wrap
+msgid ""
+"\n"
+"<comment># these entries are essential</comment>\n"
+"master:/diskless/192.168.1.21 / nfs sync,hard,intr,rw,nolock,rsize=8192,wsize=8192 0 0\n"
+"master:/opt /opt nfs sync,hard,intr,ro,nolock,rsize=8192,wsize=8192 0 0\n"
+"master:/usr /usr nfs sync,hard,intr,ro,nolock,rsize=8192,wsize=8192 0 0\n"
+"master:/home /home nfs sync,hard,intr,rw,nolock,rsize=8192,wsize=8192 0 0\n"
+"none /proc proc defaults 0 0\n"
+"<comment># useful but superfluous</comment>\n"
+"master:/var/log /var/log nfs hard,intr,rw 0 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1104
+msgid ""
+"In this example, <e>master</e> is just the hostname of the master but it "
+"could easily be the IP of the master. The first field indicates the "
+"directory to be mounted and the second field indicates where. The third "
+"field describes the filesystem and should be NFS for any NFS mounted "
+"directory. The fourth field indicates various options that will be used in "
+"the mounting process (see mount(1) for info on mount options). Some people "
+"have had difficulties with soft mount points so we made them all hard, but "
+"you should look into various <path>/etc/fstab</path> options to make your "
+"cluster more efficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1115
+msgid ""
+"The last file you should edit is <path>/etc/conf.d/nfs</path> which "
+"describes a few options for nfs when it is initialised and looks like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1120
+msgid "Sample master /etc/conf.d/nfs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1120
+#, no-wrap
+msgid ""
+"\n"
+"# Config file for /etc/init.d/nfs\n"
+"\n"
+"# Number of servers to be started up by default\n"
+"RPCNFSDCOUNT=8\n"
+"\n"
+"# Options to pass to rpc.mountd\n"
+"RPCMOUNTDOPTS=\"\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1130
+msgid ""
+"You should change <c>RPCNFSDCOUNT</c> to the number of diskless nodes on the "
+"network."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1138
+msgid "Starting the NFS server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1141
+msgid ""
+"You should start the nfs server with its init script located in <path>/etc/"
+"init.d</path> by typing:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1146
+msgid "Starting the master's nfs server"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1146
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/nfs start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1150
+msgid "If you want to this script to start when the system boots simply type:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1154
+msgid "Adding the nfs server to the master's default run level"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1154
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rc-update add nfs default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1163
+msgid "Completing the slave filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1165
+msgid "Copy the missing files"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1168
+msgid ""
+"We will now make the slave's file system in sync with the master's and "
+"provide the necessary binaries while still preserving slave specific files."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1173
+msgid "Creating a slave filesystem"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1173
+#, no-wrap
+msgid ""
+"\n"
+"# <i>rsync -avz /bin /diskless/192.168.1.21</i>\n"
+"# <i>rsync -avz /sbin /diskless/192.168.1.21</i>\n"
+"# <i>rsync -avz /lib /diskless/192.168.1.21</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):1179
+msgid ""
+"The reason for rsync -avz instead of cp is to maintain symlinks and "
+"permissions."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1186
+msgid "Configure diskless networking"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1189
+msgid ""
+"In order to prevent the networking initscript from killing the connection to "
+"your NFS server, you will need to add an option to <path>/etc/conf.d/net</"
+"path> on your diskless client's filesystem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1195
+msgid "Editing /etc/conf.d/net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1195
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Add this to the existing options for your diskless client's interface)</comment>\n"
+"config_eth0=( \"noop\" )\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(note):1200
+msgid "For more information, please read <path>/etc/conf.d/net.example</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(title):1207
+msgid "Initialisation scripts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1210
+msgid ""
+"You need as many init scripts under <path>/diskless/192.168.1.21/etc/"
+"runlevels</path> as you need services on your diskless nodes. It all depends "
+"on what you want your slaves to do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(warn):1216
+msgid ""
+"Do not use the <c>rc-update</c> program to add or remove scripts from the "
+"slave runlevels when logged on your master. This would change your master "
+"runlevels. You need to create the links manually or log into your slave "
+"nodes using ssh or connect a screen and keyboard to your slave."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre:caption):1223
+msgid "Typical slave runlevels"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(pre):1223
+#, no-wrap
+msgid ""
+"\n"
+"/diskless/192.168.1.21/etc/runlevels/:\n"
+"total 16\n"
+"drwxr-xr-x 2 root root 4096 2003-11-09 15:27 boot\n"
+"drwxr-xr-x 2 root root 4096 2003-10-01 21:10 default\n"
+"drwxr-xr-x 2 root root 4096 2003-03-13 19:05 nonetwork\n"
+"drwxr-xr-x 2 root root 4096 2003-02-23 12:26 single\n"
+"\n"
+"/diskless/192.168.1.21/etc/runlevels/boot:\n"
+"total 0\n"
+"lrwxrwxrwx 1 root root 20 2003-10-18 17:28 bootmisc -&gt; /etc/init.d/bootmisc\n"
+"lrwxrwxrwx 1 root root 19 2003-10-18 17:28 checkfs -&gt; /etc/init.d/checkfs\n"
+"lrwxrwxrwx 1 root root 17 2003-10-18 17:28 clock -&gt; /etc/init.d/clock\n"
+"lrwxrwxrwx 1 root root 22 2003-10-18 17:28 domainname -&gt; /etc/init.d/domainname\n"
+"lrwxrwxrwx 1 root root 20 2003-10-18 17:28 hostname -&gt; /etc/init.d/hostname\n"
+"lrwxrwxrwx 1 root root 22 2003-10-18 17:28 localmount -&gt; /etc/init.d/localmount\n"
+"lrwxrwxrwx 1 root root 19 2003-10-18 17:28 modules -&gt; /etc/init.d/modules\n"
+"lrwxrwxrwx 1 root root 18 2003-10-18 17:28 net.lo -&gt; /etc/init.d/net.lo\n"
+"lrwxrwxrwx 1 root root 20 2003-10-18 17:28 netmount -&gt; /etc/init.d/netmount\n"
+"lrwxrwxrwx 1 root root 21 2003-10-18 17:28 rmnologin -&gt; /etc/init.d/rmnologin\n"
+"lrwxrwxrwx 1 root root 19 2003-10-18 17:28 urandom -&gt; /etc/init.d/urandom\n"
+"\n"
+"/diskless/192.168.1.21/etc/runlevels/default:\n"
+"total 0\n"
+"lrwxrwxrwx 1 root root 23 2003-10-18 17:28 consolefont -&gt; /etc/init.d/consolefont\n"
+"lrwxrwxrwx 1 root root 19 2003-10-18 17:28 distccd -&gt; /etc/init.d/distccd\n"
+"lrwxrwxrwx 1 root root 19 2003-10-18 17:28 keymaps -&gt; /etc/init.d/keymaps\n"
+"lrwxrwxrwx 1 root root 17 2003-10-18 17:28 local -&gt; /etc/init.d/local\n"
+"lrwxrwxrwx 1 root root 16 2003-10-18 17:28 sshd -&gt; /etc/init.d/sshd\n"
+"lrwxrwxrwx 1 root root 21 2003-10-18 17:28 syslog-ng -&gt; /etc/init.d/syslog-ng\n"
+"lrwxrwxrwx 1 root root 17 2003-10-18 17:28 vixie-cron -&gt; /etc/init.d/vixie-cron\n"
+"\n"
+"/diskless/192.168.1.21/etc/runlevels/nonetwork:\n"
+"total 0\n"
+"lrwxrwxrwx 1 root root 17 2003-10-18 17:28 local -&gt; /etc/init.d/local\n"
+"\n"
+"/diskless/192.168.1.21/etc/runlevels/single:\n"
+"total 0\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(p):1263
+msgid ""
+"Now is a good time to boot your slave and cross your fingers. It works? "
+"Congratulations, you are now the proud owner of (a) diskless node(s) :)"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//diskless-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/distcc.xml.po b/doc/gettext/el/distcc.xml.po
new file mode 100644
index 0000000..a36b63e
--- /dev/null
+++ b/doc/gettext/el/distcc.xml.po
@@ -0,0 +1,565 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(guide:link):5
+msgid "/doc/en/distcc.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):7
+msgid "Gentoo Distcc Documentation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):9
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):10
+msgid "lisa@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):10
+msgid "Lisa Seelye"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):12
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):18
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):21
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):27
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):13
+msgid "vapier@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):13
+msgid "Mike Frysinger"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):16
+msgid "erwin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):16
+msgid "Erwin"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):19
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):19
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):22
+msgid "pylon@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):22
+msgid "Lars Weiler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(author:title):24
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):25
+msgid "blubber@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail):25
+msgid "Tiemo Kieft"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(mail:link):28
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(abstract):31
+msgid "This document serves as a HOWTO for using distcc with Gentoo."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(version):39
+msgid "1.22"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(date):40
+msgid "2009-06-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):43
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):45
+msgid "What is distcc?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):48
+msgid ""
+"Distcc is a program designed to distribute compiling tasks across a network "
+"to participating hosts. It is comprised of a server, <c>distccd</c>, and a "
+"client program, <c>distcc</c>. Distcc can work transparently with <uri link="
+"\"http://ccache.samba.org\">ccache</uri>, Portage, and Automake with a "
+"little setup."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):59
+msgid "Using distcc to bootstrap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):62
+msgid ""
+"If you are planning on using distcc to help you bootstrap a Gentoo "
+"installation, make sure you read the section <uri link=\"#bootstrapping"
+"\">Using distcc to Bootstrap</uri>, which is situated further down in this "
+"document."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):73
+msgid "Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):75
+msgid "Dependencies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):78
+msgid ""
+"In order to use Distcc, all of the computers on your network need to have "
+"the same GCC versions. For example, mixing 3.3.x (where the x varies) is "
+"okay, but mixing 3.3.x with 3.2.x <b>may</b> result in compilation errors or "
+"runtime errors."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):88
+msgid "Installing Distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):91
+msgid ""
+"There are a couple of options you should be aware of before you start "
+"installing distcc."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):96
+msgid ""
+"Distcc ships with a graphical monitor to monitor tasks that your computer is "
+"sending away for compilation. If you use Gnome then put 'gnome' in your USE "
+"flags. However, if you don't use Gnome and would still like to have the "
+"monitor then you should put 'gtk' in your USE flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):103
+msgid "Installing distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):103
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge distcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(impo):107
+msgid ""
+"Remember, you must be sure to install distcc on all of your participating "
+"machines."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):115
+msgid "Setting up Portage to use Distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):118
+msgid ""
+"Setting up Portage to use distcc is easy. Execute the following steps on "
+"each system that should participate in the distributed compiling:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):123
+msgid "Integrating Distcc and Portage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):123
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge distcc</i>\n"
+"# <i>nano -w /etc/make.conf</i>\n"
+"<comment>(Set N to a suitable number for your particular setup)</comment>\n"
+"<comment>(A common strategy is setting N as twice the number of total CPUs + 1 available)</comment>\n"
+"MAKEOPTS=\"-jN\"\n"
+"<comment>(Add distcc to your FEATURES)</comment>\n"
+"FEATURES=\"distcc\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):136
+msgid "Specifying Participating Hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):139
+msgid ""
+"Use the <c>distcc-config</c> command to set the list of hosts. Here is an "
+"example of some hosts that might be in your list:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):144
+msgid "Examples of host definitions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):144
+#, no-wrap
+msgid ""
+"\n"
+"192.168.0.1 192.168.0.2 192.168.0.3\n"
+"192.168.0.1/2 192.168.0.2 192.168.0.3/10\n"
+"192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4\n"
+"@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3\n"
+"<comment>(There are also several other methods of setting up hosts. See the \n"
+"distcc manpage for more details.)</comment>\n"
+"<comment>If you wish to compile on the local machine you should put 'localhost'\n"
+"in the hosts list. Conversely if you do not wish to use the local machine to\n"
+"compile (which is often the case) omit it from the hosts list. On a slow\n"
+"machine using localhost may actually slow things down. Make sure to test your\n"
+"settings for performance.</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):158
+msgid ""
+"It may all look complicated, but in most cases a variant of line 1 or 2 will "
+"work."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):163
+msgid ""
+"Since most people won't be using lines 3 or 4, I'll <uri link=\"http://"
+"distcc.samba.org/man/distcc_1.html\">refer to</uri> the distcc docs (man "
+"distcc) for more information, which includes being able to run distcc over "
+"an SSH connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):170
+msgid "For instance, to set the first line in the previous example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):174
+msgid "Sample command to set the hosts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):174
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/usr/bin/distcc-config --set-hosts \"192.168.0.1 192.168.0.2 192.168.0.3\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):178
+msgid ""
+"Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the "
+"<c>--allow</c> directive to allow only hosts you trust. For added security, "
+"you should also use the <c>--listen</c> directive to tell the distcc daemon "
+"what IP to listen on (for multi-homed systems). More information on distcc "
+"security can be found at <uri link=\"http://distcc.samba.org/security.html"
+"\">Distcc Security Design</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(impo):187
+msgid ""
+"It is important to use --allow and --listen. Please read the distccd manpage "
+"or the above security document for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):193
+msgid "Now start the distcc daemon on all the participating computers:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):197
+msgid "Starting the distcc daemon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):197
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Add distccd to the default runlevel)</comment>\n"
+"# <i>rc-update add distccd default</i>\n"
+"<comment>(Start the distcc daemon)</comment>\n"
+"# <i>/etc/init.d/distccd start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):207
+msgid "Setting up Distcc to Work With Automake"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):210
+msgid ""
+"This is, in some cases, easier than the Portage setup. What you have to do "
+"is update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</"
+"path> in front of the directory that contains <c>gcc</c> (<path>/usr/bin</"
+"path>). However, there is a caveat. If you use ccache you have to put distcc "
+"after the ccache part:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):218
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):278
+msgid "Setting your path"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):218
+#, no-wrap
+msgid ""
+"\n"
+"# <i>export PATH=\"/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}\"</i>\n"
+"<comment>(You can put this in your ~/.bashrc or equivalent file to have the PATH\n"
+"set every time you log in)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):224
+msgid ""
+"Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> "
+"(where N is an integer). The value of N depends on your network and the "
+"types of computers you are using to compile. Test your own settings to find "
+"the number that yields the best performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):236
+msgid "Cross-Compiling"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):240
+msgid ""
+"Cross-compiling is using one architecture to build programs for another "
+"architecture. This can be as simple as using an Athlon (i686) to build a "
+"program for a K6-2 (i586), or using a Sparc to build a program for a ppc. "
+"This is documented in our <uri link=\"/doc/en/cross-compiling-distcc.xml"
+"\">DistCC Cross-compiling Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):253
+msgid "Using Distcc to Bootstrap"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):255
+msgid "Step 1: Configure Portage"
+msgstr ""
+
+#. Note that this will need to become a link to the old 2005.1 networked handbooks
+#. once the 2006.0 handbooks are released. Until then, the link can stay.
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):261
+msgid ""
+"Boot your new box with a Gentoo Linux LiveCD and follow the <uri link=\"/doc/"
+"en/handbook/handbook-x86.xml?part=1\">installation instructions</uri> up "
+"until the bootstrapping part. (See the <uri link=\"/doc/en/faq."
+"xml#stage12\">Gentoo FAQ</uri> for more information about bootstrapping.) "
+"Then configure Portage to use distcc:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):269
+msgid "Preliminary Setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):269
+#, no-wrap
+msgid ""
+"\n"
+"# <i>nano -w /etc/make.conf</i>\n"
+"<comment>(Add distcc to the FEATURES</comment>\n"
+"FEATURES=\"distcc\"\n"
+"<comment>(Modify MAKEOPTS to include -jN, where N is twice the number of CPUs\n"
+"+1 available)</comment>\n"
+"MAKEOPTS=\"-jN\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"# <i>export PATH=\"/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):285
+msgid "Step 2: Getting Distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):288
+msgid "Install distcc:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):292
+msgid "Getting Distcc on the new box"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):292
+#, no-wrap
+msgid ""
+"\n"
+"# <i>USE='-*' emerge --nodeps sys-devel/distcc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):299
+msgid "Step 3: Setting Up Distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):302
+msgid "Run <c>distcc-config --install</c> to setup distcc:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):306
+msgid "Final distcc setup"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):306
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Substitute host1, host2, ... with the IP number(s) of the\n"
+"participating hosts)</comment>\n"
+"# <i>/usr/bin/distcc-config --set-hosts \"localhost host1 host2 host3 ...\"</i>\n"
+"<comment>An example: <i>/usr/bin/distcc-config --set-hosts \"localhost\n"
+"192.168.0.4 192.168.0.6\"</i></comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):314
+msgid ""
+"Distcc is now set up to bootstrap! Continue with the official installation "
+"instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge "
+"system</c>. This is to make sure that all of the dependencies you want are "
+"installed as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(note):321
+msgid ""
+"During bootstrap and <c>emerge system</c> distcc may not appear to be used. "
+"This is expected as some ebuilds do not work well with distcc, so they "
+"intentionally disable it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):332
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):334
+msgid "Some Packages Don't Use Distcc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):337
+msgid ""
+"As you emerge various packages, you'll notice that some of them aren't being "
+"distributed (and aren't being built in parallel). This may happen because "
+"the package's Makefile doesn't support parallel operations or the maintainer "
+"of the ebuild has explicitly disabled parallel operations due to a known "
+"problem."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):344
+msgid ""
+"Sometimes distcc might cause a package to fail to compile. If this happens "
+"for you, please <uri link=\"http://bugs.gentoo.org\">report</uri> it to us."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):352
+msgid "Mixed GCC Versions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):355
+msgid ""
+"If you have different GCC versions on your hosts, there will likely be very "
+"weird problems. The solution is to make certain all hosts have the same GCC "
+"version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):361
+msgid ""
+"Recent Portage updates have made Portage use <c>${CHOST}-gcc</c> instead of "
+"<c>gcc</c>. This means that if you're mixing i686 machines with other types "
+"(i386, i586) you will run into problems. A workaround for this may be to "
+"<c>export CC='gcc' CXX='c++'</c> or to put it in <path>/etc/make.conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(impo):368
+msgid ""
+"Doing this explicitly redefines some behaviour of Portage and may have some "
+"weird results in the future. Only do this if you're mixing CHOSTs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):377
+msgid "-march=native"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):380
+msgid ""
+"Starting with GCC 4.3.0, the compiler supports the <c>-march=native</c> "
+"switch which turns on CPU autodetection and optimizations that are worth "
+"being enabled on the processor the GCC is running at. This is a problem with "
+"<c>distcc</c> as it allows mixing of code optimized for different processors "
+"(like AMD Athlon and Intel Pentium). <e>Don't</e> use <c>-march=native</c> "
+"or <c>-mtune=native</c> in your <c>CFLAGS</c> or <c>CXXFLAGS</c> when "
+"compiling with <c>distcc</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):394
+msgid "Distcc Extras"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(title):396
+msgid "Distcc Monitors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):399
+msgid ""
+"Distcc ships with two monitors. The text-based one is always built and is "
+"called <c>distccmon-text</c>. Running it for the first time can be a bit "
+"confusing, but it is really quite easy to use. If you run the program with "
+"no parameter it will run once. However, if you pass it a number it will "
+"update every N seconds, where N is the argument you passed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(p):407
+msgid ""
+"The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</"
+"c> in your <c>USE</c> flags. This one is GTK+ based, runs in an X "
+"environment and it is quite lovely. For Gentoo the GUI monitor has been "
+"called <c>distccmon-gui</c> for less confusion. Elsewhere it may be referred "
+"to as <c>distccmon-gnome</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre:caption):415
+msgid "Starting the monitors"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(pre):415
+#, no-wrap
+msgid ""
+"\n"
+"# <i>distccmon-text N</i>\n"
+"<comment>(Or)</comment>\n"
+"# <i>distccmon-gui</i>\n"
+"<comment>To monitor Portage's distcc usage you can use:</comment>\n"
+"# <i>DISTCC_DIR=\"/var/tmp/portage/.distcc/\" distccmon-text N</i>\n"
+"<comment>(Or)</comment>\n"
+"# <i>DISTCC_DIR=\"/var/tmp/portage/.distcc/\" distccmon-gui</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(impo):425
+msgid ""
+"If your distcc directory is elsewhere, change the DISTCC_DIR variable "
+"accordingly."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//distcc.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/doc-languages.xml.po b/doc/gettext/el/doc-languages.xml.po
new file mode 100644
index 0000000..c297fc3
--- /dev/null
+++ b/doc/gettext/el/doc-languages.xml.po
@@ -0,0 +1,43 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(version):7
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(date):8
+msgid "2009-06-21"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(title):11
+msgid "Available Languages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(p):14
+msgid "Our documentation is also available in the following languages:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(p):18
+msgid ""
+"<uri link=\"/doc/cs/__FILE__\">Czech</uri> | <uri link=\"/doc/en/__FILE__"
+"\">English</uri> | <uri link=\"/doc/fr/__FILE__\">French</uri> | <uri link="
+"\"/doc/de/__FILE__\">German</uri> | <uri link=\"/doc/it/__FILE__\">Italian</"
+"uri> | <uri link=\"/doc/ja/__FILE__\">Japanese</uri> | <uri link=\"/doc/pl/"
+"__FILE__\">Polish</uri> | <uri link=\"/doc/zh_cn/__FILE__\">Simplified "
+"Chinese</uri> | <uri link=\"/doc/es/__FILE__\">Spanish</uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//doc-languages.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/dri-howto.xml.po b/doc/gettext/el/dri-howto.xml.po
new file mode 100644
index 0000000..a557011
--- /dev/null
+++ b/doc/gettext/el/dri-howto.xml.po
@@ -0,0 +1,497 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):6
+msgid "Hardware 3D Acceleration Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(mail:link):9
+msgid "dberkholz"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(mail:link):12
+msgid "peesh"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(mail:link):15
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(abstract):18
+msgid ""
+"This document is a guide to getting 3D acceleration working using the DRM "
+"with Xorg in Gentoo Linux."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(version):27
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(date):28
+msgid "2009-12-14"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):31
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):33
+msgid "What is hardware 3D acceleration and why do I want it?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):36
+msgid ""
+"With hardware 3D acceleration, three-dimensional rendering uses the graphics "
+"processor on your video card instead of taking up valuable CPU resources "
+"drawing 3D images. It's also referred to as \"hardware acceleration\" "
+"instead of \"software acceleration\" because without this 3D acceleration "
+"your CPU is forced to draw everything itself using the Mesa software "
+"rendering libraries, which takes up quite a bit of processing power. While "
+"Xorg typically supports 2D hardware acceleration, it often lacks hardware 3D "
+"acceleration. Three-dimensional hardware acceleration is valuable in "
+"situations requiring rendering of 3D objects such as games, 3D CAD and "
+"modeling."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):51
+msgid "How do I get hardware 3D acceleration?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):54
+msgid ""
+"In many cases, both binary and open-source drivers exist. Open-source "
+"drivers are preferable since we're using Linux and open source is one of its "
+"underlying principles. Sometimes, binary drivers are the only option, like "
+"with nVidia's cards. Binary drivers include <c>x11-drivers/nvidia-drivers</"
+"c> for nVidia cards and <c>x11-drivers/ati-drivers</c> for ATI cards."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):65
+msgid "What is DRI?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):68
+msgid ""
+"The <uri link=\"http://dri.freedesktop.org/wiki/\">Direct Rendering "
+"Infrastructure</uri>, also known as the DRI, is a framework for allowing "
+"direct access to graphics hardware in a safe and efficient manner. It "
+"includes changes to the X server, to several client libraries and to the "
+"kernel. The first major use for the DRI is to create fast OpenGL "
+"implementations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):79
+msgid "What is the DRM and how does it relate to regular Xorg?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):82
+msgid ""
+"The DRM (Direct Rendering Manager) is an <e>enhancement</e> to Xorg that "
+"adds 3D acceleration for cards by adding the kernel module necessary for "
+"direct rendering."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):91
+msgid "Purpose"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):94
+msgid ""
+"This guide is for people who can't get direct rendering working with just "
+"Xorg. The DRM works for the following drivers:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):100
+msgid "3dfx"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):101
+msgid "intel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):102
+msgid "matrox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):103
+msgid "rage128"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):104
+msgid "radeon"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):105
+msgid "mach64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):106
+msgid "sis300"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(li):107
+msgid "via"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):110
+msgid ""
+"See the <uri link=\"http://dri.freedesktop.org/\">DRI homepage</uri> for "
+"more info and documentation."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):118
+msgid "Feedback"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):121
+msgid ""
+"With suggestions, questions, etc., e-mail <mail link=\"dberkholz@gentoo.org"
+"\">Donnie Berkholz</mail>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):131
+msgid "Install Xorg and configure your kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):133
+msgid "Install Xorg"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):136
+msgid ""
+"Please read our <uri link=\"/doc/en/xorg-config.xml\">Xorg Configuration "
+"Guide</uri> to get Xorg up and running."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):144
+msgid "Configure your kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):147
+msgid "Probe for your chipset and enable just that one."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):151
+msgid "Checking your AGP chipset"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):151
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge pciutils; lspci | grep AGP</i>\n"
+"# <i>00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)</i>\n"
+"<comment>(Your output may not match the above due to different hardware.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):157
+msgid ""
+"If your chipset is not supported by the kernel you might have some succes by "
+"passing <c>agp=try_unsupported</c> as a kernel parameter. This will use "
+"Intel's generic routines for AGP support. To add this parameter, edit your "
+"bootloader configuration file!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):164
+msgid ""
+"Most, if not all, kernels should have these options. This was configured "
+"using a standard <c>gentoo-sources</c> kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):169
+msgid "Configuring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):169
+#, no-wrap
+msgid ""
+"\n"
+"# <i>ls -l /usr/src/linux </i>\n"
+"lrwxrwxrwx 1 root root 22 2007-02-14 20:12 /usr/src/linux -&gt; linux-2.6.18-gentoo-r4\n"
+"<comment>(Make sure /usr/src/linux links to your current kernel.)</comment>\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):177
+msgid "make menuconfig options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"Processor type and features ---&gt;\n"
+"&lt;*&gt; MTRR (Memory Type Range Register) support\n"
+"Device drivers ---&gt;\n"
+" Graphics support ---&gt;\n"
+" &lt;M&gt; /dev/agpgart (AGP Support) ---&gt;\n"
+" <comment>(The agpgart option is not present on 64-bit kernels; just choose your chipset support.)</comment>\n"
+" &lt;M&gt; Intel 440LX/BX/GX, I8xx and E7x05 support\n"
+" <comment>(Enable your chipset instead of the above.)</comment>\n"
+" &lt;M&gt; Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---&gt;\n"
+" &lt;M&gt; <comment>(Select your graphics card from the list)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):193
+msgid "Compile and install your kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):196
+msgid "Compiling and installing kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):196
+#, no-wrap
+msgid ""
+"\n"
+"# <i>make &amp;&amp; make modules_install</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):200
+msgid ""
+"Don't forget to set up <path>grub.conf</path> or <path>lilo.conf</path> and "
+"run <c>/sbin/lilo</c> if you use LILO."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):210
+msgid "Configure direct rendering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):212
+msgid "Configure Xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):215
+msgid ""
+"Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit "
+"it to enable DRI and GLX."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):220
+msgid "xorg.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):220
+#, no-wrap
+msgid ""
+"\n"
+"...\n"
+"Section \"Module\"\n"
+" Load \"dri\"\n"
+" Load \"glx\"\n"
+" ...\n"
+"EndSection\n"
+"...\n"
+"Section \"Device\"\n"
+" Driver \"radeon\"\n"
+" <comment>(Replace radeon with the name of your driver.)</comment>\n"
+" ...\n"
+"EndSection\n"
+"...\n"
+"Section \"dri\"\n"
+" Mode 0666\n"
+"EndSection\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):242
+msgid "Changes to modules.autoload.d"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):245
+msgid ""
+"You will need to add the module name that your card uses to <path>/etc/"
+"modules.autoload.d/kernel-2.6</path> to ensure that the module is loaded "
+"automatically when the system starts up."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):251
+msgid "Editing /etc/modules.autoload.d/kernel-2.6"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):251
+#, no-wrap
+msgid ""
+"\n"
+"<comment>(Change module name as required.)</comment>\n"
+"intel-agp\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(note):256
+msgid ""
+"If you compiled <c>agpgart</c> as a module, you will also need to add it to "
+"<path>/etc/modules.autoload.d/kernel-2.6</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):266
+msgid "Test 3D acceleration"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):268
+msgid "Reboot to the new kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):271
+msgid ""
+"Reboot your computer to your new kernel and login as a normal user. It's "
+"time to see if you have direct rendering and how good it is. <c>glxinfo</c> "
+"and <c>glxgears</c> are part of the <c>mesa-progs</c> package, so make sure "
+"it is installed before you attempt to run these commands."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):278
+msgid "Testing rendering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>startx</i>\n"
+"<comment>(No need to load modules for your driver or agpgart, even if you compiled them as a module.)</comment>\n"
+"<comment>(They will be loaded automatically.)</comment>\n"
+"$ <i>glxinfo | grep rendering</i>\n"
+"direct rendering: Yes\n"
+"<comment>(If it says \"No\", you don't have 3D acceleration.)</comment>\n"
+"$ <i>glxgears</i>\n"
+"<comment>(Test your frames per second (FPS) at the default size. The number should be\n"
+"significantly higher than before configuring DRM. Do this while the CPU is as idle as\n"
+"possible.)</comment>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(note):291
+msgid ""
+"FPS may be limited by your screen's refresh rate, so keep this in mind if "
+"<c>glxgears</c> reports only about 70-100 FPS. <c>games-fps/ut2004-demo</c> "
+"or other 3D games are better benchmarking tools, as they give you real-world "
+"performance results."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):301
+msgid "Get the most out of direct rendering"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):304
+msgid ""
+"If you want to set more features, for performance or other reasons, check "
+"out the <uri link=\"http://dri.freedesktop.org/wiki/FeatureMatrix\">feature "
+"matrix</uri> on the DRI web site or the <uri link=\"http://dri.sourceforge."
+"net/doc/dri_driver_features.phtml\">features listing</uri> on Sourceforge."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):317
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):319
+msgid "It doesn't work. I don't have rendering, and I can't tell why."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):322
+msgid ""
+"Try <c>modprobe radeon</c> before you start the X server (replace <c>radeon</"
+"c> with the name of your driver). Also, try building agpgart into the kernel "
+"instead of as a module."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):331
+msgid ""
+"When I startx, I get this error: \"[drm] failed to load kernel module agpgart"
+"\""
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):334
+msgid ""
+"That's because you compiled agpgart into the kernel instead of as a module. "
+"Ignore it unless you're having problems."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):342
+msgid "I have a Radeon, and I want TV-Out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):345
+msgid ""
+"The drivers originally developed by the <uri link=\"http://gatos.sf.net"
+"\">GATOS</uri> project have been merged into Xorg's codebase. You don't need "
+"anything special for TV-Out; <c>x11-drivers/xf86-video-ati</c> will work "
+"just fine."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):355
+msgid ""
+"It doesn't work. My card is so incredibly new and cool that it isn't "
+"supported at all."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):361
+msgid ""
+"Try out the binary drivers. For <c>ati-drivers</c>, a listing is at "
+"<uri>http://support.amd.com/us/gpudownload/Pages/index.aspx</uri>. If those "
+"don't support it, use fbdev. It's slow, but it works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):370
+msgid "I have a PCI card and it doesn't work. Help!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(p):373
+msgid ""
+"Edit <path>/etc/X11/xorg.conf</path>. In section \"Device\" enable "
+"ForcePCIMode."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre:caption):377
+msgid "Enabling ForcePCIMode"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(pre):377
+#, no-wrap
+msgid ""
+"\n"
+"Option \"ForcePCIMode\" \"True\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(title):386
+msgid "References"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(uri):391
+msgid "http://forums.gentoo.org/viewtopic.php?t=46681"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(uri):392
+msgid "http://forums.gentoo.org/viewtopic.php?t=29264"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(uri):393
+msgid "http://dri.freedesktop.org/"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(uri):394
+msgid "http://www.retinalburn.net/linux/dri_status.html"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//dri-howto.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/ebuild-submit.xml.po b/doc/gettext/el/ebuild-submit.xml.po
new file mode 100644
index 0000000..a512273
--- /dev/null
+++ b/doc/gettext/el/ebuild-submit.xml.po
@@ -0,0 +1,252 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(guide:link):5
+msgid "/doc/en/ebuild-submit.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):6
+msgid "Contributing Ebuilds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(mail:link):9
+msgid "mbutcher@frii.com"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(mail):9
+msgid "Matt Butcher"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(abstract):12
+msgid ""
+"This guide explains how to submit ebuild packages through the Bugzilla "
+"tracking system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(version):17
+msgid "1.5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(date):18
+msgid "2005-10-24"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):21
+msgid "Getting Started"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):23
+msgid "Create A Bugzilla Account"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):26
+msgid ""
+"Point your web browser to <uri>http://bugs.gentoo.org</uri>. This is the URL "
+"for the Bugzilla bug tracking database. In the list of links, one of the "
+"items reads \"Open a new Bugzilla account\". If you have not done so already "
+"(e.g. for submitting a bug), click on this link and create a new account."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):36
+msgid "Don't Submit CPAN Ebuilds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):39
+msgid ""
+"Portage provides a tool called <c>g-cpan.pl</c> which installs a given CPAN "
+"module on your Gentoo system using Portage, storing the necessary "
+"information (such as dependencies, provided files, etc.) in the Portage "
+"database, just like it would when you install an ebuild. It is therefore not "
+"needed (nor recommended) to submit CPAN ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):47
+msgid "For more information on <c>g-cpan.pl</c>, please consult its man page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):56
+msgid "Submitting an ebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):58
+msgid "Create a new bug"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):61
+msgid ""
+"At the bottom of the main page or login page, there is a yellow box. Choose "
+"the <c>New - Expert</c> link. Or, you can just go to the URL <uri>http://"
+"bugs.gentoo.org/enter_bug.cgi</uri>. Either will bring you to the <c>Enter "
+"Bug</c> page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(note):68
+msgid ""
+"In the Bugzilla system, all entries are bugs. That includes newly submitted "
+"ebuilds. Each bug is assigned a tracking id. Take note of the ID, especially "
+"if you have other ebuilds that depend on this package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):74
+msgid ""
+"Bugzilla can track multiple products. For example, in Gentoo, other products "
+"may include documentation or tools used to administrate the website. From "
+"the list of products, Ebuilds should always be submitted to <c>Gentoo Linux</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):80
+msgid ""
+"Clicking on the <c>Gentoo Linux</c> product should bring up a new bug entry "
+"form."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):88
+msgid "Completing the bug form"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):91
+msgid ""
+"The first field on the form is <c>version</c>. If you know which version "
+"your package belongs in, set it here. Otherwise, select <c>unspecified</c>. "
+"Next, set the component. All ebuild scripts are of the component type "
+"<c>Ebuilds</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(impo):97
+msgid ""
+"Ebuilds should <e>always</e> be of component type <c>Ebuild</c>. Categories "
+"such as <c>GNOME</c>, <c>Libraries</c>, and <c>Server</c> may look like they "
+"apply to your ebuild, but they are used for filing bugs against packages, "
+"not submitting ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):104
+msgid ""
+"The categories <c>Platform</c>, <c>OS</c>, and <c>Priority</c> do not need "
+"to be set for ebuilds."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):109
+msgid "The <c>Severity</c> field should be set to <c>enhancement</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):113
+msgid ""
+"Leave the <c>Assigned To</c> field blank. If you haven't changed Bugzilla's "
+"mail settings, you, as a reporter, will automatically receive email on bug "
+"updates."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):118
+msgid ""
+"Fill in the <c>Summary</c> field with a brief note of what package you are "
+"submitting and whether it's an update or a new submission. Something like "
+"the following is great: <c>foo-bar-x.y.z.ebuild (New Package)</c> or <c>foo-"
+"x.y.z.ebuild (Update)</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):125
+msgid ""
+"The <c>Description</c> field should be filled in as completely as possible. "
+"Here's an example from Bug Number 7:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(pre:caption):130
+msgid "Example description"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(pre):130
+#, no-wrap
+msgid ""
+"\n"
+"Hi!\n"
+"\n"
+"Please find attached gramps-0.7.0.ebuild and a patch so that it will\n"
+"compile against python-2.2\n"
+"\n"
+"gramps is the Genealogical Research and Analysis Management Programming\n"
+"System. It is a very cool gnome/python app. If you are in the US, you\n"
+"can head over to http://www.familysearch.com/ and you can probably find a\n"
+"GEDCOM file for your family tree to import into gramps. (Mormons sure do like\n"
+"geneaology)\n"
+"\n"
+"I suggest app-misc/gramps Also, this ebuild depend on Imaging and ReportLab\n"
+"previously submitted\n"
+"\n"
+"tod\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):148
+msgid "Once the summary is complete, click <c>Commit</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):155
+msgid "Attaching the Ebuild Script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):158
+msgid ""
+"After clicking <c>submit</c> on the <c>Enter Bug</c> page, you will go to "
+"the <c>Posting Bug</c> page. Take note of the bug number."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):163
+msgid ""
+"Toward the bottom of this page, there is a link to <c>Create a new "
+"attachment</c>. Click on this link."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):168
+msgid ""
+"Select the file using the text entry box or the <c>Browse</c> dialog. In the "
+"<c>Description</c> field, type the name of the ebuild file, much the same as "
+"you did in the <c>Summary</c> section of the last page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):174
+msgid ""
+"Make sure that the content type is set to \"text/plain\", and that the "
+"radiobutton for <c>select from list</c> is marked."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):179
+msgid ""
+"There are no other required fields on this form. Click <c>Submit</c> and you "
+"are done!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):189
+msgid "Multiple Ebuilds"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(title):191
+msgid "Dependencies"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(p):194
+msgid ""
+"In cases where you might submit multiple ebuilds, and some of them depend on "
+"others, it is very helpful if these dependencies are noted. Viewing the bug "
+"again should allow you to enter another note. Please add dependancy "
+"information here."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//ebuild-submit.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/faq.xml.po b/doc/gettext/el/faq.xml.po
new file mode 100644
index 0000000..6ee4562
--- /dev/null
+++ b/doc/gettext/el/faq.xml.po
@@ -0,0 +1,997 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):6
+msgid "Gentoo Linux Frequently Asked Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):7
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):8
+msgid "drobbins@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):8
+msgid "Daniel Robbins"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):10
+msgid "Reviewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author):10
+msgid "Colin Morey"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):13
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):16
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):19
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):22
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):25
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):28
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):31
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):34
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author:title):37
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(author):13
+msgid "John P. Davis"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):17
+msgid "stocke2@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):17
+msgid "Eric Stockbridge"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):20
+msgid "zhware@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):20
+msgid "Stoyan Zhekov"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):23
+msgid "carl@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):23
+msgid "Carl Anderson"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):26
+msgid "peesh@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):26
+msgid "Jorge Paulo"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):29
+msgid "swift@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):29
+msgid "Sven Vermeulen"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):32
+msgid "bennyc@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):32
+msgid "Benny Chuang"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):35
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail):35
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(mail:link):38
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(abstract):41
+msgid ""
+"This FAQ is a collection of questions and answers collected from the gentoo-"
+"dev mailing list and from IRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(version):50
+msgid "5"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(date):51
+msgid "2010-10-13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):54
+msgid "Questions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):56
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):59
+msgid ""
+"Please note that many of these questions are answered within the official "
+"Gentoo documents and guides. This is simply a list of common questions. "
+"Please read the documentation and/or man pages to gain a greater "
+"understanding of how Gentoo and GNU/Linux works, and for answers to "
+"questions which may not be answered here."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):72
+msgid "Getting Started"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):75
+msgid "How is Gentoo pronounced, and what does it mean?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):78
+msgid ""
+"<e>Gentoo</e> is pronounced \"gen-too\" (the \"g\" in \"Gentoo\" is a soft "
+"\"g\", as in \"gentle\"). The scientific name of the <uri link=\"http://en."
+"wikipedia.org/wiki/Gentoo_penguin\">Gentoo penguin</uri> is <e>Pygoscelis "
+"papua</e>. The name <e>Gentoo</e> has been given to the penguin by the "
+"inhabitants of the <uri link=\"http://en.wikipedia.org/wiki/Falkland_Islands"
+"\">Falkland Islands</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):90
+msgid "What makes Gentoo different?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):93
+msgid ""
+"Gentoo uses a BSD ports-like system called <uri link=\"/proj/en/portage"
+"\">Portage</uri>. Portage is a package management system that allows great "
+"flexibility while installing and maintaining software on a Gentoo system. It "
+"provides compile-time option support (through <uri link=\"/doc/en/handbook/"
+"handbook-x86.xml?part=2&amp;chap=2\">USE flags</uri>), conditional "
+"dependencies, pre-package installation summary, safe installation (through "
+"sandboxing) and uninstallation of software, system profiles, <uri link=\"/"
+"doc/en/handbook/handbook-x86.xml?part=3&amp;chap=2#doc_chap3\">configuration "
+"file protection</uri> amongst several other <uri link=\"/doc/en/handbook/"
+"handbook-x86.xml?part=2&amp;chap=1\">features</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):106
+msgid ""
+"With Gentoo you can build your entire system from source, using your choice "
+"of optimizations. You have complete control over what packages are or aren't "
+"installed. Gentoo provides you with numerous choices, so you can install "
+"Gentoo to your own preferences, which is why Gentoo is called a <e>meta-"
+"distribution</e>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):113
+msgid ""
+"Gentoo is actively developed. The entire distribution uses a rapid pace "
+"development style: patches to the packages are quickly integrated in the "
+"mainline tree, documentation is updated on daily basis, Portage features are "
+"added frequently, and official releases occur twice per year."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):125
+msgid "Installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):127
+msgid ""
+"Things are really unstable and I'm using -O9 -ffast-math -fomit-frame-"
+"pointer optimizations. What gives?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):133
+msgid ""
+"Don't bother using anything higher than <c>-O3</c> since it isn't supported "
+"by current versions of gcc. Very aggressive optimizations sometimes cause "
+"the compiler to streamline the assembly code to the point where it doesn't "
+"quite do the same thing anymore."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):140
+msgid ""
+"Please try to compile with CFLAGS <c>-O2 -march=&lt;your_arch&gt;</c> before "
+"reporting a bug."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):148
+msgid "How do I change the root (or any other user's) password?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):151
+msgid ""
+"You can use <c>passwd</c> to change the password for the user you are logged "
+"into. As root, you can change any user password by issuing the command "
+"<c>passwd username</c> For extra options and setting, please <c>man passwd</"
+"c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):160
+msgid "How do I add a normal user?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):163
+msgid ""
+"The command <c>useradd username</c> will add a user called \"username\". "
+"However, this method does not give the user many of the rights you might "
+"want to grant him, so the following command is preferred:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):169
+msgid "Using useradd"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):169
+#, no-wrap
+msgid ""
+"\n"
+"# <i>useradd -m -G users,audio,wheel username</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):173
+msgid ""
+"This will add a user named \"username\". The option <c>audio</c> adds them "
+"to the <c>audio</c> group and allows the user to access sound devices. The "
+"option <c>wheel</c> adds the user to the <c>wheel</c> group, which allows "
+"the user to execute the command <c>su</c>, which in turn allows them to gain "
+"the privileges of the <c>root</c> user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):184
+msgid "Why can't a user su to root?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):187
+msgid ""
+"For security reasons, users may only <c>su</c> to root if they belong to the "
+"wheel group. To add a username to the wheel group, issue the following "
+"command as root:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):193
+msgid "Adding a user to the wheel group"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gpasswd -a username wheel</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):200
+msgid "Can I upgrade Gentoo from one release to another without reinstalling?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):205
+msgid ""
+"In fact, there is no difference between the various releases after they have "
+"been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such, "
+"running <c>emerge --sync &amp;&amp; emerge -uDN world</c> will bring your "
+"entire system up to speed with the \"latest Gentoo\". The differences "
+"between individual releases lie in the installation medium and pre-compiled "
+"packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo "
+"Upgrading Guide</uri> for more information about profiles and their role in "
+"upgrading."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):218
+msgid "My kernel doesn't boot, what should I do now?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):221
+msgid ""
+"You don't need to redo every step of the installation, but investigating the "
+"kernel and all associated steps is necessary. Suppose you have installed "
+"Gentoo on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with "
+"<path>/dev/hda2</path> being the swap space:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):228
+msgid "Reconfiguring the kernel"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):228
+#, no-wrap
+msgid ""
+"\n"
+"<comment>Boot from the Install CD and wait until you receive a prompt</comment>\n"
+"<comment>We first mount all partitions:</comment>\n"
+"# <i>mount /dev/hda3 /mnt/gentoo</i>\n"
+"# <i>mount /dev/hda1 /mnt/gentoo/boot</i>\n"
+"# <i>swapon /dev/hda2</i>\n"
+"# <i>mount -t proc none /mnt/gentoo/proc</i>\n"
+"<comment>Then we chroot into our Gentoo environment and configure the kernel:</comment>\n"
+"# <i>chroot /mnt/gentoo /bin/bash</i>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+"# <i>cd /usr/src/linux</i>\n"
+"# <i>make menuconfig</i>\n"
+"<comment>Now (de)select anything you have (de)selected wrongly at your</comment>\n"
+"<comment>previous attempt. Then quit and compile your kernel:</comment>\n"
+"# <i>make &amp;&amp; make modules_install</i>\n"
+"<comment>Now copy over your bzImage file, overwriting your previous one:</comment>\n"
+"# <i>cp arch/i386/boot/bzImage /boot/&lt;kernel_name&gt;</i>\n"
+"<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment>\n"
+"# <i>/sbin/lilo</i>\n"
+"<comment>Now exit the chroot and reboot.</comment>\n"
+"# <i>exit</i>\n"
+"# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>\n"
+"# <i>reboot</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):253
+msgid ""
+"If, on the other hand, the problem lies with your bootloader configuration, "
+"follow the same steps, but instead of configuring/compiling your kernel, you "
+"should reconfigure your bootloader (recompilation isn't necessary)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):262
+msgid "My proxy requires authentication, what do I have to do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):265
+msgid ""
+"To have Portage automatically use this scheme, define it in <path>/etc/make."
+"conf</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):270
+msgid "/etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):270
+#, no-wrap
+msgid ""
+"\n"
+"http_proxy=\"http://username:password@yourproxybox.org:portnumber\"\n"
+"ftp_proxy=\"ftp://username:password@yourproxybox.org:portnumber\"\n"
+"RSYNC_PROXY=\"rsync://username:password@yourproxybox.server:portnumber\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):279
+msgid "How do I burn an ISO file?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):282
+msgid ""
+"You need to burn the file in raw mode. This means that you should <e>not</e> "
+"just place the file on the CD, but interpret the file as an entire CD."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):287
+msgid ""
+"There are lots of CD burning tools available; covering them all would be a "
+"Sisyphean problem. However, describing a few popular tools never hurts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):293
+msgid ""
+"With EasyCD Creator you select <c>File</c>, <c>Record CD from CD image</c>. "
+"Then you change the <c>Files of type</c> to <c>ISO image file</c>. Then "
+"locate the ISO file and click <c>Open</c>. When you click on <c>Start "
+"recording</c> the ISO image will be burned correctly onto the CD-R."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):299
+msgid ""
+"With Nero Burning ROM, cancel the wizard which automatically pops up and "
+"select <c>Burn Image</c> from the <c>File</c> menu. Select the image you "
+"want to burn and click <c>Open</c>. Now hit the <c>Burn</c> button and watch "
+"your brand new CD being burnt."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):305
+msgid ""
+"With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace <path>/"
+"dev/hdc</path> with your CD-RW drive's device path) followed by the path to "
+"the ISO file :)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):310
+msgid ""
+"With K3B, select <c>Tools</c> &gt; <c>CD</c> &gt; <c>Burn CD Image</c>. Then "
+"you can locate your ISO file within the 'Image to Burn' area. Finally click "
+"<c>Start</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):315
+msgid ""
+"With Mac OS X Panther, launch <c>Disk Utility</c> from <path>Applications/"
+"Utilities</path>, select <c>Open</c> from the <c>Images</c> menu, select the "
+"mounted disk image in the main window and select <c>Burn</c> in the "
+"<c>Images</c> menu."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):321
+msgid ""
+"With Mac OS X Jaguar, launch <c>Disk Copy</c> from <path>Applications/"
+"Utilities</path>, select <c>Burn Image</c> from the <c>File</c> menu, select "
+"the ISO and click the <c>Burn</c> button."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):332
+msgid "What CD/stage should I use for my CPU?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):335
+msgid ""
+"First you need to find out what CPU you use. Suppose it's a Pentium-M. Then "
+"you need to find out what CPU it is, instruction-wise, compatible with. You "
+"may need to consult the CPU's vendor website for this, although <uri link="
+"\"http://www.google.com\">Google</uri> is at least as efficient :-)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342
+msgid ""
+"If you are uncertain, take a \"lower\" CD/stage file, for instance a i686 or "
+"even generic x86 (or the equivalent in your arch). This will ensure that "
+"your system will work, but may not be as fast as further optimizations."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):348
+msgid ""
+"Please note that many more options exist than those for which Gentoo builds "
+"binary stages. Please see the <uri link=\"http://gcc.gnu.org/onlinedocs/"
+"gcc-4.4.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options"
+"\">gcc guide</uri> for setting <c>-march</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):358
+msgid "I can't get online after rebooting. What is wrong?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):361
+msgid ""
+"First you need to check if your network card is discovered properly by the "
+"kernel. Run <c>ifconfig&nbsp;-a</c> and look for eth0 or wlan0 (in case of "
+"certain wireless network cards). You might need to load specific kernel "
+"modules for the kernel to properly detect the network card. If that is the "
+"case, make sure that these kernel modules are listed in <path>/etc/modules."
+"autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path> if you are still "
+"using a 2.4 kernel)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):371
+msgid ""
+"If you have forgotten to include support for your network card in your "
+"kernel, you will need to reconfigure your kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):376
+msgid ""
+"If your network card is found by your kernel, but you have set your "
+"networking configuration to use DHCP, you might have forgotten to "
+"<c>emerge&nbsp;dhcpcd</c>. You will need to reboot with your installation CD "
+"to install <c>dhcpcd</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):383
+msgid ""
+"Information on how to rescue your system using the installation CD is <uri "
+"link=\"#bootrescue\">available</uri> as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):391
+msgid ""
+"I want to boot Windows from grub or lilo but it shows only black screen. "
+"What should I do?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):397
+msgid ""
+"This is a known problem. Windows refuses to boot when it isn't installed on "
+"the first hard drive and shows a black/blank screen. To handle this, you "
+"will have to \"fool\" Windows into believing that it is installed on the "
+"first hard drive with a little tweak in your boot loader configuration. "
+"Please note that in the below example, Gentoo is installed on <path>hda</"
+"path> (first disk) and Windows on <path>hdb</path> (second one). Adjust your "
+"config as needed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):406
+msgid "Example dual boot entry for Windows in grub.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):406
+#, no-wrap
+msgid ""
+"\n"
+"title Windows XP\n"
+" map (hd1) (hd0)\n"
+" map (hd0) (hd1)\n"
+" rootnoverify (hd1,0)\n"
+" chainloader +1\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):414
+msgid "Example dual boot entry for Windows in lilo.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):414
+#, no-wrap
+msgid ""
+"\n"
+"other=/dev/hdb1\n"
+" label=WindowsXP\n"
+" table=/dev/hdb\n"
+" map-drive = 0x80\n"
+" to = 0x81\n"
+" map-drive = 0x81\n"
+" to = 0x80\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):424
+msgid ""
+"This will make Windows believe it is installed on the first hard drive and "
+"boot without problems. More information can be found in the <uri link="
+"\"http://www.gnu.org/software/grub/\">GRUB documentation</uri> and in <c>man "
+"lilo.conf</c>, depending on the boot loader you're using."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):434
+msgid "How do I Install Gentoo Using a Stage1 or Stage2 Tarball?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):437
+msgid ""
+"The Gentoo Handbook only describes a Gentoo installation using a stage3 "
+"tarball. However, Gentoo still provides stage1 and stage2 tarballs. This is "
+"for development purposes (the Release Engineering team starts from a stage1 "
+"tarball to obtain a stage3) but shouldn't be used by users: a stage3 tarball "
+"can very well be used to bootstrap the system. You do need a working "
+"Internet connection."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):445
+msgid ""
+"Bootstrapping means building the toolchain (the C library and compiler) for "
+"your system after which you install all core system packages. To bootstrap "
+"the system, perform a stage3 installation. Before you start the chapter on "
+"<e>Configuring the Kernel</e>, modify the <path>bootstrap.sh</path> script "
+"to suit your needs and then run it:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):453
+msgid "Bootstrapping the system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):453
+#, no-wrap
+msgid ""
+"\n"
+"# <i>cd /usr/portage/scripts</i>\n"
+"# <i>vi bootstrap.sh</i>\n"
+"\n"
+"# <i>./bootstrap.sh</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):460
+msgid ""
+"Next, rebuild all core system packages with the newly built toolchain. We "
+"need to rebuild them since the stage3 tarball already offers them:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):465
+msgid "Rebuilding the core system packages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):465
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e system</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):469
+msgid ""
+"Now you can continue with <e>Configuring the Kernel</e>. You can not use the "
+"prebuilt GRP packages anymore though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):479
+msgid "Package Management"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):481
+msgid "In what form are the packages stored?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):484
+msgid ""
+"Packages aren't \"stored\" per se. Instead, Gentoo provides a set of scripts "
+"which can resolve dependencies, fetch source code, and compile a version of "
+"the package specifically for your needs. We generally only build binaries "
+"for releases and snapshots. The <uri link=\"/proj/en/devrel/handbook/"
+"handbook.xml?part=2&amp;chap=1\">Gentoo Ebuild HOWTO</uri> covers the "
+"contents of an ebuild script in detail."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):493
+msgid ""
+"For full ISO releases, we create a full suite of binary packages in an "
+"enhanced <c>.tbz2</c> format, which is <c>.tar.bz2</c> compatible with meta-"
+"information attached to the end of the file. These can be used to install a "
+"working (though not fully optimized) version of the package quickly and "
+"efficiently."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):500
+msgid ""
+"It is possible to create RPMs (Redhat package manager files) using Gentoo's "
+"Portage, but it is not currently possible to use already existing RPMs to "
+"install packages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):509
+msgid "I want to perform the ./configure step myself. Can I?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):512
+msgid ""
+"Yes, but it is not trivial, nor is it recommended. Since the method to do "
+"this requires a good understanding of Portage internals and commands, it is "
+"instead recommended that you patch the ebuild to do whatever it is that you "
+"want and place it in a Portage overlay (that's why overlays exist). This is "
+"<e>much</e> better for maintainability, and usually easier. See the <uri "
+"link=\"/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=1\">Ebuild "
+"HOWTO</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):525
+msgid "How do I use emerge from behind a firewall?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):528
+msgid ""
+"See the questions on <uri link=\"#proxy\">proxies</uri>, <uri link=\"#norsync"
+"\">rsync</uri>, and <uri link=\"#manualdownload\">downloading source files "
+"manually</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):537
+msgid "What if rsync doesn't work for me?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):540
+msgid ""
+"If you're behind a firewall that doesn't permit rsync traffic, then you can "
+"use <c>emerge-webrsync</c> which will fetch and install a Portage snapshot "
+"for you through regular HTTP. See the <uri link=\"#proxy\">proxy section</"
+"uri> of this document for information on downloading source files and "
+"Portage snapshots via a proxy."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):551
+msgid ""
+"I have only slow modem connection at home. Can I download sources somewhere "
+"else and add them to my system?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):557
+msgid ""
+"Definitely. You can run <c>emerge --pretend package</c> to see what programs "
+"are going to be installed. To find out the sources for those packages and "
+"where to download the sources from, you can run <c>emerge -fp package</c>. "
+"Download sources and bring them on any media home. Put the sources into "
+"<path>/usr/portage/distfiles/</path> and then simply run <c>emerge package</"
+"c>. Be warned, however, that this is a tedious process."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):569
+msgid ""
+"Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to "
+"delete these files?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):575
+msgid ""
+"Deleting these files will have no negative impact on day-to-day performance. "
+"However, it might be wise to keep the most recent version of the files; "
+"often several ebuilds will be released for the same version of a specific "
+"piece of software. If you have deleted the archive and you upgrade the "
+"software it will be necessary to download them from the internet again."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):583
+msgid ""
+"You can use the <c>eclean</c> script from <c>app-portage/gentoolkit</c> to "
+"manage the contents of <path>/usr/portage/distfiles/</path> and a few other "
+"locations. Please read <c>man eclean</c> to learn more about its usage, as "
+"well as the <uri link=\"/doc/en/gentoolkit.xml\">Gentoolkit Guide</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):593
+msgid ""
+"What's in /var/tmp/portage? Is it safe to delete the files and directories "
+"in /var/tmp/portage?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):599
+msgid ""
+"During compilation, Gentoo saves the sources of the package in <path>/var/"
+"tmp/portage</path>. These files and folder are usually deleted upon a "
+"successful merge, but this sometimes fails. It is safe to clean out all "
+"contents of this directory <e>if</e> emerge is not running. Just to be sure, "
+"always <c>pgrep emerge</c> before cleaning out this directory."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):612
+msgid "Usage"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):614
+msgid "How do I set up an International Keyboard Layout?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):617
+msgid ""
+"Edit the <c>KEYMAP</c> variable in <path>/etc/conf.d/keymaps</path>. To have "
+"console working correctly with extended characters in your keymap you might "
+"also need to set up variables <c>CONSOLETRANSLATION</c> and <c>CONSOLEFONT</"
+"c> in your <path>/etc/conf.d/consolefont</path> (for further information on "
+"localising your environment, refer to <uri link=\"/doc/en/guide-localization."
+"xml\">our localisation guide</uri>). Then, either <c>reboot</c>, or restart "
+"the keymaps and consolefont scripts:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):627
+msgid "Restarting keymaps"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):627
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/keymaps restart</i>\n"
+"# <i>/etc/init.d/consolefont restart</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):635
+msgid "DNS name resolution works for root only"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):638
+msgid ""
+"<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as "
+"follows:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):643
+msgid "Changing permissions on /etc/resolv.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):643
+#, no-wrap
+msgid ""
+"\n"
+"# <i>chmod 0644 /etc/resolv.conf</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):650
+msgid "Why can't my user use their own crontab?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):653
+msgid "You need to add that user to the <c>cron</c> group."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):660
+msgid "How do I get numlock to start on boot?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):663
+msgid ""
+"If you work in command line, you only need to <c>rc-update add numlock "
+"default &amp;&amp;/etc/init.d/numlock start</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):668
+msgid ""
+"Each GUI provides different tools for this sort of thing; please check the "
+"help section or online manuals for assistance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):676
+msgid "How do I have my terminal cleared when I log out?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):679
+msgid ""
+"To have your terminal cleared, add <c>clear</c> to your <path>~/."
+"bash_logout</path> script:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):684
+msgid "Clearing the terminal during logout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):684
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo clear &gt;&gt; ~/.bash_logout</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):688
+msgid ""
+"If you want this to happen automatically when you add a new user, do the "
+"same for the <path>/etc/skel/.bash_logout</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):693
+msgid "Making new users their terminal clear on logout"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):693
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo clear &gt;&gt; /etc/skel/.bash_logout</i>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):701
+msgid "Maintenance"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):703
+msgid "ReiserFS and filesystem corruption issues -- how to fix them, etc"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):706
+msgid ""
+"If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and "
+"run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This "
+"should make the filesystem consistent again, although you may have lost some "
+"files or directories due to the corruption."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):718
+msgid "Development"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):720
+msgid "Where can I report bugs?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):723
+msgid ""
+"Use our <uri link=\"https://bugs.gentoo.org\">Bugzilla</uri>. If you are "
+"unsure if your problem is an actual bug, you can visit <uri link=\"irc://irc."
+"gentoo.org/gentoo\">#gentoo</uri> on IRC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):732
+msgid "How often are new releases made?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):735
+msgid ""
+"Gentoo's packages are usually updated shortly after the main authors release "
+"new code. As for when Gentoo itself makes new stage/profile/ISO releases, "
+"check our <uri link=\"/proj/en/releng\">Release Engineering Project</uri> "
+"page. New releases are announced on the <uri link=\"/main/en/lists.xml"
+"\">gentoo-announce</uri> mailing list. See the question on <uri link="
+"\"#upgrade\">upgrading</uri> for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):747
+msgid "My speaker beeps like crazy. How do I disable console beeps?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):752
+msgid "Console beeps can be turned off using setterm, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):756
+msgid "Using setterm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):756
+#, no-wrap
+msgid ""
+"\n"
+"# <i>setterm -blength 0</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):760
+msgid ""
+"If you would like to turn off the console beeps on boot, you need to put "
+"this command in <path>/etc/conf.d/local.start</path>. However, this only "
+"disables beeps for the current terminal. To disable beeps for other "
+"terminals, pipe the command output to the target terminal, like this:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):766
+msgid "Using setterm (bis)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):766
+#, no-wrap
+msgid ""
+"\n"
+"# <i>setterm -blength 0 &gt;/dev/vc/1</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):770
+msgid ""
+"You need to replace /dev/vc/1 with the terminal you would like to disable "
+"console beeps for."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):780
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):782
+msgid "Where can I find more information about Gentoo Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):785
+msgid ""
+"The official Gentoo documentation can be found at <uri>http://www.gentoo.org/"
+"doc/en/</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):793
+msgid "Can I buy a CD of Gentoo Linux?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):796
+msgid ""
+"Install CDs for all supported architectures are available on our <uri link="
+"\"http://www.cafepress.com/officialgentoo/\">Gentoo Store</uri>. When you "
+"purchase a CD from our store, you are also supporting our development. So, "
+"please consider buying from our store if possible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):803
+msgid ""
+"You can also find fresh CDs from various resellers listed on our <uri link="
+"\"/main/en/where.xml\">Get Gentoo!</uri> page."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):811
+msgid "This FAQ hasn't answered my question. What do I do now?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):814
+msgid ""
+"A good first step is to browse through the relevant <uri link=\"/doc/en/"
+"index.xml\">documentation</uri>, failing that, the various Gentoo Linux "
+"mailing lists listed on <uri link=\"http://www.google.com\">Google</uri>. To "
+"search through the Gentoo mailing lists, just enter \"lists.gentoo.org foo\" "
+"to search for \"foo\". If all else fails, or you just want to hang out with "
+"Gentoo folks, visit us on irc: <uri link=\"irc://irc.gentoo.org/gentoo"
+"\">#gentoo</uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//faq.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/fluxbox-config.xml.po b/doc/gettext/el/fluxbox-config.xml.po
new file mode 100644
index 0000000..84bc07d
--- /dev/null
+++ b/doc/gettext/el/fluxbox-config.xml.po
@@ -0,0 +1,879 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(guide:link):5
+msgid "/doc/en/fluxbox-config.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):6
+msgid "The Fluxbox Configuration HOWTO"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail:link):9
+msgid "smithj@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail):9
+msgid "Jonathan Smith"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(author:title):11
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(author:title):14
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail:link):12
+msgid "alin@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail):12
+msgid "Alin Dobre"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail:link):15
+msgid "nightmorph@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail):15
+msgid "Joshua Saddler"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(author:title):17
+msgid "Contributor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(mail:link):18
+msgid "lack"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(abstract):21
+msgid ""
+"This howto will show you how to set up the Fluxbox window manager for X11."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(version):29
+msgid "1.13"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(date):30
+msgid "2009-08-01"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):33
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):35
+msgid "Introduction to the Fluxbox window manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):38
+msgid ""
+"For those who are unfamiliar with Linux's desktop model, window managers "
+"(WMs) are the applications which are run by X11 to manage other graphical "
+"programs. WMs control where each window is placed, its size, and which "
+"desktop(s) have access to it. This can be done automatically via a set of "
+"user-defined rules or can be done at runtime with the mouse and possibly "
+"keyboard shortcuts, depending on the specific WM."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):47
+msgid ""
+"Some WMs, however, take on more functionality than just window management. "
+"Fluxbox also provides a platform for launching applications, configuring "
+"keyboard shortcuts and background images, as well as displaying information "
+"with the slit. GNOME's default WM, Metacity, does not include these things, "
+"but they are available through other GNOME programs. Thus, one cannot truly "
+"say that Fluxbox is a lightweight WM. However, since Fluxbox includes "
+"everything necessary for a basic desktop, many people use it in place of "
+"larger desktop suites like GNOME or KDE."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):58
+msgid ""
+"To make things even more confusing, however, Fluxbox can replace the default "
+"WM for GNOME or KDE. For example, some people find that Metacity, GNOME's "
+"window manager, simply does not have the flexibility they need, but that "
+"Fluxbox does not have all the built-in applications and integration they "
+"desire from a complete desktop environment. Thus, a person could use Fluxbox "
+"to manage the windows and GNOME for the rest. Note, however, that with this "
+"setup there are some issues caused by overlapping feature sets."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):68
+msgid ""
+"Fluxbox can also be expanded by third party software. This is often ideal in "
+"situations where hardware resources are limited, or even just as a matter of "
+"personal taste."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):74
+msgid ""
+"This guide is aimed at those who are new to Fluxbox, curious, or who are "
+"just wanting to get more out of the Gentoo/Fluxbox experience. This guide "
+"will also illustrate how to get more (yet quite optional) functionality by "
+"using third party programs which work well with Fluxbox."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):86
+msgid "Installing Fluxbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):88
+msgid "Base installation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):91
+msgid ""
+"First, make sure you've installed a working X environment, as shown in the "
+"<uri link=\"/doc/en/xorg-config.xml\">X Server Configuration HOWTO</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):96
+msgid ""
+"Before you install Fluxbox, you should take a look at some of the available "
+"USE flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):101
+msgid ""
+"While the <c>gnome</c> and <c>kde</c> USE flags are provided to give "
+"compatibility with these environments, it has been the author's experience "
+"that these USE flags are not needed. If you desire qt, gtk+, or any KDE/"
+"GNOME utility then you are free to emerge and configure those independently. "
+"The <c>gnome</c> and <c>kde</c> flags simply add support for the respective "
+"protocols, and do not depend on external libraries. However, they do "
+"increase the Fluxbox binary size."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):111
+msgid ""
+"There is also a <c>vim-syntax</c> flag to make configuration easier later "
+"on. This flag will install <c>fluxbox-syntax</c>, a special Fluxbox color "
+"scheme for <c>vim</c>. This enables users to more readily see the contents "
+"of their keys and init files for Fluxbox. It's a tiny extension for vim, so "
+"it's highly recommended."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):119
+msgid ""
+"Finally, there are two flags that customize the functionality of Fluxbox, "
+"<c>slit</c> and <c>toolbar</c>. These flags are provided so that users who "
+"don't need the <uri link=\"http://fluxbox-wiki.org/index.php?"
+"title=Faqs#What_is_the_slit\">slit</uri> or the <uri link=\"http://fluxbox."
+"org/features/\">toolbar</uri> can compile Fluxbox without them. This is "
+"useful if you want to run an extremely minimal environment, or if you plan "
+"to use different applications that provide these features, such as "
+"standalone panels or docks."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):130
+msgid ""
+"Once you've decided on your USE flags, add them to <path>/etc/portage/"
+"package.use</path>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):135
+msgid "Example: adding USE flags"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):135
+#, no-wrap
+msgid ""
+"\n"
+"# <i>echo \"x11-wm/fluxbox -gnome -kde truetype vim-syntax\" &gt;&gt; /etc/portage/package.use</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):139
+msgid ""
+"It is also necessary to have a program lock the X display to prevent "
+"unauthorized access, so it would be wise to also emerge <c>xlockmore</c>. "
+"The vast majority of users will also want the ability to set their own "
+"background, so we will emerge <c>eterm</c>, which doubles as a nice X11 "
+"terminal."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):146
+msgid "Emerging Fluxbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):146
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge fluxbox xlockmore eterm</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):150
+msgid ""
+"Well, that's it; Fluxbox is now installed! However, it is likely that you "
+"will not be able to use it efficiently with just those tools. The following "
+"sections will help install other potentially necessary packages, and "
+"configure Fluxbox and the third party programs to work for you. Keep in mind "
+"that all these steps are optional, so feel free to pick and choose."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):164
+msgid "Configuring Fluxbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):166
+msgid "Preparing X11"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):169
+msgid ""
+"Fluxbox is simply another program that X11 runs. If desired, one can "
+"<c>startx</c> and then type <c>fluxbox</c> at an xterm. However, this is "
+"annoying to say the least. If one does not desire to boot to the GUI, but "
+"instead wants to start X11 manually, it is possible to have X automatically "
+"load Fluxbox by executing, as a normal (non-root) user:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):177
+msgid "Editing your xinit"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):177
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>echo \"exec startfluxbox\" &gt; ~/.xinitrc</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):181
+msgid ""
+"This is also not ideal for most users, as they want to have the desktop "
+"environment all the time; it is a pain to <c>startx</c> if it is desired to "
+"use a GUI everytime you boot. It also presents a security risk to the "
+"unaware. If one locks the X11 display using <c>xlock</c>, but run X11 from a "
+"console, then someone with physical access to the computer can switch to "
+"that console, kill X11, and use your account. The only way to prevent this "
+"is to either background X11 or run it in screen, detach the screen, and then "
+"logout of the console, a tedious task at best. If one uses a graphical login "
+"manager, this problem does not exist. However, you will be running X11 as "
+"root, which may be a bad thing. There are, as of this writing, no exploits "
+"that the author is aware of for the current version, but if one is "
+"concerned, then either not use X11 or use the above method with screen. Note "
+"that this is not a Fluxbox issue, but affects X11 itself."
+msgstr ""
+
+#. thanks to Josh Nichols for helping cleanup this section. see comment #4 on bug
+#. 87330
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):202
+msgid ""
+"There are a number of graphical login managers to choose from; we will be "
+"using <uri link=\"http://slim.berlios.de\">SLiM</uri>. You may use another "
+"manager at your option, but SLiM works well for Fluxbox, as well as any "
+"other environments you may have installed such as GNOME, KDE, or Xfce."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):209
+msgid "Login Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):209
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge slim</i>\n"
+"# <i>rc-update add xdm default</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(impo):214
+msgid ""
+"Be sure to emerge <c>slim</c> and add <b>xdm</b> to the bootscript, and not "
+"the other way around! Switching these will cause failure. We will also need "
+"to modify one system-wide config file:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):220
+msgid "Editing /etc/conf.d/xdm"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):220
+#, no-wrap
+msgid ""
+"\n"
+"DISPLAYMANAGER=\"slim\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):227
+msgid "Themes and Artwork"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):230
+msgid ""
+"This section can be skipped if one truly wants a minimal footprint. However, "
+"it is nice to allow users to customize their WM's appearance. Themes "
+"specific to Fluxbox, Gentoo artwork for any WM, and themes that can be used "
+"on any *box WM will be installed."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):237
+msgid "Installing styles and artwork"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):237
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge commonbox-styles commonbox-styles-extra \\\n"
+" fluxbox-styles-fluxmod gentoo-artwork</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):245
+msgid "Running Fluxbox for the first time"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):248
+msgid ""
+"Now you are ready to run Fluxbox for the first time. It will create a "
+"directory called <path>~/.fluxbox/</path> in your home directory, which is "
+"where Fluxbox stores all its settings, and populate it with some default "
+"values."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):254
+msgid "Starting Fluxbox from the console"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):254
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>startx</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):258
+msgid ""
+"If you've installed SLiM or another display manager, start it by becoming "
+"root and running:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):263
+msgid "Starting the display manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):263
+#, no-wrap
+msgid ""
+"\n"
+"# <i>/etc/init.d/xdm start</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):267
+msgid "Then choose Fluxbox as your session and login with your regular user."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):271
+msgid ""
+"Once Fluxbox is running, it will look pretty plain. You should see a blank "
+"desktop with a toolbar at the bottom. You can then right-click anywhere on "
+"your desktop to bring up the menu. From there you should be able to start up "
+"any X applications you would like to run, or open up a terminal from which "
+"you can run anything you like."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):282
+msgid "Fluxbox Keys"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):285
+msgid ""
+"Fluxbox comes with a very weak set of default keysets. It enables a user to "
+"switch windows and desktops, and no more. Before changing it, there are a "
+"few things necessary to know. In the Fluxbox keys file, there are some "
+"strange modifiers. Mod1 is commonly known as the \"Alt\" key, and Mod4 is "
+"the unspeakable (windows) key. Control and Shift are Control and Shift. "
+"However, it is usually best to use Alt/Windows keys because other X11 "
+"programs tend to use Control and Shift for their own shortcuts."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):295
+msgid ""
+"All of these are independent, so feel free to leave out anything not "
+"desired, or modify this to your own needs. This guide uses what the author "
+"assumes to be the most common programs, so also substitute the name of the "
+"package used if it differs from what appears here. For more information, "
+"read the man page for Fluxbox."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):303
+msgid ""
+"So, with that out of the way, fire up a text editor (non-root user), point "
+"it to <path>~/.fluxbox/keys</path>, and lets upgrade those shortcuts!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):308
+msgid "Modifying Keyboard Shortcuts"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):308
+#, no-wrap
+msgid ""
+"\n"
+"<comment># locks X11 display to the current user</comment>\n"
+"Mod4 l :ExecCommand xlock\n"
+"\n"
+"<comment># opens a number of programs with quickkeys. These are just examples, I am sure\n"
+"# you get the point...</comment>\n"
+"Mod1 f :ExecCommand firefox\n"
+"Mod1 t :ExecCommand thunderbird\n"
+"Mod1 o :ExecCommand oowriter\n"
+"Mod1 v :ExecCommand gvim\n"
+"\n"
+"<comment># Fluxbox has no sound control, so we need to do a hack to get one\n"
+"# (assumes alsa usage. if you use oss, then you are on your own)</comment>\n"
+"Mod1 e :ExecCommand Eterm -name alsa -e alsamixer\n"
+"\n"
+"<comment># This launches fbrun, which in turn launches other programs</comment>\n"
+"Mod1 r :ExecCommand fbrun\n"
+"\n"
+"<comment># Program Control. It just makes life simpler...</comment>\n"
+"Mod1 4 :Close\n"
+"Mod1 m :Minimize\n"
+"\n"
+"<comment># if you have aterm (emerge x11-terms/aterm), then this opens a really nice\n"
+"# transparent aterm with no borders, fitting nicely with 1024x768\n"
+"# resolution, while still leaving room for conky. Once again, feel free to\n"
+"# modify.</comment>\n"
+"Mod1 a :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg \\\n"
+"white -fade 90 -bl -tn xterm -fn \\\n"
+"-misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 -g 116x57\n"
+"\n"
+"<comment># similar to the above, but opens a transparent rooted terminal. you must, of\n"
+"# course, know the root password to use this</comment>\n"
+"Mod1 s :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg \\\n"
+"white -fade 90 -bl -tn xterm -fn \\\n"
+"-misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 -g 116x57 -e su -\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):348
+msgid "System Monitor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):351
+msgid ""
+"It is a common desire to setup a system monitor for X11 on desktop systems. "
+"Gkrellm is a commonly used monitor, but in the spirit of Fluxbox minimalism, "
+"we are going to use a simpler monitor: <c>conky</c>. If desired, use another "
+"monitor; there are plenty of HOWTOs elsewhere."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):358
+msgid "Installing conky"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):358
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge conky</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):362
+msgid ""
+"The default config file for Conky is rather weak, but more info can be found "
+"by reading the manpage or the <uri link=\"/doc/en/conky-howto.xml\">Gentoo "
+"Linux Conky Howto</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):371
+msgid "Icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):374
+msgid ""
+"Fluxbox does not come with a utility or program to draw icons to the "
+"desktop; everything is handled by keyboard shortcuts, or the right-click "
+"menu. iDesk is a program that can be used to fulfill this need. It is aimed "
+"at users of minimal WMs like ourselves who want to display icons in the root "
+"window, and it even supports funky graphic effects like transparency! "
+"Despite its name, iDesk is not affiliated with Apple or Mac (to the best of "
+"the author's knowledge). Installing iDesk is as simple as:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):384
+msgid "Installing idesk"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):384
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge idesk</i>\n"
+msgstr ""
+
+#. if someone wants to write a better description of idesk, feel free. it would be
+#. appreciated!
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):393
+msgid ""
+"Once installed, it will be necessary to configure iDesk so that it is able "
+"to display the icons we desire. Its configuration file can be found at "
+"<path>~/.ideskrc</path>. This is a rather lengthy task, and can't be well "
+"covered in this guide. The following resources might be useful in order to "
+"help you configure iDesk: <c>man idesk</c>, <uri link=\"http://idesk."
+"sourceforge.net/wiki/index.php/Idesk-usage\">iDesk's Usage Guide</uri> and "
+"this <uri link=\"http://forums.gentoo.org/viewtopic-t-87262.html\">thread in "
+"the Gentoo Forums</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):408
+msgid "Graphical File Manager Options"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):411
+msgid ""
+"It is important to note that Gentoo does not need a file manager. It is "
+"perfectly possible, and indeed simpler (in the author's humble opinion), to "
+"do all the file manipulation by command-line. However, not everyone agrees..."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):417
+msgid ""
+"Many users who are new to Gentoo/Fluxbox are put off by the lack of a "
+"graphical file manager such as <c>nautilus</c> in Gnome. Fluxbox itself does "
+"not provide such a program, but as always, it is simple to acquire one. "
+"There are many choices, but this guide will present three, one for the <uri "
+"link=\"#gentoo\">minimalist</uri> who likes text only and two for the user "
+"who likes <uri link=\"#rox\">icons</uri> to <uri link=\"#thunar\">click</"
+"uri>. It is also possible, of course, to install all three and try them out."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):430
+msgid "Gentoo File Manager - Minimalism"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):433
+msgid ""
+"Gentoo is a file manager which seeks to provide the benefits of a GUI "
+"interface without all the bloat which is commonly associated with such "
+"interfaces."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):438
+msgid "Installing the Gentoo File Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):438
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gentoo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(note):442
+msgid ""
+"The Gentoo file manager is a separate project from the Gentoo Linux "
+"distribution. For more information on this, see the Gentoo <uri link=\"/main/"
+"en/name-logo.xml#doc_chap4\">Name and Logo Usage Guidelines</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):448
+msgid ""
+"The Gentoo file manager aims to be fully configurably via GUI, so feel free "
+"to tweak."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):457
+msgid "Rox File Manager - Includes Icons"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):460
+msgid ""
+"Rox is a file manager which uses icons as well as text and is much more like "
+"Windows' Explorer."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):465
+msgid "Installing the Rox File Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):465
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge rox</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):469
+msgid ""
+"Rox behaves much like \"traditional\" file managers, so its interface should "
+"be intuitive. If not, there always are manpages."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):477
+msgid "Thunar File Manager"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):480
+msgid ""
+"<uri link=\"http://thunar.xfce.org/\">Thunar</uri> is a lightweight, fast "
+"file manager that, like Rox, behaves much like \"traditional\" file "
+"managers. It includes icons and text, and it's easy to use. Though "
+"originally designed for <uri link=\"http://www.xfce.org\">Xfce</uri>, it's a "
+"nice complement to a Fluxbox-based system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):488
+msgid "Installing Thunar"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):488
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -avt thunar</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):495
+msgid "Picture Viewer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):498
+msgid ""
+"Many WMs come with utilities to view pictures in a directory. These "
+"applications are small and lightweight, and do not allow for editing (which "
+"is assumed to be done by the <c>gimp</c> or similar). This is necessary if "
+"you use a command line, <c>gentoo</c>, or <c>rox</c> for a file manager. "
+"Though <c>thunar</c> can display image thumbnails, a separate lightweight "
+"image viewer is still a good idea."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):507
+msgid "Installing gqview"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):507
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge gqview</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):511
+msgid ""
+"<c>gqview</c> can be launched in any directory, and can browse through any "
+"supported picture format."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):519
+msgid "Setting a theme, background, and a startup script"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):522
+msgid ""
+"Fluxbox has a number of themes that can be accessed by the right click menu, "
+"then \"Fluxbox menu,\" and \"System Styles.\" These themes usually set their "
+"own background, which is either a single color or a gradient of some type. "
+"Most people prefer to set their own background, and keep it no matter what "
+"theme they chose. To do so, we need to edit another of Fluxbox's files, "
+"which governs startup behavior. So fire up that text editor again, and point "
+"it to <path>~/.fluxbox/startup</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):532
+msgid ""
+"If this file exists, then clear it. Add the following to the newly created "
+"file, uncommenting as needed, and filling in values for the CAPS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):537
+msgid "Editing Startup scripts for Fluxbox"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):537
+#, no-wrap
+msgid ""
+"\n"
+"<comment># Gentoo's Fluxbox startup script\n"
+"\n"
+"# Programs which need to run constantly, as opposed to a one time execution,\n"
+"# need \"&amp;\" at the end of the command.\n"
+"\n"
+"# Show the Fluxbox splash-screen\n"
+"#fbsetbg -C /usr/share/fluxbox/splash.jpg\n"
+"\n"
+"# This sets a background. You must have a program setup to do this\n"
+"# (x11-terms/eterm is recommended)\n"
+"#fbsetbg -f PATH_TO_IMAGE\n"
+"\n"
+"# Custom fonts directory\n"
+"#xset +fp PATH_TO_FONT_DIRECTORY\n"
+"\n"
+"# Starts the icons program\n"
+"#idesk &amp;\n"
+"\n"
+"# This MUST be the last command!</comment>\n"
+"exec /usr/bin/fluxbox -log ~/.fluxbox/log\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):563
+msgid "Menu generation"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):566
+msgid ""
+"The author uses a text editor to create menus. If this sounds appealing to "
+"you, please skip this section and proceed to <uri link=\"#manual_menu"
+"\">editing menus by hand</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):572
+msgid ""
+"It is possible to edit <path>~/.fluxbox/menu</path> by hand after using an "
+"automatic generator (see next section), to either add packages or delete "
+"those which aren't used. Note that if something is deleted from this menu, "
+"it does not delete the package from the system, just from the individual "
+"user's menu. The program can still be run by command-line."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):580
+msgid ""
+"There is a program already on your system called <c>fluxbox-generate_menu</"
+"c>, which can be used to generate menus. To run it (as a non-root user):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):585
+msgid "Generating menus"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):585
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>fluxbox-generate_menu -is -ds</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):589
+msgid ""
+"It is recommended that you use <c>fluxbox-generate_menu -is -ds</c> instead "
+"of other programs, which do not understand Gentoo's directory structure."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):594
+msgid ""
+"This can also be done from the Fluxbox menu itself. There is usually an "
+"entry in the \"Fluxbox\" menu called \"Regen Menu\" which will re-run this "
+"script, looking for any new applications that have been installed since the "
+"last time you ran it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(note):601
+msgid ""
+"It is possible to use this method to auto-generate menus and still have some "
+"manual control over your menu. Creating and editing <path>~/.fluxbox/"
+"usermenu</path> by hand (see the next section for syntax) will give a user a "
+"personalized menu which will not be erased the next time the script is run."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):612
+msgid "Editing Menus by Hand"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):615
+msgid ""
+"Fluxbox's menu is a text file that follows a quite simple syntax, described "
+"in this section. The default menu definition is present in the <path>~/."
+"fluxbox/menu</path> file."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):621
+msgid ""
+"Menu entries for executing applications are defined by the <c>[exec]</c> "
+"element. You can define an entry, either under the <c>[begin]</c> definition "
+"(the menu root), or between a <c>[submenu]</c> and its corresponding <c>[end]"
+"</c> line (submenu definitions), for example:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre:caption):628
+msgid "Defining new menu entries"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(pre):628
+#, no-wrap
+msgid ""
+"\n"
+"# Custom fluxbox menu\n"
+"[begin] (Fluxbox)\n"
+" <comment>(...)</comment>\n"
+" [exec] (XTerm White on Black) {xterm -ls -fg white -bg black}\n"
+" <comment>(...)</comment>\n"
+" [submenu] (More terminals)\n"
+" [exec] (Aterm default) {aterm}\n"
+" [exec] (Rxvt default) {rxvt}\n"
+" [end]\n"
+" <comment>(...)</comment>\n"
+"[end]\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):642
+msgid ""
+"The root menu definition begins with the <c>[begin]</c> tag, followed by its "
+"name, between parentheses and ends with its corresponding <c>[end]</c> tag. "
+"All the menu commands (called here, tags) are enclosed by square brackets, "
+"menu names will be enclosed between parentheses and the actual commands are "
+"enclosed between braces. Comments are allowed in this file, for lines "
+"beginning with <c>#</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):651
+msgid ""
+"In the example shown above, the first <c>[exec]</c> line defines a new entry "
+"named \"XTerm White on Black\", which will execute the <c>xterm -ls -fg "
+"white -bg black</c> as if from a command line. Next is a submenu which is "
+"defined using the <c>[submenu]</c> tag, and after that a section called "
+"\"More terminals\", with two more <c>[exec]</c> commands. Any submenu "
+"definition must have its corresponding <c>[end]</c> tag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):660
+msgid ""
+"There are other menu commands that you can use in your <path>~/.fluxbox/"
+"menu</path> file. Please read the <uri link=\"http://fluxbox.org/docbook.php"
+"\">official documentation</uri> available online for more information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):671
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(li):675
+msgid "The <uri link=\"http://fluxbox-wiki.org\">Fluxbox wiki</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(li):676
+msgid "Fluxbox developers and users in #fluxbox on irc.freenode.net"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(title):682
+msgid "Summary"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(p):685
+msgid ""
+"Congratulations! Fluxbox is now installed, configured, and ready to go. If "
+"any questions or suggestions come to mind, please email the author and/or "
+"file a bug report at Gentoo's <uri link=\"http://bugs.gentoo.org\">Bugzilla</"
+"uri>."
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//fluxbox-config.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/gcc-optimization.xml.po b/doc/gettext/el/gcc-optimization.xml.po
new file mode 100644
index 0000000..9a05ee2
--- /dev/null
+++ b/doc/gettext/el/gcc-optimization.xml.po
@@ -0,0 +1,724 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):6
+msgid "Compilation Optimization Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(mail:link):9
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(abstract):12
+msgid ""
+"This guide provides an introduction to optimizing compiled code using safe, "
+"sane CFLAGS and CXXFLAGS. It also as describes the theory behind optimizing "
+"in general."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(version):22
+msgid "2"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(date):23
+msgid "2010-07-26"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):26
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):28
+msgid "What are CFLAGS and CXXFLAGS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):31
+msgid ""
+"CFLAGS and CXXFLAGS are environment variables that are used to tell the GNU "
+"Compiler Collection, <c>gcc</c>, what kinds of switches to use when "
+"compiling source code. CFLAGS are for code written in C, while CXXFLAGS are "
+"for code written in C++."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):38
+msgid ""
+"They can be used to decrease the amount of debug messages for a program, "
+"increase error warning levels, and, of course, to optimize the code "
+"produced. The <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/"
+"Invoking-GCC.html#Invoking-GCC\">GNU gcc handbook</uri> maintains a complete "
+"list of available options and their purposes."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):50
+msgid "How are they used?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):53
+msgid ""
+"CFLAGS and CXXFLAGS can be used in two ways. First, they can be used per-"
+"program with Makefiles generated by automake."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):58
+msgid ""
+"However, this should not be done when installing packages found in the "
+"Portage tree. Instead, set your CFLAGS and CXXFLAGS in <path>/etc/make.conf</"
+"path>. This way all packages will be compiled using the options you specify."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):64
+msgid "CFLAGS in /etc/make.conf"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):64
+#, no-wrap
+msgid ""
+"\n"
+"CFLAGS=\"-march=athlon64 -O2 -pipe\"\n"
+"CXXFLAGS=\"${CFLAGS}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):69
+msgid ""
+"As you can see, CXXFLAGS is set to use all the options present in CFLAGS. "
+"This is what you'll want almost without fail. You shouldn't ever need to "
+"specify additional options in CXXFLAGS."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):78
+msgid "Misconceptions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):81
+msgid ""
+"While CFLAGS and CXXFLAGS can be very effective means of getting source code "
+"to produce smaller and/or faster binaries, they can also impair the function "
+"of your code, bloat its size, slow down its execution time, or even cause "
+"compilation failures!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):88
+msgid ""
+"CFLAGS are not a magic bullet; they will not automatically make your system "
+"run any faster or your binaries to take up less space on disk. Adding more "
+"and more flags in an attempt to optimize (or \"rice\") your system is a sure "
+"recipe for failure. There is a point at which you will reach diminishing "
+"returns."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):95
+msgid ""
+"Despite the bragging you'll find on the internet, aggressive CFLAGS and "
+"CXXFLAGS are far more likely to harm your programs than do them any good. "
+"Keep in mind that the reason the flags exist in the first place is because "
+"they are designed to be used at specific places for specific purposes. Just "
+"because one particular CFLAG is good for one bit of code doesn't mean that "
+"it is suited to compiling everything you will ever install on your machine!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):107
+msgid "Ready?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):110
+msgid ""
+"Now that you're aware of some of the risks involved, let's take a look at "
+"some sane, safe optimizations for your computer. These will hold you in good "
+"stead and will endear you to developers the next time you report a problem "
+"on <uri link=\"http://bugs.gentoo.org\">Bugzilla</uri>. (Developers will "
+"usually request that you recompile a package with minimal CFLAGS to see if "
+"the problem persists. Remember, aggressive flags can ruin code.)"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):124
+msgid "Optimizing"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):126
+msgid "The basics"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):129
+msgid ""
+"The goal behind using CFLAGS and CXXFLAGS is to create code tailor-made to "
+"your system; it should function perfectly while being lean and fast, if "
+"possible. Sometimes these conditions are mutually exclusive, so we'll stick "
+"with combinations known to work well. Ideally, they are the best available "
+"for any CPU architecture. We'll mention the aggressive flags later so you "
+"know what to look out for. We won't discuss every option listed on the "
+"<c>gcc</c> manual (there are hundreds), but we'll cover the basic, most "
+"common flags."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(note):139
+msgid ""
+"Whenever you're not sure what a flag actually does, refer to the relevant "
+"chapter of the <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/"
+"Optimize-Options.html#Optimize-Options\">gcc manual</uri>. If you're still "
+"stumped, try Google, or check out the <c>gcc</c><uri link=\"http://gcc.gnu."
+"org/lists.html\">mailing lists</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):150
+msgid "-march"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):153
+msgid ""
+"The first and most important option is <c>-march</c>. This tells the "
+"compiler what code it should produce for your processor <uri link=\"http://"
+"en.wikipedia.org/wiki/Microarchitecture\">architecture</uri> (or <e>arch</"
+"e>); it says that it should produce code for a certain kind of CPU. "
+"Different CPUs have different capabilities, support different instruction "
+"sets, and have different ways of executing code. The <c>-march</c> flag will "
+"instruct the compiler to produce code specifically for your CPU, with all "
+"its capabilities, features, instruction sets, quirks, and so on."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):164
+msgid ""
+"Even though the CHOST variable in <path>/etc/make.conf</path> specifies the "
+"general architecture used, <c>-march</c> should still be used so that "
+"programs can be optimized for your specific processor. x86 and x86-64 CPUs "
+"(among others) should make use of the <c>-march</c> flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):171
+msgid "What kind of CPU do you have? To find out, run the following command:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):175
+msgid "Examining CPU information"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):175
+#, no-wrap
+msgid ""
+"\n"
+"$ <i>cat /proc/cpuinfo</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):179
+msgid ""
+"Now let's see <c>-march</c> in action. This example is for an older Pentium "
+"III chip:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):184
+msgid "/etc/make.conf: Pentium III"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):184
+#, no-wrap
+msgid ""
+"\n"
+"CFLAGS=\"-march=pentium3\"\n"
+"CXXFLAGS=\"${CFLAGS}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):189
+msgid "Here's another one for a 64-bit AMD CPU:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):193
+msgid "/etc/make.conf: AMD64"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):193
+#, no-wrap
+msgid ""
+"\n"
+"CFLAGS=\"-march=athlon64\"\n"
+"CXXFLAGS=\"${CFLAGS}\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):198
+msgid ""
+"If you still aren't sure what kind of CPU you have, you may just want to use "
+"<c>-march=native</c>. When this flag is used, GCC will detect your processor "
+"and automatically set appropriate flags for it. <brite>However, this should "
+"not be used if you intend to compile packages for a different CPU!</brite>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):205
+msgid ""
+"So if you're compiling packages on one computer, but intend to run them on a "
+"different computer (such as when using a fast computer to build for an "
+"older, slower machine), then <e>do not</e> use <c>-march=native</c>. \"Native"
+"\" means that the code produced will run <e>only</e> on that type of CPU. "
+"The applications built with <c>-march=native</c> on an AMD Athlon 64 CPU "
+"will not be able to run on an old VIA C3 CPU."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):214
+msgid ""
+"Also available are the <c>-mtune</c> and <c>-mcpu</c> flags. These flags are "
+"normally only used when there is no available <c>-march</c> option; certain "
+"processor architectures may require <c>-mtune</c> or even <c>-mcpu</c>. "
+"Unfortunately, <c>gcc</c>'s behavior isn't very consistent with how each "
+"flag behaves from one architecture to the next."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):222
+msgid ""
+"On x86 and x86-64 CPUs, <c>-march</c> will generate code specifically for "
+"that CPU using all its available instruction sets and the correct ABI; it "
+"will have no backwards compatibility for older/different CPUs. If you don't "
+"need to execute code on anything other than the system you're running Gentoo "
+"on, continue to use <c>-march</c>. You should only consider using <c>-mtune</"
+"c> when you need to generate code for older CPUs such as i386 and i486. <c>-"
+"mtune</c> produces more generic code than <c>-march</c>; though it will tune "
+"code for a certain CPU, it doesn't take into account available instruction "
+"sets and ABI. Don't use <c>-mcpu</c> on x86 or x86-64 systems, as it is "
+"deprecated for those arches."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):235
+msgid ""
+"Only non-x86/x86-64 CPUs (such as Sparc, Alpha, and PowerPC) may require <c>-"
+"mtune</c> or <c>-mcpu</c> instead of <c>-march</c>. On these architectures, "
+"<c>-mtune</c>/<c>-mcpu</c> will sometimes behave just like <c>-march</c> (on "
+"x86/x86-64) . . . but with a different flag name. Again, <c>gcc</c>'s "
+"behavior and flag naming just isn't consistent across architectures, so be "
+"sure to check the <c>gcc</c><uri link=\"http://gcc.gnu.org/onlinedocs/"
+"gcc-4.4.4/gcc/Submodel-Options.html#Submodel-Options\">manual</uri> to "
+"determine which one you should use for your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(note):246
+msgid ""
+"For more suggested <c>-march</c>/<c>-mtune</c>/<c>-mcpu</c> settings, please "
+"read chapter 5 of the appropriate <uri link=\"/doc/en/handbook/\">Gentoo "
+"Installation Handbook</uri> for your arch. Also, read the <c>gcc</c> "
+"manual's list of <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/"
+"Submodel-Options.html#Submodel-Options\">architecture-specific options</"
+"uri>, as well as more detailed explanations about the differences between "
+"<c>-march</c>, <c>-mcpu</c>, and <c>-mtune</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):259
+msgid "-O"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):262
+msgid ""
+"Next up is the <c>-O</c> variable. This controls the overall level of "
+"optimization. This makes the code compilation take somewhat more time, and "
+"can take up much more memory, especially as you increase the level of "
+"optimization."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):268
+msgid ""
+"There are five <c>-O</c> settings: <c>-O0</c>, <c>-O1</c>, <c>-O2</c>, <c>-"
+"O3</c>, and <c>-Os</c>. You should use only one of them in <path>/etc/make."
+"conf</path>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):274
+msgid ""
+"With the exception of <c>-O0</c>, the <c>-O</c> settings each activate "
+"several additional flags, so be sure to read the gcc manual's chapter on "
+"<uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Optimize-Options."
+"html#Optimize-Options\">optimization options</uri> to learn which flags are "
+"activated at each <c>-O</c> level, as well as some explanations as to what "
+"they do."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):282
+msgid "Let's examine each optimization level:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):287
+msgid ""
+"<c>-O0</c>: This level (that's the letter \"O\" followed by a zero) turns "
+"off optimization entirely and is the default if no <c>-O</c> level is "
+"specified in CFLAGS or CXXFLAGS. Your code will not be optimized; it's not "
+"normally desired."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):293
+msgid ""
+"<c>-O1</c>: This is the most basic optimization level. The compiler will try "
+"to produce faster, smaller code without taking much compilation time. It's "
+"pretty basic, but it should get the job done all the time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):298
+msgid ""
+"<c>-O2</c>: A step up from <c>-O1</c>. This is the <e>recommended</e> level "
+"of optimization unless you have special needs. <c>-O2</c> will activate a "
+"few more flags in addition to the ones activated by <c>-O1</c>. With <c>-O2</"
+"c>, the compiler will attempt to increase code performance without "
+"compromising on size, and without taking too much compilation time."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):305
+msgid ""
+"<c>-O3</c>: This is the highest level of optimization possible, and also the "
+"riskiest. It will take a longer time to compile your code with this option, "
+"and in fact it <e>should not be used system-wide with <c>gcc</c> 4.x</e>. "
+"The behavior of <c>gcc</c> has changed significantly since version 3.x. In 3."
+"x, <c>-O3</c> has been shown to lead to marginally faster execution times "
+"over <c>-O2</c>, but this is no longer the case with <c>gcc</c> 4.x. "
+"Compiling all your packages with <c>-O3</c><e>will</e> result in larger "
+"binaries that require more memory, and will significantly increase the odds "
+"of compilation failure or unexpected program behavior (including errors). "
+"The downsides outweigh the benefits; remember the principle of diminishing "
+"returns. <b>Using <c>-O3</c> is not recommended for <c>gcc</c> 4.x.</b>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):318
+msgid ""
+"<c>-Os</c>: This level will optimize your code for size. It activates all "
+"<c>-O2</c> options that don't increase the size of the generated code. It "
+"can be useful for machines that have extremely limited disk storage space "
+"and/or have CPUs with small cache sizes. However, it can cause quite a few "
+"problems, which is why it is filtered out by many of the ebuilds in the "
+"tree. Using <c>-Os</c> is not recommended."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):328
+msgid ""
+"As previously mentioned, <c>-O2</c> is the recommended optimization level. "
+"If package compilations error out, check to make sure that you aren't using "
+"<c>-O3</c>. As a fallback option, try setting your CFLAGS and CXXFLAGS to a "
+"lower optimization level, such as <c>-O1</c> or even <c>-O0 -g2 -ggdb</c> "
+"(for error reporting and checking for possible problems) and recompile the "
+"package."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):339
+msgid "-pipe"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):342
+msgid ""
+"A common flag is <c>-pipe</c>. This flag actually has no effect on the "
+"generated code, but it makes the compilation process faster. It tells the "
+"compiler to use pipes instead of temporary files during the different stages "
+"of compilation, which uses more memory. On systems with low memory, gcc "
+"might get killed. In that case, do not use this flag."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):353
+msgid "-fomit-frame-pointer"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):356
+msgid ""
+"This is a very common flag designed to reduce generated code size. It is "
+"turned on at all levels of <c>-O</c> (except <c>-O0</c>) on architectures "
+"where doing so does not interfere with debugging (such as x86-64), but you "
+"may need to activate it yourself by adding it to your flags. Though the GNU "
+"<c>gcc</c> manual does not specify all architectures it is turned on by "
+"using <c>-O</c>, you will need to explicitly activate it on x86. However, "
+"using this flag will make debugging hard to impossible."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):366
+msgid ""
+"In particular, it makes troubleshooting applications written in Java much "
+"harder, though Java is not the only code affected by using this flag. So "
+"while the flag can help, it also makes debugging harder; backtraces in "
+"particular will be useless. However, if you don't plan to do much software "
+"debugging and haven't added any other debugging-related CFLAGS such as <c>-"
+"ggdb</c>, then you can try using <c>-fomit-frame-pointer</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(impo):375
+msgid ""
+"Do <e>not</e> combine <c>-fomit-frame-pointer</c> with the similar flag <c>-"
+"momit-leaf-frame-pointer</c>. Using the latter flag is discouraged, as <c>-"
+"fomit-frame-pointer</c> already does the job properly. Furthermore, <c>-"
+"momit-leaf-frame-pointer</c> has been shown to negatively impact code "
+"performance."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):390
+msgid "-msse, -msse2, -msse3, -mmmx, -m3dnow"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):393
+msgid ""
+"These flags enable the <uri link=\"http://en.wikipedia.org/wiki/"
+"Streaming_SIMD_Extensions\">SSE</uri>, <uri link=\"http://en.wikipedia.org/"
+"wiki/SSE2\">SSE2</uri>, <uri link=\"http://en.wikipedia.org/wiki/"
+"SSSE3\">SSE3</uri>, <uri link=\"http://en.wikipedia.org/wiki/MMX\">MMX</"
+"uri>, and <uri link=\"http://en.wikipedia.org/wiki/3dnow\">3DNow!</uri> "
+"instruction sets for x86 and x86-64 architectures. These are useful "
+"primarily in multimedia, gaming, and other floating point-intensive "
+"computing tasks, though they also contain several other mathematical "
+"enhancements. These instruction sets are found in more modern CPUs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(impo):406
+msgid ""
+"Be sure to check if your CPU supports these by running <c>cat /proc/cpuinfo</"
+"c>. The output will include any supported additional instruction sets. Note "
+"that <b>pni</b> is just a different name for SSE3."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):412
+msgid ""
+"You normally don't need to add any of these flags to <path>/etc/make.conf</"
+"path> as long as you are using the correct <c>-march</c> (for example, <c>-"
+"march=nocona</c> implies <c>-msse3</c>). Some notable exceptions are newer "
+"VIA and AMD64 CPUs that support instructions not implied by <c>-march</c> "
+"(such as SSE3). For CPUs like these you'll need to enable additional flags "
+"where appropriate after checking the output of <c>cat /proc/cpuinfo</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(note):421
+msgid ""
+"You should check the <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/"
+"i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options\">list</uri> of "
+"x86 and x86-64-specific flags to see which of these instruction sets are "
+"activated by the proper CPU type flag. If an instruction is listed, then you "
+"don't need to specify it; it will be turned on by using the proper <c>-"
+"march</c> setting."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):435
+msgid "Optimization FAQs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):437
+msgid "But I get better performance with -funroll-loops -fomg-optimize!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):440
+msgid ""
+"No, you only <e>think</e> you do because someone has convinced you that more "
+"flags are better. Aggressive flags will only hurt your applications when "
+"used system-wide. Even the <c>gcc</c><uri link=\"http://gcc.gnu.org/"
+"onlinedocs/gcc-4.4.4/gcc/Optimize-Options.html#Optimize-Options\">manual</"
+"uri> says that using <c>-funroll-loops</c> and <c>-funroll-all-loops</c> "
+"makes code larger and run more slowly. Yet for some reason, these two flags, "
+"along with <c>-ffast-math</c>, <c>-fforce-mem</c>, <c>-fforce-addr</c>, and "
+"similar flags, continue to be very popular among ricers who want the biggest "
+"bragging rights."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):451
+msgid ""
+"The truth of the matter is that they are dangerously aggressive flags. Take "
+"a good look around the <uri link=\"http://forums.gentoo.org\">Gentoo Forums</"
+"uri> and <uri link=\"http://bugs.gentoo.org\">Bugzilla</uri> to see what "
+"those flags do: nothing good!"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):458
+msgid ""
+"You don't need to use those flags globally in CFLAGS or CXXFLAGS. They will "
+"only hurt performance. They may make you sound like you have a high-"
+"performance system running on the bleeding edge, but they don't do anything "
+"but bloat your code and get your bugs marked INVALID or WONTFIX."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):465
+msgid ""
+"You don't need dangerous flags like these. <b>Don't use them</b>. Stick to "
+"the basics: <c>-march</c>, <c>-O</c>, and <c>-pipe</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):473
+msgid "What about -O levels higher than 3?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):476
+msgid ""
+"Some users boast about even better performance obtained by using <c>-O4</c>, "
+"<c>-O9</c>, and so on, but the reality is that <c>-O</c> levels higher than "
+"3 have no effect. The compiler may accept CFLAGS like <c>-O4</c>, but it "
+"actually doesn't do anything with them. It only performs the optimizations "
+"for <c>-O3</c>, nothing more."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):484
+msgid ""
+"Need more proof? Examine the <c>gcc</c><uri link=\"http://gcc.gnu.org/"
+"viewcvs/trunk/gcc/opts.c?revision=124622&amp;view=markup\">source code</uri>:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):490
+msgid "-O source code"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):490
+#, no-wrap
+msgid ""
+"\n"
+"if (optimize &gt;= 3)\n"
+" {\n"
+" flag_inline_functions = 1;\n"
+" flag_unswitch_loops = 1;\n"
+" flag_gcse_after_reload = 1;\n"
+" /* Allow even more virtual operators. */\n"
+" set_param_value (\"max-aliased-vops\", 1000);\n"
+" set_param_value (\"avg-aliased-vops\", 3);\n"
+" }\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):502
+msgid "As you can see, any value higher than 3 is treated as just <c>-O3</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):509
+msgid "What about redundant flags?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):512
+msgid ""
+"Oftentimes CFLAGS and CXXFLAGS that are turned on at various <c>-O</c> "
+"levels are specified redundantly in <path>/etc/make.conf</path>. Sometimes "
+"this is done out of ignorance, but it is also done to avoid flag filtering "
+"or flag replacing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):518
+msgid ""
+"Flag filtering/replacing is done in many of the ebuilds in the Portage tree. "
+"It is usually done because packages fail to compile at certain <c>-O</c> "
+"levels, or when the source code is too sensitive for any additional flags to "
+"be used. The ebuild will either filter out some or all CFLAGS and CXXFLAGS, "
+"or it may replace <c>-O</c> with a different level."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):526
+msgid ""
+"The <uri link=\"http://devmanual.gentoo.org/ebuild-writing/functions/"
+"src_compile/build-environment/index.html\">Gentoo Developer Manual</uri> "
+"outlines where and how flag filtering/replacing works."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):532
+msgid ""
+"It's possible to circumvent <c>-O</c> filtering by redundantly listing the "
+"flags for a certain level, such as <c>-O3</c>, by doing things like:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre:caption):537
+msgid "Specifying redundant CFLAGS"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(pre):537
+#, no-wrap
+msgid ""
+"\n"
+"CFLAGS=\"-O3 -finline-functions -funswitch-loops\"\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):541
+msgid ""
+"However, <brite>this is not a smart thing to do</brite>. CFLAGS are filtered "
+"for a reason! When flags are filtered, it means that it is unsafe to build a "
+"package with those flags. Clearly, it is <e>not</e> safe to compile your "
+"whole system with <c>-O3</c> if some of the flags turned on by that level "
+"will cause problems with certain packages. Therefore, you shouldn't try to "
+"\"outsmart\" the developers who maintain those packages. <e>Trust the "
+"developers</e>. Flag filtering and replacing is done for your benefit! If an "
+"ebuild specifies alternative flags, then don't try to get around it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):552
+msgid ""
+"You will most likely continue to run into problems when you build a package "
+"with unacceptable flags. When you report your troubles on Bugzilla, the "
+"flags you use in <path>/etc/make.conf</path> will be readily visible and you "
+"will be told to recompile without those flags. Save yourself the trouble of "
+"recompiling by not using redundant flags in the first place! Don't just "
+"automatically assume that you know better than the developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):564
+msgid "What about LDFLAGS?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):567
+msgid ""
+"The Gentoo developers have already set basic, safe LDFLAGS in the base "
+"profiles, so you don't need to change them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):575
+msgid "Can I use per-package flags?"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):578
+msgid ""
+"There is no supported method for using CFLAGS or other variables on a per-"
+"package basis, though there are a few <uri link=\"http://forums.gentoo.org/"
+"viewtopic-p-3832057.html#3832057\">rather abusive</uri> ways of trying force "
+"Portage to do so."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(warn):585
+msgid ""
+"You <e>should not</e> try to force Portage to use per-package flags, as it "
+"is not in any way supported and will greatly complicate bug reports. Just "
+"set your flags in <path>/etc/make.conf</path> to be used on a system-wide "
+"basis."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(title):596
+msgid "Resources"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(p):600
+msgid ""
+"The following resources are of some help in further understanding "
+"optimization:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):605
+msgid ""
+"The <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/\">GNU gcc "
+"manual</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):609
+msgid ""
+"Chapter 5 of the <uri link=\"/doc/en/handbook/\">Gentoo Installation "
+"Handbooks</uri>"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(uri:link):614
+msgid "http://en.wikipedia.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(uri):614
+msgid "Wikipedia"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):615
+msgid ""
+"<uri link=\"http://www.coyotegulch.com/products/acovea/\">Acovea</uri>, a "
+"benchmarking and test suite that can be useful for determining how different "
+"compiler flags interact and affect generated code, though its code "
+"suggestions are not appropriate for system-wide use. It is available in "
+"Portage: <c>emerge acovea</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(li):622
+msgid "The <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri>"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gcc-optimization.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/gcc-upgrading.xml.po b/doc/gettext/el/gcc-upgrading.xml.po
new file mode 100644
index 0000000..761d3f9
--- /dev/null
+++ b/doc/gettext/el/gcc-upgrading.xml.po
@@ -0,0 +1,637 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2010-10-21 23:56+0600\n"
+"PO-Revision-Date: 2010-10-21 23:56+0600\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(guide:link):6
+msgid "/doc/en/gcc-upgrading.xml"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):7
+msgid "Gentoo GCC Upgrade Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):12
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):10
+msgid "amne@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):10
+msgid "Wernfried Haas"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):13
+msgid "jkt@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):13
+msgid "Jan Kundrát"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):15
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):18
+msgid "Editor"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):16
+msgid "halcy0n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):19
+msgid "nightmorph"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):22
+msgid "This document will guide the user through the process of upgrading GCC."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):30
+msgid "23"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):31
+msgid "2008-07-19"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):34
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):80
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):167
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):333
+msgid "Introduction"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):36
+msgid "GCC Upgrading"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):39
+msgid ""
+"Why should you upgrade? Well, GCC is quite similar to any other package on "
+"your system, just a bit more critical. You should upgrade GCC whenever a new "
+"version fixes some bug that annoys you, new functionality you need is "
+"introduced, or if you want to keep your system up-to-date. If none of the "
+"previous cases apply to you, you can safely postpone upgrade as long as your "
+"GCC version is supported by Gentoo developers."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48
+msgid ""
+"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the "
+"system will not switch over to use it automatically. You'll have to "
+"explicitly request the change because the migration process might require "
+"some additional steps. If you decide not to switch, Portage will continue to "
+"use older version of your compiler until you change your mind, or remove the "
+"old compiler from the system. Non-major gcc upgrades are switched "
+"automatically for you (such as 3.4.5 to 3.4.6)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):58
+msgid ""
+"This guide will document the necessary steps required to perform a seamless "
+"upgrade of the compiler used by your Gentoo box. A specific section is "
+"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to "
+"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for "
+"users <uri link=\"#first-install\">first installing</uri> Gentoo using a "
+"stage3 tarball, after a new GCC major/minor version has been released."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(warn):67
+msgid ""
+"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or "
+"greater still requires you to follow the <uri link=\"#upgrade-general"
+"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly "
+"different ABIs."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):78
+msgid "General Upgrade Instructions"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):83
+msgid ""
+"If you're looking for instructions specific to upgrades from GCC-3.3 to "
+"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated "
+"section</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):89
+msgid ""
+"If you're looking for instructions specific to upgrades in GCC for new "
+"installs, please consult the <uri link=\"#first-install\">dedicated section</"
+"uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):95
+msgid ""
+"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to "
+"3.3.6, should be quite safe -- just emerge new version, switch your system "
+"to use it and rebuild the only affected package, <c>libtool</c>. However, "
+"some GCC upgrades break binary compatibility; in such cases a rebuild of the "
+"affected packages (or even whole toolchain and system) might be required."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):103
+msgid ""
+"When we spoke about the need to switch your compiler to the newer version by "
+"hand, we said it won't happen automatically. However, there is one exception "
+"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't "
+"use the \"multislot\" feature allowing them to coexist on one system. "
+"Multislot is disabled by default as the majority of users won't benefit from "
+"it."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):111
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):278
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):366
+msgid "Upgrading GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):111
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -uav gcc</i>\n"
+"\n"
+"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n"
+"version and CHOST settings you've upgraded to:)</comment>\n"
+"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n"
+"# <i>env-update &amp;&amp; source /etc/profile</i>\n"
+"\n"
+"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n"
+"example) you will have to run fix_libtool_files.sh manually</comment>\n"
+"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n"
+"<comment>(Replace &lt;gcc-version&gt; with your new, updated GCC version)</comment>\n"
+"# <i>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh 3.4.6</i>\n"
+"\n"
+"<comment>(Rebuilding libtool)</comment>\n"
+"# <i>emerge --oneshot -av libtool</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):129
+msgid ""
+"To be completely safe that your system is in a sane state, you <e>must</e> "
+"rebuild the toolchain and then world to make use of the new compiler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):134
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):433
+msgid "Rebuilding system"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):134
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -eav system</i>\n"
+"# <i>emerge -eav world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139
+msgid ""
+"It is safe to remove the older GCC version at this time. If you feel the "
+"need, please issue the following command (as usual, substitute <c>=sys-devel/"
+"gcc-3.4*</c> with the version you want to uninstall):"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):145
+msgid "Removing older GCC version"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):145
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):149
+msgid ""
+"Please note that the GCC 4.1 and newer can compile only kernels newer than "
+"2.4.34. Don't remove your old GCC version if you want to use an older kernel."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):154
+msgid ""
+"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot "
+"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ "
+"applications."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):165
+msgid "Upgrading from GCC-3.3 to 3.4"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):170
+msgid ""
+"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed "
+"between these two versions. There is an issue with the <c>libstdc++</c> "
+"library which must be taken care of, as well."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):179
+msgid "The Choices"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):182
+msgid ""
+"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-"
+"general\">General Update instructions</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):187
+msgid ""
+"If you're upgrading on a SPARC machine, you will have to take the way of "
+"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due "
+"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI "
+"changes</uri> in GCC's parameter passing."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):194
+msgid ""
+"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to "
+"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild"
+"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</"
+"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-"
+"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch "
+"so it will make use of new GCC features. It's up to you to decide which of "
+"these two ways you will choose. In most cases, the first method is "
+"sufficient."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):205
+msgid ""
+"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-"
+"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system "
+"rebuild</uri>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):214
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):242
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):390
+msgid "Using revdep-rebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):217
+msgid ""
+"This method requires that you first install <c>gentoolkit</c> if you have "
+"not already done so. Then we will upgrade GCC and switch to the new "
+"compiler. We will also rebuild the <c>libtool</c> package to ensure that "
+"toolchain is in healthy state."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):224
+msgid "Installing gentoolkit and upgrading GCC"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):224
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -an gentoolkit</i>\n"
+"# <i>emerge -uav gcc</i>\n"
+"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n"
+"version and CHOST settings you've upgraded to:)</comment>\n"
+"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n"
+"# <i>source /etc/profile</i>\n"
+"\n"
+"<comment>(Rebuilding libtool)</comment>\n"
+"# <i>emerge --oneshot -av libtool</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):236
+msgid ""
+"Now, we want to see which packages that revdep-rebuild will want to rebuild. "
+"Then we will tell revdep-rebuild to actually rebuild the packages. This may "
+"take some time, so have some patience."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):242
+#, no-wrap
+msgid ""
+"\n"
+"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n"
+"# <i>revdep-rebuild --library libstdc++.so.5</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):247
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):405
+msgid ""
+"It is possible that you might have problems with non-existing package "
+"versions due to them being outdated or masked. If this is the case, you will "
+"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This "
+"causes packages to be recompiled based on the package name, rather than the "
+"exact name and version."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):255
+msgid ""
+"To provide compatibility with older binary C++ applications and any packages "
+"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to "
+"be merged before you unmerge GCC 3.3 from your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):261
+msgid "Installing libstdc++-v3 and cleaning up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):261
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n"
+"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):269
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):416
+msgid "Using emerge -e"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):272
+msgid ""
+"This method, while much slower, will rebuild your whole system to ensure "
+"that everything has been rebuilt with your new compiler, and therefore "
+"safer. At first, you will upgrade GCC and libtool and switch to your new "
+"compiler."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):278
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -uav gcc</i>\n"
+"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n"
+"version and CHOST settings you've upgraded to:)</comment>\n"
+"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n"
+"# <i>source /etc/profile</i>\n"
+"\n"
+"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n"
+"example) you will have to run fix_libtool_files.sh manually</comment>\n"
+"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n"
+"<comment>(Replace &lt;gcc-version&gt; with your new, updated GCC version)</comment>\n"
+"# <i>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh 3.3.6</i>\n"
+"\n"
+"<comment>(Rebuilding libtool)</comment>\n"
+"# <i>emerge --oneshot -av libtool</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):295
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):377
+msgid ""
+"To provide compatibility with older binary C++ applications, <c>sys-libs/"
+"libstdc++-v3</c> needs to be merged onto your system."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):300
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):382
+msgid "Installing libstdc++-v3"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):300
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):382
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):304
+msgid ""
+"Now we will go about first rebuilding the system target, then the world "
+"target. This will take a very long time, depending on the number of packages "
+"that you have installed, as it will rebuild your entire toolchain and "
+"supporting system files, followed by every package on your system, including "
+"the toolchain. This is necessary to ensure that all packages have been "
+"compiled with the new toolchain, including the toolchain itself."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):313
+msgid "Rebuilding system and world"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):313
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e system</i>\n"
+"# <i>emerge -e world</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):318
+msgid "It is also safe to remove older GCC versions at this time:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):322
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):440
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):448
+msgid "Cleaning up"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):322
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):331
+msgid "Upgrading to GCC on a First Install"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):336
+msgid ""
+"A GCC upgrade on a system after installation from a stage3 tarball is a "
+"simple affair. One advantage users of new installations have is they do not "
+"have a plethora of software installed that links against the older version "
+"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts "
+"will be different if upgrading from other versions of GCC. For example, the "
+"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as "
+"well as the need to install <c>libstdc++-v3</c>."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):346
+msgid ""
+"If a user has not made any customizations to their system yet, then there "
+"are very few steps to get their system upgraded to a new GCC version. As "
+"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, "
+"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are "
+"fewer differences between the methods. The <uri link=\"#first-install-revdep-"
+"rebuild\">first method</uri> is faster and makes use of the <c>revdep-"
+"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. "
+"Using revdep-rebuild causes only packages which actually link against GCC "
+"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e"
+"\">second method</uri> causes your entire new install to be recompiled with "
+"the new GCC version and takes much longer. This second method is never "
+"required and only documented for completeness."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):361
+msgid ""
+"These first steps are common between both methods, and should be completed "
+"by everyone."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):366
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -uav gcc</i>\n"
+"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n"
+"version and CHOST settings you've upgraded to:)</comment>\n"
+"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n"
+"# <i>source /etc/profile</i>\n"
+"\n"
+"<comment>(Rebuilding libtool)</comment>\n"
+"# <i>emerge --oneshot -av libtool</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):393
+msgid ""
+"This method requires that you first install <c>gentoolkit</c> if you have "
+"not already done so. We will then run <c>revdep-rebuild</c> to actually scan "
+"the installed packages for ones we need to rebuild, then rebuild them."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):399
+msgid "Installing gentoolkit and running revdep-rebuild"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):399
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -an gentoolkit</i>\n"
+"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n"
+"# <i>revdep-rebuild --library libstdc++.so.5</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):419
+msgid ""
+"This method, while much slower, will rebuild the system target to ensure "
+"that everything has been rebuilt with your new compiler. This is not "
+"necessary, but is valid if you are also making changes to CFLAGS or other "
+"make.conf variables that will affect the system compile."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):426
+msgid ""
+"Since we are performing these actions after an initial installation, we do "
+"not need to recompile the <c>world</c> target as we would when doing an "
+"upgrade on an already installed system. However, you may choose to perform a "
+"world update in place of the system update, to ensure that all packages are "
+"updated."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):433
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -e system</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):443
+msgid ""
+"It is also safe to remove older GCC versions at this time. Please substitute "
+"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):448
+#, no-wrap
+msgid ""
+"\n"
+"# <i>emerge -aC \"&lt;sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):457
+msgid "Common Pitfalls"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):461
+msgid ""
+"It's important to disable <c>distcc</c> during upgrade. Mixing compiler "
+"versions on your nodes <e>will</e> cause build issues. This is not required "
+"for ccache, as the cache objects will be invalidated anyway."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):467
+msgid ""
+"Always use same GCC version for your kernel and additional kernel modules. "
+"Once you rebuild your world with new GCC, external modules (like <c>app-"
+"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel "
+"with the new GCC to fix that."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):474
+msgid ""
+"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> "
+"after re-emerging world to avoid possible issues."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):482
+msgid "Frequent Error Messages"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):485
+msgid ""
+"If your system complains about something like <e>libtool: link: `/usr/lib/"
+"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool "
+"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/"
+"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version "
+"numbers from the error message, and $CHOST and &lt;gcc-version&gt; with your "
+"actual CHOST and GCC version)."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):494
+msgid ""
+"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-"
+"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/"
+"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> "
+"again, followed by <c>source /etc/profile</c>. Only do this if you do not "
+"have any cross-compilers set up, though."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):502
+msgid ""
+"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, "
+"you can resume operation with <c>emerge --resume</c>. If a package fails "
+"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any "
+"other instances of emerge in between or you will lose the resume information."
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):509
+msgid ""
+"If you get an error message <e>spec failure: unrecognized spec option</e> "
+"while upgrading your compiler, try to switch back to your default compiler, "
+"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):515
+msgid "Restoring primary specs"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):515
+#, no-wrap
+msgid ""
+"\n"
+"# <i>gcc-config 1</i>\n"
+"# <i>source /etc/profile</i>\n"
+"# <i>unset GCC_SPECS</i>\n"
+"# <i>emerge -uav gcc</i>\n"
+msgstr ""
+
+#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
+#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(None):0
+msgid "translator-credits"
+msgstr ""
diff --git a/doc/gettext/el/genkernel.xml.po b/doc/gettext/el/genkernel.xml.po
new file mode 100644
index 0000000..b5cf3cd
--- /dev/null
+++ b/doc/gettext/el/genkernel.xml.po
@@ -0,0 +1,1075 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2011-01-21 01:40+0500\n"
+"PO-Revision-Date: 2011-01-21 01:40+0500\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: none\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: el\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(title):6
+msgid "Gentoo Linux Genkernel Guide"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(author:title):8
+msgid "Author"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(mail:link):9
+msgid "plasmaroo@gentoo.org"
+msgstr ""
+
+#: ../../gentoo/xml/htdocs/doc/en//genkernel.xml(mail):9
+msgid "Tim Yamin"
+msgstr ""
+</